Configuring the TrueSight Orchestration connector

As an administrator, you configure a connector to enable integration with TrueSight Orchestration for change management. For any remediation operation (patch, vulnerability, compliance, and template-based), you can now create a change ticket with an approval process in BMC Remedy IT Service Management and ServiceNow. The TrueSight Orchestration connector establishes a connection and enables communication between TrueSight Orchestration and Automation Console. For more details about the integration, see Change-automation. 

Before you begin

Before running the connector, ensure that the connector is installed and run on Windows and Linux operating systems that match the following criteria:

• AdoptOpenJDK Runtime Environment 17 is installed on the connector host

• Port requirements:

  Port	Protocol	Source	Destination	Inbound / Outbound
  open and usable port on connector VM	HTTPS	Connector	HAC Saas and Internet	Outbound
  38080 OR <Customer configured port>	HTTPS	Connector	Orchestration Server	Outbound
  open and usable port on connector VM	HTTPS	Orchestration Server	Connector	Inbound

  Port	Protocol	Source	Destination	Inbound / Outbound
  open and usable port on connector VM	HTTPS	Connector	HAC Saas and Internet	Outbound
  38080 OR <Customer configured port>	HTTPS	Connector	Orchestration Server	Outbound
  open and usable port on connector VM	HTTPS	Orchestration Server	Connector	Inbound

   

To configure the TrueSight Orchestration connector

To configure the connector, do these steps: 

1. In BMC Helix Automation Console, click Configuration and then click Connectors.
2. On the Manage Connectors page, click Add Connector.
3. On the Add Connector page, from the list of available Connector types, select Orchestration Connector.
4. On the Add Connector page, perform the following steps:
   1. (Optional) Select Enable change management for Automation Console to make change request creation and approval mandatory when an operation is created.  
   2. In the Truesight Orchestration Connector Connection String field, enter the host name where TrueSight Orchestration Grid Manager is installed in the https://<FQDN> format.
   3. In the Truesight Orchestration Connector Port field, provide the port number. 
   4. Enter theTruesight Orchestration Connector user name, password, and the grid name required to log on to the Grid Manager. 
   5. Click Create. 
5. Click Continue and download the connector zip file on a local host. 

6. On the server where the connector file is downloaded and extracted, go to the connector location, and run the following command to install and start the connector: 

   • Windows: run.bat
   • Linux: run.sh

   The connector starts running successfully. You can view the connector status on the Connectors page. 

7. (Optional) To configure the TrueSight Orchestration connector as a service, perform the following steps:
   1. Make sure the tso-connector.xml file is available in a folder where the connector zip file is unzipped.
   2. Run the tso-connector.exe install command. 
   3. A new service with the name BMC TrueSight Orchestration Connector is created on the host and can be used as any other available service.

To enable debug mode

1. Press CTRL+C twice to stop the connector, if its already running

2. Go to <ConnectorLocation>/config, open the application.properties file, add the following parameter and set it to debug, save the file

   #
   #Logging related Properties
   logging.level.com.bmc.connector.plugin.aoconnector=debug 
3. Restart the connector.

To enable web proxy support

After configuring the TrueSight Orchestration connector, perform the following steps to enable web proxy support:

1. Download the connector.
2. Download the Proxy certificate der file. Make sure the der file is imported to the cacerts of the connector machine and the jks file used for Helix Single Sign-On (HSSO).
3. If the proxy is https enabled, download and import the certificate of the proxy server into the cacerts file of the connector machine.
   keytool -importcert -file "<file name>" -keystore "<path_to_java_installation_dir>\lib\security\cacerts" -alias "<name>"
4. Navigate to the application.properties file of the connector and provide the following information:
   • proxyHost= bcx-pun-xxxxx.bmc.com
   • proxyPort=3129
   • proxyProtocol=https

Where to go next?

After successfully configuring the connector, you can now complete the tasks required to enable change automation. See Enabling-change-automation.