Installing the Application Server and the ETL Engine using the wizard

Where you are in the Installation process

StepTask
1Complete the planning activities
2Preparing for TrueSight Capacity Optimization installation
3Install Remedy Single Sign-On
4Install TrueSight Presentation Server
5Install TrueSight Capacity Optimization Application Server and ETL Engine (You are here)
6Install TrueSight Capacity Optimization Gateway Server
7Install TrueSight Capacity Optimization Capacity Agent
8Complete the post-installation activities

You can install the Application Server and ETL Engine on a Linux computer with Oracle or PostgreSQL as the database. You must deploy the Oracle database on a separate computer.

The installation of the Application Server and ETL Engine comprises the installation of these components:

  • Database Schema
  • Application Server
    • Web Server 
    • Data hub 
    • Primary Scheduler
  • ETL Engine

Ensure that all these components and database server are operating in the same time zone.

You can install using one of these settings:

  • Typical: Installs all the components on a single computer. A typical installation requires approximately 3 GB of available storage. The aging configuration that you specify during installation also affects the disk space that is required on the database server. BMC recommends that you install additional ETL Engines on separate computers for data collection, and use the ETL Engine installed on the first computer for administrative tasks.
  • Custom: Allows you to install the components on separate computers for load balancing. This is preferred when you have a distributed computing environment.

For a small environment or test environment, you can use typical installation to install all the components on a single computer. 

For most production environments, use custom installation to install the components on separate computers. By default, the Database Schema and a Web Server are always installed on the first computer. You can choose to install Datahub, Primary Scheduler, and ETL Engine on additional computers. 

