Skip Headers

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

Previous | Next |

# 3 Agile Plug-in Configuration

This chapter describes how to import, configure, and deploy the plug-in.

## 3.1 Importing a Plug-in

Plug-ins define and deploy an agent to manage and monitor a target. Before you begin the import process, you need to download the plug-in from the Agile Application server and save the plug-in file (agilePlugin.jar/ empluginpharma.jar/tomcat_plugin.jar) to the machine where the browser is running.

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

You can now log in to the Oracle Enterprise Manager Grid Control from the browser.

To import plug-ins:

1. Log in to the Oracle Enterprise Manager Grid Control.

2. Enter username and password of the Super Administrator in the Username and Password columns.

3. Press Return or click Login. The Oracle Enterprise Manager Grid Control Home page appears.

4. Click Setup. The Oracle Enterprise Manager Setup page appears.

5. Click Management Plug-ins in the Overview of Setup panel section. The Management Plug-ins page appears.

6. Click Import from the Management Plug-ins page. The Import Management Plug-ins page appears.

7. Click Browse to locate the plug-in archive file.

   The plug-in archive file is the .jar file you have downloaded. The file is located in the file system where the browser resides. (For example, if the browser resides on the Windows platform, you can locate the file on the desktop or in one of the folders on the drive).

8. Select the file. You see the path and filename of plug-in jar file in the text field named Management Plug-in Archive.

9. Click List Archive.

   The Management Plug-in Archive (MPA) plays an important role at various stages of the plug-in life cycle. It serves the following functions.

   - It acts as a transport mechanism between the development environment and the Enterprise Manager framework.

   - It acts as a transport mechanism between different Enterprise Manager installations.

   - It acts as a container for the Management Plug-in. A MPA may contain multiple Management Plug-ins.

10. Check the Select option. You can now import the plug-in.

11. Click the OK button. The process of importing the plug-in begins.

On completion, the Setup page displays a message confirming successful import. You can now deploy the plug-in to one or more agents.

## 3.2 Creating a Target Instance

You can create a target instance of the plug-in 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.

1. Click Agents on the Setup page.

2. The Agents page appears. A list of the agents you deployed the plug-in to appears.

3. Select and click the Agent link. The Agent Name page appears.

4. Click the Add drop-down list and select target type as below.

   - To add Agile PLM, select AgilePLM from the Add drop-down menu. Click Go.

   - To add Apache Tomcat, select Apache Tomcat from the Add drop-down menu. Click Go.

   - To add RMW, select AgilePharmaEM from the Add drop-down menu. Click Go.

In the Name column, you create a target instance name. Define the name as a meaningful identifier. (For example, Agile93PLM_hostname_instance). The name can be any string including letters, numbers, and special characters.

1. Enter the target instance name in the Name column.

2. Enter the host name of the Agile PLM/RMW instance in the Host column.

3. Enter the port number in the JMX Port Number column.

4. If you enable authentication,

   - Enter the JMX username in the JMX User Name column.

   - Enter the JMX password in the JMX Password column.

   - Enter the protocol in the Communication Protocol.

   - Enter the name in the Service Name column.

5. If you enable SSL,

   - Enter the SSL trust in the SSL Trust Store column.

   - Enter the JMXPassword in the SSL Trust Store JMXPassword column.

6. Enter the version of the Agile PLM/RMW instance in the Agile Version column.

7. Click OK.

You can now view information about the created target instance.

## 3.3 Deploying the Plug-in

Deploying the plug-in to one or more agents begins the process of monitoring the target. After successfully deploying the plug-in, you can configure Agile Server as one of the targets for the agent. The agent then begins the process of monitoring the target.

To deploy the plug-in:

1. Ensure you are in the Oracle Enterprise Manager Setup page.

   A table displays several columns containing information about the plug-in. For example, the name column displays Agile, Deployed Agents column displays 0 (if you have not previously deployed one or more agents), and Description column displays Management Plug-in for Agile PLM.

2. Check the Select column.

3. Click Deploy. The Deploy Management Plug-in: Select Targets page appears.

4. Click Add Agents. A dialog appears. You can now search for the known agents.

5. Click Go.

6. Check the Select option for each agent you wish to deploy the plug-in to, from the list of agents.

7. Click Select. A list of deployment agents appears.

8. Click Next. The Deploy Management Plug-in: Review page appears. This page briefly describes the deployment process.

9. Click Finish.

The Setup page displays the message: "Deploy operation completed". The number of agents deployed appears in the Deployed Agents column.

You are now ready to create a target instance.