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.
Failed to execute the [excerpt-include] macro.
Failed to execute the [excerpt-include] macro.
Failed to execute the [excerpt-include] macro.
Failed to execute the [excerpt-include] macro.
Failed to execute the [excerpt-include] macro.
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
Failed to execute the [excerpt-include] macro.
Where to go from here
Securing-communication-among-Infrastructure-Management-components