Upgrading IT Data Analytics in a multiple server environment silently

Where you are in the Upgrade process

The page .Upgrading IT Data Analytics in a single server environment using the wizard v11.3.01 was not found  -- Please check/update the page name used in the MultiExcerpt-Include macro

You can upgrade IT Data Analytics in a multiple server environment, silently, by doing a custom upgrade. The silent upgrade obtains the required user inputs from the options files. You can download sample options files from within the procedure below, or you can generate them.

To perform a custom upgrade silently

Do the following:

1. Log in to the host computer on which you want to upgrade IT Data Analytics, and delete all the files from the temporary directory: 

   • (Windows) %temp%

   • (Linux) /tmp

2. Extract the downloaded files (the installer) to a temporary location outside the following location to avoid any file sharing conflicts.

   • (Windows) C:\Program Files

   • (Linux) /opt

   It is strongly recommended that you exit all programs before starting the installation.

3. From the command prompt, navigate to the Disk1 folder:

   • (Windows) <DownloadLocation>\BMC-TrueSight-IT-Data-Analytics\Disk1\
   • (Linux) <DownloadLocation>/BMC-TrueSight-IT-Data-Analytics/Disk1/

4. Download the following sample options files depending on the component that you want to upgrade and your environment, or generate one. To generate the file, go to Step 6.

   Component	Windows Sample Options file	Linux Sample Options file
   Indexer	Windows sample options file for Indexer.txt	Linux sample options file for Indexer.txt
   Search Server Configuration Database	Windows sample options file for Search Server ConfigDB.txt	Linux sample options file for Search Server ConfigDB.txt
   Search	Windows sample options file for Search.txt	Linux sample options file for Search.txt
   Collection Station	Windows sample options file for Station.txt	Linux sample options file for Station.txt
   Console Server	Windows sample options file for Console Server.txt	Linux sample options file for Console Server.txt

5. Copy the sample options file to the following folder on every computer where you want to upgrade the components:

   • (Windows) C:\Program Files\BMC Software\TrueSight\ITDA
   • (Linux) /opt/bmc/TrueSight/ITDA

   To install the product in a different location, change the value of the installLocation property in the options file.

6. Run the following command to generate the options file:

   1. From the command prompt, run the following command to generate the options file:

      • (Windows) setup.exe –DGENERATE_OPTIONS_FILE=pathToOptionsFile

      • (Linux) As a non-root user, run setup.bin –DGENERATE_OPTIONS_FILE=pathToOptionsFile

        Note

        pathToOptionsFile must contain the name of the options file. If the file name or path includes a space, enclose the path and name in double quotes.

      Examples:

      • (Windows - path with space) setup.exe –DGENERATE_OPTIONS_FILE="C:\temp folder\Disk1\options File.txt"

      • (Linux - path with space) setup.bin –DGENERATE_OPTIONS_FILE="opt/temp folder/Disk1/options File.txt"

   2. This command launches the TrueSight IT Data Analytics installation wizard. You must complete the wizard-based installation once, to populate the options file with properties. Your options file is then ready to be used in silent installation.

7. You will need to type the Remedy Single Sign-On password in an encrypted form in the options file in Step 8. Encrypt this password using the EncryptPWD utility:
   

   
   

   1. Open the EncryptPWD utility by navigating to:
      • (Windows) <DownloadLocation>\BMC-TrueSight-IT-Data-Analytics\Disk1\utility\EncryptPWD
      • (Linux) <DownloadLocation>/BMC-TrueSight-IT-Data-Analytics/Disk1/utility/EncryptPWD 
   2. Run the tool, and click the Encrypt tab.
   3. Type the password, confirm it, and click Encrypt.
   4. Note down the encrypted password (from the Encrypted Password field)
   
   

