Oracle Cloud Installing and Configuring Oracle Application Performance Monitoring

Transcription

1 Oracle Cloud Installing and Configuring Oracle Application Performance Monitoring E December 2017

2 Oracle Cloud Installing and Configuring Oracle Application Performance Monitoring, E Copyright 2015, 2017, Oracle and/or its affiliates. All rights reserved. Primary Author: Oracle Corporation Contributors: Oracle Corporation This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agencyspecific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government. This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group. This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

3 Contents Preface Audience Related Resources Conventions vi vi vi 1 Setting Up Oracle Application Performance Monitoring Setting Up APM Java Agents 1-1 Prerequisites for Deploying an APM Java Agent 1-1 Setting up Oracle Application Performance Monitoring on Oracle WebLogic Server 1-4 Overview of Deploying APM Java Agent on an Oracle WebLogic Server 1-4 Preparing to Deploy APM Java Agent on Oracle WebLogic Server 1-5 Downloading the APM Java Agent Software for Oracle WebLogic Server 1-6 Installing and Provisioning APM Java Agent on Oracle WebLogic Server 1-7 Invoking the APM Java Agent While Starting your Oracle WebLogic Server 1-9 Installing and Provisioning APM Java Agent on Oracle WebLogic Server on Microsoft Windows 1-11 Provisioning APM Java Agent on PeopleSoft 1-13 Setting up Oracle Application Performance Monitoring on Apache Tomcat 1-14 Preparing to Deploy APM Java Agent on Apache Tomcat 1-14 Downloading the APM Java Agent Software for Tomcat 1-15 Installing and Provisioning APM Java Agent on Apache Tomcat 1-16 Modifying the Startup Script of Your Apache Tomcat Server 1-18 Setting up Oracle Application Performance Monitoring on JBoss 1-18 Preparing to Deploy APM Java Agent on JBoss 1-18 Downloading the APM Java Agent Software for JBoss 1-19 Installing and Provisioning APM Java Agent on JBoss 1-20 Modifying the Startup Script of Your JBoss Server 1-22 Installing and Provisioning APM Java Agent on JBoss on Microsoft Windows 1-24 Setting up Oracle Application Performance Monitoring on WebSphere 1-25 Preparing to Deploy APM Java Agent on WebSphere 1-25 iii

4 Downloading the APM Java Agent Software for WebSphere 1-26 Installing and Provisioning APM Java Agent on WebSphere 1-26 Modifying the Startup Script of Your WebSphere Server 1-28 Setting up Oracle Application Performance Monitoring on Jetty 1-29 Preparing to Deploy APM Java Agent on Jetty 1-29 Downloading the APM Java Agent Software for Jetty 1-30 Installing and Provisioning APM Java Agent on Jetty 1-30 Modifying the Startup Script of Your Jetty Server 1-32 Verifying APM Java Agent Installation 1-33 Examining the APM Java Agent Logs 1-33 Verifying the Installation Using the Oracle Application Performance Monitoring Web User Interface 1-34 Verifying the APM Java Agent Directory Structure 1-34 Setting Up APM Node.js Agents 1-36 Prerequisites for Deploying APM Node.js Agent 1-36 Preparing to Deploy APM Node.js Agent 1-36 Downloading the APM Node.js Agent Software 1-37 Installing and Provisioning APM Node.js Agent 1-38 Starting your Node.js Application 1-40 Verifying that the APM Node.js Agent is Monitoring the Application 1-41 Configuring Browser Injection with APM Node.js Agent 1-42 Configuring Specific URLs for Oracle Management Cloud Services 1-43 Setting Up APM.Net Agents 1-43 Prerequisites for Deploying APM.Net Agent 1-44 Preparing to Deploy APM.Net Agent 1-44 Downloading the APM.NET Agent Software 1-45 Installing APM.Net Agent 1-46 Verifying APM.Net Agent Installation 1-46 Configuring APM.Net Agent Parameters 1-47 Disabling Monitoring by APM.Net Agent 1-51 Setting Up APM Ruby Agents 1-51 Prerequisites for Deploying APM Ruby Agent 1-52 Preparing to Deploy APM Ruby Agent 1-52 Downloading the APM Ruby Agent Software 1-54 Installing and Provisioning APM Ruby Agent 1-55 Verifying that the APM Ruby Agent is Monitoring the Application 1-56 Setting up APM on Mobile Clients 1-57 Deploying APM Mobile Agent on ios 1-57 Deploying APM Mobile Agent on Android 1-61 Setting up APM on Containers iv

5 Setting up APM on Docker 1-62 Troubleshooting the Deployment of Application Performance Monitoring 1-64 Associating Application Servers to a Database Automatically 1-67 Configuring Attributes for End User Monitoring 1-71 Adding Application Classifications 1-72 Transferring Data through Reverse Proxy Managing APM Agents Upgrading APM Java Agents 2-1 Removing APM Java Agents 2-1 Task 1: Disable the APM Java Agent in the WebLogic Server Domain 2-2 Task 2: Delete the APM Java Agent Software from the WebLogic Server Domain 2-2 Task 3: Remove APM Java Agent References from Oracle Management Cloud 2-2 Upgrading APM.Net Agent 2-3 Removing APM.Net Agent 2-3 Task 1: Remove APM.Net Agent 2-3 Task 2: Remove APM.NET Agent References from Oracle Management Cloud 2-3 Upgrading APM Node.js Agents 2-4 Removing APM Node.js Agents 2-5 Task 1: Remove the APM Node.js Agent from the application 2-5 Task 2: Delete APM Node.js files from the Application folder 2-6 Task 3: Uninstall APM Node.js Agent 2-6 A Syntax for Using the APM Java Agent Installation Script v

6 Preface Preface Audience Oracle Application Performance Monitoring provides a platform for monitoring and managing your applications. This guide, Installing and Configuring Oracle Application Performance Monitoring provides instructions on deploying Oracle Application Performance Monitoring. Topics: Audience Related Resources Conventions Related Resources Conventions Installing and Configuring Oracle Application Performance Monitoring is intended for administrators who want to deploy and manage APM Agents. For more information, see these Oracle resources: About Oracle Application Performance Monitoring This table describes the text conventions used in this document. Convention boldface italic monospace Meaning Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary. Italic type indicates the book titles, emphasis, or placeholder variables for which you supply particular values. Monospace type indicates commands within a paragraph. URLs, code in examples, text that appears on the screen, or text that you enter. vi

7 1 Setting Up Oracle Application Performance Monitoring Oracle Application Performance Monitoring is a Platform as a Service (PaaS) based solution that provides deep visibility into the performance of your application, from end user to application logs. The service integrates user experience information and application metrics along with log data analytics. Topics: Setting Up APM Java Agents Setting Up APM.Net Agents Setting Up APM Node.js Agents Setting Up APM Ruby Agents Setting up APM on Mobile Clients Setting up APM on Containers Setting Up APM Java Agents APM Java Agent can be deployed on various application servers. Topics: Setting up Oracle Application Performance Monitoring on Oracle WebLogic Server Setting up Oracle Application Performance Monitoring on Apache Tomcat Setting up Oracle Application Performance Monitoring on JBoss Setting up Oracle Application Performance Monitoring on WebSphere Setting up Oracle Application Performance Monitoring on Jetty Verifying APM Java Agent Installation Prerequisites for Deploying an APM Java Agent The section covers the key considerations and prerequisites for deploying APM Java Agents. Certification Guidelines for Deploying APM Java Agents CPU Usage Guidelines for Deploying APM Java Agents Prerequisites for Deploying APM Java Agent on an Oracle WebLogic Server Prerequisites for Deploying APM Java Agent on an Apache Tomcat Server Prerequisites for Deploying APM Java Agent on a JBoss Server 1-1

