Milestone 1: Installing or upgrading BMC AMI Products for Web on Windows

This milestone guides you through the process for installing or upgrading BMC AMI Products for Web (CES, Abend-AID, Session Monitor, iStrobe, Code Pipeline Web, Automation for Batch ThruPut Web, Topaz for Java Performance, and Total Test) on Windows.

Planning

Before beginning the installation, you should verify the following conditions:

• Java 11 is installed. For supported Java 11 vendors, see Planning.
• The JAVA_HOME environment variable is set to the Java 11 path.
• The Path environment variable is set to JAVA_HOME\bin.
• (If you are using Java 11.0.20 or later) The JAVA_TOOL_OPTIONS environment variable is set to -Djdk.util.zip.disableZip64ExtraFieldValidation=true.
• Space requirements are adequate.
• Database is created.
• Permissions are correct.
• Ports are opened.

Installing

1. Click the BMC AMI Products for Web tab from the product image.
   Ex. <network or hard drive>:\Windows\setup.exe
2. Click Install BMC AMI Products for Web for Windows .
   The BMC AMI Products for Web Introduction page appears.
3. Read the introduction content, and then click Next to proceed. The License Agreement page appears.
4. Accept the terms of the License Agreement and click Next. The Oracle License Agreement page appears.
5. Accept the terms of the Oracle Technology Network Development and Distribution License Agreement and click Next. The Select Instance page appears.
6. From the Select Instance page you can either upgrade an existing CES instance or create a new instance.
   
   Select the New CES Instance check box and in the active field, type an instance name to use for the new instance of CES. Choose an instance name that is different than any of the previously installed instance names to distinguish it. That which you enter here will be appended to the string “Compuware Enterprise Services$” and be used as the servicename parameter value in the CES_service.ini file (in your CES installation folder). For example: 
   servicename = Compuware Enterprise Services$my_instance_name
7. Click Next. The Select Products to Install page appears.
8. Select the BMC AMI Products for Web to be installed along with CES. Click Next. The Choose Install Folder page appears.

9. Specify an installation folder or accept the default installation folder for CES (C:\Program Files\BMC\CES).

   • Select Restore Default to use the default folder (C:\Program Files\BMC\CES).
   • Select Choose to specify a folder. The Browse for Folder dialog box appears to navigate to a desired folder.
   • Enter a path.

   Click Next. The BMC AMI Products for Web page appears.

10. CES stores log and configuration data in a specific directory. Click Choose to specify a folder path or click Next to accept the displayed location (default: C:\ProgramData\BMC\CES\data).

    Important

    The ProgramData folder is a hidden folder in MS Windows.

11. Specify the port settings that CES will use to access BMC technology and click Next. Be sure that the ports you choose are open on your network's firewall.

    Port name	Port number (by default)
    Strobe Communication port	24354
    Web Server port	48226
    BMC AMI Common Enterprise Services shutdown port	8465
    Internal Messaging port	17667
    Derby port	1545
    Internal proxy port	11329

12. (Abend-AID only) Abend-AID communication port (default: 48301) Used to transmit messages. Specify a port number between 1024 and 65535. Click Next.
13. (iStrobe only) iStrobe stores measurement data in profiles. When a profile cannot be read, it goes to a different location referred to as Quarantine. Specify the locations for your Profile and Quarantine directories.
    • Profile folder (default: C:\ProgramData\BMC\CES\data\istrobe\profile) Used to store measurement data in profiles.
    • Quarantine folder (default: C:\ProgramData\BMC\CES\data\istrobe\quarantine) Used to store profiles that cannot be read.
    • Click Next.
14. (Topaz for Java Performance only) Agent communication port (default: 48128) Topaz for Java Performance requires a port for communication between the mainframe agent and server. Specify a port on which to listen for this communication, or click Next to accept the default.
15. (Total Test only) MongoDB host (default: localhost) and MongoDB port (default: 27017). Total Test requires this information to configure the MongoDB database. This database is used exclusively with Total Test.

