Install a Secondary Agent

Important: Before you install a secondary agent, you must Install an Agent for the Primary HA Database.

1. On the machine where you want to install the SECONDARY Agent. sign in with an account that has administrator privileges.

   Recommended: Install the Agent on the machine that hosts the MOVEit database.

2. Copy the public certificate file for the Analytics Server from the primary Agent machine to the secondary Agent machine. Place it on the secondary Agent machine's desktop or other easily accessible location. You located this file in Step 1 of Install a Primary Agent.
3. Download the appropriate Ipswitch Analytics Agent installation file, where n is the release number:
   • 64-bit: Ipswitch_Analytics_Agent64_vn.exe
   • 32-bit: Ipswitch_Analytics_Agent32_vn.exe

   Click Next.

4. Accept the License Agreement. Click Next.
5. Select a Destination Folder. Recommended: Use the default location.

   Caution: Do not specify a destination on the desktop.

6. Click Next.
7. Enter the Analytics Server Settings. The Agent forwards data from the MOVEit secondary database to the Ipswitch Analytics Server that you specify here.

   

   • Ipswitch Analytics Server IP address or hostname: (From the Tomcat Settings that you entered during the Server installation).
   • Port: The port on which the Ipswitch Analytics Server accepts HTTPS connections. Default is 8443. Adhere to your IT security or other IT network policies when configuring ports.
   • Agent Access Username: The username that the Agent uses to authenticate with the Ipswitch Analytics server. You specified this username during the Ipswitch Analytics server installation. See the Installation Worksheet.
   • Agent Access Password: See the Installation Worksheet.

   Click Next.

8. Enter the Analytics Agent Truststore Settings:

   

   • Analytics Server public certificate file: Browse to select the public certificate file that you located at the beginning of the Agent installation. It will have the extension .pem, .cer, .crt, or .der.

     IMPORTANT: Do not use the .p12 or .pfx certificate file that you used during installation of the Ipswitch Analytics Server.

   • Truststore password: Enter the same truststore password you entered for the Primary Agent installation.

   The installer creates the ‘ipswitchcerts’ truststore in /jre/lib/security.

   Click Next.

9. If the machine on which you are installing the Agent does not contain an installation of MOVEit Automation or MOVEit Transfer, select MOVEit Automation from the drop-down menu:

   

   Click Next.

10. Enter the MOVEit Database Settings.

    Note: This dialog box appears only if you selected MOVEit Automation or MOVEit Transfer in the Analytics Agent Type dialog box.

    

    • Database Type: Select either MySQL or Microsoft SQL Server, depending on the type of database used by the MOVEit server you selected in the prior step.
    • Authentication Type (SQL Server only): Select the authentication type that is used for logon to the SQL Server.

      Windows: SQL Server logon will use Windows authentication. If you select this option, username must be entered in the DOMAIN\User format.

      SQL: SQL Server logon uses a separate user/password created specifically for logon to the SQL Server database.

    • Database Name: The name of the secondary MOVEit database. If you are installing the Agent on the same machine as the MOVEit server, this field is pre-populated.
    • Hostname or IP Address: The location of the secondary MOVEit database.
      • If the secondary MOVEit database is on the same machine as the MOVEit server, value is localhost.
      • If the secondary MOVEit database and MOVEit server are on separate machines, the value is the Hostname or IP address of the machine where the database is located.

        Note: If you are installing the Agent on a machine that contains an SQL Server database with multiple instances on the same server, the Hostname or IP Address field prepopulates with the default value used by MOVEit Automation or MOVEit Transfer (for example, localhost\instance1). You can enter a different instance. If the machine does not contain MOVEit Transfer or MOVEit Automation, you must enter the instance name manually.

      • If you are installing the Agent on a machine that does not have MOVEit Transfer or MOVEit Automation, the default database name appears here (for example, moveitdmz).
    • Port: The port that is used to connect with the secondary MOVEit database. Default is the default port value for MSSQL/MySQL.

      Note: If the MOVEit primary database is using a non-standard port number, you must remove the default port number and replace it with the non-standard port number.

    • Username and Password: The username and password that allow access to the MOVEit primary database.

      If the secondary database is an SQL Server database, the selection you made in the Authentication Type field determines what user credentials you enter here. Windows authentication requires that the username be in the DOMAIN\User format.

      Tip: If you cannot locate the username and password to the MOVEit database, look in c:/MOVEitCentral_Install.INI file (MOVEit Automation/Central).

    Click Next.

    Tip: If the connection to the database fails, make sure that your firewall is open.

11. Enter the Analytics Agent Settings.

    

    • Primary Agent Name: Enter the primary Agent's Agent Display Name. You entered this value in the final step of the PRIMARY Agent's installation.
    • Is this a new or existing agent?: This item is disabled.
    • Would you like to include historical data? Select Start with current data.

    Click Next.

12. Review the installation setup, and then click Install.

    Note: If you click Cancel, the installation stops, but the Agent installation folder remains in the installation directory that you selected. You can safely delete the Analytics Agent directory to remove any files that remain after an interruption of the installation process.

    To view the installer log after the installation finishes, select the checkbox.

    To view the log at another time: the log is located in a temp directory in the user's AppData folder. For example, C:\Users\Administrator\AppData\Local\Temp\n\MSIstring.log (where n is a number, and string is an alphanumeric string).

13. Click Finish.

Installation of the secondary Agent is complete. The secondary Ipswitch Analytics Agent service is now running on this machine but reports data to the Ipswitch Analytics Server only if the primary database fails. This secondary Agent does not display in Settings > Licensing unless the primary database fails.

About Historical Data

Note: Historical data can be included for MOVEit sources.

If during the Agent installation, you chose to include historical data, it might take some time (a few minutes to a few hours) to retrieve the historical data and send it to the Ipswitch Analytics server. While the data is being captured, the MOVE it server continues to operate, and you can use Ipswitch Analytics. However, because data capture is a "trickle" process, some historical data cannot be viewed until the data capture process is complete. You are not notified when the Agent finishes including all historical data. To verify that the historical data capture process is complete, run a report for a time range in the past.

If you have a large number (more than 10) Analytics Agents to be connected to the Analytics Server, the server might face heavy data volume from the agents if they all feed historical data at the same time. To make the initial data loading process run more smoothly, start the agents by smaller groups of 10 agents. Start the second group after the first group has finished loading historical data. After the historical data is loaded, the data volume returns to normal levels and all agents can stay up. Users can then start to use the Analytics Server.

Next: Step 5: Verify Agent Functionality