Performing the Application Server components upgrade

Complete the procedures in this topic to upgrade the Application Server components by running the installation program from a wizard-based UI. 



  • When you upgrade the product, the installation wizard follows the path of the original installation. For example, if a typical installation was used for the original, Typical is chosen by default during the upgrade.
  • Any custom parameters configured during the original installation are retained during the upgrade.
  • Because you cannot change the installation directory during an upgrade, this option does not appear in the installation wizard during an upgrade.

Before you begin

  • Ensure that you are logged as the TrueSight Capacity Optimization system or root user to the host on which you are performing the upgrade.

    Advantage of running the installer as root

    Root user access is required only to start the installer. After it is started, you can also share the repository by selecting the Shared Repository option. You can specify an existing user (for instance, cpit) instead of using the installer to create a new one. However, if you do not run the installer as root, the Shared Repository option is unavailable.

  • If you are connecting to the host from a remote workstation by using an X server, ensure that the X server is running on your workstation and that the host can connect to the X server.
  • Ensure that you review the topic on Preparing to upgrade the Application Server.
  • Ensure that you create all your custom views in the TrueSight console before you upgrade to TrueSight Capacity Optimization 11.0. For more information, see Re-creating custom views.

To change from a local to a shared repository after upgrade

If you are using a local repository and want to use a shared repository after the upgrade, perform the following steps:

  1. Take a backup of your existing repository.
  2. Perform the upgrade as a root user, and select Shared Repository on the Shared Repository Configuration page.
  3. Copy the backup taken before starting the upgrade to $BCO_HOME/repository.

To upgrade the Application Server components

Steps marked with (tick) are available only if you run the upgrade using the root user.

  1. Create a temporary folder for the TrueSight Capacity Optimization installation files. For instance, /opt/cpitinstall.
    TrueSight Capacity Optimization binaries are copied from the $TEMPBASE to the final destination directory, which is the directory for the earlier TrueSight Capacity Optimization installation.
  2. Define the TrueSight Capacity Optimization system user as the owner of the temporary folder created in step 1.


    This step is not required if the upgrade is performed using the root user.

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

    Command typeCommand syntaxExample
    Unzipgunzip TSCO_AppServer_<ProdVer>_<OSver>_<arch>.tar.gzgunzip TSCO_AppServer_ver11.0.00_Linux.tar.gz
    Extracttar -xvf TSCO_AppServer_<ProdVer>_<OSver>_<arch>.tartar -xvf TSCO_AppServer_ver11.0.00_Linux.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.

  5. Change the directory: After extracting the installation files, change to the directory where you extracted the install files and then navigate to BCO/Disk1.

  6. Set the DISPLAY environment: Set the DISPLAY environment correctly to enable the Installer wizard to launch.

    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

    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 +

    export DISPLAY
  7. Run the installation: At the shell prompt, type ./ and press Enter.

  8. Welcome screen and EULA: In the product installation welcome screen, click Next. Agree to the End User License Agreement (EULA), and click Next.

  9. Directory Selection: On the Directory Selection page, specify the installation directory path where TrueSight Capacity Optimization is currently installed or click Browse to select the directory on your system, and then click Next.

    Additional information

    If the $BCO_HOME variable is set, the directory mentioned is displayed by default.

  10. (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 upgrade, and click Next.
  11. On the page that indicates that existing installation detected, verify that the required version for upgrade is selected and click Next.
  12. On the page that lists the components that are being upgraded, verify that the list is accurate and click Next.


    If you have customized aging configuration and want to use the customized configuration, select Continue to use existing aging configuration. If you want to override any customized configuration and restore it to the default values select Reset aging configuration to default. If you want to modify your customized configuration, select Review aging configuration.

  13. Web Server Configuration: Select a protocol to be used by the TrueSight Capacity Optimization console, and click Next. You can configure HTTPS during upgrade even if the previous installation used HTTP.
    • HTTP (Port 8000)
    • HTTPs (Port 8443)

    The Apache web server installed by TrueSight Capacity Optimization is used to set up the encryption for HTTPS. Any customization performed to secure the 9.0 web server or to use a trusted certificate is lost. You must backup all customized Apache HTTPD configuration files before proceeding with the upgrade, and merge the changes after the upgrade, if required. For details on the configuring Apache to use HTTPS, see Configuring a front-end web server.

  14. Remedy Single Sign-On (Remedy SSO) & TrueSight Presentation Server (TSPS) Configuration: Enter the following details
    • Enter the following details to configure Remedy SSO for TrueSight Capacity Optimization console:

      • Remedy SSO Host - Type the 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 is 448).
    • Enter the following details to configure TrueSight Presentation Server for TrueSight Capacity Optimization console:
      • TSPS Host - Type the 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 is 443).

  15. (tick) Shared Repository Configuration: Select either of the configuration options, type the details as required, and click Next.

    If you do not run the TrueSight Capacity Optimization installer as root, the Shared Repository option is unavailable.

    • 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 connect to
  16. On the Database Information - Select Database type page, verify that required type of database is selected.

  17. On the Database Information - Connection details page, verify the following details for database connection and click Next:

    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
    JDBC URLJDBC URL of the database through which it is referenced.
    Syntax for PostgreSQL:

  18. If there are custom views in your environment that are created in the TrueSight Capacity Optimization console, the Capacity views in TrueSight Capacity Optimization page is displayed. Review the capacity views and confirm that the required custom views are created in the TrueSight console. Type CONFIRM in the box and click Next.


    If you do not create required custom views in the TrueSight console before upgrade, your content will be lost after you upgrade to TrueSight Capacity Optimization 11.0. For more information about creating custom views in the TrueSight console, see Re-creating custom views.

  19. On the Data Warehouse Aging Configuration page, select the required option for the aging configuration and click Next.

  20. On the Installation Preview page, verify all the upgrade settings, and click Install.

    The installation program upgrades TrueSight Capacity Optimization. A single computer takes up to 45 minutes for upgrade.

  21. Click Done.

Where to go from here

After performing the upgrade, you must verify the upgrade and configure TrueSight Capacity Optimization.

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