16. Review the Pre-installation summary information. If anything is incorrect, click Previous and make revisions to the installation settings as necessary. If it is correct, click Install to start the CES installation. The Install Complete page appears when the installation finishes.

    Important

    Before exiting the installer, use the URL provided in the installer completion page to visit the CES page in a browser and create a bookmark for quick access. Once the CES service is started, initialization may take several minutes. You may see a 404 page in your web browser during this time.

17. Click Done.
18. The CES installation process is complete. Although the installation is complete, you must still configure CES. Continue with Configuring BMC AMI Common Enterprise Services.

Upgrading

This guides you through the process for upgrading BMC AMI Common Enterprise Services (CES, Abend-AID, Session Monitor, iStrobe, Code PipelineWeb, Automation for Batch ThruPut Web, Topaz for Java Performance, and Total Test) on Windows.

As of CES 17.2.1, a CES maintenance/update file is available for upgrading CES and installed products.

Roles involved

The following individuals are involved with this milestone:

• Systems administrator and possibly a database administrator.
• Security administrator, if security is enabled.

Planning

Before beginning the upgrade, you must ensure the following conditions:

• If you are upgrading to a version of CES that supports Microsoft SQL Server Windows Authentication for the first time, we recommend using the installer to upgrade the product.

  Important

  When you use the update center to perform the upgrade, you must manually put the SQL JDBC 6.2 Auth dll in the <CES install directory>/lib folder.

• For your environment, you should use the same space allocations as identified in the Planning section of this installation guide.
• When upgrading CES using Update Center (17.2.3 and higher), the CES data folder must be at least 1 GB to accommodate the CES maintenance file. The file will be deleted once the upgrade is complete.

Adding new web products to an existing CES installation

Any BMC AMI Products for Web not having been previously installed with the existing CES installation can only be added through a product installation, and not through the CES maintenance/update file.

Upgrading from CES 17.2.3 or higher

This upgrade can be accomplished by using either the Update Center within the CES application or through a product install.

To upgrade using the Update Center

Using the Update Center within CES will upgrade both the version of CES as well as the version of the database. If you do not want to upgrade your database at this time, then you must use the product install or temporarily switch to a different database type on the Database settings page before performing the upgrade.

1. Open CES 17.2.3+ and navigate to the Update Center in CES Administration.
   The installed products will display. Click Show Details for a complete list.
2. Select the Updates tab.
   • Set Check for updates online to On (default) - You must have an HCI defined. The maintenance file can be downloaded from the BMC server. This requires internet access. A secure proxy may be required.
   • Alternatively, set Check for updates online to Off - This allows you to obtain a maintenance file (for example, from the BMC Support Center) that can be uploaded from an accessible location.

3. After downloading or uploading an update file, click Apply to begin the upgrade process.

   Important

   This will also update your database if required. If you do not want to update your database with CES, then you must click Cancel, then switch to a temporary database on the CES Database settings page, and restart this process.

4. After some time, access CES in a new browser tab to verify that the CES UI loads successfully. If the UI does not load, it means that your Java 11 parameters are not properly configured. 

5. (Recommended) Set the JAVA_HOME variable at the system level, to point to Java 11.

   Important

   If you are not able to set the JAVA_HOME variable at the system level, go to your installation folder and perform the following steps:

   1. In the CollectSupportFiles.bat file, modify JAVA_PGM=%JAVA_HOME%\bin\java.exe to JAVA_PGM=<Java11Path>\bin\java.exe.
   2. After a successful upgrade, add the JAVA_HOME path in the following variables residing in the CES_service.ini file:
      • jrepath=%JAVA_HOME%
        (For example, jrepath=C:\Program Files\Java\jdk-11)
      • path=%JAVA_HOME%\bin;%PATH%
        (For example, path=C:\Program Files\Java\jdk-11\bin;%PATH%)
6. (If you are using Java 11.0.20 or later) Set the JAVA_TOOL_OPTIONS environment variable to -Djdk.util.zip.disableZip64ExtraFieldValidation=true.
7. Restart the CES service. You will be prompted to upgrade your database.
8. (Optional) If you switched to a temporary database to preserve the version of the database being used, re-establish the connection to the database.
   1. Navigate to the Database settings page in CES Administration and re-enter the configuration settings, and make sure to reassign the database type.
   2. Do one of the following:
      • For all database types, click Apply to automatically upgrade the database.
      • If you are using a Db2 LUW, Db2 z/OS, Oracle, or SQL Server database, you may instead choose to generate DDL to upgrade your database by clicking Generate DDL. For specific direction, see the Database settings page in the online help.
