Installing in the interactive mode

After your prepare the environment for installation, use the Stack Manager tool to install the TrueSight Automation Console database and the application components. 

You can also install the product components from a command line. See Installing-silently. 

Warning

TrueSight Automation Console is delivered to customers bundled as a set of Docker Containers. The Docker Containers and the software installed on them should not be taken out of Automation Console or used separately. Installing additional third-party software or updating existing software packages in the Docker Containers is not permitted, unless explicitly authorized by BMC Software.

Build numbers

If you have multiple images of the Stack Manager tool available on the host, BMC recommends that you provide the exact version and build number depending on the version that you want to install. 

Version

Build number

Details

24.3.00

3037

The TrueSight Automation Console installer

To install the Stack Manager tool

  1. Open a terminal and SSH into the host where you have set up the local registry, and run the following command to install the Stack Manager tool. 

    docker run -it --rm --network=host 127.0.0.1:5000/bmcsoftware/truesight-stack-manager

    Here, 127.0.0.1:5000 is the host:port of the local registry that contains the Automation Console images.  
    You are prompted to specify a location to install the product.  

    Important

    If you have any images of Stack Manager in your environment, ensure that you use the exact version and build number for installing the latest Stack Manager tool.

    Example
    docker run -it --rm --network=host <hostname>:<port>/bmcsoftware/truesight-stack-manager:24.3.00.3037

  2. Enter a username and password. 

    Important

    You can use a root or a non-root user. If using a non-root user, ensure that the user has read and write permissions to the installation directory and is a part of the docker user group on the host.

  3. Enter a location or continue with the default /opt/bmc location. The Stack Manager tool is installed at the specified location. 

    Tip

    To see the commands typically used during installation and other help, run this command:

    <stackmanager-install-dir>/stackmanager --help

    You can now continue with installing the database and the application.

To install the database

By default, PostgreSQL database is installed with the product. However, BMC recommends that you do not use the containerized DB for your production environments. Use an external PostgreSQL database instead. 

  1. On the host where the Stack Manager tool is installed, run any of the following commands to start installing the database. 

    <stackmanager-install-dir>/stackmanager install --deployment=database

    or 

    <stackmanager-install-dir>/stackmanager install --deployment database
  2. Verify whether the default Docker registry details are accurate and press Enter to continue. 
    The End User License Agreement is displayed. 
  3. Read, and type y to continue with the installation. 

  4. After accepting the license agreement, you must provide the values that match your environment (for external database) or accept the default values: 

    Field

    Default value

    Notes

    Docker network subnet prefix

    -

    Note: Ensure that the subnet prefix does not conflict with the subnet CIDR or the IP address (172.xx.0.0/16) of your datacenter for the docker0 (docker network adapter/ bridge).

    The IP address can be set to either a single octet (For example, 192 which will create the docker networks as 192.X.X.X and so on) or two octets (For example, 192.112 which will create docker networks as 192.112.X.X and so on). This value is used to create internal docker network (application and data network) for container communications and is not visible outside the host machine.

    Note

    You have to avoid the subnet/IP of the network, the host is connected to.

    To view the current docker settings, run the docker network inspect bridge command.

    Alternatively, if you have created a daemon.json configuration file after setting up Docker, verify the current settings in the file.

    For example, go to cat /etc/docker/daemon.json
    The file shows the current setting as { "bip": "172.17.0.1/16" }. 

    Port number for PostgreSQL server

    5432

    Do not change the default port number.

    PostgreSQL Admin username

    postgres


    PostgreSQL Admin password

    -


    PostgreSQL database installation is complete. 

  5. To verify whether the installation is successful, run the following command:

    <stackmanager-install-dir>/stackmanager status  --deployment=database

    The installation is successful if the status is running.

Now that you have successfully installed the database, you can begin installing the application.

Important

BMC recommends to install TrueSight Automation Console Application Server and the database on different host servers. However, for a proof-of-concept or a test environment, both the TrueSight Automation Console application and database can be installed on the same host.

To install the Automation Console application

