Post-installation tasks for TrueSight Orchestration in containers

Where you are in the installation process

Complete the post-installation tasks to ensure that your TrueSight Orchestration environment in containers is functional:

Configure Development Studio to connect to a CDP in containers

Before connecting Development Studio to a Configuration Distribution Peer (CDP), on the computer where your Development Studio is installed, you must map the IP address and hostname of the repository and the CDP in the hosts file.

To update the containerized platform details in the hosts file:

1. On the computer where Development Studio is installed, go to C:\Windows\System32\drivers\etc\ and open the hosts file and specify the IP address and hostname of the host where the repository and the CDP are installed. 

   <Repo_IP_Address> tso-repo-service <Repo_hostname>
   <CDP_IP_Address> tso-cdp-service <CDP_hostname>

2. Save changes. 

After successfully performing these steps, you can now establish a connection between the Development Studio and the CDP. For instructions, see Connecting to an environment.

Map LAP to CDP

If you are using a Lightweight Activity Peer (LAP) to host windows-based adapters, ensure that you map the LAP host to the host where CDP is installed in containers.

1. On the computer where the LAP is installed, go to C:\Windows\System32\drivers\etc\ and open the hosts file and specify the IP address and hostname of the host where the repository and the CDP are installed. 

   <Repo_IP_Address> tso-repo-service <Repo_hostname>
   <CDP_IP_Address> tso-cdp-service <CDP_hostname>

2. Save changes. 
   You can now successfully work with the LAP. 

Change to an external Remedy SSO

By default, repository image contains embedded Remedy Single Sign-On, which is used as an external Remedy SSO for the CDP.
If you have chosen to install external Remedy SSO, and want to use it with the containerized platform, then components must be reconfigured to point to the external Remedy SSO instance.

In a containerized platform, you configure the repository and the CDP to point to an external Remedy SSO. 

1. Open a terminal and SSH into the host where the repository is installed, go in the container and stop the repository service. 

   # docker exec -it <containerID> bash

   # sh AO_HOME/bin/server.sh stop

2. Go to the AO_Home\config directory and edit the authentication.xml file.

   # vi /opt/bmc/BAO/repo/config/authentication.xml

3. In the <config> tag, change the <service-type> to RSSO_EXTERNAL, and specify the URL, tenant name for the external Remedy SSO.

   <authentication>
     <config>
       <service-type>RSSO_EXTERNAL</service-type>
       <url><ExternalRSSOHostName>:<port></url>
       <tenant>BAOLocal</tenant>
   	<version>19.08</version>
     </config>
   </authentication>

4. Save changes and restart the repository service. 

   # sh AO_HOME/bin/server.sh start

5. Perform Step 1 to Step 4 on the host where the CDP is installed. 

Configure adapters that require file system paths

Containers are stateless, this means that containers may stop running and the component starts running on a different container. Hence, you cannot use the container ID to specify the file paths while configuring adapters. 

To ensure that the adapters that require files (such as the script adapter) to be enabled on the grid, you must place the files in the /opt/bmc/BAO/CDP/tomcat/temp location where the CDP container is running. The files placed in the temp folder are stored on the CDP's mounted volumes and available even if the container ID changes. While configuring the adapter on the grid, ensure that you provide the path where the files are placed.

For example, if using a script adapter, you must place your Perl or Jython scripts at the /opt/bmc/BAO/CDP/tomcat/temp location. While configuring the script adapter on the Grid Manager, specify the temp folder path in the <script-install-path> configuration element.

Where to go from here

Now that you have installed TrueSight Orchestration in containers successfully, you can use other sections in the documentation for learning more about the product features.