Verify APM Java Agent Installation on Linux

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. Examine the APM Java Agent Logs
2. Use the Oracle Application Performance Monitoring Web Console
3. Verify the APM Java Agent Directory Structure

Examine 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.
   1. 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>

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

   3. 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:

   % more AgentErrors.log
   <2015-01-16T12:36:27.27-0800> 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 Console

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 console:

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 web console.
   1. Use the application that you want to monitor, and make multiple transactions.
   2. In the Oracle Application Performance Monitoring home page, click the Time Selector drop-down list and select Last Hour.
   3. See the Top 5 Server Requests or click the number above Server Requests to see the Server Requests view.
   4. 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.

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

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 sub-directories.