Install the application after successfully installing the database. 

  1. On the host where the Stack Manager tool is installed, run any of the following commands to start installing the application. 

    ./stackmanager install  --deployment=tsac+

    or

    ./stackmanager install  --deployment tsac+

    If installing the application on a host where containerized database is installed, the installer will confirm whether the database is already installed.
    If using an external database (containerized or non-containerized), the installer asks for the additional inputs during application installation. The End User License Agreement is displayed. 

  2. Read, and type y to continue with the installation. 

  3. After accepting the license agreement, you must provide the values that match your environment or accept the default values: 

    Field

    Default value/notes

    Docker network subnet prefix (The installer prompts for this field only if a containerized or an external database is installed on a different host.)

    Ensure that the subnet prefix does not conflict with the subnet CIDR or the IP address (172.xx.0.0/16) of your data center for the docker0 (docker network adapter/ bridge).

    The IP address can be set to either a single octet (For example, 192 which will create the docker networks as 192.X.X.X and so on) or two octets (For example, 192.112 which will create docker networks as 192.112.X.X and so on). This value is used to create internal docker network (application and data network) for container communications and is not visible outside the host machine.

    Note

    You have to avoid the subnet/IP of the network, the host is connected to.

    To view the current docker settings, run the docker network inspect bridge command.

    Alternatively, if you have created a daemon.json configuration file after setting up Docker, verify the current settings in the file.

    For example, go to cat /etc/docker/daemon.json
    The file shows the current setting as { "bip": "172.17.0.1/16" }.

    This field is required when you install the database and application on separate hosts.

    Fully-qualified domain name or IP address of the PostgreSQL server installed in the previous step

    BMC recommends that you do not use the containerized DB for your production environments. Use an external PostgreSQL database instead. 

    Port number of the PostgreSQL server

    5432. This field is required when you install the database and application on separate hosts.

    Password for the PostgreSQL Admin user 'postgres':


    Name of the database

    tsac_database

    New username for the database

    tsac_database_user

    Password for the new database user

    -

    PostgreSQL tablespace

    tsac_tablespace

    Directory for the system tablespace on the PostgreSQL server

    - For containerized PostgreSQL server installed by the StackManager, the default directory, which is not configurable, is: /var/lib/postgresql/data/tsac_tablespace - For an external non-containerized PostgreSQL database, provide a different database directory.

    Automation Console port number

    10443

  4. To configure the connector based on your requirement, select one of the following options:
    • TrueSight Server Automation
    • TrueSight Network Automation
    • Configure both the connectors (Default)

  5. If you choose to configure the TrueSight Server Automation connector, enter 1 and provide the following values: 

    Field

    Default values/Notes

    TrueSight Server Automation hostname

    Fully-qualified domain name or IP address of TrueSight Server Automation

    TrueSight Server Automation port number

    9843

    TrueSight Server Automation protocol

    https

    TrueSight Server Automation admin role name

    BLAdmins

    TrueSight Server Automation Service Account username

    BLAdmin

    TrueSight Server Automation password for the Service Account user


    TrueSight Server Automation role name for the Service Account user

    BLAdmins

    TrueSight Server Automation login authentication type for the Service Account user

    SRP  Valid values: SRP, Domain

    Do you want to configure support for RSSO authentication (y/n)

    If using BMC Remedy Single Sign-On for TrueSight Server Automation, specify y.

    If not, specify n.

    Enter the RSSO Server URL

    If specified y in the previous field, enter the BMC Remedy Single Sign-On URL in a fully-qualified domain name format.

  6. If you choose to configure TrueSight Network Automation connector, enter 2 and then provide the values that match your environment.

    Field

    Default values/Notes

    TrueSight Network Automation host name

    Fully-qualified domain name or IP address of TrueSight Network Automation

    TrueSight Network Automation port number

    443

    TrueSight Network Automation protocol

    Valid values: http, https (default)

    TrueSight Network Automation realm name

    Default

    TrueSight Network Automation Service Account user name

    sysadmin

    TrueSight Network Automation password for the Service Account user 


  7. If you want to configure both the connectors, enter 3 and then provide the values described for the TrueSight Server Automation and TrueSight Network Automation connectors. 

    Connector configuration options

    If you choose option 1 (TrueSight Server Automation connector) or option 2 (TrueSight Network Automation connector) you will not be able to configure the other connector using the Stack Manager. If required, you can configure the connector from the UI later. For details, see Managing-connectors.

    After all the details are provided, the Stack Manager installs the application. 

  8. Run the following command to verify whether the application is installed successfully:

    ./stackmanager status  --deployment=application

    All the container names must display their status as running.
    Excerpt named 242_status was not found in document xwiki:Automation-DevSecOps.Automation-Console.TrueSight-Automation-Console.tsac243.Deployment-by-using-Stack-Manager.Upgrading-the-product-by-using-Stack-Manager.Performing-the-upgrade.WebHome.

Where to go next?

Now that you have installed the product successfully, administrators can start setting up the application for your patch, vulnerability, or compliance management needs. You can start using its features based on your role and requirements. 

If you want to integrate with BMC Discovery to identify discovered assets, and TrueSight Orchestration to enable change automation, configure the connectors. For details, see Managing-connectors. 

 

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