Migrating PATROL Agents

This topic provides instructions on how to reconfigure PATROL Agents in the following scenarios:

• When you migrate from TrueSight Operations Management to BMC Helix Operations Management
• When you migrate from an instance of BMC Helix Operations Management to another

To configure PATROL Agents when you migrate from TrueSight Operations Management to BMC Helix Operations Management

Do the following:

1. Download the PATROL Agent security certificate:
   1. Log in to the BMC Helix Operations Management console.
   2. On the Administration > Repository page, click the action menu of the appropriate pre-defined package, and select Download.
      
      • (Windows) Predefined_Package_For_Windows_x64
      • (Linux) Predefined_Package_For_Linux_x64
   3. Extract the downloaded package and locate the mca_ca.cer file in the following directory:
      
      • (Windows) bmc_products\Install\instdata
      • (Linux) bmc_products/Install/instdata
2. Log in to the host computer on which the PATROL Agent is installed.
3. Copy the mca_ca.cer file from the extracted package in Step1c to the following directory:
   • (Windows) %PATROL_HOME%\security\certificates
   • (Linux) $PATROL_HOME/../security/certificates/

4. Update the following configuration variables: 

   • (Windows)

     1. On the BMC Helix Operations Managementconsole, go to the Administration > Repository page, and click Copy API Key.

     2. Create a text file called config_file.cfg and add the following information:

        PATROL_CONFIG "/SecureStore/mca/tenant/apiKey" = {REPLACE = "MCA/<API Key>"}, 
        "/AgentSetup/integration/integrationServices" = {REPLACE="https:<FQDN of BMC Helix Operations Management tenant>:443"}

        Replace <API Key> with the API Key that you copied in the previous step.

     3. Save the config_file.cfg file.

     4. Run the following command to apply the configuration variable changes: 

        pconfig -p <port> -host <PATROL Agent host name> <config_file.cfg>

     5. Restart the PATROL Agent using the following command:

        pconfig +RESTART -p <port>

   • (Linux)

     1. On the BMC Helix Operations Managementconsole, go to the Administration > Repository page, and click Copy API Key.

     2. Go to the PATROL Agent installation directory and run the following script: 

        #For Korn and Bourne shell:
        . ./patrolrc.sh
         
        #For C shell:
        source .patrolrc

     3. Create a text file called config_file.cfg and add the following information:

        PATROL_CONFIG "/SecureStore/mca/tenant/apiKey" = {REPLACE = "MCA/<API Key>"}, 
        "/AgentSetup/integration/integrationServices" = {REPLACE="https:<FQDN of BMC Helix Operations Management tenant>:443"}

        Replace <API Key> with the API Key that you copied in the previous step.

     4. Save the config_file.cfg file.

     5. Run the following command to apply the configuration variable changes: 

        pconfig -p <port> -host <PATROL Agent host name> config_file.cfg

     6. Restart the PATROL Agent using the following command:

        pconfig +RESTART -p <port>

   How do I do apply these changes to a large number of PATROL Agents?

   If you have a large number of PATROL Agents in your environment, you can update the configuration variables of all the PATROL Agents by doing the following:

   1. Create the config_file.cfg file as explained in the Step4.

   2. Run the pconfig Reload command for all the PATROL Agents by replacing the hostnames. For example, if you have 3 PATROL Agents (hostA, hostB,hostC) in your environment, then run the pconfig Reload command as shown in the following example:

      pconfig +Reload -p 4181 -host hostA.bmc.com config_file.cfg
      pconfig +Reload -p 4181 -host hostB.bmc.com config_file.cfg
      pconfig +Reload -p 4181 -host hostC.bmc.com config_file.cfg

5. (Optional) You can set up a proxy server for the PATROL Agent to communicate with BMC Helix Operations Management. For more information, see Configuring PATROL Agents to support a forward proxy server.

   If you plan to set up a proxy server, you can add the proxy server configuration details to the config_file.cfg file. This will enable you to update the proxy server configuration changes on all the PATROL Agents easily. The following example shows you how to add the proxy server details to the config_file.cfg file.

   PATROL_CONFIG "/AgentSetup/integration/forwardProxyServer" = {REPLACE = "proxyServer.bmc.com:3128"},
"/AgentSetup/integration/forwardProxyUser" = {REPLACE = "user1"},
"/SecureStore/mca/tenant/forwardProxyPasswd" = {REPLACE = "MCA/user123"}

