Configuring TrueSight Infrastructure Management to enable TLS 1.2
Before you begin
Ensure to complete the certificate creation and import tasks for the relevant components before you configure TLS 1.2 between them. For more information about how to create and import private certificates, see Implementing-private-certificates-in-TrueSight-Operations-Management.
To configure the TrueSight Infrastructure Management components to enable TLS 1.2
There are different communication channels established between the TrueSight Infrastructure Management components. Perform the TLS configurations per communication channel. Select the communication channel which you want to make TLS compliant and perform the tasks accordingly. The flowchart in the following diagram explains the complete TLS configuration workflow.
To enable TLS 1.2, complete the procedures by navigating the following tabs, or select the procedures from documentation links in the flowchart.
Navigate to the <Presentation Server Install Directory>\truesightpserver\bin directory, and run the following command to check whether the TrueSight Presentation Server is running.
tssh server statusLog on to the TrueSight console and select Administration> Components.
Displays the components that are registered with the Presentation Server. Ensure that no TrueSight Infrastructure Management Server is registered with the TrueSight Presentation Server. If a TrueSight Infrastructure Management Server is registered delete the same. For more information, see To delete a component
Set the property in the database by running the following command:
tssh properties set tsps.cell.conntype ssl
tssh properties set pronet.jms.conntype ssl- Using a text editor, open the mcell.dir file located in <Presentation Server Install Directory>\conf directory.
Comment out the instances of the code lines having the encryption key value as mc as shown in the following code block:
#Type <name> encryption key <host>/<port>
#gateway.gateway_subtype ts_event_gateway mc tsps_server1.bmc.com:1900
#cell pncell_tsim_server1 mc tsim_server1.bmc.com:1828Set the encryption key value to *TLS as shown in the following code block:
#Type <name> encryption key <host>/<port>
gateway.gateway_subtype ts_event_gateway *TLS tsps_server1.bmc.com:1900
cell pncell_tsim_server1 *TLS tsim_server1.bmc.com:1828- Save and close the file.
Set the property in the database by running the following command:
tssh properties set server.eventgateway.encryption.key *TLSStop the Presentation Server by running the following command:
tssh server stop
The following sections describe the configuration steps for both the local Integration Service and remote Integration Service in TLS 1.2 mode. Perform the configuration steps based on the type of Integration Service installed:
- Step 1: To configure the local Integration Service
- Step 2: To configure the remote Integration Service
- Step 3: To start the servers
To configure the local Integration Service
Failed to execute the [excerpt-include] macro.
To configure the remote Integration Service
Failed to execute the [excerpt-include] macro.
To start the servers
Failed to execute the [excerpt-include] macro.
The following section guides you to configure the Integration Service to Cell communication in TLS 1.2. Choose the appropriate configuration steps based on the type (local / remote) of the Integration Service and the cell used.
- Step 1: To configure the local Integration Service
- Step 2: To configure the remote Integration Service
- Step 3: To configure the local Cell
- Step 4: To configure the remote Cell
- Step 5: To start the servers
To configure the local Integration Service
Failed to execute the [excerpt-include] macro.
To configure the remote Integration Service
Failed to execute the [excerpt-include] macro.
To configure the local Cell
Failed to execute the [excerpt-include] macro.
To configure the remote Cell
Failed to execute the [excerpt-include] macro.
To start the servers
Failed to execute the [excerpt-include] macro.
Perform the following steps to configure the Infrastructure Management Server to Oracle database communication to enable TLS 1.2 mode:
To configure the Infrastructure Management Server to Oracle database communication to enable TLS 1.2
Perform the following steps to enable the Infrastructure Management Server to Oracle database communication to be TLS compliant:
Stop the Infrastructure Management Server by running the following command:
pw system stopNavigate to the <Infrastructure Management Server Install Directory>\pw\pronto\bin directory, and run the switchTLSMode.pl script as shown in the following code block:
#Syntax
perl switchTLSMode.pl -<on/off> -flow <communication channel> -dbport <Oracle Database port> -dbver <Oracle Database version>
#Example
perl switchTLSMode.pl -on -flow oracle –dbport 1521 -dbver 11GStart the Infrastructure Management Server by running the following command:
pw system start
By default, the PATROL Agent communicates using either Transmission Control Protocol (TCP) or Secure Sockets Layer (SSL) protocol, but you can configure PATROL Agents to enable TLS 1.2 mode.
The following process workflow guides you to configure the PATROL Agent to Integration Service communication to be TLS compliant:
- Ensure that the signed certificates are generated for the Integration Service and imported into the PATROL Agent's client DB certificate store.
To generate signed certificates for the Integration Service, see Implementing-private-certificates-in-the-Integration-Service. - Ensure that the PATROL Agent and the TrueSight Integration Service are running at the same security level.
To change the PATROL Agent's security level, see Changing the PATROL Agent's security level.
To change the Integration Service's security level, see Changing the Integration Service's security level.
- Configure the PATROL Agent to Integration Service communication to enable TLS mode.
- Run the set_unset_tls command in the PATROL Agent
- Run the set_unset_tls_is command in the Integration Service
For details, see Configuring-the-PATROL-Agent-to-Integration-Service-communication-to-enable-TLS-1-2.
Update the PATROL Agent's registry files.
For details, see Updating the PATROL Agent registry files.Update the Integration Service's registry files.
For details, see Updating the Integration Service registry files.
Perform the following steps to enable the Infrastructure Management Server to BMC Impact Integration Web Services (IIWS) communication to be TLS compliant:
- Step 1: To configure the Infrastructure Management Server
- Step 2: To configure the BMC Impact Integration Web Services server
- Step 3: To start the servers
To configure the Infrastructure Management Server
Failed to execute the [excerpt-include] macro.
To configure the BMC Impact Integration Web Services server
Failed to execute the [excerpt-include] macro.
To start the servers
Failed to execute the [excerpt-include] macro.
Perform the following steps to enable the Infrastructure Management server main cell to Reporting engine communication to be TLS compliant:
- Step 1:To configure the Infrastructure Management server cell component
- Step 2:To configure the Reporting Engine component
To configure the Infrastructure Management server cell component
- Using a text editor, open the mcell.dir file on the BMC TrueSight Infrastructure Management Server host computer. The file is located in the <Infrastructure Management server Install Directory>\pw\server\etc directory.
Check for the instance of the code line having encryption key value as shown in the following code block:
gateway.reportengine bpre.<fullyQualifiedHostName> <encryptionKey> <fullyQualifiedHostName>:<3783>#Example
gateway.reportengine bpre.vs-pun-tsim-bp03.bmc.com mc vs-pun-tsim-bp03.bmc.com:3783
Modify the existing value of encryption key to *TLS as shown in the following example:
gateway.reportengine bpre.vs-pun-tsim-bp03.bmc.com *TLS vs-pun-tsim-bp03.bmc.com:3783- Save and close the file.
Reload the mcell.dir file by entering the following command from a command line:
#Syntax
mcontrol -n cellName reload dir#Example
mcontrol -n pncell_vm-w23-rds1016 reload dir
To configure the Report Engine component
Navigate to the reportsCLI directory by running the following command:
# Microsoft Windows operating system
CurrentDirectory>cd <TrueSight Operations Management Reporting Install directory>\bin\reportsCLI# Unix operating system
$cd <TrueSight Operations Management Reporting Install directory>/bin/reportsCLIInitiate the configuration settings by running the following command:
#Syntax
tls_config init -truststore <truststore file> -truststorepassword <truststore password> [-keystore <keystore file> -keystorepassword <keystore password>][-SqlAnywhereCert <trust certificate path>]#Example
tls_config init -truststore cacerts -truststorepassword <truststore password> -keystore cacerts -keystorepassword <keystore password> -SqlAnywhereCert <BMC TrueSight Operations Management Report Engine Install Directory>\ReportEngine\tools\jre\binEnable the TLS configuration by running the following command:
tls_config enable -component cell
Perform the following steps to configure the Infrastructure Management server to Publishing Server communication to enable TLS 1.2 mode:
To configure the Infrastructure Management server
Perform the following steps to enable the Infrastructure Management server to Publishing Server communication to be TLS compliant:- Stop the Infrastructure Management Server by running the following command:pw system stop
- Using a text editor, open the pronet.conf located in the <Infrastructure Management Server Install Directory>\pw\custom\conf directory.
- Add the following properties in pronet.conf as shown in the following code block:pronet.jms.passwd.file=pronto/conf/.ks_pass
pronet.apps.ipc.ssl.context.pserver.truststore.filename=messagebroker.ts
pronet.apps.ipc.ssl.context.pserver.keystore.filename=pnserver.ks
pronet.apps.ipc.ssl.context.pserver.enabledsuites=TLS_RSA_WITH_AES_128_CBC_SHA256
pronet.apps.ipc.ssl.context.pserver.keystore.passwdfile=pronto/conf/.ks_pass - Using a text editor, open the mcell.dir located in the <Infrastructure Management Server Install Directory>\pw\server\etc directory.
- Comment out any existing instances of the code lines having encryption key value as mc as shown in the following code block:#Type <name> encryption key <host>/<port>
#cell pncell_hostname mc pncell_hostname.bmc.com:1828
#gateway.imcomm gw_ps_pncell_hostname mc hostname.bmc.com:1839 - Add the code lines to set the encryption key value to *TLS as shown in the following code block:#Type <name> encryption key <host>/<port>
cell pncell_hostname *TLS pncell_hostname.bmc.com:1828
gateway.imcomm gw_ps_pncell_hostname *TLS hostname.bmc.com:1839 - Save and close the file.
- Using a text editor, open the smmgr.conf located in the <Infrastructure Management Server Install Directory>\pw\server\etc directory.
- Comment out any existing instance of the code line having ServerTransportProtocol value as tcp as shown in the following code block:#ServerTransportProtocol=tcp
- Add the code lines to set the ServerTransportProtocol value to tls, and server certificate file name and key values as shown in the following code block:ServerTransportProtocol=tls
ServerCertificateFileName=mcell.crt
ServerPrivateKeyFileName=mcell.key - Save and close the file.
- Start the Infrastructure Management Server by running the following command:pw system start
Where to go from here
Securing-communication-among-Infrastructure-Management-components