Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Installing the Integration Service in HA mode on Windows

In the OS level high availability (HA) mode, you must install the Integration Service on both, the primary and the secondary servers.

Note

The Integration Service cannot be installed on HA mode on UNIX and Linux systems. The Integration Service has an internal failover mechanism. You can install the Integration Service on two UNIX computers separately, and configure the PATROL Agent with the names of both the Integration Services. If one UNIX computer goes down, the PATROL Agent automatically switches to the other computer in which the other Integration Service is installed.

Installing the Infrastructure Management Integration Service on the primary server

  1. Log in to a virtual node (assuming that the cluster service is started on both the primary and secondary servers).
  2. Ensure that you are on the primary server.
  3. Copy the Integration Service installer (TSIMAgent.zip) on the local drive (for example, C:\).
  4. Set the environment variable PATROL_VIRTUALNAME=<virtual IP address of the cluster>.
  5. Open the command prompt using the Run as administrator option and access the install.cmd file located in the TSIMAgent\windows directory.
  6. Run the following command:
    install.cmd -J INSTALL_TYPE=PRIMARY
    The installation will be performed on the shared drive.
  7. On the Welcome screen, click Next.

  8. On the License Agreement screen, select I agree to the terms of the license agreement and click Next.

    The pre-installation check utility verifies whether or not the computer meets the requirements for installing the Integration Service.

  9. If the pre-installation check fails, click Cancel, correct the issues if there are errors or warnings listed in the Pre-install Validation Summary window, and restart the installation process. If you do not want to resolve the warnings click Next.

    If Microsoft .NET Framework is not found on the computer, a warning message is displayed. Install Microsoft .NET Framework version 3.0 using the Role Management tool.

  10. On the Directory Selection screen, accept the default directory or choose a different directory and click Next. Do not install the product in a root directory (for example, C:\ or D:\), shared drive, or directly under the Documents and Settings folder.
  11. Select the features for Integration Service. By default, Integration Service and Remote Cell are selected.

  12. On the Configuring Remote Cell screen, enter the following details:

    Field

    Description

    Instance Name

    Type the cell instance name. The default is <host name>.

    Note: Hyphens and underscores are the only special characters allowed for cell instance names.

    Port

    Enter a port number in the range of 1024 to 65535. The default port number of the cell is 1828.

    Encryption Key

    Enter the cell encryption key. The default is mc. No special characters are allowed.

     

  13. Enter the Integration Service Port and Staging Adapter Port details, and click Next. By default, the Integration Service port is 12124 and Staging Adapter port is 3183.
  14. On the Installation Preview screen where the installation details are displayed, click Install.
  15. The Integration Service installation process begins. This process may take several minutes to complete. 
  16. On the Installation Summary screen, click View Log to view the log file and click Done to exit the installation. 
    A message that the installation is complete on the primary server is displayed. 

Notes

  • If you modify the control port of an Integration Service explicitly using the pronet.conf file, the port number is not updated in the Add/Remove Programs applet and in the Agent Service display name. If you modify the control port, the port number is not displayed when you use Add/Remove Programs.
  • Each Integration Service on a system runs in a separate JVM.
  • You can check the version of the Integration Service at installationDirectory\Agent\Pronto\Bin\AGENT_VERSION.

