Skip to Content

Milestone 3: Installing or upgrading BMC AMI Products for Web on Linux

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 Linux.

Warning

Important

Roles involved with this milestone:

  • A Linux system administrator to install BMC AMI Products for Web.
  • A single user to install or upgrade CES and all web products into CES. This allows CES and those installed web products to run with a single set of permissions.
    If multiple users have already installed web products into an installed version of CES, then the permissions must be modified in the install directory of CES to grant read & write permissions to all users.
    To change the permissions for the CES install directory, execute the following command: chmod -R 755 /<path to CES>

For example, depending on your CES version and where CES is installed, execute either of the following commands:


    • For versions prior to 20.14.01, the default CES install directory is /opt/cpwr/ces. Hence, execute the command, chmod -R 755 /opt/cpwr/ces.
    • For version 20.14.01, the default CES install directory is /opt/bmc/ces. Hence, execute the command, chmod -R 755 /opt/bmc/ces. 
    • The value in the java.io.tmpdir property indicates the temporary directory location. You can check the location by running the command, java -XshowSettings. Verify the user privileges, and ensure that the read and write permissions (755) are granted to all users for this temporary directory.

Planning

Before beginning the installation, you should verify the following:

  • Java 11 is installed and the JAVA_HOME environment variable in CES is set to the Java 11 path. For supported Java 11 vendors, see Planning.
  • (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

systemd

  • systemd is an "init system" and is the supported system on newer Enterprise Linux distributions.
  • CES supports SUSE and RHEL which, in versions 12+ and 7.2+ respectively, use systemd.
  • This service can be managed as mentioned above (like any other systemd service).
  • This service can be uninstalled by removing the script and running "systemctl daemon-reload" again.

Installing

  1. Click the BMC AMI Products for Web tab from the product image.
    Ex. <network or hard drive>:\Linux\setup.exe
  2. Click Install BMC AMI Products for Web for Linux. The Linux FTP Information tab appears.
  3. Specify a valid Host, User ID/Password, Port number (default = 21), and finally an existing Linux path in which to upload the install.bin file from the CES product image to the mainframe.
  4. Click Upload files to begin the upload.

  5. Be sure that the install.bin file has execute authority. Perform a chmod 755 to open up permissions if necessary. This file is located at Disk1\InstData\NoVM.

    Warning

    Important

    By default, the install uses the system's TEMP location, typically the /tmp directory. To specify an alternate tmp location, you need to define the environment variable IATEMPDIR prior to running the install command.
    export IATEMPDIR=<alternateTempDir>

  6. Execute the following commands:

    JAVA_HOME=/<path to JRE>
    PATH=$JAVA_HOME/bin:$PATH
    /install.bin

    InformationJAVA_HOME=/usr/lib/jdk11
    PATH=$JAVA_HOME/bin:$PATH
    /install.bin    The CES installer starts.

    Warning

    Important

    • You can cancel the installation at any time by typing quit.
    • You can go back in the installation panels at any time by typing back.

    After reading the Introduction panel, press Enter. The License Agreement panel appears.

  7. Read the BMC AMI Products for Web license agreement, pressing Enter until you have scrolled through and read the entire agreement. When prompted, type Y and press Enter to accept the terms of the license agreement. The Oracle License Agreement panel appears.
  8. Read the Oracle Technology Network Development and Distribution License Agreement, continuing to press Enter until you have scrolled through and read the entire agreement.
  9. Again, type Y and press Enter to accept the terms of the license agreement. The BMC AMI Products for Web panel appears.

  10. Specify the absolute directory path in which to install CES, or press Enter to accept the default location (Default: /opt/BMC/CES).

    Warning

    Important

    • If you choose an alternate installation directory instead of the default, the directory (and any parent directories) will be created with privileges of 775. To use CES following installation, be sure that the CES job has write permission to the CES directory created by the installation.
    • The installer requires use of up to 1.2 GB (or 1,125,000 1k blocks of pre-allocated space to install properly. You may be prompted to create free space in the specified directory in order to continue with the installation.
    Error
    Warning

    If you are upgrading from a previous release, enter the existing CES installation directory.

  11. Select the BMC AMI Products for Web to be installed along with CES by entering a comma delimited numbered list corresponding to the products and press Enter.
  12. Confirm your selection. If you would like to make changes to your selection, type Back. Otherwise, press Enter.
  13. CES stores log and configuration data in the /data directory under the installation directory specified in Step 10. Press Enter to accept the default location (<Installation_directory>/data) or specify the absolute path to another location.
  14. Specify an Instance Name for the CES Service. This is used to distinguish between different versions that can run on your system. The name entered here will be appended to ‘cpwrenterpriseservices’ as the daemon name.
    Ex. cpwrenterpriseservices_CES_18.2
  15. Specify the user ID needed to install and run the CES daemon (Default: root).

  16. Specify Y (Yes) or N (No) whether you want to modify the default port numbers. 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

    Web Application Stop port

    8465

    Internal Messaging port

    17667

    Derby port

    1545

  17. (

    Abend-AID

     only) Abend-AID communication port (default: 48301) Used to transmit messages. Specify a port number between 1024 and 65535. Press Enter.

  18. (

    iStrobe

     only) Profile directory (default: <installation_directory>/data/istrobe/profiles) Used to store measurement data in profiles. Specify the absolute directory path for the Profile directory. Press Enter.

  19. (

    iStrobe

     only) Quarantine directory (default: <installation_directory>/data/istrobe/quarantine) Used to store profiles that cannot be read. Specify the absolute directory path for the Profile directory. Press Enter.

  20. (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. Enter the port on which to listen for this communication, or press Enter to accept the default.

  21. (

    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.

  22. Review installation information you selected in the Pre-installation summary panel. If anything is incorrect, type Back and revise the installation settings as necessary. If the information is correct, press Enter to start the BMC AMI Products for Web installation. The Installation Complete panel appears when the installation finishes.

    Warning

    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.

  23. Restart the CES service.

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

Starting BMC AMI Common Enterprise Services on Linux

Starting and stopping CES on Linux is dependent on whether or not systemd is being used.

Systemd in use

When starting CES, execute the following:

systemctl start cpwrenterpriseservices_servicename

When stopping CES, execute the following:

systemctl stop cpwrenterpriseservices_servicename

Systemd not in use

When starting CES, execute the following:

/etc/init.d/cpwrenterpriseservices_servicename start

When stopping CES, execute the following:

/etc/init.d/cpwrenterpriseservices_servicename stop

A legacy service script is created during the installation in /etc/init.d. If using systemd, a script is installed that converts the legacy script to a systemd service definition file, either on restart or with a call to "systemctl daemon-reload".

Upgrading

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

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 should have the following:

  • For your environment, you should use the same space allocations as identified in the Planning chapter of this installation space.
  • 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.
Warning

Important

For 18.2.1 or later, security settings that were enabled for iStrobe in the prior release will now be used to access CES after the upgrade. For example, if LDAP security was enabled for iStrobe 17.2.0, the LDAP ID/PW will be required to access CES. All security will now be handled through CES.

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 later

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 (e.g. from the BMC Support) that can be uploaded from an accessible location.

    • To show the latest versions only of the web-based products, set the Show latest versions only switch to On.

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

    Warning

    Important

    This will also update your database if required. If you do not want to update your database with CES, then 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.

    Warning

    Important

    If you have not set the JAVA_HOME variable at the system level, perform the following steps to set the Java path to Java 11:

    1. Identify the location of Java 11 JDK/JRE.
      For example, Java 11 location path = /usr/lib/jdk11/
    2. Edit the following files and set JAVA_HOME to /usr/lib/jdk11.
      • In the CollectSupportFiles.sh file, modify JAVA_PGM=${JAVA_HOME}/bin/java to JAVA_PGM=/usr/lib/jdk11/bin/java
      • In the execces.sh file, modify JAVA_HOME to JAVA_HOME=/usr/lib/jdk11/
      • In the execcesSystemD.sh file, modify JAVA_HOME to JAVA_HOME=/usr/lib/jdk11/
  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 server and refresh your browser.
  8. (Optional) At this point, if you switched to a temporary database to preserve the version of the database being used, you will want to re-establish that connection.
    1. Navigate to the Database settings page in CES Administration and re-enter the configuration settings, being sure to reassign the database type.
    2. Do one of the following:
      • For all database types, click Apply to automatically upgrade the database.
      • If 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. See the Database settings page in the online help for specific direction.
  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. As well, you should 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. See the instructions under Installing, following steps 1 through 10 where you enter your existing CES installation directory.

  3. (Recommended) After the upgrade is complete, set the JAVA_HOME variable at the system level, to point to Java 11.

    Warning

    Important

    If you have not set the JAVA_HOME variable at the system level, perform the following steps to set the Java path to Java 11:

    1. Identify the location of Java 11 JDK/JRE.
      For example, Java 11 location path = /usr/lib/jdk11/
    2. Edit the following files and set JAVA_HOME to /usr/lib/jdk11.
      • In the CollectSupportFiles.sh file, modify JAVA_PGM=${JAVA_HOME}/bin/java to JAVA_PGM=/usr/lib/jdk11/bin/java
      • In the execces.sh file, modify JAVA_HOME to JAVA_HOME=/usr/lib/jdk11/
      • In the execcesSystemD.sh file, modify JAVA_HOME to JAVA_HOME=/usr/lib/jdk11/
  4. (If you are using Java 11.0.20 or later) Set the JAVA_TOOL_OPTIONS environment variable to -Djdk.util.zip.disableZip64ExtraFieldValidation=true.
  5. In the execcesSystemD.sh file, right after ARGS="$ARGS -Dosgi.instance.area=$CESDATA_HOME/workspace", add the following new argument:
    ARGS="$ARGS -Djavax.xml.bind.context.factory=org.eclipse.persistence.jaxb.JAXBContextFactory"
  6. Start the CES service and open CES in a browser. You will be prompted to upgrade your database.
  7. 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. See the Database settings page in the online help for specific direction.
  8. If security was previously enabled, you will be prompted to verify and apply your security settings.

  9. (

    iStrobe

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

CES has been upgraded and is ready to use.

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.

      Warning

      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 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 both in sandbox as well as 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.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC AMI Web Products Installation and Configuration 23.03