Performing the Application Server installation

This topic describes how you can install Application Server components on your computer by running the installation program from a wizard-based UI. During the installation process, you can choose whether to follow a typical or custom installation path. This topic provides the details for both options.

This topic provides the following information:

Space requirements

A typical installation requires approximately 3 GB of available storage. The Data Warehouse aging configuration can be specified during installation and will impact the disk space required on the database server.

Before you begin

Installation options

The following options are available for installing the Application Server components:

  • Install using the root user:  You can use any existing user or create a new user for the product during installation. You can also enter the details required for setting up a shared repository.

    • If you do not have a sysdba password, follow the steps described in Preparing to install without a sysdba password, and then continue with Installing the Application Server and components

    • If you have a sysdba password, continue with Installing the Application Server and components.

      Note

      • When installing as a root user, the installation wizard displays the option to set the name of the new user. If the user exists, that user is associated to a specific OS group (cpit - gid: 87654321). If this OS group does not exist, this OS group will be created. If the installer is executed by a user of the OS group, no changes will be applied to that user and associated groups.
      • BMC strongly recommends that you use the root user to install TrueSight Capacity Optimization. Several steps in the installation process (marked with (tick) in the procedure below) are available only if you run the installer using the root user.
  • Install using the non-root user: The default non-root user is cpit. 

