1.the collection agent (Oracle Management Agent or OMA)
2.the aggregation agent (Oracle Management Server or OMS)
3.the repository agent (Oracle Management Repository or OMR)
To start/stop/monitor OMS components
The emctl command is the Enterprise Manger Control Utility. Like opmnctl, it starts and stops the OMS components. Notice that emctl does not start or stop OracleAS Web Cache.
If OracleAS Web Cache is on then you can access to OEM by: http://oms-server:7777/em and with no OracleAS Web Cache, you need to directly connect to the OHS: http://oms-server:7778/em.
The following are some of examples of how to manipulate the OMS components using emctl.
# emctl start oms -- start oms components except web cache.
# emctl stop oms -- stop …
# emctl status oms -- show the status of oms components
# emctl start iasconsole – starts an individual component
# emctl stop iasconsole -- stop and …
Basic commands an Oracle Database Administrator must know (using default port).
1. Use the http://
2. Use the ias_admin username to connect to the OMS.
3. Use the iSQL*Plus tool if was installed by using the http://
Commands
$ emctl start oms -- This will start oms as well as the required weblogic processes. [starts opmn, HTTP_SERVER, Node Manager]
$ emctl status oms [-details] -- details require Sysman password.
$ emctl stop oms [-all] -- Using the "all" option stop node manager and Admin Server as well.
$ emctl list oms -- This provides the oms name configured in the local ORACLE_HOME. A "*" is displayed next to OMS name if admin server is configured on the same host.
emctl status / start / stop agent
Log file locations
OMS Application logs:
OPMN logs:
HTTP Server:
$export ORACLE_INSTANCE=/u01/gc_inst/WebTierIH1
$ cd $ORACLE_INSTANCE/bin
$ ./opmnctl status -- check status of HTTP Server components
To start/stop/monitor OMS
Use the opmnctl command. It control the OMS. It stands for Oracle Process Monitor and Notification control. The following are some of examples of how to manipulate the OMS components.
# opmnctl startall -- starts all components of OMS.
# opmnctl stopall -- stops all components of OMS.
# opmnctl startproc ias-component=OC4J -- starts OC4J component
# opmnctl stopproc ias-component=OC4J -- stops OC4J component
# opmnctl status – l – show OMS status components.
Installation
Before installing Enterprise Manager Grid Control, we need to install Oracle WebLogic Server 10.3.2. This is available on OTN under the Oracle Fusion Middleware 11g Software Downloads category.
The installation will create a new Web Logic domain called GCDomain and we need to provide the location of the Oracle Middleware Home which was used to install the Web Logic server.
The Oracle Middleware Home will be the location for the Web Logic Server and it’s components, the OMS and the Management Agent as well.
In earlier releases of EM Grid Control, we had the option of using an existing database as the repository database or let the installer create a new database to house the repository. In 11g EM, we do not have that option and we have to provide the connection details of an existing Oracle database.
