Upgrading the Application Server and the ETL Engine silently

Where you are in the Upgrade process

A silent upgrade is one in which you run the installation program from a command line, enabling you to upgrade the product in situations where the operating system of the target computer does not support a graphical user interface (UI).

The silent upgrade provides a direct upgrade from the two most recent versions of the product to the latest version. When upgrading from an earlier version, you must perform at least one interim upgrade before you can perform this task.

To upgrade the Application Server and the ETL Engine silently

1. 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 upgrade steps are available only to the root user.

2. Extract the downloaded files to the temporary directory. Ensure that the temporary directory is different from the installation directory to avoid any file sharing conflict.
3. At the shell prompt, change to the directory where you extracted the installation files. Example: TSCO_temp/BCO/Disk1.
4. Navigate to the directory where you extracted the downloaded files and locate the sample config files. Example: TSCO_temp/BCO/Disk1/silentInstallTemplates.

5. Based on the upgrade scenario, use the applicable options file. This is a text file that defines the installation properties in the form of a prefix tag followed by a property name and value pair. You can either retain the default values or change them and save the file. The following table lists the upgrade scenarios and the applicable options files:
   
   

   Upgrade scenarios and options files

   Scenario	Options file
   Upgrade all components on the first computer with Oracle.	BCO_FIRST_SERVER_TYPICAL_ORACLE.txt
   Upgrade all components on the first computer with PostgreSQL.	BCO_FIRST_SERVER_TYPICAL_POSTGRES.txt
   Upgrade only the Database Schema and Web Server on the first computer with Oracle.	BCO_FIRST_SERVER_CUSTOM_AS_FRONTEND_WEB_ORACLE.txt
   Upgrade only the Database Schema and Web Server on the first computer with PostgreSQL.	BCO_FIRST_SERVER_CUSTOM_AS_FRONTEND_WEB_POSTGRES.txt
   Upgrade the Data hub, Primary Scheduler, and ETL Engine on the additional computer.	BCO_ADDITIONAL_SERVER_AS_BACKEND_DH_PS.txt
   Upgrade the Web Server on the additional computer.	BCO_ADDITIONAL_SERVER_AS_WEB.txt
   Upgrade ETL Engine over a direct connection on the additional computer.	BCO_ADDITIONAL_SERVER_EE.txt
   Upgrade ETL Engine over a remote connection on the additional computer.	BCO_ADDITIONAL_SERVER_REMOTE_EE.txt
   Upgrade Primary Scheduler on the additional computer.	BCO_ADDITIONAL_SERVER_AS_PS.txt

6. Based on the options file you are using, set the appropriate parameters. The following table lists all the parameters that are found in the various options files. 
   Based on the upgrade scenario, the options files have some of these parameters commented out. 
   You must update the following parameters as per your current TrueSight Capacity Optimization installation: #Tablespaces, #Console Schema, #Views Schema, and #Reporting User. 
   By default -J BCO_DB_CREATE_SCHEMA=false; this value should not be changed.

   Property details

   Prefix tags for the silent installation properties:

   • -P: Precedes the directory properties
   • -A: Precedes the application features

   • -J: Precedes the Java properties

   
   

7. Open a shell prompt and navigate to the directory that contains the installation files (example: /BCO/Disk1).

8. Launch the silent installer:

   ./setup.sh -i silent -DOPTIONS_FILE=<file path>/<options file name>.txt

   If the path contains spaces, enclose the path and options file name in quotation marks.
   Example: ./setup.sh -i silent -DOPTIONS_FILE="/opt/TSCO_temp/BCO/Disk1/silentInstallTemplates/BCO_FIRST_SERVER_TYPICAL_ORACLE.txt"
   After the installation is completed on the first computer, (i) the encrypted keys, (ii) CA keys and certificate, and (iii) client keys and certificate are generated in the respective folders of the $BCO_HOME/secure directory. 

9. Verify the Application Server and ETL Engine installation.

   1. Log in as a root user and set the password for the user that you specified during installation (example: cpit).
   2. Log in as the user that you specified during installation (example: cpit).
   3. Navigate to the installation directory (example: /opt/bmc/BCO).
      
   4. Run the command: ./cpit status

   A list of installed TrueSight Capacity Optimization services and their current status is displayed. Verify that the services for all installed components are RUNNING.

   Example

   

   
   
   

   TrueSight Capacity Optimization components and their services

   Component	Web service	Scheduler service	Service Container service	Data Hub service	Httpd service	DynServices
   Web	✅️	✅️	✅️	-	✅️	✅️
   Primary Scheduler	-	✅️	✅️	-	-
   Data Hub	-	✅️	✅️	✅️	✅️	✅️
   ETL	-	✅️	-	-	-

   For example, if you have a Primary Scheduler and the Data Hub, verify that the Scheduler, Data Hub, and Httpd services, are RUNNING; if you have enabled the Service Container component, verify that the Service Container is also RUNNING.

10. 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.
11. 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.