There are 2 cases you should consider.
OEM Agent installed on same host as the WebLogic Administration Server
1. Login to the OEM Grid Control console (e.g., http://server:port/em)
2. Click Targets
3. Click Middleware
4. From the Add list, select Oracle Fusion Middleware/WebLogic Domain and click Go
5. Specify the Administration Server Host, Port, Username, Password, Unique Domain Identifier (any unique name), and keep Agent as default, then click Continue
6. Click on Add Targets then Close then OK
7. Navigate to the WebLogic Server target, right-click on the domain, and select the Refresh WebLogic Domain option from the menu
OEM Agent not installed on same host as the WebLogic Administration Server
Keep in mind that Oracle documentation states that if you are "using a remote agent which may be running on a host that is different from the host on which the Administration Server is running... you may not be able to perform certain operations like instance tracing and viewing recoverable instances."
1. Manually discover Oracle WebLogic Managed Server (see steps above)
2. Copy the following files to your server:
soa-infra-mgmt.jar3. Create the directory on your Agent home and copy the JARs to it:
oracle-soa-client-api.jar
mkdir -p $AGENT_HOME/sysman/jlib/extjlib directory
cp soa-infra-mgmt.jar $AGENT_HOME/sysman/jlib/extjlib directory
cp oracle-soa-client-api.jar $AGENT_HOME/sysman/jlib/extjlib directory4. Navigate to the WebLogic Server target, and select the Refresh Domain option from the menu
Refer to the Oracle Enterprise Manager Getting Started with Oracle Fusion Middleware Management 11g Release 1 (11.1.0.1) documentation (link below) for additional information.
Applicable Versions:
- Oracle Enterprise Manager Grid Control 11g (11.1.0.x)
- Oracle SOA Suite 11g (11.1.1.x)
References:
- http://download.oracle.com/docs/cd/E11857_01/install.111/e17558.pdf
No comments:
Post a Comment