2 Monitoring Agile Targets

Oracle Enterprise Manager Grid Control 12c Release 4 enables the monitoring of Agile PLM applications along with other Oracle and non-Oracle technologies through a single Oracle Enterprise Manager Grid Control console.

2.1 Key Benefits

It provides:

• Centralized, multi-tier, multi-instance Agile PLM monitoring.

• Discovery of Agile PLM servers and instances for each monitored SID.

• Comprehensive, efficient, and secure health status data collection.

• End-user experience monitoring for Agile PLM application modules.

• Agile PLM business service dashboards and performance trend reports.

Note: Use of other Oracle Enterprise Manager capabilities may require additional licenses.

2.2 Prerequisites for Monitoring Agile Targets

After deploying Agile, perform the following steps to monitor an Agile target by using the Enterprise Manager Grid Control:

• Install Enterprise Manager Grid Control with licenses.

• You must install EMGC 12.1.0.5.

• Name the queues OEM_AGENTS and OEM_METRICS.

2.3 Creating a Target Instance

You can create a target instance on one or more agents and for each unique Agile PLM Server. You can configure Agile Server as one of the targets for the agent and the agent begins the process of monitoring the target.

Note: Enterprise Manager does not monitor the target, once an entry is deleted from the Enterprise Manager Repository.

2.3.1 For Agile PLM

Note: In OEM 12c, the system throws an error while monitoring Agile.

1. Click Add Target. Add Target Manually on the Set-up page.

2. Select Oracle Fusion Middleware/Weblogic Domain and the Middleware page appears.

3. Click 'Add Using Guided Process'.

Figure 2-1 Details to find Targets

1. Administration Server Host: Select a host where Agile is installed by using the search button.

2. Agent: The Agent is selected once the user selects the Administration Server host.

3. Port: Weblogic Communication Protocol.

4. Username: superadmin

5. Password: Password for superadmin

6. Unique Domain Identifier: Define the name as a meaningful identifier (For example: - Agile93PLM_hostname_instance).

2.3.2 Check Agile Status

1. Click Targets > All Targets. The All Targets page appears.

2. Click the Target Name which you created for Agile.

3. The following status is displayed.

   Figure 2-2 Status for Agile PLM

   
   

2.3.3 For Apache Tomcat

For details on how to enable JMX, please follow http://tomcat.apache.org/tomcat-8.5-doc/monitoring.html

Note: After removing JMX_SET, the system does not monitor Tomcat.

1. Click Add Targets Declaratively by Specifying Target Monitoring Properties.

2. Select Apache Tomcat of Target Type.

3. Click Add Manually... and the Target page appears.

4. Select the Monitoring Agent.

   Figure 2-3 Apache Tomcat Monitoring Credentials

   
   

   1. Target Name: Define the name as a meaningful identifier. (For example, FileManage_hostname_instance).

   2. Apache Tomcat Monitoring Credentials: Enter the Credential details configured on Tomcat.

   3. Properties:

      Apache Tomcat Version(5, 6 or 7): 8.5

      Communication Protocol: rmi

      Host: Enter a host where the File Manager is installed.

      JMX Port Number: Enter the JMX port Number configured in Tomcat.

      SSL Trust Store (requird when SSL is enabled): Enter the SSL Trust Store if SSL is enabled.

      Services Name: jmxrmi

2.3.3.1 Check Tomcat Status:

1. Click Targets > All Targets. The All Targets page appears.

2. Click the Target Name created for Tomcat, and the status appears.

Note: We can only check if Tomcat is up and running. No other details can be checked.