Unsupported content This version of the product has reached end of support. The documentation is available for your convenience. However, you must be logged in to access it. You will not be able to leave comments.

Setting up the TrueSight Orchestration connector

This topic describes a process for setting up a connector for TrueSight Orchestration. This connector enables communication between TrueSight Vulnerability Management and a TrueSight Orchestration configuration distribution peer (CDP) server. 

After the configuration process is complete, you can set up job approval and change tracking for operator actions by integrating TrueSight Vulnerability Management and TrueSight Server Automation with BMC Remedy ITSM and TrueSight Orchestration.

Note

  • When using TrueSight Orchestration, TrueSight Vulnerability Management supports operator-initiated Change Automation use case with all endpoint managers.
  • TrueSight Orchestration must be running version 8.1 or later.

The following sections in this topic describe how to set up the TrueSight Orchestration connector. 

Before you begin

To set up a connector for TrueSight Orchestration, confirm that a system connector for TrueSight Server Automation has already been set up. 

Note

When setting up connectors, a single machine cannot host more than one connector of the same type. For example, if you have set up a connector for TrueSight Orchestration on a host, you cannot set up another TrueSight Orchestration connector on the same host.

To set up a TrueSight Orchestration connector

  1. Log on to TrueSight Vulnerability Management as a TrueSight Server Automation administrator with your registered credentials.
  2. Click the External Connectors tab. 
  3. Click Add External Connector. 
    The Create External Connection page appears. It lets you choose the connectors that interact with TrueSight Vulnerability Management.
    You cannot add a connector for TrueSight Orchestration without first adding a system connector for TrueSight Server Automation. 

    AOConnector.png
  4. From Type, select Orchestration if not selected by defualt.

  5. Provide the following information for the TrueSight Orcehstration connector.

    Tip

    If you have access to the TrueSight Server Automation application server, you can obtain most of the following information by going to Configuration > Integration Configuration > AO Configuration.

    Option

    Description

    Connection String

    IP address or fully-qualified host name of the TrueSight Orchestration configuration distribution peer (CDP) server. The host name should be in the format https://<hostname>.

    Port

    Port number used to connect to the TrueSight Orchestration CDP.

    Username

    Name of the TrueSight Orchestration user required to log on to the CDP. This user must be associated with the ADMIN role in TrueSight Orchestration.

    Password

    TrueSight Orchestration password for the specified user.

    Grid

    Name defined for the TrueSight Orchestration grid.

    A grid is a logical collection of servers, called peers, where the TrueSight Orchestration Platform is installed. The peers on the grid communicate with each other and work as a group. They communicate concurrently to every other peer in the group, and can detect which peers are running and the load on those peers.

  6. Click Test Connection to confirm that the connection to TrueSight Orchestration is working correctly.
    A message confirms that the connection is valid.
  7. Click Create External Connector. 

Where to go next

Set up job approval and change tracking for operator actions in TrueSight Vulnerability Management.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*