Integrating with BMC Helix CMDB

Remedy ITSM Suite streamlines and automates the processes around IT service desk, asset management, and change management operations. It also enables you to link your business services to your IT infrastructure to help you manage the impact of technology changes on business and business changes on technology — in real time and into the future. In addition, you can understand and optimize the user experience, balance current and future infrastructure investments, and view potential impact on the business by using a real-time service model.

For more information, see the Remedy ITSM documentation.

The following figure depicts the technical architecture of this integration:

Configuring the Helix environment for the BMC Helix CMDB integration

Do the following:

1. In the Helix portal, create a work order requesting a new integration by using the client gateway from Helix to the TrueSight Operations Management on-prem environment. Provide the following information:
   • URL: For example, https://acme-smartit.onbmc.com.

   • Inbound connection to Helix:

   • Outbound connection from Helix:
2. Specify the CMDB extensions to be installed in the Helix enviroment.

The BMC Helix network team does the following:

1. Configures the host mapping to map the TrueSight Infrastructure Management sever host to the gateway server IP address.
2. Creates and configures the gateway configuration file.
3. Schedules a full restart of TrueSight Infrastructure Management for the host mapping to take effect.
4. Provides a copy of the client gateway configuration file.
5. Provides a copy of the Helix certificates for importing into the on-prem TrueSight Infrastructure Management environment.
6. Provides a copy of the CMDB extensions to be installed on the TrueSight Infrastructure Management server.

Configuring the TrueSight Environment for the BMC Helix CMDB integration

Do the following:

1. Import certificates into the TrueSight Infrastructure Management server.
2. Configure the Helix Client Gateway.
3. Configure the BMC Helix Change Management integration in TrueSight Infrastructure Management.
4. Verify the integration.

This section explains each procedure in detail.

Step 1: Importing certificates into the TrueSight Infrastructure Management server

Do the following:

1. Obtain the certificates from the Helix Network team or use the following URL to download them:
   https://testssl.onbmc.com/
   The following certificates are required:
   • Name: digicert_global_root.cer
     Alias: rootCA
   • Name: digicert_sha_256.cer
     Alias: intermediateCA

   • Name: onbmc_wildcard.cer
     Alias: onbmc_wildcardCA

     Keystore location

     The cacerts keystore is located at <TrueSight Infrastructure Management Installation Directory>/pw/jre/lib/security.

     The pnserver.ks keystore is located at <TrueSight Infrastructure Management Installation Directory>/pw/pronto/conf.

2. On the computer where the TrueSight Infrastructure Management server is installed, back up the following files:

   • <

     TrueSight Infrastructure Management

      Installation Directory>/pw/jre/bin/lib/security/cacerts

   • <

     TrueSight Infrastructure Management

      Installation Directory>/pw/jre/bin../../pronto/conf/pnserver.ks

3. Run the following commands in the order shown below:
   1. keytool -printcert -sslserver <helix server name:port> -rfc | keytool -importcert -keystore ../lib/security/cacerts -storepass changeit -noprompt -alias rootCA -file digicert_global_root.cer
   2. keytool -printcert -sslserver <helix server name:port> -rfc | keytool -importcert -keystore ../lib/security/cacerts -storepass changeit -noprompt -alias intermediateCA -file digicert_sha_256.cer
   3. keytool -printcert -sslserver <helix server name:port> -rfc | keytool -importcert -keystore ../lib/security/cacerts -storepass changeit -noprompt -alias onbmc_wildcard -file onbmc_wildcard.cer
   4. keytool -printcert -sslserver <helix server name:port> -rfc | keytool -importcert -keystore ../../pronto/conf/pnserver.ks -storepass get2net -noprompt -alias rootCA -file digicert_global_root.cer
   5. keytool -printcert -sslserver <helix server name:port> -rfc | keytool -importcert -keystore ../../pronto/conf/pnserver.ks -storepass get2net -noprompt -alias intermediateCA -file digicert_sha_256.cer
   6. keytool -printcert -sslserver <helix server name:port> -rfc | keytool -importcert -keystore ../../pronto/conf/pnserver.ks -storepass get2net -noprompt -alias onbmc_wildcard -file onbmc_wildcard.cer
