Skip Headers

Oracle® Enterprise Manager Grid Control Installation and Basic Configuration
10g Release 1 (10.1)
Part No. B12012-03
  Go To Table Of Contents
Contents
Go To Index
Index

Previous Next  

4 Getting Started with Enterprise Manager

After the Enterprise Manager installation, the Management Service and Grid Control are automatically started. You can immediately log in to Grid Control with the SYSMAN account and begin using Enterprise Manager to manage your enterprise.

This chapter describes Enterprise Manager's out-of-box configuration, recommends tasks to perform after installation to begin customizing Enterprise Manager for your particular environment, and contains information on how to configure the Oracle Management Agent and Management Service. The following topics are covered in this chapter:

Enterprise Manager's Out-of-Box Configuration

At install time, the following tasks are automatically performed, with no user interaction required:

Default Super Administrator: SYSMAN

A default Super Administrator account, SYSMAN, is created with the password you specified during the installation. After installation, you can immediately log in to the Grid Control Console with this user name and password to perform management tasks. The SYSMAN account owns the database schema containing the Management Repository.


See Also:

To learn more about the SYSMAN user account, refer to the "Setting Up Enterprise Manager for Your Environment" chapter of Oracle Enterprise Manager Concepts.

E-mail Notifications

The SYSMAN account is automatically configured to receive e-mail notifications from Enterprise Manager if, during installation, you specified the Outgoing (SMTP) Mail Server and SYSMAN e-mail address. Also, as part of the self-monitoring feature, a script is created that enables the user to be notified by e-mail in the event that Enterprise Manager goes down unexpectedly.


Note:

If you do not specify the mail server, there will be no notification. If you specify the mail server, but not the e-mail address, the system is set up to send e-mail notifications, but the SYSMAN account will not receive any notifications. If you did not specify the information during install, you can set up e-mail notification afterwards using Enterprise Manager Grid Control.

Notification Rules

E-mail notifications are set up with default Notification Rules for the critical conditions that could occur for all supported target types. For example, for the database target type, a rule is created such that e-mail notifications are sent when any database becomes unavailable, or if any of its key health metrics (Datafile Usage %, Archiver Hung Error Stack, Tablespace Space Used %, and others) becomes critical. The e-mail notifications will be sent to the e-mail address associated with the SYSMAN account. These rules are public; when other administrators are created, they can subscribe to them later.


See Also:

For more information on the notification rules, in Enterprise Manager, click Preferences, then Rules. Click Help on that page.

Automatic Discovery

The first time the Management Agent is started, most supported targets that are located on the same host machine as the Management Agent are automatically discovered and default monitoring levels and data collections are automatically enabled.

Note that you may need to manually discover some targets, such as Oracle Collaboration Suite targets, Web applications, clusters, and Beacons. The Grid Control Enterprise Manager Web Application is discovered automatically.

If you install a Windows Management Agent on a Real Application Cluster database, automatic discovery of database and application server targets may fail. Use the Add Target page of the Grid Control Console to add these targets.


See Also:

For a list of certified targets for Enterprise Manager Grid Control, refer to "Certified Enterprise Manager Targets".

Refer to Managing Oracle Collaboration Suite, available on Oracle Technology Network, for instructions on discovering OCS targets.

For information on manual discovery, refer to "Adding Targets to Be Monitored and Administered by Enterprise Manager" in the Oracle Enterprise Manager online help.


Troubleshooting Problems with Target Discovery

If you are unable to discover targets on a Management Agent host, check for the following problems:

When the Management Agent is installed, an automatic discovery is performed to detect any existing Oracle9iAS 9.0.2 or 9.0.3 instances. If the 9.0.2 or 9.0.3 Oracle9iAS instances were installed by a different OS user than the user that installs the Management Agent, then the file protections on targets.xml within that Oracle9iAS installation may prevent the Management Agent from reading the file. This will prevent the discovery of that Oracle9iAS instance.

To confirm that this is the problem, check the Management Agent logs located at AGENT_HOME/sysman/log/ for "permission denied" errors, where AGENT_HOME is the Oracle home for the Management Agent. To correct the problem, set the file permissions so that it can be read by the user who installed the Management Agent.

This problem does not occur when discovering other existing Oracle Application Server versions on a machine.


See Also:

If you encounter problems monitoring Oracle Database 10g or ASM targets, refer to "Configuring Database and ASM Targets for Monitoring" in this book.

Targets Subtabs

The Hosts, Databases, Application Servers, Web Applications, Groups, and All Targets target subtabs are created. These subtabs are categories of targets that provide immediate access to the targets you may want to access most often.


See Also:

Refer to the Enterprise Manager online help for detailed information on managing each of these target areas.

Using the Grid Control Console for the First Time


Note:

Enabling/Disabling Licensed Functionality

Before you begin using Enterprise Manager Grid Control, you must first set the access levels according to your licensing agreement with Oracle. To do this, perform the following steps using a Super Administrator account, such as SYSMAN.

  1. The first time you log in using SYSMAN, you are taken to the licensing setup page. Otherwise, to get to the licensing setup page, in the Grid Control Console, click Setup, then Management Pack Access.

  2. Select Grant Access or Remove Access for each pack, according to the terms of your licensing agreement.

  3. Click Apply to save your changes. Once access is removed, the functionality associated with the selected pack is no longer available for any targets managed by Enterprise Manager Grid Control.


Enterprise Manager Grid Control provides a Web-based console for managing your entire enterprise. Table 4-1 provides a roadmap of the actions you may want to perform now that Enterprise Manager is installed and running.

The first column describes actions that you may wish to perform; the second contains considerations and reasons for performing the action; the third helps you navigate to the appropriate online help page in Enterprise Manager.