6. Restart the PATROL Agent.

To configure PATROL Agents when you migrate from a BMC Helix Operations Management instance to another

Do the following:

1. Download the PATROL Agent security certificate:
   1. Log in to BMC Helix Operations Management console of the new BMC Helix Operations Management instance to which the PATROL Agent needs to communicate with.
   2. On the Administration > Repository page, click the action menu of the appropriate pre-defined package, and select Download.
      
      • (Windows) Predefined_Package_For_Windows_x64
      • (Linux) Predefined_Package_For_Linux_x64
   3. Extract the downloaded package and locate the mca_ca.cer file in the following directory:
      
      • (Windows) bmc_products\Install\instdata
      • (Linux) bmc_products/Install/instdata
2. Log in to the host computer on which the PATROL Agent is installed.
3. Copy the mca_ca.cer file from the extracted package in Step1c to the following directory:
   • (Windows) %PATROL_HOME%\security\certificates
   • (Linux) $PATROL_HOME/../security/certificates/

4. Update the following configuration variables: 

   • (Windows)

     1. On the BMC Helix Operations Managementconsole, go to the Administration > Repository page, and click Copy API Key.

     2. Create a text file called config_file.cfg and add the following information:

        PATROL_CONFIG "/SecureStore/mca/tenant/apiKey" = {REPLACE = "MCA/<API Key>"}, 
        "/AgentSetup/integration/integrationServices" = {"https:<FQDN of BMC Helix Operations Management tenant>:443"}

        Replace <API Key> with the API Key that you copied in the previous step.

     3. Save the config_file.cfg file.

     4. Run the following command to apply the configuration variable changes: 

        pconfig -p <port> -host <PATROL Agent host name> <config_file.cfg>

     5. Restart the PATROL Agent using the following command:

        pconfig +RESTART -p <port>

   • (Linux)

     1. On the BMC Helix Operations Managementconsole, go to the Administration > Repository page, and click Copy API Key.

     2. Go to the PATROL Agent installation directory and run the following script: 

        #For Korn and Bourne shell:
        . ./patrolrc.sh
         
        #For C shell:
        source .patrolrc

     3. Create a text file called config_file.cfg and add the following information:

        PATROL_CONFIG "/SecureStore/mca/tenant/apiKey" = {REPLACE = "MCA/<API Key>"}, 
        "/AgentSetup/integration/integrationServices" = {REPLACE="https:<FQDN of BMC Helix Operations Management tenant>:443"}

        Replace <API Key> with the API Key that you copied in the previous step.

     4. Save the config_file.cfg file.

     5. Run the following command to apply the configuration variable changes: 

        pconfig -p <port> -host <PATROL Agent host name> config_file.cfg

     6. Restart the PATROL Agent using the following command:

        pconfig +RESTART -p <port>

   How do I do apply these changes to a large number of PATROL Agents?

   If you have a large number of PATROL Agents in your environment, you can update the configuration variables of all the PATROL Agents by doing the following:

   1. Create the config_file.cfg file as explained in the Step4.

   2. Run the pconfig Reload command for all the PATROL Agents by replacing the hostnames. For example, if you have 3 PATROL Agents (hostA, hostB,hostC) in your environment, then run the pconfig Reload command as shown in the following example:

      pconfig +Reload -p 4181 -host hostA.bmc.com config_file.cfg
      pconfig +Reload -p 4181 -host hostB.bmc.com config_file.cfg
      pconfig +Reload -p 4181 -host hostC.bmc.com config_file.cfg

5. (Optional) You can set up a proxy server for the PATROL Agent to communicate with BMC Helix Operations Management. For more information, see Configuring PATROL Agents to support a forward proxy server.

   If you plan to set up a proxy server, you can add the proxy server configuration details to the config_file.cfg file. This will enable you to update the proxy server configuration changes on all the PATROL Agents easily. The following example shows you how to add the proxy server details to the config_file.cfg file.

   PATROL_CONFIG "/AgentSetup/integration/forwardProxyServer" = {REPLACE = "proxyServer.bmc.com:3128"},
"/AgentSetup/integration/forwardProxyUser" = {REPLACE = "user1"},
"/SecureStore/mca/tenant/forwardProxyPasswd" = {REPLACE = "MCA/user123"}

6. Restart the PATROL Agent.