4. Restart the TrueSight Infrastructure Management server.

Step 2: Configuring the BMC Helix client gateway

1. Install the Helix client gateway. For information, see the BMC Helix documentation.

2. Back up the kwic_config.xml file. <Where is the file located?>
3. Copy the kwic_config.xml file to the proper location. <Need info. From where do you copy it? What is the proper location to paste?

Step 3: Configure the BMC Helix Service Resolution integration TrueSight Infrastructure Management

1. If UDDI is configured for the HTTPS protocol, do the following:
   1. In the pw/custom/conf/pronet.conf file, set the following parameter to true:
      bmc.uddi.registryserver.secure.enabled=true
   2. Restart the TrueSight Infrastructure Management console.
2. Edit the host's file. Add the IP address of the gateway, and point it to ONMBC-s as shown below: <Which file? where is it located?>
   <gateway ipaddress> ONMBC-s
3. Enable BMC Server Resolution 3.5 on the TrueSight Infrastructure Management server. Do the following:
   1. Use the command prompt to navigate to the <InstallationDirectory>/integrations/EventIntegrator directory.
   2. Run the following command:
      (Windows) it30.bat enablebsr35
      (Linux) bash it30.sh enablebsr35
   3. Run the following command:
      pw jproperties reload
4. Log in to the TrueSight Infrastructure Management console.
5. In the top right corner, click Options and then click Administration.
6. In the Integrations area, click Edit.
   
7. Select the BMC AR/CMDB Integration checkbox.
   
8. Add information in the following fields for the Helix AR Server:
   • AR Server Hostname: ONBMC-s
   • AR Server Port: dev-4600, qa-4700, prod-4800
   • AR Server User: Obtain the user name from the BMC Helix team.
     
   • AR Server password: Obtain the user name from the BMC Helix team.
9. Select the Publishing mode.
10. If you want to enable the cross-launch capability, enter information in the following fields:
    • UDDI Hostname: <customer name>-<dev or qa or prod>.onbmc.com
    • UDDI Port: 443
    • UDDI User: Obtain the user name from the BMC Helix team.
    • UDDI Password: Obtain the password from the BMC Helix team.
    • Infrastructure Management Server Port: 8080, 443
11. Select a protocol for the TrueSight Infrastructure Management server.

12. If you integrate with Atrium CMDB in an AR Server Group, manually configure the pserver.conf file (location?). Edit the ARSGroupMembers in the pserver.conf file and set to all AR Servers of the group that have the reconciliation function enabled.

    For more information, see Configuring the Publishing Server to integrate with an AR Server group.

