Configuring the TrueSight Server Automation connector

TrueSight Server Automation connector is used to establish a connection between Automation Console and the TrueSight Server Automation Application Server. Automation Console sends notifications for jobs such as updating catalogs, and running patching jobs to the connector, which sends it to the TrueSight Server Automation. The connector ensures that even if the application server is in an air-gapped environment, communication between Automation Console and the application server is uninterrupted. 

By default, the connector establishes a connection over the HTTPS protocol using out-of-the-box self-signed certificates. To ensure seamless communication, you must provide the connector information in the hosts file on Server Automation server as mentioned below:

You create a service account and specify the data refresh interval while configuring the connector. The Data Refresh capability monitors jobs that affect the status of the missing patches and managed assets and regularly updates the job data in Automation Console. This service account is also used for change automation while obtaining approvals from BMC Remedy IT Service Management. 

If you have multiple Application Servers (MAS) set up in your TrueSight Server Automation environment, in case of failure of one of the instances, you can edit the connector configuration and specify a different TrueSight Server Automation server. 

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 18.9 (build 11.0.7+10) is installed on the connector host

• Port requirement as below -

  Port	Protocol	Source	Destination	Inbound /outbound
  9843	HTTPS	Connector	TSSA Application Server	Outbound
  443	HTTPS	TSSA Application Server	Connector	Inbound

Updating the Server Automation connector for TrueSight Automation Console

When you install TrueSight Automation Console, the TrueSight Server Automation connector is already configured and running. From the briefcase menu, go to Connectors and the TrueSight Server Automation connector is shown as running. 

On the Connectors > Manage Connectors page do the following:

1. Click the  option against the TrueSight Server Automation connector and then click Edit.
   On the Update a Connector page, the TrueSight Server Automation server details, service account user details, and the data refresh interval is displayed. 
   By default, the time interval is 60 minutes. Minimum is 5 minutes and maximum is 10080 minutes.

2. Make changes as per your requirement and save the connector configuration. 
   After entering the password, click Save.

   Can I provide a different TrueSight Server Automation host details while editing the connector?

   Yes, in case of failure of the existing Application Server, you can specify another Application Server only if it belongs to a multiple Application Servers (MAS) set up.

3. Click > Enable to run the connector with the new changes. 

Enabling debug mode

BMC recommends that you do not modify any other configuration files available in the /config directory. However, you can enable the debug mode on the connector to obtain detailed logging information.

Do this:

1. Press CTRL+C twice to stop the connector.

2. Go to <ConnectorLocation>/config, open the log4j.properties file, and change the logging option to debug.

   # Root logger option
   log4j.rootLogger=debug, file
3. Start the connector.

Where to go next?

Log in to Automation Console with the appropriate credentials to successfully verify the connector installation. See Accessing-and-navigating-the-interface-for-using-with-TrueSight-Server-Automation.