Child pages
    • Upgrading Application server and components
    Skip to end of metadata
    Go to start of metadata

    This topic describes how to upgrade the Application server and components from versions 9.5.x or 10.0.x to version 10.3.

    Before you begin

    Perform the following tasks:

    • Ensure that you are logged in as the BMC 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 launch the installer. After it is launched, the choice is yours on whether or not you want to share the repository by selecting the Shared Repository option. You can specify an already existing user (for instance, cpit) instead of using the installer to create a new one. However, if you do not launch 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.

    Using a shared repository after upgrade

    If you are using a local repository, and want to use a shared repository after upgrade, follow the procedure given below:

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

    To upgrade BMC TrueSight Capacity Optimization

    Tip

    You can also use the procedure outlined in Upgrading silently for performing the upgrade.

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

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

      Note

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

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

      Unzip/Extract commands with examples

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

      Example:
      gunzip TSCO_AppServer_ver10.3.00_Linux.tar.gz

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

      Example:
      tar -xvf TSCO_AppServer_ver10.3.00_Linux.tar

      Note

      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 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
    7. Run the installation: At the shell prompt, type ./setup.sh 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: In the Directory Selection screen, specify the installation directory path where BMC TrueSight Capacity Optimization is currently installed, or click Browse to select the directory on your system, and click Next.

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


    10. On the page that lists the components that are being upgraded, verify that the list is accurate, and then click Next.

      Important

      If you have a customized aging configuration, or if you are not sure of the changes in the aging configuration, on the Data Warehouse Aging Configuration page of the installer, use Modify default aging configuration to review the aging configuration. If you select Use default aging configuration, the upgrade procedure overrides any customized configuration and restores the configuration to the default values.

    11. On the Oracle Database Information page, perform one of the following procedures:

      If you are upgrading the First/Primary Application ServerIf you are upgrading components other than the Primary Application Server
      1. Verify the following information:
        • Oracle Client Home: Verify the local directory path of the Oracle client.
        • Oracle Alias: Verify the alias for the local Oracle client (TNS).
        • Oracle Service Name: Verify the name of the global Oracle SID.
        • Database Host Name: Verify the host name of your Oracle database host.
        • Listener Port: Verify the Oracle Listener port number.
      2. If the installation program is migrating the database users and tablespaces, select Migrate the Database Users and Tablespaces, and then verify the following information, and update if required:
        • User Name: Verify the name of the Oracle user that is setting up the database schema. This is either sys or another user that your Oracle database administrator has created for this purpose.
        • Password: Type the password of the Oracle user that is setting up the database schema.
        • Datafile Path: Verify the path of the Oracle datafile.

      3. If the installation program is verifying existing database users and tablespaces, select Verify Database Users and Tablespaces.
      4. If you are upgrading and migrating database users and tablespaces, or verifying existing database users and tablespaces, verify the following information:
        • TNS Names File Location: Verify the location of tnsnames.ora.
        • Catalog Tablespace: Verify the name of the catalog tablespace.
        • Catalog Index: Verify the name of the catalog index.
        • Data Tablespace: Verify the name of the data tablespace.
        • Data Index: Verify the name of the data index.
        • Reporting Role: Verify the Oracle role for reporting.
        • DB Owner: Type the name of the BMC TrueSight Capacity Optimization database owner.
        • DB Owner Password: Type the password of the BMC TrueSight Capacity Optimization database owner.
        • Views User Name: Verify the name of the user that the BMC TrueSight Capacity Optimization Dashboard JSP engine uses to access the database.
        • Views Password: Verify the password of the user that the BMC TrueSight Capacity Optimization Dashboard JSP engine uses to access the database.
        • Reports User Name: Verify the name of the user that the BMC TrueSight Capacity Optimization Reports uses to access the database. The default name is CPIT_REP.

        • Reports Password: Verify the password of the user that the BMC TrueSight Capacity Optimization Reports uses to access the database. The default password is CPIT_REP.

          Note

          If you are upgrading to BMC TrueSight Capacity Optimization 10.3 and you have customized this password, you must verify the password. For the default user name CPIT_REP, the password is CPIT_REP.

      5. If you are upgrading BMC TrueSight Capacity Optimization in a high-availability configuration, select High Availability Information, and then type the JDBC URL – the URL for Oracle RAC Java database connectivity.
      6. Click Next.
      1. Verify the following information:
        • Oracle Client Home: Verify the local directory path of the Oracle client.
        • Oracle Alias: Verify the alias for the local Oracle client (TNS).
      2. Click Next.
      3. On the Connect with existing BMC TrueSight Capacity Optimization Server page, perform one of the following actions:
        • If the server you are upgrading connects to an existing BMC TrueSight Capacity Optimization application server over a LAN, select LAN Connection, and then verify or type the following information:
          • Web Server Address: Type the address of the web server on the existing BMC TrueSight Capacity Optimization server.
          • Web Port: Verify the Apache web server consult port on the existing BMC TrueSight Capacity Optimization server.
        • If the server you are upgrading connects to an existing BMC TrueSight Capacity Optimization application server over a WAN, select WAN Connection, and then verify or type the following actions:
          • DataHub Server Address: Type the address of the DataHub on the existing BMC TrueSight Capacity Optimization server.
          • DataHub Port: Verify the port of the DataHub on the existing BMC TrueSight Capacity Optimization server.
      4. Click Next.
    12. Web Server Configuration: Select a protocol to be used by the BMC TrueSight Capacity Optimization console, and click Next. You can configure HTTPS during upgrade even if the previous installation was using HTTP.
      1. HTTP (Port 8000)
      2. HTTPS (Port 8443)

        The Apache Web server installed by BMC TrueSight Capacity Optimization will be used to set up the encryption for HTTPS. Any customization performed to secure the current installation of Web Server or to use a trusted certificate will be lost. You must backup any customized Apache HTTPD configuration file 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 an external front-end web server.

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

      If you do not launch the BMC 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:

        For an environment with multiple Application Server, the Content Repository directory should be shared.

        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

        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 (this 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 subdirectories structure: see also System level administration) from either AS1 or AS2 to the shared Content Repository location.
        4. Mount the Content Repository location from both AS1 and AS2.

        Note

        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 connect to.
    14. JMS over HTTPS for Remote ETLs on WAN: Refer to KA351188 that describes how to secure the JMS communication layer between Datahub and all ETLs and especially for data exchange of Remote ETL engines. In version 10.0, the data API used by Remote ETLs does not use JMS to transmit data; this channel is now used only for control purposes (commands transmission and status acknowledgements) and the default configuration is to not encrypt it with the standard TCP communication. Concepts in the KA article are still valid and if required they must be performed again after the upgrade (any previous customization will be available only in the datahub backup folder).
    15. Installation Preview: On the Installation Preview page, verify the information displayed, and click Install.
      The installation program upgrades BMC TrueSight Capacity Optimization.

    16. Click Done to exit the upgrade.

     

    Error rendering macro 'show-if' : Failed to render Visibility macro due to: Invalid group name(s): @bmc-employees

    Where to go from here

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

    3 Comments

    1.  

      1.  

    2.