8. Open and edit the options file. You can either retain the default values for the properties or change them, and save the file. The options file defines the installation properties in the form of a prefix tag followed by a property name and value pair.
   

    Property details

   Prefix tags for silent installation properties:

   • -P: Precedes directory properties

   • -A: Precedes application features

   • -J: Precedes Java properties

   Property name	Description
   Installation
   -P installLocation	The full path to the installation directory. Default value: Windows: C:\Program Files\BMC Software\TrueSight\ITDA Linux: /opt/bmc/TrueSight/ITDA Example: -P installLocation=C:\Program Files\BMC Software\TrueSight\ITDA
   Feature selection
   -A <Feature-Name>	The components that you want to install. A typical installation installs all the components. For a custom installation, you can specify components while generating an options file. Note: The TomcatHiddenProduct feature is only required if you want to install the Search component or the Console Server component. Example: # Install Indexer -A Indexer # Install Configuration Database -A Configuration Database # Install Collection Station -A Collection Station # Install Console Server -A Console Server # Install Search -A Search # Install Tomcat Hidden Product -A TomcatHiddenProduct
   Installation type
   -J INSTALL_SET	The installation type: custom. Example: -J INSTALL_SET=TYPICAL -J INSTALL_SET=CUSTOM
   Pinning the product to Start menu and starting services
   -J STARTMENU_SHORTCUT	Whether you want to pin the product to the Start menu on your computer (Windows only). Example: -J STARTMENU_SHORTCUT=true
   -J STARTSERVICES_ITDA	Whether you want to start the product services immediately after the installation is complete. Example: -J STARTSERVICES_ITDA=true
   Skipping port validation
   -J SKIP_VALIDATION	Whether you want to skip port validation during installation. You might want to use this property if you know that the ports used for the installation are available before starting the installation. Example: -J SKIP_VALIDATION=true Note: This feature is only available for silent installation. If you do not add this property or set the value of this property to false, and if the defaults ports are in use, then the installation will fail.
   Indexer details
   -J itda.indexinghost	The host name of the computer where you want to install the Indexer. The default is your local host name. Example: -J itda.indexinghost=Indexer.bmc.com
   -J itda.indexingport	The port number of the computer where you want to install the Indexer. The default is 9300. Example: -J itda.indexingport=9300
   -J itda.indexing.unicast.hosts	If you want to install an Indexer that must function as the master, leave this value blank. If you are installing an Indexer that must function as a peer or a component that communicates with the master Indexer, provide the fully qualified host name and port number of the master Indexer installed on the primary node. This value must be in the format, hostName1:Port. Example: -J itda.indexing.unicast.hosts= MasterIndexer.bmc.com:9300
   -J itda.indexer.box.type	The Indexer type of the computer where you want to install the Indexer. The default is live. If you want the Indexer type to be an archive node, specify archive. If you want the Indexer type to be a restore node, specify restore. Example: -J itda.indexer.box.type=live or -J itda.indexer.box.type=archive
   Configuration Database details
   -J itda.configdbhost	The host name of the computer where you want to install the configuration database. The default is your local host name. Example: -J itda.configdbhost=ConfigDB.bmc.com
   -J itda.configdbport	The port number of the computer where you want to install the configuration database The default is 9999. Example: J itda.configdbport=9999
   Collection Station details
   -J itda.stationinstancename	The name of the Collection Station as it must be displayed under the Administration> Hosts tab. Example: -J itda.stationinstancename= Collection-Station.bmc.com
   -J itda.stationhttpbindaddress	The HTTP service bind address that the Collection Agent and the Console Server must use to connect with the Collection Station. The default is 0.0.0.0. Example: -J itda.stationhttpbindaddress=0.0.0.0
   -J itda.stationhttpbindport	The HTTP service bind port number that the Collection Agent and the Console Server must use to connect with the Collection Station. The default is 8080. Example: -J itda.stationhttpbindport=8080
   -J itda.stationpayloadbindaddress	The Payload Service bind address that the Collection Station must use for listening to incoming data. The default is 0.0.0.0. Example: -J itda.stationpayloadbindaddress=0.0.0.0
   -J itda.stationpayloadbindport	The Payload Service bind port number that the Collection Station must use for listening to incoming data. The default is 41414. Example: -J itda.stationpayloadbindport=41414
   -J agent.pool.name	Whether you want to implement data collection redundancy. If you specify the value as true, it implies that the Collection Station installed will be added to a common pool. If this Collection Station goes down, Collection Agents communicating with the Collection Station are moved to another Collection Station in the pool. Example: -J agent.pool.name=true
   Search details
   -J itda.searchenginehost	The host name of the computer where you want to install the Search component. The default is your local host name. Example: -J itda.searchenginehost=Indexer.bmc.com
   -J itda.searchengineport	The port number of the computer where you want to install the Search component. The default is 9797. Example: -J itda.searchengineport=9797
   Console Server details
   -J itda.consoleserverhost	The host name of the computer where you want to install the Console Server component. The default is your local host name. Example: -J itda.consoleserverhost=ConsoleServer.bmc.com
   -J itda.consoleserverport	The port number of the computer where you want to install the Console Server component. The default is 9797. Example: -J itda.consoleserverport=9797
   Remedy Single Sign-On details
   These details are only applicable while installing the Console Server. Configuring Remedy Single Sign-On is an optional step. If you do not want to use Remedy Single Sign-On as your authentication mechanism or if you want to install a standalone instance of IT Data Analytics, you can skip these details.
   -J enable_rsso	Whether you want to use Remedy Single Sign-On as an authentication mechanism. Example: -J enable_rsso=true
   -J rsso_protocol	The protocol used for connecting with the Remedy Single Sign-On server. The default value is HTTPS. It can be set to HTTP or HTTPS. Example: -J rsso_protocol=HTTPS
   -J rsso_host	The Fully Qualified Domain Name (FQDN) of the Remedy Single Sign-On server. Example: -J rsso_host=RSSOHost.bmc.com
   -J rsso_port	The port number of the Remedy Single Sign-On server. The default is 448. Example: -J rsso_port=448
   -J rsso.tenant	The name of the tenant (also known as Realm in Remedy Single Sign-On) that you configured while integrating TrueSight IT Data Analytics with TrueSight Operations Management. If you want to use Remedy Single Sign-On without integrating with TrueSight Presentation Server, then provide the name of the tenant that is present on Remedy Single Sign-On. Example: -J rsso.realm=*
   -J rsso_username	The user name for connecting with the Remedy Single Sign-On server. The default Remedy Single Sign-On administrator user name is "Admin". Example: -J rsso_username=Admin
   -J rsso_password	The password for connecting with the Remedy Single Sign-On server. The password is the one that you provided while installing Remedy Single Sign-On. You must type the Remedy Single Sign-On password in an encrypted form. Copy the encrypted password created in Step 5. Example: -J rsso_password=6G0MnPoXCyHIJ/abMcoHwQ==
   -J tsps_host	The Fully Qualified Domain Name (FQDN) of the TrueSight Presentation Server. Example: -J tsps_host=TSPSHost.bmc.com If TrueSight Presentation Server is installed in a high-availability environment, specify the FQDN of the Load Balancer.
   -J tsps_port	The port number of the Presentation Server. The default is 443 for Windows (HTTPS) and 8043 for Linux (HTTPS). Example: -J tsps_port=443

