1. Installing and Configuring Oracle Application Performance Monitoring
  2. Install and Configure APM Java Agents on Websphere Application Server

3 Install and Configure APM Java Agents on Websphere Application Server

Here are the requirements and instructions to install APM Java Agent on a Websphere Application Server.

Websphere: Requirements and Installation Instructions

Prerequisites for Deploying APM Java Agent on a WebSphere Application Server

  • Supported versions:

    • WebSphere Application Server 8.5 and 9.0

  • JDK version 1.7 or above. If you are using JDK 1.6, either use a JDK 1.6 that supports TLS 1.2 security protocol, or connect to OMC through a Gateway.

  • If the JDK version you are running doesn't support TLS 1.2 security protocol, refer to My Oracle Support Doc ID 2703411.1 before proceeding with the APM agent installation.

  • Other considerations:

    • The machine hosting the WebSphere Application Server should be able to establish an HTTPS connection either directly or indirectly (using a proxy server or an Oracle Management Cloud gateway) to Oracle Management Cloud. For more information about Oracle Management Cloud gateway, see Install a Gateway.

    • The HTTPS connection must use TLS 1.2 security protocol.

    • The install user of APM Java Agent should be the same as the WebSphere Application Server user.

    • The WebSphere Application Server user should have read and write permissions to the directories that host the APM Java Agent, as well as the WebSphere Application Server Home.

Set the WAS_HOME Variable

Set the WAS_HOME variable to point to the WebSphere Server domain directory.

  • If you're using a Bash shell:

    export WAS_HOME=<WebSphere Server Domain>

  • If you're using a C shell:

    setenv WAS_HOME "<WebSphere Server Domain>"

Deploy a Gateway (Optional)

Gateway is not a mandatory component while deploying Oracle Application Performance Monitoring; you can use a gateway in the following scenarios:

  • If you have an application server that does not support Transport Layer Security (TLS) protocol 1.2

  • If you have older versions of Java Application Servers with JDK less than 1.7 (for example, Oracle WebLogic 10.3.6)

For instructions on how to deploy a gateway, see Install a Gateway.

Set the Gateway Variables (Optional)

Set the values for Gateway host and port.

  • If you're using a Bash shell:

    export GW_HOST=<Gateway Host Name>
export GW_PORT=<Gateway Port>

  • If you're using a C shell:

    setenv GW_HOST "<Gateway Host Name>"
setenv GW_PORT "<Gateway Port>"

If you are using more than one gateway, use the -additional-gatewaysoption with the provisioning script.

Download the APM Java Agent Software for Websphere

  1. On the Oracle Management Cloud home page, click the Oracle Management Cloud Navigation icon on the top-left corner to view the Management Cloud navigation pane.

  2. Select Administration and Agents.

  3. On the Oracle Management Cloud Agents page, click the Action Menu on the top right corner of the page and select Download Agents.

    The Agent Software Download page is displayed.

  4. From the Agent Type drop-down list, select APM Agent.

  5. Click APM Java Agent.

  6. Extract the contents of the installer ZIP file.

  7. Create a registration key that will be used during the time of installing a new agent. Oracle Application Performance Monitoring Cloud Service verifies this key before accepting any data sent by APM Java Agent deployed on your on-premises hosts. For more information about creating a registration key, see Manage Registration Keys.

Install and Provision APM Java Agent on WebSphere

  • Before you install the APM Java Agent, log in to the machine running the application server as the user identity your WebSphere runs as.

  • The application server user should have Read-Write access to the APM Java Agent directories.

To install and provision the APM Java Agent:
  1. Navigate to the directory where you downloaded the APM Java Agent software.
  2. Run the provisioning script as per your installation preference:
    Installation Preference Provisioning Script
    Windows Basic Installation 
    ProvisionApmJavaAsAgent.cmd /d ${WAS_HOME} /no-wallet

    For example: ProvisionApmJavaAsAgent.cmd /d "C:\ibm\WebSphere\AppServer" /no-wallet
    Linux Basic Installation 
    chmod +x ProvisionApmJavaAsAgent.sh
./ProvisionApmJavaAsAgent.sh -d ${WAS_HOME} -no-wallet
    Silent Installation 
    chmod +x ProvisionApmJavaAsAgent.sh
