Upgrading the Application Server and the ETL Engine using the wizard
Where you are in the Upgrade process
Complete the procedures in this topic to upgrade the Application Server and ETL Engine 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. As you cannot change the installation directory during an upgrade, this option does not appear in the installation wizard during an upgrade.
To upgrade the Application Server and ETL Engine
Log in to the host computer on which you want to upgrade the Application Server and ETL Engine, and create a temporary directory. Example: TSCO_temp.
You can upgrade the product as a root or a non-root user. BMC recommends that you upgrade it as a root user, because some of the installation steps are available only to the root user.
- Extract the downloaded files to the temporary directory. Ensure that the temporary directory is different from the existing installation directory to avoid any file sharing conflict.
- At the shell prompt, change to the directory where you extracted the installation files (example: TSCO_temp) and navigate to /BCO/Disk1.
Set the DISPLAY environment variable to ensure that the wizard-based installer launches the screens appropriately:
DISPLAY=<IP address of the host computer>:0.0 export DISPLAY
Run the installer. At the shell prompt, type ./setup.sh and press Enter.
- Review the welcome page, and click Next.
- Read the license agreement, agree to the terms, and click Next.
(Displayed to a root user) Provide the name of the user (new or existing) for running TrueSight Capacity Optimization after installation, and click Next. The default user name is cpit.
This user can be a root or a non-root user. BMC recommends that you run the application as a non-root user. If you want to run the application as a root user, ensure that the specified user name is not root.
- (Displayed to a root user) Confirm the user specification, and click Next.
- Review the existing installation detected, verify that the required version for upgrade is selected, and click Next.
- Review the list of components that are being upgraded, and click Next.
- (On the first computer) Specify the following:
Select the protocol, and click Next. The port numbers are 8443 for HTTPS and 8000 for HTTP. You can choose to configure HTTPS though your previous installation used HTTP.
- Review the following details to connect to Remedy SSO and the TrueSight Presentation Server, and click Next.
- The FQDN of the host computer on which you have installed Remedy SSO and the port number to communicate with it. If two instances of Remedy SSO are running, use the Remedy SSO server that is configured with the TrueSight Presentation Server. The default port number for Remedy SSO is 448 (Windows) or 8048 (Linux).
- The FQDN of the host computer on which you have installed TrueSight Presentation Server and the port number to communicate with it. The default port number for TrueSight Presentation Server is 443 (Windows) or 8043 (Linux).
- (Displayed to a root user) Select one of the configuration options, type the details, and click Next.
- Local Repository: Select if you have a single Application Server.
- Shared Repository: Select if you have distributed or multiple Application Servers. All the Application Servers must use the same shared repository.
Depending on the shared repository, specify the following details:- For Network File Sharing (NFS), specify the name of the NFS server and a path to the shared repository. Example: nfs://server1/share/path
- For Common Internet File System (CIFS), specify the address of the shared URL, the username and password to access the directory, and the name of the domain.
Review the database information, and click Next. Verify that the database type that is used for the previous installation is selected.
Based on your selection, the applicable configuration pages are displayed.
- (Oracle only) Review the following Oracle database connection details and modify, if necessary.
- Verify the path to the Oracle client home directory and SQL*Net configuration folder.
Ensure that you use a supported version of the Oracle client. If you use an unsupported version, the upgrade fails with a validation error. - Select one of the following options to connect to the database, and click Next:
- For Database connection, provide the following details:
- Specify whether to use service name or database SID, and type the value.
- Host name of the computer that is running the Oracle database instance.
- Oracle listener port on the computer. The default port is 1521.
- Oracle alias name.
- For LDAP Database connection (advanced), provide the following details:
- Host name or IP address of the computer that is running LDAP. Only LDAP servers that allow anonymous bind connections are supported.
- Port number through which the LDAP server communicates.
- Service name of the Oracle server.
- Node from which the database instance search is initiated.
- For Custom JDBC connection URL (advanced), provide the JDBC URL for referencing the database. The syntax is jdbc:odbc:<data source name>.
- For Database connection, provide the following details:
- Verify the path to the Oracle client home directory and SQL*Net configuration folder.
- (PostgreSQL only) Review the following PostgreSQL database connection details and modify, if necessary. Select one of the following options to connect to the database, and click Next:
- For Database connection, provide the following details:
- The name of the database host where the PostgreSQL database schema is stored.
- The listener port number for the database. The default port is 5432.
- For Custom JDBC connection URL (advanced), provide the JDBC URL for referencing the database. The syntax for PostgreSQL is jdbc:postgresql://hostname:port/database_name.
- For Database connection, provide the following details:
- Review the aging configuration and select one of the following settings:
- Continue to use existing aging configuration if you have customized aging configuration and continue to use the customized configuration.
- Reset aging configuration to default to override any customized configuration and restore it to the default values.
- Review aging configuration to modify your customized configuration.
- Configure the aging settings to specify how long you want to retain the historical data that is collected in the data warehouse, and click Next.
- (On the additional computer) Specify the following:
- Connect with the first Application Server using one of the following options, and click Next:
- Direct connection: The server you are installing connects to the first application server over a direct connection. This server can directly access the TrueSight Capacity Optimization database. Type the following information:
- The address of the web server.
- Protocol to be used and a corresponding web port. The port numbers are 8443 for HTTPS and 8000 for HTTP.
- Remote connection: The server you are installing connects to the first application server over a remote connection. This server is located on a remote network with an unstable or slow connection. Type the following information:
- External data API server name
- Protocol to be used, data API port (default value 8443), and control port (default value 8280). Port should be open for communications.
- Direct connection: The server you are installing connects to the first application server over a direct connection. This server can directly access the TrueSight Capacity Optimization database. Type the following information:
Type the name and password of the administrative user, and click Next. Default user name is Admin.
Ensure that the administrative user is present in the Capacity_Administration user group of your Remedy SSO server. See Configuring users and user groups.
- Ensure that the required components to upgrade are selected, and click Next.
- Specify the following details to connect to the Oracle database, and click Next.
- Path of your Oracle Client's Home directory.
- Name of your Oracle Alias (TNS).
- Connect with the first Application Server using one of the following options, and click Next:
- Review the Installation Preview information and click Install to start the upgrade. The upgrade may take up to 45 minutes.
After the upgrade is complete, the Installation Summary page is displayed. - Click View Logs to open the upgrade logs.
- Click Done to exit the upgrade program.
Verify the Application Server and ETL Engine upgrade.
- Log in as the user that you specified during upgrade (example: cpit).
- Navigate to the installation directory (example: /opt/bmc/BCO).
- Run the command: ./cpit status
A list of all TrueSight Capacity Optimization services and their current status is displayed. Verify that the services for all upgraded components are RUNNING.
- 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 default port numbers are 8443 for HTTPS and 8000 for HTTP.The browser cookie domain assigned to FQDN should be the same for Remedy Single Sign-On, the Presentation Server, and the Application Server. - 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 Upgrade process
Now that you have successfully upgraded the Application Server and ETL Engine, you must upgrade the Gateway Server.
