Skip to main content
Skip table of contents

FileNet Connector Installation

Ensure that you run the installer as the Local Administrator.

Upon launching the FileNet Connector installer, the following screen displays:

Installing the FileNet Connector

Before you install the FileNet Connector, verify the Connector system requirements. This installation section assumes that you have already installed the Records Management Core platform.

When you install the FileNet Connector, a Configuration Application and two Records Management Windows Services are installed automatically as part of this process.

To install the FileNet Connector, perform the following steps:

  1. From the Records Management splash screen, click the Install FileNet Connector link. The User Account Control window opens.

  2. Click Yes to allow the installer to make changes to your computer. The FileNet Connector installation screen displays.

  3. On the FileNet Connector installation screen, click Install to the right of the FileNet Connector option. The first screen that displays is the check for prerequisites. This screen validates the following information before allowing the installation to proceed:

    • The current user is Local Administrator

    • You have installed .NET Framework 4.5



  4. Click Next. The installation location screen displays, which determines where the connector will be installed.



  5. Leave the installation path as the default, or to change it, click the ... icon next to the installation location field, select the desired installation location, and then click Next. The Service Settings screen displays.

    You must have at least 100MB of disk space available.

  6. Enter the following required information to specify which user account to use when you run the Windows Services:

    • Username (Ex. DOMAIN\Username)

    • Password

    The user account can be a domain account (DOMAIN\username) or a computer account if it has access to the SQL Server database (COMPUTERNAME\username). The account must have the following file system permissions:

    • Read/Write: %Install path%\Logs

  7. Click Next. The Database Settings screen displays.



    The "Database Server" and the "Database Name" settings, and the "Automatically Create Database" checkbox, will be populated automatically, however, you can change these settings. For information on the settings, see below.

  8. Enter/select the following database settings to determine the connection information that will be used by the FileNet Connector to connect to SQL Server:

    • Database Server: The name of the SQL Server Install (ex. SERVERNAME\InstanceName)

    • Database Name: The name of the actual SQL Server Database (The default name for the database is “FileNetConnector”, but you can change it here.)

    • Automatically Create Database: See description below

    • Use SQL Authentication: Specifies that the connection information should use SQL Authentication with the Username and Password indicated below

    • Username: The SQL Server username to use if SQL Authentication is specified

    • Password: The SQL Server password to use if SQL Authentication is specified

    If SQL Authentication is not specified, the connection information will use Windows Authentication by specifying a trusted connection.  This means that the Service account will be used to connect to SQL Server, therefore, this account will need the following database permissions. If SQL Authentication is specified, the SQL user will also require the following permissions.

    • db_datareader

    • db_datawriter

    • GRANT EXECUTE on all Stored Procedures

    • GRANT EXECUTE on all Scalar User Defined Functions

    • GRANT SELECT on all Table and Inline User Defined Functions

    If Automatically Create Database is specified, the installation will automatically attempt to create the database using the Database Server and Database Name indicated.  The appropriate account will also be automatically granted the appropriate rights to this database. This option requires that the current user has permission to create databases and manage security in the SQL Server instance indicated.

    If Automatically Create Database is not specified, the installation will configure connection information but will not attempt to create the database. In this case, you will need to leverage the SQL Script at the following location to manually create the database in the SQL Server instance indicated. You will also need to manually configure security as indicated above.

    • %Install Path%\Configuration\Sql\RecordLion.RecordsManager.FileNet.sql

  9. Click Next to perform the final installation using the database settings you specified above. The progress bar indicates the state of the installation.

  10. When the application finishes installing, click Next to continue to the Finish screen. This screen indicates that everything installed successfully.

  11. Click Finish to return to the main Setup screen, which should now indicate that the FileNet Connector was installed successfully.

  12. After you have finished installing the FileNet Connector, you must perform the following steps to run the newly installed Windows Services. (For information on how to run Windows Services, see Microsoft's online documentation.)

    • Open the Windows Services Manager.

    • In the Services window, verify that the Gimmal FileNet Classification Service and the Gimmal FileNet Retention Services are listed.

    • Start both services. When the services begin, the Status column will display "Running".

    • Using the SQL Server Management Studio, connect to the SQL database and navigate to the Databases folder. The database you applied settings to in step 9 is located under this Databases folder.

    • Verify that FileNetConnector is listed.

    • Expand the nodes: FileNetConnector > Security > Users, and then verify that the Service/User account that was created during the installation steps above is listed and has the correct permissions.

  13. Continue the installation process by installing the FileNet Services component. For information, see Installing FileNet Services.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.