Technical bulletin — Announcing hotfix 20.02.00.002
Hotfix 20.02.00.002 is now available for TrueSight Smart Reporting - Platform version 20.02, which is the required base version.
This hotfix fixes the following issue:
Issue
TrueSight Smart Reporting - Platform should support disaster recovery.
Installing the hotfix
From the BMC Electronic Product Distribution (EPD) website, download the TrueSight Smart Reporting - Platform 20.02 zip or tar file.
- Copy the zip file to the server where you want to install the secondary node TrueSight Smart Reporting - Platform.
- Unzip the TrueSight Smart Reporting - Platform 20.02 file on the secondary server in a temporary directory.
From the FTP location, download the TrueSightSmartReporting_HotFix_20.02.00.002.zip file.
- Unzip the TrueSightSmartReporting_HotFix_20.02.00.002.zip file on the same server in a separate temporary directory.
- Navigate to the <TrueSight Smart Reporting 20.02_install_directory>Disk1 directory, and replace the setup.jar file with the hot fix setup.jar file that you downloaded.
- From the temporary directory where you saved the installation files, copy the silent.options file, and paste it in the <TrueSight Smart Reporting 20.02_install_directory>Disk1 directory.
- Open the <TrueSight Smart Reporting 20.02_install_directory>Disk1>silent.options file.
In this file, the value of the -J NODBACCESS parameter is set to true for the disaster recovery configuration. Ensure that this value remains unchanged. - Ensure that the following parameter values are set as shown below:
-J REPORTING_DB_OPTION=EXISTING_DB
-J REPORTING_USER_OPTION=EXISTING_USER
For the disaster recovery configuration, the secondary node uses the existing database and database user of the primary node. Change the values of the other installation parameters as required. Ensure that the repository database details are the same as that of the primary node of TrueSight Smart Reporting - Platform.
For more information about all silent installation parameters, see Installing TrueSight Smart Reporting - Platform silently- Ensure the following:
- The system meets all the requirements and the JAVA_Home environment variable is set. For more information, see System-requirements.
- You review the performance and scalability recommendations for the product. For more information, see Performance-and-scalability-recommendations.
- You set up the TrueSight Smart Reporting - Platform repository database. For more information, see Setting-up-the-TrueSight-Smart-Reporting-Platform-repository-database.
- You grant the permission to log an as a service for installation on the SQL database with windows authentication. For more information, see Granting-permission-to-log-on-as-a-service-for-installation-on-the-SQL-Server-database-with-Windows-authentication.
In the command prompt, navigate to the <TrueSight Smart Reporting 20.02_install_directory>Disk1 directory and run the following command:
Windows
setup.exe -i silent -DOPTIONS_FILE<TrueSight Smart Reporting 20.02_install_directory>Disk1\silent.options
Linux
./setup.bin -i silent -DOPTIONS_FILE=<TrueSight Smart Reporting 20.02_install_directory>Disk1/silent.optionsTo view information about the installation progress, see the TrueSightSmartReporting_install_log.txt file in the temp directory.
Apply the TrueSight Smart Reporting - Platform 20.02.00.001 hotfix. For information about applying this hotfix, see Technical bulletin — Announcing hotfix 20.02.00.001.
Activating the secondary TrueSight Smart Reporting - Platform instance
- Go to the secondary TrueSight Smart Reporting - Platform node, and log in as TrueSight Smart Reporting - Admin.
You can see the component, for example, TrueSight Server Automation - Datawarehouse, as connected in the primary node. - Click Edit against the component, and do one of the following:
- If the component node is the same as before, click Save.
- If the component has failed over and the secondary node is active, do the following:
- Edit the TrueSight Smart Reporting - Platform host name and update the values of the component secondary node.
- Click Save.
When the component status changes to Connected, the component is registered to the secondary TrueSight Smart Reporting - Platform node.
You can now cross-launch from the component to the secondary node of TrueSight Smart Reporting - Platform.
Rolling back the hotfix
This hotfix is applicable to the fresh installation or an upgrade of TrueSight Smart Reporting - Platform version 20.02. Therefore, in case of any issues, you can uninstall TrueSight Smart Reporting - Platform to roll back the hotfix and reinistall the product without replacing the hotfix setup.jar file.
Troubleshooting
Issue: A CLI does not automatically affect both nodes
When you run a CLI on a node, it does not automatically affect the other node. You need to run the CLI on each node separately.
Issue: Problems with using the modifysmartreportinguserpassword CLI to change the password
As a TrueSight Smart Reporting - Platform administrator, if you use the modifysmartreportinguserpassword CLI to change the password on one node, the following issues occur:
- You cannot use the CLI to change the password on the other node.
- If you log in to TrueSight Smart Reporting - Platform on the other node, the cross-launch to the Admin Console fails.
- If you perform a failover of TrueSight Smart Reporting - Platform, the cross-launch to the platform from the component fails.
Workaround
Do the following:
- Stop the TrueSight Smart Reporting - Platform node where you have not changed the password.
- Go to the TrueSight Smart Reporting - Platform node where you changed the password.
- Open the <Smart Reporting Home>\appserver\conf\redbDetails.properties file in an editor and copy the value of the yf.password parameter.
- Go to the TrueSight Smart Reporting - Platform node where you have not changed the password.
- Open the <Smart Reporting Home>\appserver\conf\redbDetails.properties file in an editor.
- Replace the value of the yf.password parameter with the value that you copied earlier.
- Start TrueSight Smart Reporting - Platform on this node.