./ProvisionApmJavaAsAgent.sh -d ${WAS_HOME}-no-prompt -no-wallet

    With Gateway in a Linux Environment

    If you are using more than one gateway, use the -additional-gateways option. 

    chmod +x ProvisionApmJavaAsAgent.sh
./ProvisionApmJavaAsAgent.sh -d ${WAS_HOME} -no-wallet gateway-host {gw_host_value}, -gateway-port {gw_port_value} 
-additional-gateways https://<gw_host_1>:<gw_port_1>,https://<gw_host_2>:<gw_port_2>

    With Gateway in a Windows Environment

    If you are using more than one gateway, use the -additional-gateways option. 

    ProvisionApmJavaAsAgent.cmd /d ${WAS_HOME} /no-wallet gateway-host {gw_host_value} /gateway-port {gw_port_value} 
/additional-gateways https://<gw_host_1>:<gw_port_1>,https://<gw_host_2>:<gw_port_2>
    In a Proxy Environment 
    chmod +x ProvisionApmJavaAsAgent.sh
./ProvisionApmJavaAsAgent.sh -d ${WAS_HOME} -no-wallet -ph {http_proxy_host} -pp {http_proxy_port} -pt {http_proxy_auth_token}

    • -d is the absolute path of the home directory of your WebSphere installation. The APM Java Agent will be installed under this directory.

    • -ph {http_proxy_host} (Optional) — the proxy server’s host name.

    • -pp {http_proxy_port} (Optional) — the proxy server’s port.

    • -pt {http_proxy_auth_token}(Optional) — the authorization token that the agent will use if the proxy server requires authentication. This parameter will be passed literally as the proxy authorization header to the proxy server.

      If you are using HTTP Basic authentication, it is recommended that you omit this parameter. For details on HTTP Basic authentication, see Generate Proxy Token. You can also specify the proxy wallet entry or NTLM credentials token in the following format: domain/username:password. For example: exampledomain/sampleuser:welcome

    The command line displays your tenant name and the value you specified.
  3. When prompted, provide the value of the registration key that you've created or downloaded earlier.
    If you are running the provisioning script with the -no-prompt option, create a text file containing the value of registration key, and provide the path to the file.

    Example: ./ProvisionApmJavaAsAgent.sh -d mydir -no-prompt < regkey.txt where regkey.txt contains a single line with the registration key.

  4. Review the values and confirm. To change the values, enter n and run the script again with new values. 
  5. To proceed with the installation, enter y.
    The APM Java Agent is installed.
Provision APM Java Agent with Offline Installer

You can install and provision the APM Java Agent from an offline installer that you have received over email.

To install from the emailed ZIP, the provisioning script needs to download the configuration file from Oracle Management Cloud. Specify these additional options while running the provisioning script:

Option Description
-tenant-id The Oracle Management Cloud tenant name.
-omc-server-url The URL of the Oracle Management Cloud server. Example: https://omchost:port

Modify the Startup Script of Your WebSphere Server

To modify the server.policy startup script of your WebSphere server:
  1. From your WebSphere Admin console, click the Servers tab and select the server on which you want to provision the APM Java Agent.
  2. Expand Java and Process Management tab and select Process Definition.
  3. Under Additional Properties tab, select Java Virtual Machine.
  4. In the Generic JVM arguments field, add the following line to —javaagent and -Dws.ext.dirs flags:
    -javaagent:\$WAS_HOME/apmagent/lib/system/ApmAgentInstrumentation.jar -Dws.ext.dirs=\$WAS_HOME/apmagent/lib/agent/ApmEumFilter.jar
  5. Make a copy of your server.policy file:
    % cd $WAS_HOME/properties
% cp server.policy server.policy.orig
  6. Using a text editor, edit the original server.policy file:
    grant codeBase "file:$WAS_HOME/apmagent/-"
{
permission java.security.AllPermission;
};
  7. From your WebSphere administration console, stop and start the WebSphere server. You can also use the command line:
    cd $WAS_HOME/bin
./stopServer.sh <servername>
./startServer.sh <servername>

Verify APM Java Agent Installation

See Verify APM Java Agent Installation.