Installing the Topaz for Java Performance Agent on z/OS UNIX


This section describes the installation procedure for installing the Topaz for Java Performance Agent on z/OS UNIX. Unlike the Topaz for Java Performance web product which may be installed on z/OS UNIX, Linux, or Windows 64-bit, the Topaz for Java Performance Agent is installed only on z/OS UNIX. Depending on your site standards, you may need the assistance of the following individuals:

  • z/OS UNIX system administrator should install Topaz for Java Performance. 
  • Security administrator to grant access to end users.

Before you begin

Before you begin the Topaz for Java Performance Agent installation, you should be sure of the following:

  • A compatible BMC AMI Common Enterprise Services (CES) installation has been installed and configured with Topaz for Java Performance.
  • Location of the CES instance (installation folder).
  • An installed and supported database that has been configured for this CES instance.
  • An installed and supported Java version.
  • A host name used as part of the Topaz for Java Performance and CES URLs. For example, http://<yoursitehostname>.<yoursitedomain>.com:<port number>/topazjava
  • The Topaz for Java Performance Agent installer requires 20000 1K blocks of preallocated temporary space during the installation. When the installation is complete, the temporary installation files are removed.

Installing the Topaz for Java Performance Agent

  1. Click the Topaz for Java Performance Agent tab from the product image.
    Ex. <network or hard drive>:\Windows\setup.exe
  2. Click Install BMC AMI Products for Web Agent for z/OS UNIX.
    The Mainframe FTP Information tab appears.
  3. Specify the following valid information for your site:
    • Host
    • Host Port
    • User ID
    • Password
    • Existing z/OS UNIX Path to the planned Agent installation location
  4. Click Upload files to the mainframe.
    The z/OS UNIX installation includes a file transfer utility that sends the Topaz for Java Performance product files to the mainframe. The install.jar and the install.sh are both uploaded as binary.
  5. Log on to the mainframe and navigate to an OMVS command prompt. Change the directory to the location where the Agent install.jar and the install.sh files were transferred. For example: cd /installation_folder/agent
  6. Be sure that the install.sh file has execute authority. Perform a chmod 755 to open up permissions if necessary.
  7. Start the installation script by entering: ./install.sh
    The system displays RUNNING in the lower-right corner for a few seconds. When it requests INPUT, press Enter.
  8. At the Java version prompt, enter the path to a supported Java 11 version you want to use with this Topaz for Java Performance installation. For example, /usr/lpp/java/J11.0_64
  9. Respond Y or N whether you want to use another folder instead of the default system temporary folder for the Agent installation files. Press Enter . 

    • If you responded Y, enter the new folder name.
    • If you responded N, the default system temporary file will be used.

    The system displays Launching installer and displays RUNNING in the lower-right corner for a few seconds.

  10. When the system requests INPUT, press Enter.
    The Introduction panel appears.

    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.

  11. After reading the Introduction panel, press Enter. The License Agreement panel appears.
  12. Press Enter until you have read and scrolled through the agreement.
  13. Enter Y to accept the terms of the license agreement.
    The Choose Install Folder panel appears.
  14. On the Choose Install Folder panel, enter an absolute path to specify the location of this Topaz for Java Performance Agent installation, or press Enter to accept the default path.
  15. On the Topaz for Java Performance Agent panel:

    • Enter the Topaz for Java Performance Manager host, or press Enter to accept the default.
    • Enter the Topaz for Java Performance Service port, or press Enter to accept the default.

    The Ready to Install panel appears.

  16. Review the displayed entries for the Install location, Topaz for Java Performance Manager host, and the Topaz for Java Performance Service port.
  17. Enter back to return to the previous panels to change any entries.
  18. Review the display of any changes, and press Enter to begin the installation.
    The system displays Installing and displays RUNNING in the lower-right corner for a few seconds.
  19. When the system requests INPUT, press Enter
    The Installation Complete panel appears.
  20. Take note of the following for this Topaz for Java Performance Agent installation:
    • Agent Install location path
    • Topaz for Java Performance Manager host
    • Topaz for Java Performance Service port
  21. Press Enter to exit the Topaz for Java Performance Agent installer.

Post-installation

After you successfully complete the Topaz for Java Performance Agent installation procedure, do the following:

  1. The Agent is the licensed Topaz for Java Performance component. Configure a Host Connection in CES for BMC AMI License Management System (LMS) license(s) for Topaz for Java Performance Agents.
  2. Define a Host Communications Interface (HCI) with licenses available on the LPAR where you plan to use Topaz for Java Performance Agents.
  3. To use the Topaz for Java Performance Agent, the following parameter must be added to the command line used to launch your Java installation: java -javaagent:<install-dir>/TopazJavaAgent.jar
    where: <install-dir> is the directory where the Topaz for Java   

    Performance Agent is installed.

    It is recommended that this parameter be placed immediately after the ‘java’ command.

    For Web Sphere usage, update the "Generic JVM arguments" to include the -javaagent parameter.

    As well, review the server policy file to ensure the Topaz for Java Performance has the required security permissions to access required MXBeans and data.

  4. For WebSphere usage, update the Generic JVM arguments to include the -javaagent parameter. Also, review the server policy file to be sure that the Topaz for Java Performance has the required security permissions to access required MXBeans and data.
  5. In order to initiate any performance measurements, install at least one agent per LPAR.

 

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