9. If security was previously enabled, you will be prompted to verify and apply your security settings.

10. (

    iStrobe

     only) Profiles, notes, tags, folders, and any other configuration settings should now be found in the upgraded release.

11. Tokens were previously using a host and a port but are now using HCI connections. Ensure that each token is now pointing to a valid HCI. You should also remove those invalid HCI definitions that were created during the upgrade process.

CES has been upgraded and is ready to use.

To upgrade using the product installer

1. If you are performing an upgrade installation of CES, be sure to stop the CES service before beginning the upgrade.
2. From the CES (current version) media image downloaded from an RFN order or from the Enterprise Common Components (ECC) EP media, select Install CES for Windows, and click Start Install.
3. Read the introduction content and agree to the License Agreements, clicking Next for each to proceed.
4. Select an existing CES instance to upgrade (for example: CES_17.n.n.nnn).
5. Optionally change the CES Instance name.
6. If you select new products to install, you will be prompted to configure those products. Products already installed will be upgraded.
7. Click Install to begin the upgrade.

8. (Recommended) Set the JAVA_HOME variable at the system level, to point to Java 11.

   Important

   If you are not able to set the JAVA_HOME variable at the system level, go to your installation folder and perform the following steps:

   1. In the CollectSupportFiles.bat file, modify JAVA_PGM=%JAVA_HOME%\bin\java.exe to JAVA_PGM=<Java11Path>\bin\java.exe.
   2. After a successful upgrade, add the JAVA_HOME path in the following variables residing in the CES_service.ini file:
      • jrepath=%JAVA_HOME%
        (For example, jrepath=C:\Program Files\Java\jdk-11)
      • path=%JAVA_HOME%\bin;%PATH%
        (For example, path=C:\Program Files\Java\jdk-11\bin;%PATH%)
9. (If you are using Java 11.0.20 or later) Set the JAVA_TOOL_OPTIONS environment variable to -Djdk.util.zip.disableZip64ExtraFieldValidation=true.
10. Restart the CES service and open CES in a browser. You will be prompted to upgrade your database.
11. Click the Database Configuration page link. Do one of the following:
    • For all database types, click Apply to automatically upgrade the database.
    • If you are using a Db2 LUW, Db2 z/OS, Oracle, or SQL Server database, you may instead choose to generate DDL to upgrade your database by clicking Generate DDL. For more information, see the Database settings page in the online help.
12. If security was previously enabled, you will be prompted to verify and apply your security settings.

13. (

    iStrobe

     only) Profiles, notes, tags, folders, and any other configuration settings can now be found in the upgraded release.

Moving from a sandbox to a production environment

• If you use a different database in production other than the sandbox database, then only the profiles can be synchronized. All other configuration settings or user-specific settings will be lost as mentioned.
  1. Make a backup of all files within the profile directory of the existing 05.02.0x install (Default: < iStrobe install directory >/samples).
  2. After installing the BMC AMI Products for Web, move the backed-up profiles into the profile directory specified during the install (Default: < CES install directory >/data/istrobe/profiles).

  3. Within iStrobe, navigate to iStrobe Administration > General Configuration and click Synchronize to process the profiles into the install.

     Important

     • Any note or tag (created in iStrobe) associated with a particular profile will be lost.
     • Past user folder information will be lost. Synchronized profiles will go to the iStrobe folder.
     • Any user-configured settings under the General Configuration page will be lost.
     • Any saved measurements record or measurement groups record will not be there.
     • iStrobe old SMF data will be lost. So, in the new database it needs to be loaded from the beginning.
     • Schedule settings for Profile Autodelete or SMF Data Management will be lost.
     • SMF Archive Database Configuration needs to be redone.
     • Usage statistics data will be lost.
     • Users, roles, groups will need to be reconfigured.

• If you use the same type of database in sandbox and in production, then all the data can be copied from the sandbox database to the production database to restore all the configuration settings. The version number and the build number of the product must exactly match that being used in sandbox and in production.