9. Run the following command to start the silent installation. Type the complete path to the options file in the command. If the path includes a blank space, enclose the path within double quotes.

   • (Windows) setup.exe -silent -DOPTIONS_FILE="<path_to_itda_silent_options_file>"

   • (Linux) ./setup.bin -silent -DOPTIONS_FILE="<path_to_itda_silent_options_file>"


   The installation may take up to 10 minutes. After the installation is complete, the Installation Summary page is displayed.

10. You can periodically check the installation status by checking the itda_install_log.txt file located at: 

    • (Windows)%temp%

    • (Linux)  /tmp

      Search for the following log message in the itda_install_log.txt file to ensure that TrueSight IT Data Analytics is installed successfully:

      BMC TrueSight IT Data Analytics 11.3.01 install succeeded

11. The following environment variable points to the IT Data Analytics installation path after the upgrade. 

    • (Windows) %BMC_ITDA_HOME%

    • (Linux) $BMC_ITDA_HOME

12. Run the following command to verify the TrueSight IT Data Analytics status:

    • (Windows) Navigate to the TrueSight\ITDA\bin directory, and run run.bat -status command.
    • (Linux) Navigate to the TrueSight/ITDA/bin directory, and run ./run.sh -status command.

    A list of IT Data Analytics services are displayed as shown in the following example:

    TrueSight IT Data Analytics Indexer:
    The requested service has already been started.
    TrueSight IT Data Analytics ConfigDB:
    The requested service has already been started.
    TrueSight IT Data Analytics Server:
    The requested service has already been started.
    TrueSight IT Data Analytics Collection Station:
    The requested service has already been started.

