| Steps for configuration | Description |
| Run Configuration Assistant to create repository | Within OEM V2.x, a repository contains state information for the managed environment and is used as a back-end store by the Management Servers.This repository within version 2.x is different from version 1.x, where there was a repository for each user, whereas now, it is a singlerepository for all users. |
| Start Intelligent Agent | OEM uses Intelligent Agents, which are processes running on remote nodes within the network, to run jobs, monitor events, and gather data onremote sites and to discover services on the node where it resides. |
| Start Data Gatherer | The Oracle Data Gatherer is responsible for handling requests from client applications (for example, Oracle Capacity Planner and OraclePerformance Manager) that want to collect data. For each client application, you specify the performance data to collect (for example, file I/Oor CPU usage data) and the time interval between data samples. The Oracle Data Gatherer then collects the requested data for the client at thespecified interval. It is part of the Oracle Intelligent Agent. |
| Start Management Server | The Management Server provides distributed control between clients and managed nodes. A central engine for notification, it processes all systemmanagement tasks and administers the distribution of these tasks across the enterprise. You can also add Management Server to providefault-tolerance, in case another Management Server becomes unavailable. High performance and scalability is ensured, because the workload isshared and balanced when there are multiple Management Servers. |
| Start Console | The Console gives you a central point of control for the Oracle environment through an intuitive Graphical User Interface (GUI) that providespowerful and robust system management. OEM can be run in three ways:
- From the Windows Start menu (Windows platforms)
- From the command line (UNIX)
- From the browser
|
| Create administrator accounts | OEM 2.0 is a multi-administrator system. Each person who is administering systems using OEM has his or her own administrator account, which heor she uses to log into the Console or standalone application. The installation of OEM creates a single super administrator. This superadministrator account name is sysman, and the initial password is oem_temp. The super administrator has the ability to create administratorsusing the Manage Administrators item within the System menu. In addition to a username and password, each account can be tagged as a superadministrator account or a regular account. |
| Discover services | The Console Navigator provides a Service Discovery function for identifying network services and populating the Navigator tree. These services,such as databases and listeners, can be administered with OEM components. |
| Create Windows NT user account with privileges to submit jobs | For the agent to execute jobs on a managed node, an NT user account must exist that has the advanced user right, logon as batch job. Thisprivilege can be assigned to an existing local or domain user, or a new NT user. The preferred credentials for the node must be set for thatuser within the OEM console. The user must have read/write permissions to ORACLE_HOME\NET80 directory as well as write permissions tothe TEMP directory or the ORACLE_HOME directory. Creating a Windows NT user account is required to permit many of thecomponents to allow the agent node to submit jobs to the server node. |
| Set up Preferred Credentials on nodes | For the agent to execute jobs or monitor for events on a managed node, each administrator must specify valid credentials for the servicesrunning on that node. Preferred credentials are set from within the Console for each managed service. |
| Configure a remote database for backup or SYSDBA administration | Before using one of the backup management Wizards or submitting an administration task, such as database shutdown or startup, through the OEMJob system, you need to set up your database for remote SYSDBA management. |
| Set up and register recovery catalog | The RMAN recovery catalog should be created and registered within OEM for managing the target database. |
