For OHS server, there is no stand-alone OHS server monitoring capability in OEM 11g. we can configure customized status monitor by using below options
Process:1 Add OHS details in targets.xml file in agent home for STATUS monitoring
1. Take Backup of /oracle/app/agent11g/sysman/emd/targets.xml
2. Add below details in targets.xml file, modify according to your server which are in BOLD letters.
<Target TYPE="oracle_apache" NAME="web1_ohs_instance1">
<Property NAME="HTTPMachine" VALUE="Server HostName"/>
<Property NAME="HTTPPort" VALUE="80"/>
<Property NAME="useDefaultProxy" VALUE="false"/>
<Property NAME="version" VALUE="11.1.1.4.0"/>
<Property NAME="VersionCategory" VALUE="StdApache"/>
<Property NAME="OracleHome" VALUE="/oracle/app/product/fmw/web"/>
</Target>
3. Restart the OEM agent.
---------------------------------------------------------------------------------------------------------------------------
Process :2 OHS server to any
weblogic domain as web tier (This will monitor status and performance)
How to register Oracle HTTP Server with Weblogic Server
Environment = Oracle Enterprise Linux 5.7, Oracle DB 11g, Oracle Weblogic Server 10.3.5
Resolution = Follow the below mentioned steps:
Step 1 - Login as Oracle user and complete all the prerequisites as mentioned here
Step 2 - Go to the directory where HTTP Server (Webtier) has been installed
$ cd /u01/app/oracle/admin/ohs_inst1/bin
Step 3 - Register your Admin Server URL (of HTTP server) with Weblogic:
$ ./opmnctl registerinstance -adminHost ADMIN.mycompany.com -adminPort 7001 -adminUsername weblogic
Command requires login to weblogic admin server (ADMIN.mycompany.com):
Username: weblogic
Password:
Username: weblogic
Password:
Deploying NonJ2EEManagement Application...weblogic.Deployer invoked with options: -adminurl ADMIN.mycompany.com:7001 -username weblogic -name NonJ2EEManagement -source /u01/app/oracle/product/fmw/Oracle_WT1/opmn/applications/NonJ2EEManagement.ear -nostage -deploy -upload -noexit
<Apr 3, 2012 6:29:18 PM NZST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, NonJ2EEManagement [archive: /u01/app/oracle/product/fmw/Oracle_WT1/opmn/applications/NonJ2EEManagement.ear], to configured targets.>
Task 1 initiated: [Deployer:149026]deploy application NonJ2EEManagement [Version=11.1.1] on AdminServer.
Task 1 completed: [Deployer:149026]deploy application NonJ2EEManagement [Version=11.1.1] on AdminServer.
Target state: deploy completed on Server AdminServer
<Apr 3, 2012 6:29:18 PM NZST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, NonJ2EEManagement [archive: /u01/app/oracle/product/fmw/Oracle_WT1/opmn/applications/NonJ2EEManagement.ear], to configured targets.>
Task 1 initiated: [Deployer:149026]deploy application NonJ2EEManagement [Version=11.1.1] on AdminServer.
Task 1 completed: [Deployer:149026]deploy application NonJ2EEManagement [Version=11.1.1] on AdminServer.
Target state: deploy completed on Server AdminServer
Done
Registering instance
Command succeeded.
Registering instance
Command succeeded.
Errors reported while registering Oracle HTTP Server with Weblogic Server
<Warning> <Deployer> <BEA-149124> <Failures were detected while initiating deploy task for application 'NonJ2EEManagement'. Error is: '[Deployer:149163]The domain edit lock is owned by another session in non-exclusive mode - this deployment operation requires exclusive access to the edit lock and hence cannot proceed. If you are using "Automatically Aquire Lock and Activate Changes" in the console, then the lock will expire shortly so retry this operation.'>
opmnctl registerinstance: failed.
Resolution - This is an issue with the Weblogic Server configuration. Follow the below mentioned steps:
Step 1 - Login to Oracle Weblogic Administration Console
Step 2 - Give user/password and hit login
Step 3 - In the top, go to "preferences" and give following setttings:
Warn If User Holds Lock - checked
Perform Asynchronous Activation - unchecked
Warn User Before Taking Lock - checked
Automatically Acquire Lock and Activate Changes: false
Perform Asynchronous Activation - unchecked
Warn User Before Taking Lock - checked
Automatically Acquire Lock and Activate Changes: false
Step 4 - Save your changes
Step 5 - Activate Changes
Step 6 - Now retry registering HTTP Server with Weblogic with following command:
./opmnctl registerinstance -adminHost ADMIN.mycompany.com -adminPort 7001 -adminUsername weblogic
-------------------------------------------------------------------------------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------------------------------------------------------------------------------
No comments:
Post a Comment