To install the Application server components

  1. Unzip and extract the installation files: Create a temporary directory (For example, TSCO_temp) and unzip and extract the installation archive in this directory by using the following commands:

    Unzip command with exampleExtract command with example

    Unzip:
    gunzip TSCO_AppServer_<ProdVer>_<OS>.tar.gz

    Example:
    gunzip TSCO_AppServer_ver11.0.00_Linux.tar.gz

    Extract:
    tar -xvf TSCO_AppServer_<ProdVer>_<OS>.tar

    Example:
    tar -xvf TSCO_AppServer_ver11.0.00_Linux.tar

    Notes

    • The temporary directory must be different from the installation directory.

    • Ensure that the directory permissions are preserved during extraction to avoid any folder permission related errors when you install from a read-only location.

    • Retain the installation archive if you plan to install additional machines.

  2. Navigate to the directory: Navigate to the directory where you extracted the installation files. For example, TSCO_temp/BCO/Disk1.

  3. Set the DISPLAY environment: Set the DISPLAY environment correctly to enable the Installer UI to launch.

    ScenarioCommand
    If the computer has a local graphical console: Set the DISPLAY environment variable to start the installer UI locally.
    DISPLAY=<Local IP Address>:0.0
    export DISPLAY

    If the computer does not have a local graphical console: Set the DISPLAY environment variable to export to an XServer on a different workstation.

    Note: On the workstation used to display the UI, provide access grants to every incoming X window. If the workstation is a Linux computer, or running X over a bash shell for Windows, type the command xhost +

    DISPLAY=<WorkstationName>:0.0
    export DISPLAY

    Note

    For launching the installer UI for Linux from the remote a Windows computer, see Forwarding using Xming and Putty .

  4. Run the installation: 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 the installation that will help debug installation issues.

  5. Welcome screen and EULA: At the product installation Welcome screen, click Next. Agree to the End User License Agreement (EULA), and click Next again.

  6. Directory Selection: In the Directory Selection screen, type the destination directory (default: /opt/bmc/BCO) to which you want to install the product, or click Browse to select a directory on your system, and click Next.

    Do not use the home directory of the user as the installation directory.
  7. (tick) Enter a username: In the BMC TrueSight Capacity Optimization User screen, provide a user name (new or existing user) for running the product after the installation, and click Next.

    The installer will not proceed with the default entry, root, in the username box.

  8. Select the installation step: In the Installation Step screen, select Install the first machine and click Next.

    (To install the Application Server components on additional computers, see Installing Application Server components on additional computers.)

  9. Select the type of installation: In the Select Install Setup Type screen, select any one of the following options and click Next.
    • Typical Setup: Application Server: Install all Application Server components, including ETL Engine for troubleshooting purposes.
    • Custom Setup: Select the check box corresponding to the components you want to install.


      Typical Setup: Application Server
      ScreenDescription/options
      Web Server Configuration
      Select a protocol to be used by the TrueSight Capacity Optimization console, and click Next.
      • HTTP - Select to use the HTTP protocol for transferring information. (Default Port: 8000)
      • HTTPS - Select to use the HTTP protocol over SSL/TLS for transferring information. (Default Port: 8443)


      info Info: The Apache Web server installed by TrueSight Capacity Optimization will be used to set up the encryption for HTTPS.

      Remedy Single Sign-On (Remedy SSO) & TrueSight Presentation Server (TSPS) Configuration

      Enter the following details to configure Remedy SSO for TrueSight Capacity Optimization console:

      • Remedy SSO Host - Type the fully qualified domain name of the server on which Remedy SSO is hosted.

        If you have two instances of Remedy SSO running, then use the same Remedy SSO server that is configured with the TrueSight Presentation Server.

      • Remedy SSO Port - Type the port to be used for connecting with Remedy SSO server (default port: 8048).

      Enter the following details to configure TrueSight Presentation Server for TrueSight Capacity Optimization console:

      • TSPS Host - Type the fully qualified domain name of the server on which TrueSight Presentation Server is hosted.
      • TSPS Port - Type the port to be used for connecting with TrueSight Presentation Server (default port: 8043).
      (tick) Shared Repository ConfigurationSelect either of the configuration options, type the details as required, and click Next.
      • Local Repository: Select this option if you have a single Application Server.
      • Shared Repository:

        In an environment that has multiple Application Servers or a distributed Application Server, you must share the Content Repository directory.

        The Content Repository directory needs to be accessed in read/write mode by the web console and Primary Scheduler, and in read-only mode by the web application component. In addition, the TrueSight Capacity Optimization user on each computer must have permissions to read, write, and update files in the Content Repository. For users to have the required permissions, the UID of the cpit users must be same across all Application Servers in an environment.

        To share the Content Repository between two Application Servers AS1 that is running the web application component, and AS2 that is running the Data hub and Primary scheduler, do the following:

        1. Run the installer first on AS1 and then on AS2.
        2. Share the Content Repository that has been created by the installer on each Application Server via a shared file system (that is, NFS, by configuring a mount point on all servers, that maps an external storage).
        3. Copy the Content Repository both directory and subdirectories structure, from either AS1 or the AS2 to the shared Content Repository location. For more information, see System-level administration overview.
        4. Mount the Content Repository location from both AS1 and AS2.

        Select any one of the following options, and enter the required information:

        • NFS: If you are mounting the repository folder from a network share through Network File Sharing.

          • Server: Name of the NFS server. For example, server1
          • Path: Address of the NFS server.
            For example, nfs://server1/share/path
        • CIFS: If you are mounting the repository folder from a network share through a Common Internet File System.
          • Shared URL: Address of the shared location in URL format.
          • User: Name of the user.
          • Password: User password.
          • Domain: Name of the domain to which you want to connect.
      Database Information - Select Database type

      Select the Database you want to use for installation:

      • Oracle - Select to use the Oracle Database.

      Expand the following section to view the details required to use a PostgreSQL database for installing TrueSight Capacity Optimization.


       Click here

      Database Information - Select Database type

      Select the Database you want to use for installation:

      • PostgreSQL - Select to use the PostgreSQL Database. Select one of the following options for configuring the database connection.
      Database Information - Connection details

      Enter information for connecting to and configuring the database.

      Your database administrator should set up a database schema that will used by BMC TrueSight Capacity Optimization. Use the information you filled in the installation worksheet.

      Select Database connection properties OR Custom JDBC connection URL (Advanced) for advanced settings.
      PropertyDescription
      Database connection properties
      Database Host NameName of the database host where the database schema is stored.
      Listener PortListener port number for the database. (Default: 5432)
      Custom JDBC connection URL (Advanced)
      JDBC URLJDBC URL of the database through which it is referenced.
      Syntax for PostgreSQL:
      jdbc:postgresql://hostname:port/database_name
      Database Information - Schema creation

      Select Standard OR Advanced for creating the database schema.

       PropertyDescription
       Privileged User Name (superuser)
      Name of the user setting up the database schema. This is either sys or another user that your database administrator has created for the purpose.
       Privileged User PasswordPassword of the user that is setting up the database schema.
       Tablespaces parent directory

      Specify a fully qualified path for the datafile stored on the BMC TrueSight Capacity Optimization database server. For example, /data1/postgresql

      Database Information - Customize names

      This step will be displayed only if you select Advanced from the Database Information - Schema creation screen.
      PropertyDescription

      Console Role

      Role of the database owner.
      Console User NameUser Name of the database owner.
      Console PasswordPassword of the database owner.

      Views Role

      The database role used by the console for storing view configuration.

      Views User Name

      Name of the database user used by the console for storing view configuration.
      Views PasswordPassword of the database user used by the console for storing view configuration.
      Reporting RoleName of the database role that the console uses to access data for Data Marts and Advanced Reporting public views.
      Reporting User NameName of the database user that console uses to access data for Data Marts and Advanced Reporting public views.
      Reporting PasswordPassword of the database user that console uses to access data for Data Marts and Advanced Reporting public views.
      Catalog TablespaceName of the tablespace for the database Catalog.
      Catalog Indexes Tablespace
      Name of the catalog index.

      Data Tablespace

      Name of the database tablespace where all the data is stored.

      Data Indexes Tablespace

      Name of the data index.

      Views Tablespace

      Name of the tablespace where all database views is stored.
      Database information - Advanced optionsThis step will be displayed only if you select Advanced from the Database Information - Schema creation screen.
       

      Select one of the following options if the database instance you have selected has partitioning enabled:

      Yes - Create partitioned tables

      No - Do not use partitioned tables. This option might lead to a degradation in performance.


      If you want to use Oracle database as source for an ETL, ensure that you configure the Oracle database and follow Using Oracle database as source for an ETL.

      Database Information - Connection details

      Enter information for connecting to and configuring the database.

      Your database administrator should set up a database schema that will used by TrueSight Capacity Optimization. Use the information you supplied in the installation worksheet.

      Select Database connection properties OR LDAP Database connection properties (Advanced) or Custom JDBC connection URL (Advanced) for advanced settings.
      PropertyDescription
      Database connection properties
      Use SID (for Oracle only)
      System ID or service name. Specify the details for the database instance that your database administrator created.
      Use Service Name (for Oracle only)
      Database Host NameName of the database host where the database schema is stored.
      Listener PortListener port number for the database. (Default: 1521)
      LDAP Database connection properties (Advanced)
      LDAP Host Name

      Host name or IP address of the LDAP server.

      Note: Only LDAP servers that allow anonymous bind connections are supported.
      LDAP PortPort that should be used for connecting to the LDAP server.
      Service NameService name for the database instance.
      LDAP Context

      Node from which the database instance search is initiated.

      Custom JDBC connection URL (Advanced)
      JDBC URLJDBC URL of the database through which it is referenced.
      Syntaxfor Oracle: jdbc:odbc:<data source name>
      Database Information - Schema creation













      Enter information for creating schema and configuring the database.
      From the Creation of database users and tablespaces section, select Installer shall create Database users and tablespaces OR Database users and tablespaces have already been created externally for advanced settings.
      PropertyDescription
      Installer shall create Database users and tablespaces
      Privileged User Name
      Name of the user setting up the database schema. This name is either sys or another user that your database administrator has created for the purpose.
      Privileged User PasswordPassword of the user that is setting up the database schema.
      Tablespaces parent directory

      Path where the datafile is saved by your database administrator.

      Some of the common ways to specify the datafile path are:

      • Specify an ASM (Automatic Storage Management) path. For example, +ORATBS1/bcoasm/datafile.
      • Specify a Fully qualified path for the datafile stored on the TrueSight Capacity Optimization database server. For example, /apps/oracle/product/SID.
      • In a non-ASM environment, this path must exist on the database. Typically, the path should be changed from the default /opt/bmc/BCO path to a directory on the database side.

      Testing database connectivity
      Use sqlplus from the command line, and connect to the TrueSight Capacity Optimization  database as the sysuser.

      export ORACLE_HOME=[Oracle Client Home]
      export ORACLE_SID=[Oracle Alias]
      $ORACLE_HOME/bin/sqlplus sys@$ORACLE_SID AS SYSDBA

      Database users and tablespaces have already been created externally
      Select this option if you have already created database users and tablespaces for your database externally (manually).
      Testing database connectivity
      Use sqlplus from the command line, and connect to the TrueSight Capacity Optimization database as the [DB Owner]user.

      export ORACLE_HOME=[Oracle Client Home]
      export ORACLE_SID=[Oracle Alias]
      export DBUSR=[DB Owner]
      $ORACLE_HOME/bin/sqlplus $DBUSR@$ORACLE_SID

      From the Please select a Database configuration type section, select Standard or Advanced for advanced settings.
      Standard
      Select this option if you want to use the default values for database user names and partitioning options provided by TrueSight Capacity Optimization.
      Advanced
      PropertyDescription

      TNS Names File Location

      Location of tnsnames.ora, a configuration file that defines database addresses for establishing connections. It is normally located in
      /<Oracle Home>/network/admin.
      Catalog TablespaceName of the tablespace for the database Catalog.
      Catalog IndexName of the catalog index.

      Data Tablespace

      Name of the database tablespace where all the data is stored.

      Data Index

      Name of the data index.

      Views Tablespace

      Name of the tablespace where all database views are stored.

      DB Owner

      Name of the database owner.

      DB Owner Password

      Password of the database owner.

      Console Role

      Role of the database owner.

      Views Role

      Database role used by the console for storing view configuration.

      Reporting Role

      Name of the database role that the console uses to access data for Data Marts and Advanced Reporting public views.

      Reporting User Name

      Name of the database user that console uses to access data for Data Marts and Advanced Reporting public views.
      Reporting PasswordPassword of the database user that console uses to access data for Data Marts and Advanced Reporting public views.
      Database Information - Advanced optionsThis screen is displayed when the database instance that you are using has partitioning option enabled. Select either of the options and click Next.
      • Yes, create partitioned tables: This is a recommended option.

      • No, do not use partitioned tables: This might lead to a performance degradation.
      Data Warehouse Aging Configuration


      Enter the following information and click Next.
      PropertyDescription
      Use default aging configurationUse the default setting for aging configuration, which is approximately 280 GB space for the database considering 5000 systems. This configuration allows you to import historical data from the last two months. 

      Specify custom aging configuration

      Set the following Data Warehouse aging parameters for System Data and Business Driver Data. This aging configuration will affect the amount of storage used by the Data Warehouse.

      • Detail: Specify Detail values that will be summarized in days or weeks or months or years for System and Business Driver Data.
      • Hour: Specify Hourly values that will be summarized in days or weeks or months or years for System and Business Driver Data.
      • Day: Specify Daily values that will be summarized in days or weeks or months years for System and Business Driver Data.
      • Month: Specify Monthly values that will be summarized in days or weeks or months or years for System and Business Driver Data.
       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


      Note: The summary field below the parameter entry boxes will be updated with the actual total amount of storage that will be used by the DWH for 5000 systems, based on your custom values. This information provides a good overview of your configuration.



      To finish a Typical Install on the first computer, go to Step 10.

      Custom setup

      Custom setup
      ScreenDescription/Options
      Select the Components




      Select any or all of the following components to install:
      ComponentDescription
      TrueSight Capacity Optimization 11.0.00 InstallationSelects all components. If you select this option, the installation is similar to a Typical install.

      Install Database Schema 11.0.00

      Install and set up the database schema.

      Note

      By default, the Database Schema will be installed when you install the Application Server. You cannot clear the option selected for installing the Database Schema.

      Install Application Server 11.0.00

      If you install the Web Server before installing Datahub, an error is displayed on the web console home page.
      The Application Server computer will stay in a suspended state until the Datahub is installed and registered in the database.

      Install the following Application Server components:
      • Install Web Server 11.0.00: Install the web server.
        Note: An Apache Web Server is installed, even if a server already exists.
      • Install Datahub 11.0.00: Install the TrueSight Capacity Optimization Datahub.
      • Install Primary Scheduler 11.0.00: Installs the Primary Scheduler.
      Install ETL Engine Server 11.0.00Install the ETL Engine Server component:
      • Install ETL Engine 11.0.00: Install the ETL Engine.
      Web Server ConfigurationThe task from this screen onwards (including this screen) is the same as that for performing a Typical Setup.

  10. Connect with existing TrueSight Capacity Optimization Server: Select one of the options given below:

    FieldDescription
    Direct connectionThis computer is able to directly access the Database. Enter details for the Web Server Address, Protocol, Web Port.
    Remote connectionThis computer is located on a remote network with an unstable or slow connection, and only has HTTP visibility to the DataHub.


  11. Installation Preview: In the Installation Preview screen, verify all the installation settings, and click Install.
    The installation can take up to 15 minutes. 
    The Installation Summary screen provides information about whether the installation was completed successfully. You can click View Log from this screen to see more details. Otherwise, proceed to step 12.

  12. Click Done to exit the installer.
  13. (Optional) If required, add additional computers to your deployment. For more information, see Installing Application Server components on additional computers.

    Best Practice

    To block the upload of malicious files to the Application Server file system, install antivirus software on the systems that host the Application Server.

Troubleshooting

For information about installer-related error codes, see Working with error codes.

Where to go from here

Before you can start using the product, you must verify the installation and configure TrueSight Capacity Optimization.

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

Comments