Installing the Integration Service on the secondary server

  1. Log in to the virtual node (assuming clustering service is started on both the primary and the secondary servers).
  2. Ensure that you are on the secondary server.
  3. Copy the Integration Service installer (TSIMAgent.zip) on the local drive (for example, C:\).
  4. Set the environment variable PATROL_VIRTUALNAME=<virtual IP address of the cluster>.
  5. At the command prompt, access the install.cmd file located in the TSIMAgent\Windows directory.

  6. Run the following command as an administrator:

    Note

    Before running the following command, ensure to do the following in the options file:

    • If the options file does not contain the INSTALL_TYPE parameter, add this parameter with value as SECONDARY, that is, INSTALL_TYPE=SECONDARY.
    • If the options file contains this parameter with the value as PRIMARY, update it to SECONDARY. That is, modify the value of INSTALL_TYPE=PRIMARY to INSTALL_TYPE=SECONDARY .
    • In a case of UI installation:
      install.cmd -DOPTIONS_FILE=<options file generated using primary install log>
      All options provided in the first installation automatically gets included on all screens. 
    • In the case of silent installation:
      install.cmd -i silent -DOPTIONS_FILE=<options file generated using primary install log>
      You may update the options file, if required.

    The installation is performed on the shared drive.

  7. On the Installation Summary screen, click View Log to view the log file and click Done to exit the installation.

  8. After the Integration Service is installed on both the primary and secondary servers, a “TrueSightAgent” resource is created on the cluster.

    If this resource is not created automatically, you may receive warnings. To create the resource, perform the following steps:

    1. Go to the <installation directory>\Agent directory and execute the following file:
      (Windows Server 2008)GenericService.bat
      (Windows Server 2012)GenericService.ps1
    2. Execute the following command to enable the TrueSightAgent cluster resource:(Windows Server 2008)cluster.exe resource TrueSightAgent /ONLINE /WAIT:500
      (Windows Server 2012)powershell.exe Start-ClusterResource -Name TrueSightAgent -Wait 500
  9. Create dependencies for the Integration Service cluster resources:
    1. Stop the BMC TrueSight Infrastructure Management Integration Service using Services.msc.
    2. Go to Start > All Programs > Administrative Tools > Failover Cluster Manager and click on the cluster name.
    3. Scroll down to Cluster Core Resources section, right-click TrueSightAgent, and click Properties.
    4. Click the Dependencies tab in the TrueSightAgent Properties window and click Insert to add a resource.
    5. Select the cluster name as a resource and click Insert.
    6. Select the cluster resource with the ‘AND’ option. Similarly, add all the resources.
    7. Click Apply and OK.
    8. Restart the BMC TrueSight Infrastructure Management Integration Service using Services.msc. 
  10. Restart both the primary and the secondary servers. If the Integration Services do not start, manually bring it up by starting the Integration Service.

Notes

  • The Integration Service takes time to come up during failover, as it runs on a Microsoft active/passive cluster. If the Integration Service (cluster resource) does not come up, select the online option to manually set the status.
  • To increase the maximum uptime and to avoid the Integration Service to be in the failed state, BMC recommends you to set the value for the Maximum failures in the specified period option to a higher value (for example, 100 for 6 hours). To set this value, in Failover Cluster Manager, select Roles properties and click Failover.
  • For Top IP traffic to work on a remote Windows 2008 R2 64 bit agent, go to www.winpcap.org, download WinPcap, and execute the file on the secondary server.

Performing the post-install tasks for Cell to start or stop automatically during failover

Perform the following steps on the secondary node to start or stop the cell automatically during failover:

  1. Go to the <installation directory>\Agent directory and make the copy of the following file:
    (Windows Server 2008) GenericService.bat
    (Windows Server 2012) GenericService.ps1
  2. Edit the copied file:
    1. Replace the cluster resource value from "TrueSightAgent" to"TrueSightCell".
    2. Modify the ServiceName value from "TrueSightAgent" to the Cell service name (you can obtain the cell service name from services.msc). 
  3. Execute the modified file with the Run as administrator option to create the new cluster resource as "TrueSightCell".
  4. Create the similar dependencies for TrueSightCell as of TrueSightAgent. 
  5. Execute the following command with the Run as administrator option to enable the TrueSightCell cluster resource:(Windows Server 2008) cluster.exe resource TrueSightCell /ONLINE /WAIT:500
    (Windows Server 2012) powershell.exe Start-ClusterResource -Name TrueSightCell -Wait 500  
  6. If the cell service is set to Automatic in services.msc, update it to Manual. 

Where to go from here

After installing the Integration Service in HA mode, you can configure it for extended security. This allows the BMC PATROL Agent to connect only to the Integration Service that you specify and not to multiple Integration Services.

Related topics

Preparing-to-install-Infrastructure-Management-in-high-availability-mode

Installing-the-BMC-TrueSight-Infrastructure-Management-Server-in-HA-mode-on-Windows

Installing the BMC TrueSight Infrastructure Management Server in HA mode on Linux/Solaris

Configuring-the-Integration-Service-for-extended-security

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*