To perform a typical installation

  1. Log in to the host computer on which you want to install the Application Server and ETL Engine, and create a temporary directory. Example: TSCO_temp.

    You can install the product as a root or a non-root user. BMC recommends that you install it as a root user, because some of the installation steps are available only to the root user.

  2. Extract the downloaded files to the temporary directory. Ensure that the temporary directory is different from the installation directory to avoid any file sharing conflict.

  3. At the shell prompt, change to the directory where you extracted the installation files. Example: TSCO_temp/BCO/Disk1.
  4. Set the DISPLAY environment variable to ensure that the wizard-based installer launches the screens appropriately:

    DISPLAY=<IP address of the host computer>:0.0 export DISPLAY
  5. Run the installer. At the shell prompt, type ./setup.sh and press Enter

    Tip

    You can start another session and type tail –f on the installation log (bco_install_log.txt) to view detailed messages during installation.

  6. Review the welcome page, and click Next.
  7. Read the license agreement, agree to the terms, and click Next.
  8. Review the available disk space. The default installation directory is /opt/bmc/BCO. You can change the default directory if required, and click Next.
    Avoid using the home directory of the user as the installation directory.
  9. (Displayed to a root user) Provide the name of the user (new or existing) for running TrueSight Capacity Optimization after installation, and click Next. The default user name is cpit

    This user can be a root or a non-root user. BMC recommends that you run the application as a non-root user. If you want to run the application as a root user, ensure that the specified user name is not root

  10. Confirm the user specification, and click Next.
  11. If you are running the first instance of the installation, select Install the first machine, and click Next

    If you are running the next instance of the installation to install selected components, select Install additional machines, and click Next.

    Based on whether you are installing on the first computer or on an additional computer, the applicable pages are displayed.

  12. Retain the default selection, Typical Setup: Application Server, and click Next.

  13. (On the first computer) Specify the following: 

    1. Select the protocol, and click Next. The port numbers are 8443 for HTTPS and 8000 for HTTP.

    2. Provide the following details to connect to Remedy SSO and the TrueSight Presentation Server, and click Next.

      • The FQDN of the host computer on which you have installed Remedy SSO and the port number to communicate with it. If two instances of Remedy SSO are running, use the Remedy SSO server that is configured with the TrueSight Presentation Server. The default port number for Remedy SSO is 8048.
      • Type the FQDN of the host computer on which you have installed TrueSight Presentation Server and the port number to communicate with it. The default port number for TrueSight Presentation Server is 8043.

    3. (Displayed to a root user) Select one of the configuration options, type the details, and click Next.

      • Local Repository: Select if you have a single Application Server.
      • Shared Repository: Select if you have multiple Application Servers. All the Application Servers must use the same shared repository.
        Depending on the shared repository, specify the following details:

        • For Network File Sharing (NFS), specify the name of the NFS server and a path to the shared repository. Example: nfs://server1/share/path

        • For Common Internet File System (CIFS), specify the address of the shared URL, the username and password to access the directory, and the name of the domain.
    4. Select the database, and click Next.

      Based on your selection, the applicable configuration pages are displayed.

    5. (Oracle only) Configure the Oracle database.

      1.  Configure connection details
        1. Provide the path to the Oracle client home directory and SQL*Net configuration folder.

        2. Select one of the following options to connect to the database, and click Next:

          • For Database connection, provide the following details:
            • Specify whether to use service name or database SID, and type the value.
            • Host name of the computer that is running the Oracle database instance.
            • Oracle listener port on the computer. The default port is 1521.
            • Oracle alias name.
          • For LDAP Database connection (advanced), provide the following details:
            • Host name or IP address of the computer that is running LDAP. Only LDAP servers that allow anonymous bind connections are supported.
            • Port number through which the LDAP server communicates.
            • Service name of the Oracle server.
            • Node from which the database instance search is initiated.
          • For Custom JDBC connection URL (advanced), provide the JDBC URL for referencing the database. The syntax is jdbc:odbc:<data source name>.

      2.  Configure schema creation
        1. Specify whether to create new database users and tablespaces (default) or use existing database users and tablespaces. If you do not have a sysdba password and have manually set up the database users and tablespaces before starting installation, use the existing database users and tablespaces option.

        2. To use the default values for database name and partitioning, select Standard. To customize the values, select Advanced. Click Next.
      3.  If you are creating new users and tablespaces, provide schema creation details

        Provide the following schema creation details, and click Next:

        • Name and password of the privileged user who creates the database schema. This name is either sys or a different user name that your database administrator has created.

        • Path where the datafile is saved by your database administrator.

      4.  If you selected Advanced, customize the database names

        Customize the default names, and click Next.

        • Role, name, and password of the database owner.
        • Role of the database that the console uses to store views configuration.
        • Role, name, and password of the database user that the console uses to access data for data marts and advanced reporting.
        • Name of the catalog tablespace, catalog index, data tablespace, data index, and views tablespace.
      5.  If you selected Advanced, specify table partitioning

        Select one of the following options, and click Next:

        • Yes, create partitioned tables. This option is recommended.
        • No, do not use partitioned tables
    6. (PostgreSQL only) Configure the PostgreSQL database.

      1.  Configure connection details

        Select one of the following options to connect to the database, and click Next:

        • For Database connection, provide the following details:
          • The name of the database host where the PostgreSQL database schema is stored.
          • The listener port number for the database. The default port is 5432.
        • For Custom JDBC connection URL (advanced), provide the JDBC URL for referencing the database. The syntax for PostgreSQL is jdbc:postgresql://hostname:port/database_name.
      2.  Configure schema creation
        1. Specify whether to create new database users and tablespaces (default) or use existing database users and tablespaces. If you do not have a sysdba password and have manually set up the database users and tablespaces before starting installation, use the existing database users and tablespaces option.

        2. To use the default values for database name and partitioning, select Standard. To customize the values, select Advanced. Click Next.

      3.  If you are creating new users and tablespaces, provide schema creation details

        Provide the following details, and click Next:

        • Name and password of the privileged user who creates the database schema. This name is either sys or a different user name that your database administrator has created.

        • Path where the datafile is saved by your database administrator.

      4.  If you selected Advanced, customize the database names

        Customize these values, and click Next.

        • Role, name, and password of the database owner.
        • Role, name, and password of the database user that the console uses to store view configuration.
        • Role, name, and password of the database user that the console uses to access data for data marts and advanced reporting.
        • Names of the catalog tablespace, catalog index, data tablespace, and data index.
      5.  If you selected Advanced, specify table partitioning

        Select one of the following options, and click Next:

        • Yes, create partitioned tables. This option is recommended.
        • No, do not use partitioned tables
    7. Configure the aging settings to specify how long you want to retain the historical data that is collected in the data warehouse. Select one of the following options:

      •  Use default aging configuration

        Select the default setting for aging configuration, which is approximately 290 GB space for the database when you have 5000 systems. With the default setting, you can retain historical data for the last two months.

      •  Specify custom aging configuration

        Select the custom setting to configure the aging parameters for the system and business driver data. Specify the duration in days, weeks, or months for preserving the detailed, hourly, daily, and monthly summarized data.

        The short, medium, and long properties are used in the aging class mappings. Metric profiles, when used in combination with the aging class mappings, enable you to be more granular with the metrics that are included or excluded for a specific ETL. These metric profiles also define the duration for which the data is retained in the data warehouse. This aging configuration affects the amount of storage that is used by the data warehouse.


        DetailHourDayMonth

        SystemBusinessSystemBusinessSystemBusinessSystemBusiness
        ShortOne weekOne monthTwo monthsOne yearFour monthsTwo yearsOne yearTen years
        MediumTwo weeksOne monthFour monthsOne yearEight monthsTwo yearsTwo yearsTen years
        LongOne monthOne monthSix monthsOne yearOne yearTwo yearsThree yearsTen years
  14. (On the additional computer) Specify the following:

    1. Connect with the first Application Server using one of the following options, and click Next:

      • Direct connection: The server you are installing connects to the first application server over a direct connection. This server can directly access the TrueSight Capacity Optimization database. Type the following information:
        • The address of the web server.
        • Protocol to be used and a corresponding web port. The port numbers are 8443 for HTTPS and 8000 for HTTP.
      • Remote connection: The server you are installing connects to the first application server over a remote connection. This server is located on a remote network with an unstable or slow connection. Type the following information:
        • External data API server name
        • Protocol to be used, data API port (default value 8443), and control port (default value 8280). Port should be open for communications.
    2. Type the name and password of the administrative user, and click Next. Default user name is Admin.

      Ensure that the administrative user is present in the Capacity_Administration user group of your Remedy SSO server. See  Configuring users and user groups .

      The installer automatically detects the database installed with the existing Application Server. 

    3. Specify the following details to connect to the Oracle database, and click Next.

      • Path of your Oracle Client's Home directory.
      • Name of your Oracle Alias (TNS).
  15. Click Install to start the installation. The installation may take up to 15 minutes.
    After the installation is complete, the Installation Summary page is displayed.
  16. Click View Logs to open the installation logs.
  17. Click Done to exit the installation program.
  18. Verify the Application Server and ETL Engine installation.

    1. Log in as the user that you specified during installation (example: cpit).

    2. Navigate to the installation directory (example: /opt/bmc/BCO).

    3. Run the command: ./cpit status

    A list of installed TrueSight Capacity Optimization services and their current status is displayed. Verify that the services for all installed components are RUNNING.

     Example

  19. Define the TrueSight Capacity Optimization URL and launch the application in a browser. Use one of the following formats:

    https://<FQDN>:<portNumber>

    http://<FQDN>:<portNumber>

    The browser cookie domain assigned to FQDN should be the same for Remedy Single Sign-On, the Presentation Server, and the Application Server.

  20. Type the default Admin credentials (User name: admin, Password: admin12345), and click Log In.

    The TrueSight Capacity Optimization console opens.

    BMC recommends that you change the password for admin immediately after installation. See  Configuring users and user groups .

