Installing the Application Server and the ETL Engine silently

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

A Service Container is automatically installed when you install any of the Application Server components.

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. 

The silent installation obtains the required user input from the options files, which are bundled with the installer. 

To install the Application Server and the ETL Engine silently

  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. (On the first computer) Generate the common keys that are used for secure communication between the components: 
    ./BCOEncoder.sh -genkeys

  5. (On the additional computer) Navigate to the /tmp folder and extract the contents of the tar file of the secure folder that you created after the installation was completed on the first computer.
  6. You will need to type the database administrator password and the schema passwords in an encrypted form in the config file. Encrypt these passwords by running the command:
    ./BCOEncoder.sh <password>
    Note down the encrypted password displayed on the screen. Example: DES\:097133405e7ea7a6bcc58bbe70ece4c2.
  7. Navigate to the directory where you extracted the downloaded files and locate the sample config files. Example: TSCO_temp/BCO/Disk1/silentInstallTemplates.
  8. Based on the installation scenario, use the applicable options file. This is a text file that defines the installation properties in the form of a prefix tag followed by a property name and value pair. You can either retain the default values or change them and save the file. The following table lists the installation scenarios and the applicable options files:

     Installation scenarios and options files
    ScenarioOptions file
    Typical installation on the first computer with Oracle.BCO_FIRST_SERVER_TYPICAL_ORACLE.txt
    Typical installation on the first computer with PostgreSQL.BCO_FIRST_SERVER_TYPICAL_POSTGRES.txt
    Custom installation on the first computer with Oracle. Installs the Database Schema and Web Server.BCO_FIRST_SERVER_CUSTOM_AS_FRONTEND_WEB_ORACLE.txt
    Custom installation on the first computer with PostgreSQL. Installs the Database Schema and Web Server.BCO_FIRST_SERVER_CUSTOM_AS_FRONTEND_WEB_POSTGRES.txt
    Custom installation on the additional computer. Installs the Data hub, Primary Scheduler, and ETL Engine.BCO_ADDITIONAL_SERVER_AS_BACKEND_DH_PS.txt
    Custom installation on the additional computer. Installs the Web Server.BCO_ADDITIONAL_SERVER_AS_WEB.txt
    Custom installation on the additional computer. Installs ETL Engine over a direct connection.BCO_ADDITIONAL_SERVER_EE.txt
    Custom installation on the additional computer. Installs ETL Engine over a remote connection.BCO_ADDITIONAL_SERVER_REMOTE_EE.txt
    Custom installation on the additional computer. Installs Primary Scheduler.BCO_ADDITIONAL_SERVER_AS_PS.txt
  9. Based on the options file you are using, set the appropriate parameters. The following table lists all the parameters that are found in the various options files.
    Based on the installation scenario, the options files have some of these parameters commented out. 

     Property details

    Prefix tags for the silent installation properties:

    • -P: Precedes the directory properties

    • -A: Precedes the application features

    • -J: Precedes the Java properties

    Property nameDescription
    Installation settings
    -P installLocation

    Retain the following default installation directory path or type a new path: /opt/bmc/BCO

    Example: -P installLocation=/opt/bmc/BCO

    -J INSTALLATION_TYPE_SELECTION

    Specify the installation type:

    INSTALLATION_TYPE_SELECTION=APPLICATION_SERVER|EXTERNAL_SERVER

    The default values are:

    • (On the first computer) -J INSTALLATION_TYPE_SELECTION=APPLICATION_SERVER
    • (On an additional computer) -J INSTALLATION_TYPE_SELECTION=EXTERNAL_SERVER
    -J INSTALL_SET

    Specify the installation setup:

    INSTALL_SET=TYPICAL|CUSTOM

    The default values are:

    • (Typical) -J INSTALL_SET=TYPICAL
    • (Custom) -J INSTALL_SET=CUSTOM
    Installing components
    -A <feature name>

    If INSTALL_SET=CUSTOM, specify the components to be installed:

    -A <feature name>
    • Database Schema: -A featureDatabaseSchema
    • Web components: -A featureWeb
    • Datahub: -A featureDatahub
    • Primary Scheduler: -A featurePrimaryScheduler
    • ETL Engine: -A featureCoreETL
    On the first computer only
    Protocol
    -J ENABLE_HTTPS_

    Retain the default value.

    Default value: true

    Example: -J ENABLE_HTTPS_=true

    When set to true, it enables SSL using a self-signed certificate (port 8443). If set to false, the HTTP web server accepts unsecured TCP connections (port 8000).

    For root user
    -J BCO_USER

    Specify the name of the user (new or existing) for running TrueSight Capacity Optimization after installation.

    Default value: cpit

    Example: -J BCO_USER=cpit

    -J REPOSITORY_CONFIGURATION

    Specify the repository configuration.

    REPOSITORY_CONFIGURATION=LOCAL_REPOSITORY|SHARED_REPOSITORY

    Default value: LOCAL_REPOSITORY

    Example: -J REPOSITORY_CONFIGURATION=LOCAL_REPOSITORY

    -J SRC_TYPE

    If REPOSITORY_CONFIGURATION=SHARED_REPOSITORY, select the source type.

    SRC_TYPE=NFS|CIFS

    Default value: NFS

    Example: -J SRC_TYPE=NFS

    • If SRC_TYPE=NFS, specify the following values:
    • If SRC_TYPE=CIFS, specify the following values:
      • -J CIFS_SHAREDURL: Address of the shared URL.
      • -J CIFS_DOMAIN: Name of the network domain.
      • -J CIFS_USER: Name of the network user.
      • -J CIFS_PASSWORD: Password of the network user to access the directory.
    Database
    -J _BCO_DB_TYPE_

    Specify the database.

    -J _BCO_DB_TYPE_=ORACLE|POSTGRES

    The default values are:

    • (Oracle) -J _BCO_DB_TYPE_=ORACLE
    • (PostgreSQL) -J _BCO_DB_TYPE_=POSTGRES
    For Oracle
    -J BCO_DB_HOST

    Specify the host name of the computer that is running the Oracle database instance.

    Example: -J BCO_DB_HOST=abc-qa1.xyz.com

    -J BCO_DB_PORT

    Specify the Oracle listener port on the computer. 

    Default value: 1521

    Example: -J BCO_DB_PORT=1521

    -J _ORACLE_HOME_

    Provide the path to the Oracle client home directory.

    Example: -J _ORACLE_HOME_=/opt/oracle/product/11.2.0/client_1

    -J _ORACLE_TNSNAMES_

    Provide the path to the SQL*Net configuration folder.

    Example: -J _ORACLE_TNSNAMES_=$ORACLE_HOME/network/admin

    -J _ORACLE_SID_

    Specify the Oracle alias name.

    Example: -J _ORACLE_SID_=ORA12C

    -J _ORACLE_SERVICENAME_

    Specify database service name or SID name.

    Example: -J _ORACLE_SERVICENAME_=ORA12C

    -J _HA_JDBC_URL_

    This is an advanced property. If you modify this property, you must also provide values for database host name and listener TCP port.

    Example: -J _HA_JDBC_URL_=jdbc:oracle:thin:@//[HOST][:PORT]/SERVICE

    -J BCO_DB_CREATE_SCHEMA

    Specify whether to create new database users and tablespaces (default) or use existing database users and tablespaces.

    Default value: true

    Example: -J BCO_DB_CREATE_SCHEMA=true

    If BCO_DB_CREATE_SCHEMA=true, specify the following values for the sysdba user:

    • -J BCO_DB_LOGIN: Name of the privileged user who creates the database schema. The default value is sys.
    • -J BCO_DB_PASSWORD: Password of the user. Provide the encrypted value generated using BCOEncoder.sh.

    • -J _PATH_: Tablespace datafiles path. Example: -J _PATH_=/u01/oradata/


    If you do not have a sysdba password and have manually set up the database users and tablespaces before starting installation, set the property to false.
    -J BCO_DB_ADVANCED

    Specify whether to use default or customized values for database name and partitioning.

    Default value: false

    When set to false, the default database values are used.

    When set to true, customize the values.

    1. Specify the database names.

      • Tablespaces:
        • Catalog Tablespace: -J _TBSCATALOG_=BCO
        • Catalog Indexes Tablespace: -J _CATALOGIDX_=BCO_IDX
        • Data Tablespace: -J _TBSDATA_=BCO_DATA
        • Data Indexes Tablespace: -J _DATAIDX_=BCO_DATA_IDX
      • Console Schema:
        • Console Role Name: -J _DBOWNROLE_=BCO_OWN_ROLE
        • Console User Name: -J _DBUSR_=BCO_OWN
        • Console Password: -J _SECDBPWD_=<Encrypted value generated using BCOEncoder.sh>
      • Reporting User:
        • Reporting Role Name: -J _DBREPROLE_=BCO_REP_ROLE
        • Reporting User Name: -J _DBREPUSR_=BCO_REP
        • Reporting Password: -J _SECDBREPPWD_=<Encrypted value generated using BCOEncoder.sh>

    2. Specify whether you want to create partitioned tables.
    -J IS_PARTITIONING_ENABLE
    Default value: true
    Example: -J IS_PARTITIONING_ENABLE=true

    For PostgreSQL
    -J BCO_DB_HOST

    Specify the host name of the computer that is running the PostgreSQL database instance.

    Example: -J BCO_DB_HOST=abc-qa1.xyz.com

    -J BCO_DB_PORT

    Specify the listener TCP port on the computer. 

    Default value: 5432

    Example: -J BCO_DB_PORT=5432

    -J _HA_JDBC_URL_

    This is an advanced property. If you modify this property, you must also provide values for database host name and listener TCP port.

    Example: -J _HA_JDBC_URL_=jdbc:postgresql://[HOST][:PORT]/DB_NAME

    -J BCO_DB_CREATE_SCHEMA

    Specify whether to create new database users and tablespaces (default) or use existing database users and tablespaces.

    default value: true

    Example: -J BCO_DB_CREATE_SCHEMA=true

    If BCO_DB_CREATE_SCHEMA=true, specify the following values for the sysdba user:

    • -J BCO_DB_LOGIN: Name of the privileged user who creates the database schema. The default value is sys.
    • -J BCO_DB_PASSWORD: Password of the user. Provide the encrypted value generated using BCOEncoder.sh.

    • -J _PATH_: Tablespace datafiles path. Example: -J _PATH_=/u01/oradata/

    If you do not have a sysdba password and have manually set up the database users and tablespaces before starting installation, set the property to false.
    -J BCO_DB_ADVANCED

    Specify whether to use default or customized values for database name and partitioning.

    Default value: false

    When set to false, the default database values are used.

    When set to true, customize the values.

    1. Specify the database names.

      • Tablespaces:
        • Catalog Tablespace: -J _TBSCATALOG_=BCO
        • Catalog Indexes Tablespace: -J _CATALOGIDX_=BCO_IDX
        • Data Tablespace: -J _TBSDATA_=BCO_DATA
        • Data Indexes Tablespace: -J _DATAIDX_=BCO_DATA_IDX
      • Console Schema:
        • Console Role Name: -J _DBOWNROLE_=BCO_OWN_ROLE
        • Console User Name: -J _DBUSR_=BCO_OWN
        • Console Password: -J _SECDBPWD_=<Encrypted value generated using BCOEncoder.sh>
      • Views Schema:
        • Views Role Name: -J _DBDASHROLE_=BCO_DASH_ROLE
        • Views User Name: -J _DBDASHUSR_=BCO_DASH
        • Views Password: -J _SECDBDASHPWD_=<Encrypted value created using BCOEncoder.sh>
      • Reporting User:
        • Reporting Role Name: -J _DBREPROLE_=BCO_REP_ROLE
        • Reporting User Name: -J _DBREPUSR_=BCO_REP
        • Reporting Password: -J _SECDBREPPWD_=<Encrypted value generated using BCOEncoder.sh>

    2. Specify whether you want to create partitioned tables.
    -J IS_PARTITIONING_ENABLE
    Default value: true
    For example: -J IS_PARTITIONING_ENABLE=true

    Remedy SSO and TrueSight Presentation Server details

    -J BCO_RSSO_HOSTNAME

    Specify the FQDN of the host computer on which you have installed Remedy SSO.

    -J BCO_RSSO_HOSTNAME=<RSSO_HOSTNAME>

    Example: -J BCO_RSSO_HOSTNAME=vw-abc-qa01.bmc.com

    -J BCO_RSSO_PORT

    Specify the port number to communicate with Remedy SSO.

    Default value: 8048

    Example: -J BCO_RSSO_PORT=8048

    -J BCO_TSPS_HOSTNAME

    Specify the FQDN of the host computer on which you have installed TrueSight Presentation Server.

    -J BCO_TSPS_HOSTNAME=<TSPS_HOSTNAME>

    Example: -J BCO_TSPS_HOSTNAME=vw-abc-qa01.bmc.com

    -J BCO_TSPS_PORT

    Specify the port number to communicate with the TrueSight Presentation Server.

    Default value: 8043

    Example: -J BCO_TSPS_PORT=8043

    Custom aging configuration
    -J AGING_CONF_SELECTION

    Configure the aging settings to specify how long you want to retain the historical data that is collected in the data warehouse. Type one of the following values:

    • DEFAULT: Configures the aging parameters using the default values
    • CUSTOM: Configures the aging parameters using the custom values
    • LEAVE_SELECTION: Performs no change on the values of the aging parameters

    Example: -J AGING_CONF_SELECTION=CUSTOM

    If -J AGING_CONF_SELECTION=CUSTOM, provide the following values:

    -J AGING_MONTH_SHORT_WKLD=720
    -J AGING_MONTH_MEDIUM_WKLD=1440
    -J AGING_MONTH_LONG_WKLD=2880

    -J AGING_DAY_SHORT_WKLD=360
    -J AGING_DAY_MEDIUM_WKLD=720
    -J AGING_DAY_LONG_WKLD=1440

    -J AGING_HOUR_SHORT_WKLD=180
    -J AGING_HOUR_MEDIUM_WKLD=360
    -J AGING_HOUR_LONG_WKLD=720

    -J AGING_DET_SHORT_WKLD=14
    -J AGING_DET_MEDIUM_WKLD=30
    -J AGING_DET_LONG_WKLD=60

    -J AGING_MONTH_SHORT_SYS=720
    -J AGING_MONTH_MEDIUM_SYS=1440
    -J AGING_MONTH_LONG_SYS=2880

    -J AGING_DAY_SHORT_SYS=180
    -J AGING_DAY_MEDIUM_SYS=360
    -J AGING_DAY_LONG_SYS=720

    -J AGING_HOUR_SHORT_SYS=90
    -J AGING_HOUR_MEDIUM_SYS=180
    -J AGING_HOUR_LONG_SYS=360

    -J AGING_DET_SHORT_SYS=14
    -J AGING_DET_MEDIUM_SYS=30
    -J AGING_DET_LONG_SYS=60

    On the additional computer only
    Connection with the first computer
    -J IS_REMOTE_COMPONENT

    Specify whether the additional computer connects to the first computer over a direct connection or over a remote connection.

    Default value: false

    Example: -J IS_REMOTE_COMPONENT=false

    When set to false, the additional computer connects to the first computer over a direct connection.

    When set to true, the additional computer connects to the first computer over a remote connection.

    For a direct connection, provide the following details:

    • -J URL_HOST: The address of the web server.

    • -J URL_PORT: The port number where the Application Server runs.

    For a remote connection, provide the following details:

    • -J URL_HOST: External data API server name

    • -J URL_PORT: The port number where the Application Server runs.

    • -J CUSTOM_CONNECTION_PROTOCOL: The protocol to be used.
    Proxy server connection
    -J IS_PROXY_CONFIGUREDSpecify whether you want to configure the proxy server.

    Default value: false

    Example: -J IS_PROXY_CONFIGURED=false

    -J REE_PROXY_HOSTSpecify the name of the proxy server host.

    -J REE_PROXY_HOST=<proxy_server_hostname>

    Example: -J REE_PROXY_HOST=vw-abc-dev01.bmc.com

    -J REE_PROXY_PORT

    Specify the port number to communicate with the proxy server.

    Example: -J REE_PROXY_PORT=8090

    -J REE_PROXY_USER

    Specify the proxy server user name.

    Example: -J REE_PROXY_USER=proxy_user

    -J REE_PROXY_SECPWD

    Specify the proxy server password.

    Example: -J REE_PROXY_SECPWD=proxy_user_password

    If using Oracle with the first computer
    -J _ORACLE_HOME_

    Provide the path to the Oracle client home directory.

    Example: -J _ORACLE_HOME_=/opt/oracle/product/11.2.0/client_1

    -J _ORACLE_SID_

    Specify the Oracle alias name.

    Example: -J _ORACLE_SID_=ORA12C

    Advanced properties for reconfiguration 
    -J IS_RECONFIGURATION_FLOW -J IS_REPAIR_FLOW

    To run the installer on the existing installation, choose one of the following modes. You can set only one of these properties to true as the installer can run only in one of these modes.

    • Reconfigure: Use the reconfigure mode to modify certain values that you had provided during installation, such as database connection or repository option, in the installed product.
      -J IS_RECONFIGURATION_FLOW
      Default value: false
    • Re-installation: Use the re-installation mode to re-install the Application Server or ETL Engine. BMC recommends that you back up your database before starting the re-installation.
      -J IS_REPAIR_FLOW
      Default value: false

  10. Open a shell prompt and navigate to the directory that contains the installation files (example: /BCO/Disk1).
  11. Launch the silent installer:

    ./setup.sh -i silent -DOPTIONS_FILE=<file path>/<options file name>.txt

    If the path contains spaces, enclose the path and options file name in quotation marks.
    Example: ./setup.sh -i silent -DOPTIONS_FILE="/opt/TSCO_temp/BCO/Disk1/silentInstallTemplates/BCO_FIRST_SERVER_TYPICAL_ORACLE.txt"

    After the installation is completed on the first computer, (i) the encrypted keys, (ii) CA keys and certificate, and (iii) client keys and certificate are generated in the respective folders of the $BCO_HOME/secure directory. 

  12. (On the first computer) If you are planning to install on an additional computer, create a compressed tar file of the $BCO_HOME/secure folder. Copy this tar file to the /tmp folder of the additional computer using the SCP command.

  13. 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

    The following table lists the TrueSight Capacity Optimization components and their corresponding 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.

  14. 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.

  15. 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 must install the Gateway Server.

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

Comments