Page tree
Skip to end of metadata
Go to start of metadata

This topic describes how you can install BMC TrueSight Capacity Optimization on your machine.

Before you begin

Before you begin installing the product, ensure that you have read through Planning topic.

If you are performing the installation as a non-root user, ensure that you have completed all the procedures explained in Setting up the installation environment.

Installation scenarios

You can install BMC TrueSight Capacity Optimization on a single machine or install individual components on separate machines.

Single machine installation

TaskComponents
Installing the Application Server and componentsInstall all components on the same machine

Multiple machine installation

TaskComponents
Installing the Application Server and componentsMinimum components required
BMC TrueSight Capacity Optimization 10.0.00
Database Schema 10.0.00
Application Server - Web Server 10.0.00
Installing additional machinesInstall one or more 1 component per machine
Application Server - Datahub 10.0.00 2
Application Server - Primary Scheduler 10.0.00
ETL Engine Server 10.0.00

1 It is recommended that you install front-end components (such as Web Server) and back-end components (such as Datahub and Primary Scheduler) on separate machines. If required, you can install individual back-end components on separate machines.
If you install Application Server components on multiple machines, you must provide each of them with access to a shared content repository. For more information, see Sharing the Content Repository directory.

2 You can install only one instance of the Datahub. An error will be displayed, if you attempt to install multiple instances.

Installation options

The following options are available for installing the product:

  • Install using the cpit user: Follow the steps described in Setting up the installation environment, then continue with Installing the Application Server and components. Some of the screens are available only when the installation is run using the root user.

  • Install using the root user: Follow the steps in the task below. 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.

    Note

    All steps marked with (tick) are available only if you run the installer using the root user.

Installing Application Server and components

Additional Information

A typical product install 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.

To install the first machine to run BMC TrueSight Capacity Optimization in a new setup, perform the following task:

  1. Unzip and extract the installation files: In the temporary directory that you created, unzip and extract the installation archive by using the following commands.

    Unzip command with example

    Unzip:
    gunzip TSCO_AppServer_<ProdVer>_<OSver>_<Arch>.tar.gz

    Example:
    gunzip TSCO_AppServer_ver10.0.00_RHEL6_x86-64.tar.gz

    Extract command with example

    Extract:
    tar -xvf TSCO_AppServer_<ProdVer>_<OSver>_<Arch>.tar

    Example:
    tar -xvf TSCO_AppServer_ver10.0.00_RHEL6_x86-64.tar

    Ensure that the directory permissions are preserved during extraction. This avoids any folder permission related errors when you are installing from a read-only location.

    BMC recommends you to retain the installation archive if you plan on installing additional machines to your deployment.

  2. Change the directory: After extracting the installation files, change to the directory where you extracted the install files. For instance BCO/Disk1.

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

    ScenarioCommand
    If the machine 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 machine 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 machine, or running X over a bash shell for Windows, type the command xhost +

    DISPLAY=<WorkstationName>:0.0
    export DISPLAY
  4. Run the installation: At the shell prompt, type ./setup.sh and press Enter.

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

    Avoid using 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 username (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 an additional machine, see Installing additional machines.)

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

      Typical Setup: Application Server
      ScreenDescription/options
      Web Server ConfigurationSelect a protocol to be used by the BMC 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 for transferring information. (Default Port: 8443)

        To set up encryption for HTTPS, BMC TrueSight Capacity Optimization uses the Apache Web server (installed by default) with a default SSL certificate.

        It is recommended that you replace this default SSL certificate with one that is trusted by a public or internal Certification Authority. For more details, see Managing SSL certificate on the default Apache front-end web server

      (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 some deployment configurations, you need to share the Content Repository directory.

        The Content Repository directory needs to be accessed in read/write mode by the Web Console and by the Primary Scheduler, and in read-only mode by the Web application component. Moreover, the BMC TrueSight Capacity Optimization user on each machine 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 directory

        In order to share the Content Repository between two Application Servers AS1 (running the Web application component) and AS2 (running the Data hub and Primary scheduler), perform the following procedure:

        1. Run the installer first on AS1 and then on AS2 (the order is important).
        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 on all servers a mount point that maps an external storage).
        3. Copy the Content Repository (both directory and sub-directories structure: see also System level administration) from either the AS1 or AS2 to the shared Content Repository location.
        4. Mount the Content Repository location from both AS1 or AS2.

        Due to Operating System limitations, only NFS mount is supported on Oracle Solaris 10.x.

        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.

      Click below to view the details required to use a PostgreSQL database for installing BMC 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 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
      Use SID (for Oracle only)
      Select either of the options to use the 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)
      Custom JDBC connection URL (Advanced)
      JDBC URLJDBC URL of the database through which it is referenced.
      Syntax for Oracle: jdbc:odbc:<data source name>
      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 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 BMC 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 BMC 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 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 BMC 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 Names for database users and tablespaces section, select Use defaults OR Allow me to customize names for advanced settings.
      Use defaults
      Select this option if you want to use the (default) database user names and tablespace names provided by BMC TrueSight Capacity Optimization.
      Allow me to customize names
      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 is stored.

      Console Role

      Role of the database owner.

      DB Owner

      Name of the database owner.

      DB Owner Password

      Password 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 Password

      Password of the database user used by the console for storing view configuration.

      Reports Role

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

      Reports User Name

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

      Reports Password

      Password of the database user that console uses to access data for Data Marts and Advanced Reporting public views.
      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. 

      Modify default 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 months for System and Business Driver Data. Defaults are 2 and 4 months.
      • Hour: Specify Hourly values that will be summarized in months for System and Business Driver Data. Defaults are 6 and 12 months.
      • Day: Specify Daily values that will be summarized in months for System and Business Driver Data. Defaults are 12 and 24 months.
      • Month: Specify Monthly values that will be summarized in months for System and Business Driver Data. Defaults are 60 and 120 months.

      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 gives you a fair idea about your configuration.


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

      Custom Setup

      Custom Setup
      ScreenDescription/Options
      Select the Components




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

      Install Database Schema 10.0.00

      Install and set up the database schema.

      Install Application Server 10.0.00

      If you install the Web Server before installing Datahub, an error is displayed on the web console home page. The Application Server machine 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 10.0.00: Install the web server.
        Note: An Apache Web Server is installed, even if a server already exists.
      • Install Datahub 10.0.00: Install the BMC TrueSight Capacity Optimization Datahub.
      • Install Primary Scheduler 10.0.00: Installs the Primary Scheduler.
      Install ETL Engine Server 10.0.00Install the ETL Engine Server component:
      • Install ETL Engine 10.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 BMC TrueSight Capacity Optimization Server: Select one of the options given below:

    FieldDescription
    Direct connectionThis machine is able to directly access the Database. Enter details for the Web Server Address, Protocol, Web Port.
    Remote connectionThis machine 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 to complete.

    For information on installer related error codes, see Working with error codes.

  12. Installation Summary: The Installation Summary screen tells you whether or not your installation was completed successfully. To view the installation log, click View Log on this screen, else proceed to Step 12.
  13. Click Done to exit the installer.

After you install the Application Server and components

After you are done with installing, you may want to add additional machines to your deployment. For more information, see Installing additional machines.

Where to go from here

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

Related topics

Verifying the installation

Installing additional machines

Installing silently

Working with installation error codes