8 Setting Up APM Java Agents Prerequisites for Deploying APM Java Agent on a WebSphere Application Server Prerequisites for Deploying APM Java Agent on a Jetty Server Certification Guidelines for Deploying APM Java Agents Starting from Oracle Management Cloud 1.21, the APM Java Agent ships with a root Verisign certificate in its config directory and uses it to communicate with Oracle Management Cloud. Make sure that this certificate remains on the agent's certificate path for proper communication across Oracle Management Cloud versions. CPU Usage Guidelines for Deploying APM Java Agents The following tables lists the CPU usage guidelines for deploying APM Java agents on different platforms: Metrics - Without Agent Oracle WebLogic Server With Agent Without Agent Apache Tomcat With Agent Without Agent JBoss With Agent CPU Usage 2.11% 2.73% 7.20% 8.40% 1.90% 3.23% Prerequisites for Deploying APM Java Agent on an Oracle WebLogic Server Supported versions of Oracle WebLogic Server: Oracle WebLogic Server Oracle WebLogic Server Oracle WebLogic Server , also known as Oracle WebLogic Server 11g Release 1 Note: In the host running Oracle WebLogic Server, you can run the following command from $WLS_HOME/server/lib to check the Oracle WebLogic Server version: java -cp weblogic.jar weblogic.version Unzip Other considerations: The machine hosting the Oracle WebLogic Server should be able to establish an HTTPS connection (either over a proxy server or not) to Oracle Management Cloud. The install user of APM Java Agent should be the same as the Oracle WebLogic Server user. The Oracle WebLogic Server user should have read and write permissions to the directories that host the APM Java Agent. Prerequisites for Deploying APM Java Agent on an Apache Tomcat Server Supported versions of Apache Tomcat Server: 1-2

9 Setting Up APM Java Agents 7 8 TomEE Unzip Other considerations: The machine hosting the Apache Tomcat Server should be able to establish an HTTPS connection (either over a proxy server or not) to Oracle Management Cloud. The install user of APM Java Agent should be the same as the Apache Tomcat user. The Apache Tomcat Server user should have read and write permissions to the directories that host the APM Java Agent, as well as the CATALINA_BASE APM Java Agent logging and config directories if different from CATALINA_HOME. If you are installing the APM Java Agent on minor Tomcat version or earlier, please add the following command line option to enable local: jmx: -Dcom.sun.management.jmxremote Prerequisites for Deploying APM Java Agent on a JBoss Server Supported versions: JBoss EAP 6.1 Wildfly Unzip Other considerations: The machine hosting the JBoss Server should be able to establish an HTTPS connection (either over a proxy server or not) to Oracle Management Cloud. The install user of APM Java Agent should be the same as the JBoss user. The JBoss Server user should have read and write permissions to the directories that host the APM Java Agent, as well as the JBOSS Home. Prerequisites for Deploying APM Java Agent on a WebSphere Application Server Supported versions: WebSphere Application Server 8.5 Unzip Other considerations: The machine hosting the WebSphere Application Server should be able to establish an HTTPS connection (either over a proxy server or not) to Oracle Management Cloud. 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. 1-3

10 Setting Up APM Java Agents Prerequisites for Deploying APM Java Agent on a Jetty Server Supported versions: Jetty Server 7, 8, and 9 Unzip You can install one APM Agent in one instance of Jetty. Other considerations: The machine hosting the Jetty Server should be able to establish an HTTPS connection (either over a proxy server or not) to Oracle Management Cloud. The install user of APM Java Agent should be the same as the Jetty Server user. The Jetty Server user should have read and write permissions to the directories that host the APM Java Agent, as well as the Jetty Server Home. Setting up Oracle Application Performance Monitoring on Oracle WebLogic Server Complete the following tasks sequentially, to set up the APM Java Agent on Oracle WebLogic Server. Overview of Deploying APM Java Agent on an Oracle WebLogic Server Preparing to Deploy APM Java Agent on Oracle WebLogic Server Downloading the APM Java Agent Software for Oracle WebLogic Server Installing and Provisioning APM Java Agent on Oracle WebLogic Server Invoking the APM Java Agent While Starting your Oracle WebLogic Server Overview of Deploying APM Java Agent on an Oracle WebLogic Server An APM Java Agent is deployed on the Oracle WebLogic Managed Server where the application to be monitored is installed. The APM Java Agent collects and shares data about the performance of the application to the Oracle Application Performance Monitoring web user interface, from where you can closely monitor your application s performance. This image depicts how an APM Java Agent is deployed on the Oracle WebLogic Managed Server. 1-4

11 Setting Up APM Java Agents Here are some details about the inbound and outbound traffic of the APM Java Agent. Inbound Traffic: The APM Java Agent doesn't open any ports to listen on. Outbound Traffic: The only outbound traffic the APM Java Agent initiates is sent to Oracle Management Cloud over HTTPS protocol. For information about how to deploy Oracle Application Performance Monitoring, see Setting Up Oracle Application Performance Monitoring. Preparing to Deploy APM Java Agent on Oracle WebLogic Server Before you can download and install an APM Java Agent, ensure that you set the values for these variables. Setting the DOMAIN_HOME Variable Set the DOMAIN_HOME variable to point to the Oracle WebLogic Server domain. If you're using a Bash shell: export DOMAIN_HOME=<WebLogic Server Domain> If you're using a C shell: setenv DOMAIN_HOME "<WebLogic Server Domain>" 1-5

12 Setting Up APM Java Agents Deploying the Gateway (Optional) Gateway is not a mandatory component while deploying Oracle Application Performance Monitoring. Use the 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.net IIS servers and Java Application Servers with JDK less than 1.7 (for example, Oracle WebLogic ) For instructions on how to deploy the Gateway, see Installing a Gateway. Setting 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>" Downloading the APM Java Agent Software for Oracle WebLogic Server Download the APM Java Agent software from the Oracle Management Cloud Agents page, and install the agent. Download the APM Java Agent software to a shared directory that can be accessed by all the Oracle WebLogic managed servers in the application server domain where APM Java Agents will be deployed. To download the APM Java Agent software: 1. On the Oracle Management Cloud home page, click the Oracle Management Cloud navigation icon on the top-left corner to view the Oracle Management Cloud navigation pane. 2. Select Administration and Agents. 3. On the Oracle Management Cloud Agents page, click the Download tab. The Agent Software Download page is displayed. 4. From the Agent Type drop-down list, select APM Agent. 5. Click APM Java Agent. This downloads the agent software ZIP file to the selected location. 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 Managing Registration Keys. You can also install and provision the APM Java Agent from an offline installer that you have received over

13 Setting Up APM Java Agents Installing and Provisioning APM Java Agent on Oracle WebLogic Server After you have downloaded and extracted the agent software, install and provision the APM Java Agent in your application server domain. Before you install the APM Java Agent, log in to the machine running the application server as a user who installed the application server. The application server user should have Read-Write access to the APM Java Agent directories. Provisioning APM Java Agent 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 Basic Installation Provisioning Script chmod +x ProvisionApmJavaAsAgent.sh./ProvisionApmJavaAsAgent.sh -d ${DOMAIN_HOME} Silent Installation chmod +x ProvisionApmJavaAsAgent.sh./ProvisionApmJavaAsAgent.sh -d ${DOMAIN_HOME} -no-prompt Without Oracle Wallet An Oracle Wallet is a passwordprotected container used to store authentication and signing credentials. See Using Oracle Wallet Manager for details. chmod +x ProvisionApmJavaAsAgent.sh./ProvisionApmJavaAsAgent.sh -d ${DOMAIN_HOME} -no-wallet With Gateway chmod +x ProvisionApmJavaAsAgent.sh./ProvisionApmJavaAsAgent.sh -d ${DOMAIN_HOME} -gatewayhost, -gateway-port, -additional-gateways With Gateway and without Oracle Wallet chmod +x ProvisionApmJavaAsAgent.sh./ProvisionApmJavaAsAgent.sh -d ${DOMAIN_HOME} -gatewayhost, -gateway-port, -additional-gateways -no-wallet In a Proxy Environment with Oracle Wallet chmod +x ProvisionApmJavaAsAgent.sh./ProvisionApmJavaAsAgent.sh -d ${DOMAIN_HOME} -ph {http_proxy_host} -pp {http_proxy_port} -pt {http_proxy_auth_token} 1-7