To perform a custom installation

  1. Log in to the host computer on which you want to install the Application Server and ETL Engine, and create a temporary directory. Example: TSCO_temp.

    You can install the product as a root or a non-root user. BMC recommends that you install it as a root user, because some of the installation steps are available only to the root user.

  2. Extract the downloaded files to the temporary directory. Ensure that the temporary directory is different from the installation directory to avoid any file sharing conflict.

  3. At the shell prompt, change to the directory where you extracted the installation files. Example: TSCO_temp/BCO/Disk1.
  4. Set the DISPLAY environment variable to ensure that the wizard-based installer launches the screens appropriately:

    DISPLAY=<IP address of the host computer>:0.0 export DISPLAY
  5. Run the installer. At the shell prompt, type ./setup.sh and press Enter

    Tip

    You can start another session and type tail –f on the installation log (bco_install_log.txt) to view detailed messages during installation.

  6. Review the welcome page, and click Next.
  7. Read the license agreement, agree to the terms, and click Next.
  8. Review the available disk space. The default installation directory is /opt/bmc/BCO. You can change the default directory if required, and click Next.
    Avoid using the home directory of the user as the installation directory.
  9. (Displayed to a root user) Provide the name of the user (new or existing) for running TrueSight Capacity Optimization after installation, and click Next. The default user name is cpit

    This user can be a root or a non-root user. BMC recommends that you run the application as a non-root user. If you want to run the application as a root user, ensure that the specified user name is not root

  10. Confirm the user specification, and click Next.
  11. If you are running the first instance of the installation, select Install the first machine, and click Next

    If you are running the next instance of the installation to install selected components, select Install additional machines, and click Next.

    Based on whether you are installing on the first computer or on an additional computer, the applicable pages are displayed.

  12. Select Custom Setup, and click Next. The list of Application Server components is displayed.

  13. Select the components that you want to install:

    • TrueSight Capacity Optimization: Select to install all the components on the computer where the installer is being run. This installation is similar to the Typical installation.

    • Database Schema: By default, the Database Schema is installed when you install the Application Server. This component is always installed on the first computer. Hence, you cannot clear this check box.

    • Application Server: Select the components that you want to install on this computer.

      • Web Server: This component is always installed on the first computer. Hence, you cannot clear this check box.
        An Apache Web Server is installed even if a different web server already exists on the computer.
      • Data hub
      • Primary Scheduler

    • ETL Engine

      Note

      By default, the Web Server is always installed on the first computer. If you choose to install Datahub on a separate computer, an error is displayed on the TrueSight Capacity Optimization console home page until the Datahub installation is completed. 

  14. (On the first computer) Specify the following: 

    1. Select the protocol, and click Next. The port numbers are 8443 for HTTPS and 8000 for HTTP.

    2. Provide the following details to connect to Remedy SSO and the TrueSight Presentation Server, and click Next.

      • The FQDN of the host computer on which you have installed Remedy SSO and the port number to communicate with it. If two instances of Remedy SSO are running, use the Remedy SSO server that is configured with the TrueSight Presentation Server. The default port number for Remedy SSO is 8048.
      • Type the FQDN of the host computer on which you have installed TrueSight Presentation Server and the port number to communicate with it. The default port number for TrueSight Presentation Server is 8043.

    3. (Displayed to a root user) Select one of the configuration options, type the details, and click Next.

      • Local Repository: Select if you have a single Application Server.
      • Shared Repository: Select if you have multiple Application Servers. All the Application Servers must use the same shared repository.
        Depending on the shared repository, specify the following details:

        • For Network File Sharing (NFS), specify the name of the NFS server and a path to the shared repository. Example: nfs://server1/share/path

        • For Common Internet File System (CIFS), specify the address of the shared URL, the username and password to access the directory, and the name of the domain.
    4. Select the database, and click Next.

      Based on your selection, the applicable configuration pages are displayed.

    5. (Oracle only) Configure the Oracle database.

      1.  Configure connection details
        1. Provide the path to the Oracle client home directory and SQL*Net configuration folder.

        2. Select one of the following options to connect to the database, and click Next:

          • For Database connection, provide the following details:
            • Specify whether to use service name or database SID, and type the value.
            • Host name of the computer that is running the Oracle database instance.
            • Oracle listener port on the computer. The default port is 1521.
            • Oracle alias name.
          • For LDAP Database connection (advanced), provide the following details:
            • Host name or IP address of the computer that is running LDAP. Only LDAP servers that allow anonymous bind connections are supported.
            • Port number through which the LDAP server communicates.
            • Service name of the Oracle server.
            • Node from which the database instance search is initiated.
          • For Custom JDBC connection URL (advanced), provide the JDBC URL for referencing the database. The syntax is jdbc:odbc:<data source name>.

      2.  Configure schema creation
        1. Specify whether to create new database users and tablespaces (default) or use existing database users and tablespaces. If you do not have a sysdba password and have manually set up the database users and tablespaces before starting installation, use the existing database users and tablespaces option.

        2. To use the default values for database name and partitioning, select Standard. To customize the values, select Advanced. Click Next.
      3.  If you are creating new users and tablespaces, provide schema creation details

        Provide the following schema creation details, and click Next:

        • Name and password of the privileged user who creates the database schema. This name is either sys or a different user name that your database administrator has created.

        • Path where the datafile is saved by your database administrator.

      4.  If you selected Advanced, customize the database names

        Customize the default names, and click Next.

        • Role, name, and password of the database owner.
        • Role of the database that the console uses to store views configuration.
        • Role, name, and password of the database user that the console uses to access data for data marts and advanced reporting.
        • Name of the catalog tablespace, catalog index, data tablespace, data index, and views tablespace.
      5.  If you selected Advanced, specify table partitioning

        Select one of the following options, and click Next:

        • Yes, create partitioned tables. This option is recommended.
        • No, do not use partitioned tables
    6. (PostgreSQL only) Configure the PostgreSQL database.

      1.  Configure connection details

        Select one of the following options to connect to the database, and click Next:

        • For Database connection, provide the following details:
          • The name of the database host where the PostgreSQL database schema is stored.
          • The listener port number for the database. The default port is 5432.
        • For Custom JDBC connection URL (advanced), provide the JDBC URL for referencing the database. The syntax for PostgreSQL is jdbc:postgresql://hostname:port/database_name.
      2.  Configure schema creation
        1. Specify whether to create new database users and tablespaces (default) or use existing database users and tablespaces. If you do not have a sysdba password and have manually set up the database users and tablespaces before starting installation, use the existing database users and tablespaces option.

        2. To use the default values for database name and partitioning, select Standard. To customize the values, select Advanced. Click Next.

      3.  If you are creating new users and tablespaces, provide schema creation details

        Provide the following details, and click Next:

        • Name and password of the privileged user who creates the database schema. This name is either sys or a different user name that your database administrator has created.

        • Path where the datafile is saved by your database administrator.

      4.  If you selected Advanced, customize the database names

        Customize these values, and click Next.

        • Role, name, and password of the database owner.
        • Role, name, and password of the database user that the console uses to store view configuration.
        • Role, name, and password of the database user that the console uses to access data for data marts and advanced reporting.
        • Names of the catalog tablespace, catalog index, data tablespace, and data index.
      5.  If you selected Advanced, specify table partitioning

        Select one of the following options, and click Next:

        • Yes, create partitioned tables. This option is recommended.
        • No, do not use partitioned tables
    7. Configure the aging settings to specify how long you want to retain the historical data that is collected in the data warehouse. Select one of the following options:

      •  Use default aging configuration

        Select the default setting for aging configuration, which is approximately 290 GB space for the database when you have 5000 systems. With the default setting, you can retain historical data for the last two months.

      •  Specify custom aging configuration

        Select the custom setting to configure the aging parameters for the system and business driver data. Specify the duration in days, weeks, or months for preserving the detailed, hourly, daily, and monthly summarized data.

        The short, medium, and long properties are used in the aging class mappings. Metric profiles, when used in combination with the aging class mappings, enable you to be more granular with the metrics that are included or excluded for a specific ETL. These metric profiles also define the duration for which the data is retained in the data warehouse. This aging configuration affects the amount of storage that is used by the data warehouse.


        DetailHourDayMonth

        SystemBusinessSystemBusinessSystemBusinessSystemBusiness
        ShortOne weekOne monthTwo monthsOne yearFour monthsTwo yearsOne yearTen years
        MediumTwo weeksOne monthFour monthsOne yearEight monthsTwo yearsTwo yearsTen years
        LongOne monthOne monthSix monthsOne yearOne yearTwo yearsThree yearsTen years
  15. (On the additional computer) Specify the following:

    1. Connect with the first Application Server using one of the following options, and click Next:

      • Direct connection: The server you are installing connects to the first application server over a direct connection. This server can directly access the TrueSight Capacity Optimization database. Type the following information:
        • The address of the web server.
        • Protocol to be used and a corresponding web port. The port numbers are 8443 for HTTPS and 8000 for HTTP.
      • Remote connection: The server you are installing connects to the first application server over a remote connection. This server is located on a remote network with an unstable or slow connection. Type the following information:
        • External data API server name
        • Protocol to be used, data API port (default value 8443), and control port (default value 8280). Port should be open for communications.
    2. Type the name and password of the administrative user, and click Next. Default user name is Admin.

      Ensure that the administrative user is present in the Capacity_Administration user group of your Remedy SSO server. See  Configuring users and user groups .

      The installer automatically detects the database installed with the existing Application Server. 

    3. Specify the following details to connect to the Oracle database, and click Next.

      • Path of your Oracle Client's Home directory.
      • Name of your Oracle Alias (TNS).
  16. Click Install to start the installation. The installation may take up to 15 minutes.
    After the installation is complete, the Installation Summary page is displayed.
  17. Click View Logs to open the installation logs.
  18. Click Done to exit the installation program.

  19. Verify the Application Server and ETL Engine installation.

    1. Log in as the user that you specified during installation (example: cpit).

    2. Navigate to the installation directory (example: /opt/bmc/BCO).

    3. Run the command: ./cpit status

    A list of installed TrueSight Capacity Optimization services and their current status is displayed. Verify that the services for all installed components are RUNNING.

     Example

     TrueSight Capacity Optimization components and their services

    Component

    Web service

    Scheduler service

    Service Container service

    Data Hub service

    Httpd service

    Web

    (tick)

    (tick)

    (tick)

    -

    (tick)

    Primary Scheduler

    -

    (tick)

    (tick)

    -

    -

    Data Hub

    -

    (tick)

    (tick)

    (tick)

    (tick)

    ETL

    -

    (tick)

    -

    -

    -

    For example, if you have installed a Primary Scheduler and the Data Hub, verify that the Scheduler, Data Hub, and Httpd services, are RUNNING; if you have enabled the Service Container component, verify that the Service Container is also RUNNING.

  20. Define the TrueSight Capacity Optimization URL and launch the application in a browser. Use one of the following formats:

    https://<FQDN>:<portNumber>

    http://<FQDN>:<portNumber>

    The browser cookie domain assigned to FQDN should be the same for Remedy Single Sign-On, the Presentation Server, and the Application Server.

  21. Type the default Admin credentials (User name: admin, Password: admin12345), and click Log In.

    The TrueSight Capacity Optimization console opens.

    BMC recommends that you change the password for admin immediately after installation. See  Configuring users and user groups .


Next step in the Installation process

Now that you have successfully installed the Application Server and ETL Engine, you can install the Gateway Server if required.

Was this page helpful? Yes No Submitting... Thank you

Comments

  1. Jim Waring

    Gateway Server is optional. you must should be changed to you may if required install the Gateway Server.

    Nov 23, 2018 02:46
    1. Bipin Inamdar

      Hi Jim,

      Thanks for the feedback. I have updated the statement to say that the Gateway Server installation is not mandatory.

      Regards,

      Bipin Inamdar

      Nov 23, 2018 03:45