All help topics are contained within the "Setting Up Enterprise Manager" directory of the online help.

Table 4-1 Using Grid Control for the First Time

Action Purpose For More InformationFoot 
Plan Target Management Consider:
  • Which administrators have access to which targets?

  • How much access does each administrators have to the targets?

  • Which administrators, if any, get system level access?

With proper planning, you will have a clearer picture on how to divide the workload among the administrators.

"Setting Up Targets to Monitor and Manage"

"Defining Administrators"

Create Additional Notification Methods If the default e-mail notification is not sufficient.

When new administrators are created, they can immediately have access to the methods.

"Setting Up Notifications for Alerts"
Review and Edit Default Notification Rules If you want SYSMAN to receive notifications for all conditions.

If you want a method other than e-mail to be used.

"Managing Notification Methods" in "Setting Up Notifications for Alerts" subdirectory
Create Groups Logically organize your targets into groups for effective management.

You can later grant group access to administrators rather than individual target access.

"Defining Groups"
Create Roles Create roles to access certain targets and specific management features.

Roles are especially useful if there are several administrators that share similar responsibilities.

"Creating, Editing, and Viewing Roles" in "Defining Administrators" subdirectory
Create Administrators Make sure administrators reflect your management team.

Assign administrators roles/privileges to divide their responsibilities.

Ensure that no one shares an account.

SYSMAN should be the only Super Administrator account.

"Creating, Editing, and Viewing Administrators" in "Defining Administrators" subdirectory
Perform Advanced Configuration Tasks Enable Secure Mode for Enterprise Manager.

Configure firewalls that exist between various components of Enterprise Manager.

For advanced configuration topics, refer to Oracle Enterprise Manager Advanced Configuration.

Footnote For more information, go to the online help topic listed in this column. All topics are contained in the Setting Up Enterprise Manager directory.

Controlling the Management Repository, Service, and Agent

The Management Service and the Grid Control Console are automatically started after the Enterprise Manager installation. This section provides information on how to manipulate the Management Agent and Management Service after installation.


See Also:

For information on Enterprise Manager's directory structure, refer to the "Understanding the Enterprise Manager Directory Structure" section of Oracle Enterprise Manager Advanced Configuration.

For information about configuring Enterprise Manager components, such as Management Agents and Beacons, for use in a firewall environment, refer to Oracle Enterprise Manager Advanced Configuration.


Starting the Management Repository Database

If you need to start the Management Repository database, use SQL*Plus to connect to Oracle as SYSDBA, and then issue the STARTUP command.


See Also:

For instructions on managing the repository database, such as how to drop the repository schema, refer to the "Maintaining and Troubleshooting the Management Repository" chapter of Oracle Enterprise Manager Advanced Configuration.

For detailed instructions on starting up a database, refer to the "Starting Up and Shutting Down" chapter in the Oracle Database Administrator's Guide.


Starting and Stopping the Management Service

The relevant emctl commands for Solaris are listed in the following table. For Windows, start and stop all services using the Services Control Panel.

You must be in the AS_HOME/bin directory to issue the emctl commands, where AS_HOME is the Oracle Application Server home directory in which the Oracle Management Service is installed and deployed.

If you want to ... Enter the following command
Start the Management Service
emctl start oms
Stop the Management Service
emctl stop oms
Verify status of the Management Service
emctl status oms
Start all components of the Application Server, including the Management Service and WebCache
opmnctl startall
Stop all components of the Application Server, including the Management Service and WebCache
opmnctl stopall


See Also:

For detailed instructions, refer to the "Starting and Stopping Enterprise Manager Components" section of the "Introduction to Enterprise Manager Advanced Configuration" chapter of Oracle Enterprise Manager Advanced Configuration. You can find this guide at:
http://otn.oracle.com/documentation/oem.html

Starting and Stopping the Management Agent

The relevant emctl commands for Solaris are listed in the following table. For Windows, start and stop all services using the Services Control Panel.

You must be in the AGENT_HOME/bin directory to issue the emctl commands, where AGENT_HOME is the Oracle home directory for your Management Agent. Note that this directory is different than the AS_HOME/bin directory, which is for the Oracle Application Server Control Agent.

If you want to ... Enter the following command
Start the Management Agent
emctl start agent
Stop the Management Agent
emctl stop agent
Verify status of the Management Agent
emctl status agent


See Also:

For detailed instructions, refer to the "Starting and Stopping Enterprise Manager Components" section of the "Introduction to Enterprise Manager Advanced Configuration" chapter of Oracle Enterprise Manager Advanced Configuration. You can find this guide at:
http://otn.oracle.com/documentation/oem.html

Accessing Enterprise Manager Grid Control

The Enterprise Manager Grid Control Console is the primary tool for managing your Oracle environment.

Use the following URL to log in to the Grid Control Console:

http://<oms_hostname>.<domain>:<port>/em

or

https://<oms_hostname>.<domain>:<port>/em

If you are uncertain about the port number, you can refer to one of the following files:

  • ORACLE_HOME/install/setupinfo.txt as displayed by the Oracle Universal Installer at the end of the install

  • ORACLE_HOME/install/portlist.ini on the Management Service machine

When the login dialog appears, enter the user name and password for the Super Administrator SYSMAN.


See Also:

For more information on Grid Control security, refer to the "Enterprise Manager Security" chapter of Oracle Enterprise Manager Advanced Configuration.

For more information on port settings, refer to the "Viewing a Summary of the Ports Assigned During the Application Server Installation" section of the "Configuring Firewalls" chapter of Oracle Enterprise Manager Advanced Configuration.

Refer also to "Viewing and Modifying Application Server Port Assignments" in the Enterprise Manager online help.