14 Setting Up APM Java Agents Installation Preference In a Proxy Environment without Oracle Wallet Provisioning Script chmod +x ProvisionApmJavaAsAgent.sh./ProvisionApmJavaAsAgent.sh -d ${DOMAIN_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 the Oracle WebLogic Server domain. 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 Generating 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. ProvisionApmJavaAsAgent.shSyntax for Using the Installation Script Provisioning APM Java Agent with Offline Installer You can install and provision the APM Java Agent from an offline installer that you have received over . To install from the ed ZIP, the provisioning script needs to download the configuration file from Oracle Management Cloud. Specify these additional options while running the provisioning script: Option -tenant-id -omc-server-url Description The Oracle Management Cloud tenant name. The URL of the Oracle Management Cloud server. Example: 1-8

15 Setting Up APM Java Agents Generating Proxy Token The APM Java agent can generate a token for HTTP Basic authentication using a username and password instead of a token that is user-generated. Once the user provides a user name and password as property file entries, the APM Java agent will automatically generate a HTTP Basic authentication token. To get HTTP Basic authentication token generated by the APM Java Agent: 1. In the <agent>/config/agenthttpbasic.properties file, specify the following properties: oracle.apmaas.agent.http.proxy.basic.username = myhttpbasicproxyuser oracle.apmaas.agent.http.proxy.basic.password = myhttpbasicproxypass Note: If along with the above properties, an authentication is also specified with the property oracle.apmaas.agent.http.proxy.token, it will take precedence over the username and password properties. Setting the NTLM Workstation APM Java agent uses the user name and password to generate a HTTP Basic authentication token, and authenticate the user. Administrators can set the Microsoft Windows NT LAN Manager (NTLM) workstation in case your proxy has this requirement. To set the NTLM workstation: Add the following property to the AgentStartup properties file: oracle.apmaas.agent.transport.proxy.ntlm.workstation Configuring NTLM Proxy Authentication in the APM Java Agent You can configure NTLM proxy authentication in the APM Java agent to support NTLM authentication. To configure NTLM proxy authentication: 1. In the AgentHttpBasic.properties file, specify the oracle.apmaas.agent.http.proxy.token property with a value in this format: domain/username:password Example: oracle.apmaas.agent.http.proxy.token = testdomain/user1:hello Invoking the APM Java Agent While Starting your Oracle WebLogic Server There are three ways to invoke the APM Java agent when your Oracle WebLogic server starts up. Modifying startweblogic.sh: This will start APM Agent on startup of the domain s Oracle WebLogic administration server. Modifying startmanagedweblogic.sh: This will start APM Agent on startup of the Oracle WebLogic managed servers on the domain. 1-9

16 Setting Up APM Java Agents Using the administration console: If you are using Node Manager, use the Oracle WebLogic Server administration console to configure the servers you want to add the APM Agent to. To invoke APM Agent on the domain s Oracle WebLogic administration server by modifying the startweblogic.sh script of your Oracle WebLogic Server domain: 1. Make a copy of your startweblogic.sh file: % cd $DOMAIN_HOME/bin % cp startweblogic.sh startweblogic.sh.orig 2. Using a text editor, edit the original script to add the -javaagent option to the set of Java options: a. Add the following line after the setdomainenv.sh call: JAVA_OPTIONS="${JAVA_OPTIONS} -javaagent:${domain_home}/apmagent/lib/ system/apmagentinstrumentation.jar" Here is an example of the startweblogic.sh file with the above -javaagent option added. DOMAIN_HOME=<path to your domain home>. ${DOMAIN_HOME}/bin/setDomainEnv.sh $* JAVA_OPTIONS="${JAVA_OPTIONS} -javaagent:${domain_home}/apmagent/lib/system/ ApmAgentInstrumentation.jar" JAVA_OPTIONS="${JAVA_OPTIONS} - Djava.util.logging.manager=oracle.core.ojdl.logging.ODLLogManager" SAVE_JAVA_OPTIONS="${JAVA_OPTIONS}" SAVE_CLASSPATH="${CLASSPATH}" 3. Restart the Oracle WebLogic Server: % cd $DOMAIN_HOME/bin %./stopweblogic.sh % cd.. % nohup./startweblogic.sh >& startup.log & You can check the entries present in the $DOMAIN_HOME/startup.log file to verify that the Oracle WebLogic Server has started. Note: Note that the $DOMAIN_HOME version of the startweblogic.sh is used, even though you edited the $DOMAIN_HOME/bin version. Invoking the startweblogic.sh script from one level higher (from $DOMAIN_HOME) invokes the script from a lower level (from $DOMAIN_HOME/bin). However, the stopweblogic.sh script will be called from the $DOMAIN_HOME/bin directory. 4. If you have any managed Oracle WebLogic application servers, restart them. To invoke APM Agent on the Oracle WebLogic managed servers by modifying the startmanagedweblogic.sh script of your Oracle WebLogic Server domain: You can choose to monitor only the managed servers through Oracle Application Performance Monitoring, without monitoring the administration server. In such a case, make the modifications listed above in the bin/startmanagedweblogic.sh file instead of bin/startweblogic.sh file. 1-10

17 Setting Up APM Java Agents 1. Make a copy of your startmanagedweblogic.sh file: % cd $DOMAIN_HOME/bin % cp startmanagedweblogic.sh startmanagedweblogic.sh.orig 2. Using a text editor, edit the file startmanagedweblogic.sh, and locate the DOMAIN_HOME definition in the file: DOMAIN_HOME=<path_to_domain_home> 3. Add the below JAVA_OPTIONS line right after the DOMAIN_HOME definition: DOMAIN_HOME=<path to your domain home> JAVA_OPTIONS="${JAVA_OPTIONS} -javaagent:${domain_home}/apmagent/lib/system/ ApmAgentInstrumentation.jar" 4. Restart the Oracle WebLogic Server. To invoke APM Agent using the administration console: If your servers are started using the Node Manager, specify the -javaagent parameter in the management console: Environment/Servers/Configuration/Server Start, in the Argument field. Installing and Provisioning APM Java Agent on Oracle WebLogic Server on Microsoft Windows You can install and provision the APM Java Agent on your Oracle WebLogic domain installed on a Microsoft Windows machine. Before you install: Download the installer. See Downloading the APM Java Agent Software for Oracle WebLogic Server. Log in to the machine running the application server, as the same user who installed the application server. Ensure that the application server user has Read-Write access to the APM Java Agent directories. To install and provision APM Java Agent on Oracle WebLogic Server on Microsoft Windows: 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 Basic Installation Provisioning Script set DOMAIN_HOME=<path to domain home>provisionapmjavaasagent.cmd /d %DOMAIN_HOME% / Silent Installation set DOMAIN_HOME=<path to domain home>provisionapmjavaasagent.cmd /d %DOMAIN_HOME% /no-prompt 1-11

18 Setting Up APM Java Agents Installation Preference Provisioning Script Without Oracle Wallet An Oracle Wallet is a passwordprotected container used to store authentication and signing credentials. See Using Oracle Wallet Manager for details. set DOMAIN_HOME=<path to domain home>provisionapmjavaasagent.cmd /d %DOMAIN_HOME% /no-wallet With Gateway set DOMAIN_HOME=<path to domain home>provisionapmjavaasagent.cmd /d %DOMAIN_HOME% /gatewayhost, /gateway-port, /additional-gateways With Gateway and without Oracle Wallet set DOMAIN_HOME=<path to domain home>provisionapmjavaasagent.cmd /d %DOMAIN_HOME% /gatewayhost, /gateway-port, /additional-gateways /no-wallet In a Proxy Environment with Oracle Wallet set DOMAIN_HOME=<path to domain home>provisionapmjavaasagent.cmd /d %DOMAIN_HOME% /ph {http_proxy_host} /pp {http_proxy_port} /pt {http_proxy_auth_token} In a Proxy Environment without Oracle Wallet set DOMAIN_HOME=<path to domain home>provisionapmjavaasagent.cmd /d %DOMAIN_HOME% /nowallet /ph {http_proxy_host} /pp {http_proxy_port} /pt {http_proxy_auth_token} -d is the absolute path of the home directory of the Oracle WebLogic Server domain. 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. 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.cmd -d mydir -no-prompt < regkey.txt, where regkey.txt contains a single line with the registration key. 4. Provision the APM Java agent. This enables the APM agent to be invoked when you restart the Oracle WebLogic Server. 1-12

19 Setting Up APM Java Agents a. Make a backup copy of your startweblogic.cmd file: cd %DOMAIN_HOME%\bin cp startweblogic.cmd startweblogic.cmd.orig b. Using a text editor, edit the startweblogic.cmd file and add the -javaagent option to the set of JAVA_OPTIONS. Add the following line after the setdomainenv.cmd call: set JAVA_OPTIONS=%JAVA_OPTIONS% -javaagent:%domain_home%\apmagent\lib\system \ApmAgentInstrumentation.jar 5. Restart your Oracle WebLogic application server: % cd %DOMAIN_HOME%\bin % stopweblogic.cmd % cd.. % startweblogic.cmd > startup.log Note: Notice that the %DESTINATION% version of startweblogic.cmd is used, even though you edited the %DESTINATION%/bin version. Invoking the command from one level higher (from %DESTINATION%) invokes the command from a lower level (from %DESTINATION%/bin). However, the stopweblogic.cmd command will be called from the %DESTINATION%/bin directory. 6. If you have any managed Oracle WebLogic application servers, restart them: % cd %DOMAIN_HOME%\bin % stopmanagedweblogic.cmd {SERVER_NAME} {ADMIN_URL} {USER_NAME} {PASSWORD} % startmanagedweblogic.cmd {SERVER_NAME} {ADMIN_URL} > {SERVER_NAME}.log Note: If you are running Oracle WebLogic Server as a Microsoft Windows service, add the -javaagent flag to the JAVA_OPTIONS of your custom registration script, and register your WebLogic Windows service again. Provisioning APM Java Agent on PeopleSoft You can install and provision APM Java Agent on your PeopleSoft environment. Prerequisites: PeopleSoft running on PeopleTools 8.55 with WebLogic container for PeopleSoft UI PeopleSoft Internet Architecture (PIA) Download the APM Java Agent software. See Downloading the APM Java Agent Software. Install the APM Java Agent software. See Installing and Provisioning APM Java Agent. After installing the APM Java Agent software, perform these steps to provision the APM Java Agent on PeopleSoft: 1-13

20 Setting Up APM Java Agents 1. Navigate to the PIA Domain Administration Menu: a. From the shell prompt, start the psadmin utility with the following command: psadmin b. Select 4 for Web (PIA) Server. c. Select 1 to administer a domain. d. Select the PIA domain where to install the APM agent. 2. Edit the configuration files: a. View the list of configuration files to edit, by executing command 5. b. Select 1 to edit the setenv file. The setenv file will open in a Vi editor. c. Search for the corresponding JAVA_OPTIONS_<Operating System> variable and add the following option: JAVA_OPTIONS_<Operating System>="${JAVA_OPTIONS_<Operating System} - javaagent:${domain_home}/apmagent/lib/system/apmagentinstrumentation.jar" where <Operating System> is the operating system that PeopleSoft PIA runs on. d. Save the changes made to the setenv file and exit the Vi editor, to see the list of configuration files. e. Type q to exit this menu, and to see the PIA Administration menu. 3. Reboot the PIA domain: a. Navigate to the PIA Domain Administration menu. Refer step 1. b. Select 2 to shut down the domain. c. Select 3 to get the status of the domain to check if it is still running. d. Select 1 to boot this domain to complete the restart of the PIA domain. Setting up Oracle Application Performance Monitoring on Apache Tomcat Complete the following tasks sequentially to set up the APM Java Agent on Apache Tomcat. Preparing to Deploy APM Java Agent on Apache Tomcat Downloading the APM Java Agent Software for Tomcat Installing and Provisioning APM Java Agent on Apache Tomcat Modifying the Startup Script of Your Apache Tomcat Server Preparing to Deploy APM Java Agent on Apache Tomcat Before you can download and install an APM Java Agent, ensure that you set the values for these variables. Setting the DESTINATION Variable Set the DESTINATION variable to point to the Tomcat destination directory. If you're using a Bash shell: 1-14

21 Setting Up APM Java Agents export DESTINATION=<Tomcat destination directory> If you're using a C shell: setenv DESTINATION "<Tomcat destination directory>" Deploying the Gateway (Optional) Gateway is not a mandatory component while deploying Oracle Application Performance Monitoring. Use the 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.net IIS servers and Java Application Servers with JDK less than 1.7 (for example, Oracle WebLogic ) For instructions on how to deploy the Gateway, see Installing a Gateway. Setting 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>" Downloading the APM Java Agent Software for Tomcat Download the APM Java Agent software from the Oracle Management Cloud Agents page, and install the agent. Download the APM Java Agent software to a shared directory that can be accessed by the application server domain where APM Java Agents will be deployed. To download the APM Java Agent software 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 Download tab. The Agent Software Download page is displayed. 4. From the Agent Type drop-down list, select APM Agent. 5. Click APM Java Agent. This downloads the agent software ZIP file to the selected location. 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 Managing Registration Keys. 1-15

22 Setting Up APM Java Agents You can also install and provision the APM Java Agent from an offline installer that you have received over . Installing and Provisioning APM Java Agent on Apache Tomcat After you have downloaded and extracted the installer, install and provision the APM Java Agent in your application server domain. Before you install the APM Java Agent, log in to the machine running the application server as a user who installed the application server. 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 Basic Installation Provisioning Script cd ${STAGE_DIR} chmod +x ProvisionApmJavaAsAgent.sh./ProvisionApmJavaAsAgent.sh -d ${CATALINA_HOME} chmod +x ProvisionApmJavaAsAgent.sh./ProvisionApmJavaAsAgent.sh -d ${CATALINA_HOME} Silent Installation chmod +x ProvisionApmJavaAsAgent.sh./ProvisionApmJavaAsAgent.sh -d ${CATALINA_HOME}-no-prompt Without Oracle Wallet An Oracle Wallet is a passwordprotected container used to store authentication and signing credentials. See Using Oracle Wallet Manager for details. chmod +x ProvisionApmJavaAsAgent.sh./ProvisionApmJavaAsAgent.sh -d ${CATALINA_HOME} -no-wallet With Gateway chmod +x ProvisionApmJavaAsAgent.sh./ProvisionApmJavaAsAgent.sh -d ${CATALINA_HOME} -gatewayhost, -gateway-port, -additional-gateways With Gateway and without Oracle Wallet chmod +x ProvisionApmJavaAsAgent.sh./ProvisionApmJavaAsAgent.sh -d ${CATALINA_HOME} -gatewayhost, -gateway-port, -additional-gateways -no-wallet In a Proxy Environment with Oracle Wallet chmod +x ProvisionApmJavaAsAgent.sh./ProvisionApmJavaAsAgent.sh -d ${CATALINA_HOME} -ph {http_proxy_host} -pp {http_proxy_port} -pt {http_proxy_auth_token} 1-16

23 Setting Up APM Java Agents Installation Preference In a Proxy Environment without Oracle Wallet Provisioning Script chmod +x ProvisionApmJavaAsAgent.sh./ProvisionApmJavaAsAgent.sh -d ${CATALINA_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 the WebLogic Server domain. 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 Generating 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. ProvisionApmJavaAsAgent.shSyntax for Using the Installation Script Provisioning APM Java Agent with Offline Installer You can install and provision the APM Java Agent from an offline installer that you have received over . To install from the ed ZIP, the provisioning script needs to download the configuration file from Oracle Management Cloud. Specify these additional options while running the provisioning script: Option -tenant-id -omc-server-url Description The Oracle Management Cloud tenant name. The URL of the Oracle Management Cloud server. Example:

24 Setting Up APM Java Agents Modifying the Startup Script of Your Apache Tomcat Server Modify the startup script of your application server to invoke Oracle Application Performance Monitoring when you start your application server. To modify the catalina.sh script of your Tomcat server home: 1. Make a copy of your catalina.sh file: % cd $CATALINA_HOME/bin % cp catalina.sh catalina.sh.orig 2. Using a text editor, edit the original script to add the -javaagent option to the set of CATALINA_OPTS. To send the Tomcat server data to APM Agent, append the following class path, along with ApmAgentInstrumentation.jar to CATALINA_OPTS: CATALINA_OPTS="$CATALINA_OPTS -javaagent:${catalina_home}/apmagent/lib/system/ ApmAgentInstrumentation.jar - Datlassian.org.osgi.framework.bootdelegation=oracle.apmaas.*,sun.*,org.apache.xer ces,org.apache.xerces.*,org.apache.naming,org.apache.naming.*,org.apache.catalina,org.apache.catalina.*,org.apache.tomcat.util.*" The -Datlassian.org.osgi.framework.bootdelgation option is required if you are running an Atlassian Jira application. 3. Restart the Tomcat Servers: % cd $CATALINA_HOME/bin %./shutdown.sh %./startup.sh Setting up Oracle Application Performance Monitoring on JBoss Complete the following tasks sequentially, to set up APM Java Agent on JBoss/ WildFly. Preparing to Deploy APM Java Agent on JBoss Downloading the APM Java Agent Software for JBoss Installing and Provisioning APM Java Agent on JBoss Modifying the Startup Script of Your JBoss Server Preparing to Deploy APM Java Agent on JBoss Before you can download and install an APM Java Agent, ensure that you set the values for these variables. Setting the JBOSS_HOME Variable Set the JBOSS_HOME variable to point to the JBoss home directory. If you're using a Bash shell: export JBOSS_HOME=<JBoss home directory> If you're using a C shell: setenv JBOSS_HOME "<JBoss home directory>" 1-18

25 Setting Up APM Java Agents Deploying the Gateway (Optional) Gateway is not a mandatory component while deploying Oracle Application Performance Monitoring. Use the 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.net IIS servers and Java Application Servers with JDK less than 1.7 (for example, Oracle WebLogic ) For instructions on how to deploy the Gateway, see Installing a Gateway. Setting 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>" Downloading the APM Java Agent Software for JBoss Download the APM Java Agent software from the Oracle Management Cloud Agents page, and install the agent. Download the APM Java Agent software to a shared directory that can be accessed by all the managed servers in the application server domain where APM Java Agents will be deployed. To download the APM Java Agent software: 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 Download tab. The Agent Software Download page is displayed. 4. From the Agent Type dropdown list, select APM Agent. 5. Click APM Java Agent. This downloads the agent software ZIP file to the selected location. 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 Managing Registration Keys. You can also install and provision the APM Java Agent from an offline installer that you have received over

26 Setting Up APM Java Agents Installing and Provisioning APM Java Agent on JBoss After you have downloaded and extracted the installer, install and provision the APM Java Agent in your JBoss/WildFly server domain. Before you install the APM Java Agent, log in to the machine running the application server as a user who installed the application server. 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 Basic Installation Provisioning Script chmod +x ProvisionApmJavaAsAgent.sh./ProvisionApmJavaAsAgent.sh -d ${JBOSS_HOME} Silent Installation chmod +x ProvisionApmJavaAsAgent.sh./ProvisionApmJavaAsAgent.sh -d ${JBOSS_HOME} -no-prompt Without Oracle Wallet An Oracle Wallet is a passwordprotected container used to store authentication and signing credentials. See Using Oracle Wallet Manager for details. chmod +x ProvisionApmJavaAsAgent.sh./ProvisionApmJavaAsAgent.sh -d ${JBOSS_HOME} -no-wallet With Gateway chmod +x ProvisionApmJavaAsAgent.sh./ProvisionApmJavaAsAgent.sh -d ${JBOSS_HOME} -gatewayhost, -gateway-port, -additional-gateways With Gateway and without Oracle Wallet chmod +x ProvisionApmJavaAsAgent.sh./ProvisionApmJavaAsAgent.sh -d ${JBOSS_HOME} -gatewayhost, -gateway-port, -additional-gateways -no-wallet In a Proxy Environment with Oracle Wallet chmod +x ProvisionApmJavaAsAgent.sh./ProvisionApmJavaAsAgent.sh -d ${JBOSS_HOME} -ph {http_proxy_host} -pp {http_proxy_port} -pt {http_proxy_auth_token} 1-20

27 Setting Up APM Java Agents Installation Preference In a Proxy Environment without Oracle Wallet Provisioning Script chmod +x ProvisionApmJavaAsAgent.sh./ProvisionApmJavaAsAgent.sh -d ${JBOSS_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 JBoss 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 Generating 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. ProvisionApmJavaAsAgent.shSyntax for Using the Installation Script Provisioning APM Java Agent with Offline Installer You can install and provision the APM Java Agent from an offline installer that you have received over . To install from the ed ZIP, the provisioning script needs to download the configuration file from Oracle Management Cloud. Specify these additional options while running the provisioning script: Option -tenant-id -omc-server-url Description The Oracle Management Cloud tenant name. The URL of the Oracle Management Cloud server. Example:

28 Setting Up APM Java Agents Modifying the Startup Script of Your JBoss Server Modify the startup script of your application server to invoke Oracle Application Performance Monitoring, when you start your JBoss/WildFly server. To modify the standalone.conf script of your JBoss/WildFly server: 1. Make a copy of your standalone.conf file: % cd \$JBOSS_HOME/bin % cp standalone.conf standalone.conf.orig 2. Using a text editor, edit the original standalone.conf file: a. Search for the text JBOSS_MODULES_SYSTEM_PKGS b. Add the following at the end of its value: oracle.apmaas.agent,oracle.apmaas.repackaged,org.jboss.logmanager c. Example: If your standalone.conf file originally contained JBOSS_MODULES_SYSTEM_PKGS="org.jboss.byteman", it should look like the following after adding to the value: JBOSS_MODULES_SYSTEM_PKGS="org.jboss.byteman,oracle.apmaas.agent,oracle.ap maas.repackaged,org.jboss.logmanager" 3. Move to the end of the standalone.conf file, and add the following Java options as per your the version of your application server. JBoss 9: JAVA_OPTS="$JAVA_OPTS -Djboss.modules.system.pkgs=$JBOSS_MODULES_SYSTEM_PKGS - Djava.awt.headless=true" JAVA_OPTS="$JAVA_OPTS - Djava.util.logging.manager=org.jboss.logmanager.LogManager" JAVA_OPTS="$JAVA_OPTS -Xbootclasspath/p:<JBOSS_HOME>/modules/system/layers/ base/org/jboss/logmanager/main/jboss-logmanager final.jar:<jboss_home>/ modules/system/layers/base/org/jboss/logging/main/jbosslogging final.jar:<jboss_home>/modules/system/layers/base/org/jboss/log4j/ logmanager/main/log4j-jboss-logmanager final.jar:<jboss_home>/modules/com/ oracle/main/oraclepki jar" JAVA_OPTS="$JAVA_OPTS -javaagent:<jboss_home>/apmagent/lib/system/ ApmAgentInstrumentation.jar" JBoss 7: JAVA_OPTS="$JAVA_OPTS -Djboss.modules.system.pkgs=$JBOSS_MODULES_SYSTEM_PKGS - Djava.awt.headless=true" JAVA_OPTS="$JAVA_OPTS - Djava.util.logging.manager=org.jboss.logmanager.LogManager" JAVA_OPTS="$JAVA_OPTS -Xbootclasspath/p:<JBOSS_HOME>/modules/org/jboss/ logmanager/main/jboss-logmanager ga.jar:<jboss_home>/modules/org/jboss/ logmanager/log4j/main/jboss-logmanager-log4j ga.jar:/<jboss_home>/ modules/org/apache/log4j/main/log4j jar:/<jboss_home>/modules/com/oracle/ main/oraclepki jar"java_opts="$java_opts -javaagent:/<jboss_home>/ apmagent/lib/system/apmagentinstrumentation.jar" EAP 6.2: JAVA_OPTS="$JAVA_OPTS -Djboss.modules.system.pkgs=$JBOSS_MODULES_SYSTEM_PKGS - Djava.awt.headless=true" JAVA_OPTS="$JAVA_OPTS

29 Setting Up APM Java Agents Djava.util.logging.manager=org.jboss.logmanager.LogManager" JAVA_OPTS="$JAVA_OPTS -Xbootclasspath/p:<JBOSS_HOME>/modules/system/layers/ base/org/jboss/logmanager/main/jboss-logmanager finalredhat-1.jar:<jboss_home>/modules/system/layers/base/org/jboss/logging/main/ jboss-logging ga-redhat-1.jar:<jboss_home>/modules/system/layers/base/org/ jboss/log4j/logmanager/main/log4j-jboss-logmanager finalredhat-1.jar:<jboss_home>/modules/com/oracle/main/oraclepki jar" JAVA_OPTS="$JAVA_OPTS -javaagent:<jboss_home>/apmagent/lib/system/ ApmAgentInstrumentation.jar" EAP 6.1: JAVA_OPTS="$JAVA_OPTS -Djboss.modules.system.pkgs=$JBOSS_MODULES_SYSTEM_PKGS - Djava.awt.headless=true" JAVA_OPTS="$JAVA_OPTS - Djava.util.logging.manager=org.jboss.logmanager.LogManager" JAVA_OPTS="$JAVA_OPTS -Xbootclasspath/p:<JBOSS_HOME>/modules/system/layers/ base/org/jboss/logmanager/main/jboss-logmanager finalredhat-1.jar:<jboss_home>/modules/system/layers/base/org/jboss/log4j/logmanager/ main/log4j-jboss-logmanager final-redhat-2.jar:<jboss_home>/modules/com/ oracle/main/oraclepki jar:<jboss_home>/apmagent/lib/agent/ osdt_cert.jar:<jboss_home>/apmagent/lib/agent/osdt_core.jar:<jboss_home>/ apmagent/lib/agent/osdt_cms.jar:<jboss_home>/apmagent/lib/agent/osdt_cmp.jar" JAVA_OPTS="$JAVA_OPTS -javaagent:<jboss_home>/apmagent/lib/system/ ApmAgentInstrumentation.jar" a. Download jboss-as-logging final-redhat-10.jar and add it to the <JBOSS_HOME>/modules/system/layers/base/org/jboss/as/logging/main folder. b. Make a backup copy of the module.xml file. cp <JBOSS_HOME>/modules/system/layers/base/org/jboss/as/logging/main/ module.xml <JBOSS_HOME>/modules/system/layers/base/org/jboss/as/logging/main/ module.orig.xml c. Edit the module.xml file. vi <JBOSS_HOME>/modules/system/layers/base/org/jboss/as/logging/main/ module.xml d. Replace <resource-root path="jboss-as-logging final-redhat-8.jar /> with <resource-root path="jboss-as-logging final-redhat-10.jar /> EAP 6.4: JAVA_OPTS="$JAVA_OPTS -Djboss.modules.system.pkgs=$JBOSS_MODULES_SYSTEM_PKGS - Djava.awt.headless=true" JAVA_OPTS="$JAVA_OPTS - Djava.util.logging.manager=org.jboss.logmanager.LogManager" JAVA_OPTS="$JAVA_OPTS -Xbootclasspath/p:<JBOSS_HOME>/modules/system/layers/ base/org/jboss/logmanager/main/jboss-logmanager finalredhat-1.jar:<jboss_home>/modules/system/layers/base/org/jboss/logging/main/ jboss-logging ga-redhat-2.jar:<jboss_home>/modules/system/layers/base/org/ jboss/log4j/logmanager/main/log4j-jboss-logmanager final-redhat-1.jar:/ scratch/bjrao/jboss_install/jboss-eap-6.4/modules/com/oracle/main/ oraclepki jar" JAVA_OPTS="$JAVA_OPTS -javaagent:<jboss_home>/apmagent/lib/system/ ApmAgentInstrumentation.jar" 4. Restart the JBoss Server: 1-23

30 Setting Up APM Java Agents % cd $JBOSS_HOME/bin %./jboss-cli.sh -c :shutdown % nohup./standalone.sh -b &> startup.log & You can check the entries present in the $JBOSS_HOME/startup.log file to verify that the JBoss Server has started. 5. If you have any managed JBoss application servers, stop and restart them. Installing and Provisioning APM Java Agent on JBoss on Microsoft Windows You can install and provision the APM Java Agent on your JBoss domain installed on a Microsoft Windows machine. Before you install: Download the installer. See Downloading the APM Java Agent Software for JBoss. Log in to the machine running the application server, as the same user who installed the application server. Ensure that the application server user has Read-Write access to the APM Java Agent directories. To install and provision APM Java Agent on JBoss Server on Microsoft Windows: 1. Run the following command to provision the APM Java agent: set the DOMAIN HOME : set JBOSS_HOME=<JBoss_Home Path> ProvisionApmJavaAsAgent.cmd /d %JBOSS_HOME% /no-wallet 2. Provision the APM Java agent. This enables the APM agent to be invoked when you restart the JBoss Server. a. Make a backup copy of your standalone.conf.bat file: %cd %JBOSS_HOME%\bin %cp standalone.conf.bat standalone.conf.bat.orig b. Using a text editor, edit the standalone.conf.bat file. Search for the text Djboss.modules.system.pkgs=, and add oracle.apmaas,org.jboss.logmanager to it. For example, if the original text is, -Djboss.modules.system.pkgs=org.jboss.byteman the new text will be Djboss.modules.system.pkgs=org.jboss.byteman,oracle.apmaas,org.jboss.logmanag er 3. At the end of the file, add these statements, after modifying the location and versions of these.jar files specific to your installation. If needed, you can download the.jar files and modify the paths in the below statements: set "JAVA_OPTS=%JAVA_OPTS% - Djava.util.logging.manager=org.jboss.logmanager.LogManager" set "JAVA_OPTS=%JAVA_OPTS% -Xbootclasspath/p:<JBOSS_HOME>\modules\system\layers \base\org\jboss\logmanager\main\jboss-logmanager finalredhat-1.jar;<jboss_home>\modules\system\layers\base\org\jboss\log4j\logmanager \main\log4j-jboss-logmanager final-redhat-1.jar" 1-24

31 Setting Up APM Java Agents set "JAVA_OPTS=%JAVA_OPTS% -javaagent:<jboss_home>\apmagent\lib\system \ApmAgentInstrumentation.jar" 4. Stop and restart the JBoss Server: % cd <JBOSS_HOME>\bin %./standalone.bat -b You can check the entries present in the <JBOSS_HOME>\startup.log file to verify that the JBoss Server has started. 5. If you have any managed JBoss application servers, stop and restart them. Setting up Oracle Application Performance Monitoring on WebSphere Complete the following tasks sequentially, to set up APM Java Agent on WebSphere. Preparing to Deploy APM Java Agent on WebSphere Downloading the APM Java Agent Software for WebSphere Installing and Provisioning APM Java Agent on WebSphere Modifying the Startup Script of Your WebSphere Server Preparing to Deploy APM Java Agent on WebSphere Before you can download and install an APM Java Agent, ensure that you set the values for these variables. Setting 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>" Deploying the Gateway (Optional) Gateway is not a mandatory component while deploying Oracle Application Performance Monitoring. Use the 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.net IIS servers and Java Application Servers with JDK less than 1.7 (for example, Oracle WebLogic ) For instructions on how to deploy the Gateway, see Installing a Gateway. Setting the Gateway Variables (Optional) Set the values for Gateway host and port. If you're using a Bash shell: 1-25

32 Setting Up APM Java Agents 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>" Downloading the APM Java Agent Software for WebSphere Download the APM Java Agent software from the Oracle Management Cloud Agents page, and install the agent. Download the APM Java Agent software to a shared directory that can be accessed by all the managed servers in the application server domain where APM Java Agents will be deployed. To download the APM Java Agent software: 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 Download tab. The Agent Software Download page is displayed. 4. From the Agent Type dropdown list, select APM Agent. 5. Click APM Java Agent. This downloads the agent software ZIP file to the selected location. 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 Managing Registration Keys. You can also install and provision the APM Java Agent from an offline installer that you have received over . Installing and Provisioning APM Java Agent on WebSphere After you have downloaded and extracted the installer, install and provision the APM Java Agent in your WebSphere server domain. 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: 1-26

33 Setting Up APM Java Agents Installation Preference Basic Installation Provisioning Script chmod +x ProvisionApmJavaAsAgent.sh./ProvisionApmJavaAsAgent.sh -d ${WAS_HOME} Silent Installation chmod +x ProvisionApmJavaAsAgent.sh./ProvisionApmJavaAsAgent.sh -d ${WAS_HOME}-no-prompt Without Oracle Wallet An Oracle Wallet is a passwordprotected container used to store authentication and signing credentials. See Using Oracle Wallet Manager for details. chmod +x ProvisionApmJavaAsAgent.sh./ProvisionApmJavaAsAgent.sh -d ${WAS_HOME} -no-wallet With Gateway chmod +x ProvisionApmJavaAsAgent.sh./ProvisionApmJavaAsAgent.sh -d ${WAS_HOME} -gateway-host, -gateway-port, -additional-gateways With Gateway and without Oracle Wallet chmod +x ProvisionApmJavaAsAgent.sh./ProvisionApmJavaAsAgent.sh -d ${WAS_HOME} -gateway-host, -gateway-port, -additional-gateways -no-wallet In a Proxy Environment with Oracle Wallet chmod +x ProvisionApmJavaAsAgent.sh./ProvisionApmJavaAsAgent.sh -d ${WAS_HOME} -ph {http_proxy_host} -pp {http_proxy_port} -pt {http_proxy_auth_token} In a Proxy Environment without Oracle Wallet 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 Generating 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 1-27

34 Setting Up APM Java Agents 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. ProvisionApmJavaAsAgent.shSyntax for Using the Installation Script Provisioning APM Java Agent with Offline Installer You can install and provision the APM Java Agent from an offline installer that you have received over . To install from the ed ZIP, the provisioning script needs to download the configuration file from Oracle Management Cloud. Specify these additional options while running the provisioning script: Option -tenant-id -omc-server-url Description The Oracle Management Cloud tenant name. The URL of the Oracle Management Cloud server. Example: Modifying the Startup Script of Your WebSphere Server Modify the startup script of your WebSphere application server to invoke the Oracle Application Performance Monitoring Cloud Service configuration settings, when you start 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/-" { 1-28

35 Setting Up APM Java Agents 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> Setting up Oracle Application Performance Monitoring on Jetty Complete the following tasks sequentially to set up the APM Java Agent on Jetty. Preparing to Deploy APM Java Agent on Jetty Downloading the APM Java Agent Software for Jetty Installing and Provisioning APM Java Agent on Jetty Modifying the Startup Script of Your Jetty Server Preparing to Deploy APM Java Agent on Jetty Before you can download and install an APM Java Agent, ensure that you set the values for these variables. Setting the JETTY_HOME Variable Set the JETTY_HOME variable to point to the Jetty destination directory. If you're using a Bash shell: export JETTY_HOME=<Jetty destination directory> If you're using a C shell: setenv JETTY_HOME"<Jetty destination directory>" Deploying the Gateway (Optional) Gateway is not a mandatory component while deploying Oracle Application Performance Monitoring. Use the 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.net IIS servers and Java Application Servers with JDK less than 1.7 (for example, Oracle WebLogic ) For instructions on how to deploy the Gateway, see Installing a Gateway. Setting 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: 1-29

36 Setting Up APM Java Agents setenv GW_HOST "<Gateway Host Name>" setenv GW_PORT "<Gateway Port>" Downloading the APM Java Agent Software for Jetty Download the APM Java Agent software from the Oracle Management Cloud Agents page, and install the agent. Download the APM Java Agent software to a shared directory that can be accessed by all the managed servers in the application server domain where APM Java Agents will be deployed. To download the APM Java Agent software: 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 Download tab. The Agent Software Download page is displayed. 4. From the Agent Type dropdown list, select APM Agent. 5. Click APM Java Agent. This downloads the agent software ZIP file to the selected location. 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 Managing Registration Keys. You can also install and provision the APM Java Agent from an offline installer that you have received over . Installing and Provisioning APM Java Agent on Jetty After you have downloaded and extracted the installer, install and provision the APM Java Agent in your application server domain. Before you install the APM Java Agent, log in to the machine running the application server as a user who installed the application server. 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 Basic Installation Provisioning Script chmod +x ProvisionApmJavaAsAgent.sh./ProvisionApmJavaAsAgent.sh -d ${JETTY_HOME} 1-30

37 Setting Up APM Java Agents Installation Preference Silent Installation Provisioning Script chmod +x ProvisionApmJavaAsAgent.sh./ProvisionApmJavaAsAgent.sh -d ${JETTY_HOME}-no-prompt Without Oracle Wallet An Oracle Wallet is a passwordprotected container used to store authentication and signing credentials. See Using Oracle Wallet Manager for details. chmod +x ProvisionApmJavaAsAgent.sh./ProvisionApmJavaAsAgent.sh -d ${JETTY_HOME} -no-wallet With Gateway chmod +x ProvisionApmJavaAsAgent.sh./ProvisionApmJavaAsAgent.sh -d ${JETTY_HOME} -gatewayhost, -gateway-port, -additional-gateways With Gateway and without Oracle Wallet chmod +x ProvisionApmJavaAsAgent.sh./ProvisionApmJavaAsAgent.sh -d ${JETTY_HOME} -gatewayhost, -gateway-port, -additional-gateways -no-wallet In a Proxy Environment with Oracle Wallet chmod +x ProvisionApmJavaAsAgent.sh./ProvisionApmJavaAsAgent.sh -d ${JETTY_HOME} {http_proxy_host} -pp {http_proxy_port} -pt {http_proxy_auth_token} -ph In a Proxy Environment without Oracle Wallet chmod +x ProvisionApmJavaAsAgent.sh./ProvisionApmJavaAsAgent.sh -d ${JETTY_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 Jetty 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 Generating 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. 1-31

38 Setting Up APM Java Agents 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. ProvisionApmJavaAsAgent.shSyntax for Using the Installation Script Installing APM Java Agent on a Microservice When installing the APM Java agent on an application or microservice using Dropwizard or similar embedded Jetty framework, installation is very similar to standalone Jetty. Simply add -javaagent:<path-to-agent>/apmagent/lib/system/apmagentinstrumentation.jar to the startup command line or script for your application or microservice. Example: java -javaagent:/scratch/apmagent/lib/system/apmagentinstrumentation.jar -jar mymicroservice-1.0.jar server config.yml Provisioning APM Java Agent with Offline Installer You can install and provision the APM Java Agent from an offline installer that you have received over . To install from the ed ZIP, the provisioning script needs to download the configuration file from Oracle Management Cloud. Specify these additional options while running the provisioning script: Option -tenant-id -omc-server-url Description The Oracle Management Cloud tenant name. The URL of the Oracle Management Cloud server. Example: Modifying the Startup Script of Your Jetty Server Modify the startup script of your application server to invoke the Oracle Application Performance Monitoring Cloud Service configuration settings, when you start your application server. To modify the java -jar start.jar script of your Jetty server home: 1. Make a copy of your java -jar start.jar file: % cd $JETTY_HOME/bin % cp java -jar start.jar java -jar start.jar.orig 2. Using a text editor, edit the original script to add the -javaagent option. To send the Jetty server data to APM Agent, append the following class path, along with ApmAgentInstrumentation.jar java -javaagent:/scratch/apmagent/lib/system/apmagentinstrumentation.jar -jar start.jar 1-32

39 Setting Up APM Java Agents 3. Restart the Jetty server. Verifying APM Java Agent Installation You can verify that the installation of Oracle Application Performance Monitoring Cloud Service is successful by examining the logs and verifying that the user interface displays the Application Server. You can also verify the structure of the installation directory. Verify that the installation of Oracle Application Performance Monitoring is successful by: 1. Examining the APM Java Agent Logs 2. Using the Oracle Application Performance Monitoring Web UI 3. Verifying the APM Java Agent Directory Structure Examining the APM Java Agent Logs Examine the log files after installing Oracle Application Performance Monitoring: 1. Verify that the Oracle Application Performance Monitoring log directories and files were created. a. After restarting the application server, verify that the APM Java Agent created a log directory for each server it is now monitoring: % cd $DESTINATION/apmagent/logs % ls -lf Verify that the following log directory was created: $DESTINATION/apmagent/logs/<application server name> b. If there are multiple servers in the domain, as each server is restarted, it will be represented by a separate directory under $DESTINATION/apmagent/logs. For example, if you are monitoring the Application Server, AdminServer1, you should see the following entry: $DESTINATION/apmagent/logs/AdminServer1 c. Verify that the correct set of log files were created inside each server log directory: % cd $DESTINATION/apmagent/logs/AdminServer % ls -lf *.log Verify that the following set of log files were added to the directory along with other files: AgentErrors.log Agent.log AgentStartup.log AgentStatus.log If all the expected log directories and the log files were not created, then the Oracle Application Performance Monitoring installation was not successful. 2. Check for errors in the AgentErrors.log file. The AgentErrors.log file should have a line similar to the following: 1-33

40 Setting Up APM Java Agents % more AgentErrors.log < T12:36: > INFO Exception log is initialized 3. In the AgentStartup.log file, the message Agent startup successfully completed should be seen. 4. Look for agent activity in the AgentStatus.log file. As the APM Java Agent starts monitoring traffic, it logs short status information in the AgentStatus.log file. If the traffic and transport counts are more than zero, then that indicates that the APM Java Agent is active, and it is monitoring and reporting data successfully. Verifying the Installation Using the Oracle Application Performance Monitoring Web User Interface Access the Oracle Application Performance Monitoring web user interface from the Oracle Management Cloud home page and verify that the Oracle Application Performance Monitoring installation was successful. To check for successful Oracle Application Performance Monitoring installation from the web user interface: 1. Log in to the Oracle Management Cloud home page. 2. In the Oracle Management Cloud Home page, click the Application Performance Monitoring tile. The Oracle Application Performance Monitoring home page is displayed. 3. Ensure that your user name is displayed in the upper right corner of the home page. 4. To verify that your Application Server was discovered, in the Oracle Application Performance Monitoring home page, click AppServers. Your application server should be displayed in the AppServers view. 5. Use your applications, and then check for data in the Application Performance Monitoring UI. a. Use the application that you want to monitor, and make multiple transactions. b. In the Oracle Application Performance Monitoring home page, click the Time Selector drop-down list and select Last Hour. c. See the Top 5 Server Requests or click the number above Server Requests to see the Server Requests view. d. If you are on the Enterprise Edition, click Pages to see the Pages view. Ensure that the operations you performed on the application are reflected in the Server Requests or the Pages view. Verifying the APM Java Agent Directory Structure After installing and provisioning APM Java Agent, you can find the following directory structure on your WebLogic Managed Server. 1-34

41 Setting Up APM Java Agents Directory Sub-directory Description ${DOMAIN_HOME} The home directory of the WebLogic Server domain, where the APM Java Agent is installed. apmagent The root of the APM Java Agent's installation directory. No files are stored directly in this directory. Note that there will be exactly one APM Java Agent installation directory for this domain (on this host) regardless of how many WebLogic Servers are being monitored. config/ All of the APM Java Agent's domain-level configuration files are stored directly in this directory. agentwallet If this domain is using an Oracle Wallet to hold the APM Java Agent's Authorization Token (acting as the APM Java Agent's Credential Store), then this directory will exist, and will hold the cwallet.sso file which is the wallet. (server 1)...(server N) For each server in the domain that is being monitored, a configuration directory will be created when the APM Java Agent first discovers that server. Configuration data that can be modified on a server-by-server basis (as opposed to that for the entire domain), will be found here. lib/ All of the APM Java Agent's.jar files will be found under the lib directory. action agent system The three sub-directories under the lib directory. logs/ The APM Java Agent's log files will be stored in one of this directory's sub-directories. No files will be found directly in this directory. (server 1)...(server N) For each server in the domain being monitored, a log directory will be created when the APM Java Agent first discovers that server. All log files pertaining to a particular server will be stored in these subdirectories. 1-35