13. (Optional) Start using Remedy Single Sign-On as your authentication mechanism by running the  enablesso CLI command . Using Remedy Single Sign-On is required if you plan to use TrueSight IT Data Analytics in conjunction with the  TrueSight products For more information, see User authentication options.

14. (Optional) If you are upgrading from TrueSight IT Data Analyticsversion 2.7, ensure that you modify the properties for re-indexing after upgrading.

     To modify the properties for re-indexing

    When you upgrade from TrueSight IT Data Analyticsversion 2.7, the indexes are migrated to TrueSight IT Data Analytics11.3.01 by default. You can modify some properties to manage the way you are re-indexing the data. Search features of TrueSight IT Data Analytics such as histogram, facets, and search counts of older data are available after the migration is complete. The migration may take some time depending on the size of data.

    Notes

    • After upgrading, if you create an Upload file  type of data collector to collect earlier data, then it is possible that the collected data is added to an existing index. As a result, the search performed on this data will work in a case-sensitive way.
    • If you have existing external configurations for the TrueSight Infrastructure Management (or ProactiveNet) cells, you might need to edit them and change the encryption key. Changing the encryption key is required if TLS is enabled for TrueSight Infrastructure Management on TrueSight Operations Management 10.7. You must import the certificates generated on the TrueSight Operations Management side to be able to create new external configurations in version  11.3.01 of TrueSight IT Data Analytics. For more information, see  Enabling security for communication with Infrastructure Management server
    • Re-indexing may increase CPU utilization. You can use throttling, which increases the time taken for re-indexing, but reduces the CPU utilization. For more information refer to the table.

    Do the following:

    1. Log in to the host computer on which you have installed TrueSight IT Data Analytics.

    2. Navigate to the following location: 

       <ITDA_INSTALLATION_DIRECTORY>\BMC Software\TrueSight\ITDA\custom\conf\server\olaengineCustomConfig.properties

    3. Modify the values of the following properties in the olaengineCustomConfig.properties file:

       Property	Additional information
       reindex.enabled	Enables re-indexing. Example reindex.enabled=true By default the value is set to true. Note: If reindexed.enabled is set to false, the previously indexed data may not be compatible with the new version of TrueSight IT Data Analytics . Features such histograms and facets of older data will not be available.
       #reindex.number.of.last.days	Sets the number of days for which the re-indexing is to be done. Example #reindex.number.of.last.days=14 You can set the value to the number of days for which you want the re-indexing to be done. Depending on the number of days that you specify, the previously indexed data will be available for re-indexing. Tip You must uncomment the property if you want to change it.
       reindex.wait.before.next.bulk.write.millis	Sets the wait time in milliseconds before writing the next bulk (or chunk) into new Indexes while re-indexing. Example reindex.wait.before.next.bulk.write.millis=0 The default value is 0. The default value 0 means that there should be no wait time. Setting this value enables you to decrease the Indexer CPU usage while re-indexing. Increasing this value will decrease the CPU usage on the indexer.
       reindex.bulk.flush.threshold.millis	Sets the time in milliseconds; that are passed after the last bulk flush or start of the bulk process. The bulk that is accumulated will be flushed (written) into the Indexer after this period is over. This happens irrespective of the bulk size. Example reindex.bulk.flush.threshold.millis=60000 The default value is 60000.

       Note

       After changing the properties, if the Console Server component is already running, restart it.

15. Restore the backed up keystore file (bmcitda.jks), and restart the IT Data Analytics server after upgrading.

    Note: The bmcitda.jks keystore file is backed up before upgrading to ensure that the custom certificates are not lost after upgrading.

The page .Upgrading IT Data Analytics in a single server environment using the wizard v11.3.01 was not found  -- Please check/update the page name used in the MultiExcerpt-Include macro