13. Install the CMDB extension jar files that you received from the BMC Helix team. Do the following:
    • Click to see the instructions for Linux...

      1. Back up the pw/server/bin/pserver file.
      2. Stop the pserver. Use the following command:
         pw p e pserver
      3. Edit the in the pw/server/bin/pserver file as follows:
         1. Comment the older jar files:
            #PS_CP="$PS_CP:$ATRIUM_CMDB_HOME/cmdbapi<old version>.jar"
            #PS_CP="$PS_CP:$ATRIUM_CMDB_HOME/arapi<old version>..jar"
            #PS_CP="$PS_CP:$ATRIUM_CMDB_HOME/arpluginsvr<old version>..jar"
            #PS_CP="$PS_CP:$ATRIUM_CMDB_HOME/noeapi<old version>..jar"
         2. Add the new jar files:
            PS_CP="$PS_CP:$ATRIUM_CMDB_HOME/cmdbapi<new_version>.jar"
            PS_CP="$PS_CP:$ATRIUM_CMDB_HOME/arapi<new_version>._build001.jar"
            PS_CP="$PS_CP:$ATRIUM_CMDB_HOME/arpluginsvr<new_version>._build001.jar"
            PS_CP="$PS_CP:$ATRIUM_CMDB_HOME/noeapi<new_version>..jar"
      4. Copy the jar files from the CMDB to the pw/cmdb/lib folder and change the permissions to 775 for the new files.  Do not remove the existing jar files because they are used by other processes.  The new jar files can exist along with the existing files.
      5. Start the pserver. Use the following command:
         pw p s pserver

      6. Close the publishing environment. Use the following command:
         penv close -e PROD

         Important: Closing the publishing environment removes all published data

         Closing the publishing environment removes all published data from the Cell and removes all publishing filters and published data from CMDB.

      7. Restart the publishing server.
      8. Once the publishing server starts and the output of psstat is Started, run the publish command to publish the data again.
    • Click to see the instructions for Windows...

      1. Back up the in the pw\server\bin pserver.bat file to a backup location.
      2. Stopthe pserver. Use the following command:
         pw p e pserver
      3. Edit the pw\server\bin\pserver.bat file as follows:
         1. Remove the older jar files:
            rem set PS_CP=%PS_CP%;%ATRIUM_CMDB_HOME%\arapi<old version>.jar
            rem set PS_CP=%PS_CP%;%ATRIUM_CMDB_HOME%\arpluginsvr<old version>.jar
            rem set PS_CP=%PS_CP%;%ATRIUM_CMDB_HOME%\cmdbapi<old version>.jar
            rem set PS_CP=%PS_CP%;%ATRIUM_CMDB_HOME%\noeapi<old version>.jar
         2. Add the new jar files:
            set PS_CP=%PS_CP%;%ATRIUM_CMDB_HOME%\arapi<new version>_build001.jar
            set PS_CP=%PS_CP%;%ATRIUM_CMDB_HOME%\arpluginsvr<new version>__build001.jar
            set PS_CP=%PS_CP%;%ATRIUM_CMDB_HOME%\cmdbapi<new version>.jar
            set PS_CP=%PS_CP%;%ATRIUM_CMDB_HOME%\noeapi<new version>.jar
      4. Copy the jar files from the CMDB to the pw/cmdb/lib folder and change the permissions to 775 for the new files.  Do not remove the existing jar files because they are used by other processes. The new jar files can exist along with the existing files.
      5. Start the pserver. Use the following command:
         pw p s pserver

      6. Close the publishing environment. Use the following command:
         penv close -e PROD

         Important: Closing the publishing environment removes all published data

         Closing the publishing environment removes all published data from the Cell and removes all publishing filters and published data from CMDB.

      7. Restart the publishing server.
      8. Once the publishing server starts and the output of psstat is Started, run the publish command to publish the data again.
14. Restart the TrueSight Infrastructure Management server.

Step 4: Verifying the integration

1. Log in to the BMC Helix MidTier Server as the user given to you by the BMC Helix team.
2. Go to Atrium Core > Atrium Core console.
3. Execute the Impact module designer.
4. Create a test model in the Impact module designer.
5. Verify that the test model is published in the TrueSight Infrastructure Management.

Configuring the integration

Do the following:

1. Open the TrueSight console.
2. Click Administration > Integrations.
3. Under Remedy ITSM, BMC Helix ITSM and BMC CMDB Integrations, click the Configure TrueSight Presentation Server with ITSM Change Management menu and then click Edit.
4. On the Change Management Integration page, do the following:
   1. Add the following information:
      • CMDB user name and password
      • UDDI host name
      • CMDB UDDI port number, user name, and password
   2. Select the HTTP or HTTPS protocol for the mid-tier server.'
   3. Select Activate Integration. If you do not want to active the integration at this time, you can do it later.
5. Click Save.
   You can see the integration added on the Change Management Integration page.