Skip Headers

Agile Product Lifecycle Management Agile Plug-in for Enterprise Manager User Guide Release 9.3.3 E39304-01 |
| Contents

Previous | Next |

# 1 Introduction

This document (Agile PLM Monitoring Guide 10g Release 4 (10.2.0.4.0)) introduces Agile PLM Monitoring using Oracle Enterprise Manager Grid Control. It guides you through the process of creating and configuring Agile Landscape targets and discusses Agile transactions. It provides the following information:

## 1.1 Agile PLM Monitoring with Oracle Enterprise Manager Grid Control

Oracle Enterprise Manager 10g provides multi-instance monitoring of Agile PLM applications to deliver comprehensive, efficient, and vital health status information such as performance metrics, availability, and end-user experience. To enable this, you need to configure the following plug-ins:

- agilePlugin - to monitor Agile PLM instances.

- empluginpharma - to monitor Recipe & Material Workspace instances.

- tomcat_plugin - to monitor Agile File Manager instances

This manual describes how you can install and configure these plug-ins. The configuration procedures for both plug-ins are similar and any variances are noted.

The plug-ins are available at the following location within the Agile PLM installation directory.

Name | Plug-in | Location
--- | --- | ---
Agile PLM | agilePlugin.jar | <AGILE_HOME>\agileDomain\emplugin\
Recipe& Material Workspace | empluginpharma.jar | <AGILE_HOME>\AgilePharma\emplugin\
Tomcat | tomcat_plugin.jar | <AGILE_HOME>\agileDomain\emplugin\

Supported releases:

- Oracle Enterprise Manager Agent 10.2.0.4 and 10.2.0.3.

Note: Oracle recommends Oracle Enterprise Manager Agent Release 10.2.0.4

## 1.2 System Requirements

Before configuring Grid Control 10g Release 4 (10.2.0.4) to manage Agile applications, you must:

- Install and configure Grid Control 10gR4 and 10g Release 2 (10.2.0.2) on at least one host computer on the network.

- Install the Grid Control components on their own host or hosts. For example, if you install Agile monitoring middle tier on host1.us.oracle.com, then install and configure the Oracle Management Service and Oracle Management Repository on host2.us.oracle.com.

- Install the Grid Control 10.4 Oracle Management Agent on every host that includes components that you want to manage with Grid Control.

See Oracle Enterprise Manager Basic Installation and Configuration for Oracle Enterprise Manager Grid Control 10.2 at: `http://www.oracle.com/technology/documentation/oem.html` `http://www.oracle.com/technology/documentation/oem.html`

### 1.2.1 Prerequisites:

1. Install Oracle Enterprise Manager Agent Release 10.2.0.3 or later. Make sure the agent can successfully communicate with Oracle Enterprise Manager Server and upload data. For example, Agent Availability must be UP, Last Load Time must show a recent date/timestamp, and ensure to update the Last Load Time periodically.

2. Install Agile PLM Release 9.3.1.

Note: The Oracle Enterprise Manager Agent need not reside on the same machine where Agile PLM is installed.

While you are installing Agile, you need to know:

- The Host of Agile PLM instance.

- The JMX Port Number of the Agile PLM instance.

- If you are enabling authentication for JMX on Agile PLM instance, you require the JMX Username and the JMX Password.

- The Communication Protocol of Agile PLM instance.

- The Service Name of Agile PLM instance.

- If you are enabling SSL for JMX on Agile PLM instance, you require the SSL Trust Store and the SSL Trust Store JMXPassword.

- The Agile Version of the Agile PLM instance (Not mandatory).

Note: Note Ensure that you load the Agile PLM instance.

- Note that the installer hard codes the below Port Numbers.

  - Port number for Agile PLM - 9899

  - port number for Recipe&Material Workspace-8899

  - Port Number for Apache Tomcat - 9898

- Default Communication Protocol and Services names are rmi and jmxrmi.

- Before configuring Grid Control 10g Release 4 (10.2.0.4) to manage Agile application, Oracle recommends that you install the Grid Control components on their own host or hosts. For example, if you install Agile on host1.us.oracle.com, then install and configure the Oracle Management Service and Oracle Management Repository on host2.us.oracle.com.

- Install the Grid Control 10.2 Oracle Management Agent on every host that includes the components you want to manage with Grid Control.

See Enterprise Manager Grid Control Installation and Basic Configuration Guide for details on performing these steps.

## 1.3 Setting Credentials in Oracle Enterprise Manager

You need to set credentials in Oracle Enterprise Manager for the user that the agent runs as. Either you can set default credentials (credentials are the same for all agents) or you can set different credentials for each agent (target credentials). Target credentials override default credentials.

To set credentials:

1. Click Preferences in the Oracle Enterprise Manager home page.

2. Click Preferred Credentials.

3. Click the icon in the Set Credentials column in the row for the agent. The Agent Preferred Credentials page appears.

4. Enter default and target credentials by entering the operating system username and password for the agent.

5. In the Host UserName column, enter username.

6. In the Host Password column, enter password.

7. Click Apply.

## 1.4 Granting 'Log on as a Batch Job' Privilege

On Windows, you need to grant to the host username the Log on as a Batch Job privilege. Set credentials for agents by setting the host username and host password in Oracle Enterprise Manager Grid Control. For more information on setting credentials, see Setting Credentials in Oracle Enterprise Manager on page 3.

To grant Logon as a batch privilege on Windows:

1. Set the control panel to classic view.

2. From the desktop, choose Start > Control Panel > Administrative Tools.

3. Double click Local Security Policy.

4. Click Local Policies.

5. Click User Rights Assignment.

6. Double-click Log on as a Batch Job. The Log on as a Batch Job Properties dialog appears.

7. Click Add User or Group. The Select Users or Group dialog appears.

8. In the Enter the Object Names to Select dialog, enter username of the host.

9. Click OK.

## 1.5 Additional Sources of Information

Refer to the URL below for additional information about Agile instance monitoring. The base documentation is applicable in many cases, because Agile instance monitoring leverages many of Enterprise Manager's underlying capabilities.

See also: Enterprise Manager Concepts Guide, which gives you more information on the capabilities of Oracle Enterprise Manager Grid Control at Oracle Technology Network`http://www.oracle.com/technetwork/documentation/agile-085940.html`.