| Oracle® Enterprise Manager Configuration for Oracle Collaboration Suite 10g Release 2 (10.2) Part Number B16224-02 |
|
|
View PDF |
| Oracle® Enterprise Manager Configuration for Oracle Collaboration Suite 10g Release 2 (10.2) Part Number B16224-02 |
|
|
View PDF |
Part II of this manual describes how to set up Oracle Enterprise Manager Grid Control 10g Release 2 (10.2) to monitor Oracle Collaboration Suite Release 2 (9.0.4).
This chapter contains the following sections:
Grid Control 10g Release 2 Features for Oracle Collaboration Suite Release 2 Components
Benefits of Managing Oracle Collaboration Suite with Grid Control
Before You Configure Grid Control to Manage Oracle Collaboration Suite
General Configuration Tasks for Managing Oracle Collaboration Suite
|
Note: See the chapters in Part I, "Configuring Collaboration Suite 10g Release 1 Targets" for information on setting up Grid Control 10g Release 2 to monitor Oracle Collaboration Suite 10g Release 1 components. |
You can use the following Grid Control 10g Release 2 features designed for monitoring Oracle Collaboration Suite 10g Release 1 components with Oracle Collaboration Suite Release 2 components:
You can create generic services and systems for Oracle Collaboration Suite Release 2 components. To do this:
In Grid Control, navigate to the Targets tab.
Click Services.
In the Add box, choose Generic Service and click Go.
In the Create Generic Service tool, click Help on any page to learn how to use that page.
Note that the "Creating a Collaboration Suite Service and System" instructions are only valid for Oracle Collaboration Suite 10g Release 1 components. You cannot create Oracle Collaboration Suite Release 2 component services using those instructions. Instead, you must create generic services, as described above.
Oracle Collaboration Suite data can be collected from any Oracle Collaboration Suite client machine, regardless of whether the client uses Oracle Collaboration Suite 10g Release 1 or Oracle Collaboration Suite Release 2. However, the collected Oracle Collaboration Suite client configuration data can be viewed only by clicking the Client Configurations link for an Oracle Collaboration Suite 10g Release 1 instance on the Oracle Collaboration Suite Service Home page.
When you configure Grid Control 10g Release 2 to manage Oracle Collaboration Suite Release 2 components, Grid Control provides the following benefits:
An Enterprise Manager Home page for each Oracle Collaboration Suite target that you manage.
From the home page, you can monitor the performance of the component and drill down to analyze specific performance metrics.
A set of charts and performance metrics for each Oracle Collaboration Suite component.
Descriptions of each metric are available from the All Metrics link on each component home page, or by browsing the Target Metrics category in the online help table of contents.
The ability to manage your Oracle Collaboration Suite components as part of your larger computing environment.
For example, using the same Grid Control, you can monitor your Oracle Collaboration Suite components, as well as your application server and database targets.
Oracle Collaboration Suite group home pages that allow you to monitor all the various subcomponents of an Oracle Collaboration Suite component from one set of monitoring pages.
The following sections describe some of the tasks you should accomplish before you begin configuring Grid Control 10g Release 2 to manage Oracle Collaboration Suite Release 2 components:
Gathering Information About Your Oracle Collaboration Suite Release 2 Installation
Installing Oracle Enterprise Manager Grid Control 10g Release 2
Installing the Oracle Management Agent on Your Host Computers
When you are configuring Grid Control 10g Release 2 to manage Oracle Collaboration Suite Release 2 components, it is important that you are familiar with the location of key Oracle Collaboration Suite configuration information.
In particular, you should have the following information available before you begin:
The directory path for the Oracle Collaboration Suite Oracle home
You can obtain this information by reviewing the contents of the following Oracle configuration file on UNIX systems:
/etc/oratab
The Oracle Internet Directory host and port number
You can obtain this information by reviewing the contents of the following Oracle Collaboration Suite configuration file:
OCS_HOME/config/ias.properties
Before you begin configuring Grid Control 10g Release 2 to manage your Oracle Collaboration Suite Release 2 components, you must install and configure Grid Control 10g Release 2 on at least one host computer on your network.
Oracle recommends that you install the Grid Control components on their own host or hosts. For example, if the Oracle Collaboration Suite middle tier is installed on host1.us.oracle.com, then install and configure the Oracle Management Service and Oracle Management Repository on host2.us.oracle.com.
See also Oracle Enterprise Manager Basic Installation and Configuration for Oracle Enterprise Manager 10g Release 2 at:
The following sections provide some guidelines and considerations to keep in mind when you install the Management Agent on your Oracle Collaboration Suite host computers:
After Oracle Collaboration Suite Release 2 and Grid Control 10g Release 2 are installed, you can begin installing the Oracle Management Agent for Grid Control 10g Release 2 on each host computer where an Oracle Collaboration Suite Release 2 component has been installed.
Note that monitoring only your Oracle Collaboration Suite middle-tier components may not provide you with a complete understanding of how your systems are running. For example, if you identify a performance problem with one of your Oracle Collaboration Suite components, you may find that the cause of the problem is not Oracle Collaboration Suite. Instead, the problem might be caused by a database performance problem that could be fixed by using the database tuning features of Grid Control.
As a result, you should install the Management Agent not only on the Oracle Collaboration Suite hosts, but also on the host computers where Oracle Collaboration Suite supporting software has been installed. For example, you should install the Management Agent on your database hosts and Oracle Application Server Infrastructure hosts.
When you install the Management Agent, you must be sure to follow these guidelines:
Install the Management Agent in its own Oracle home.
For example, if the Oracle Collaboration Suite component is installed in /data/ocsmtier, install the Management Agent in /data/emAgent.
Install the Management Agent using the same operating system user group that you used to install the Oracle Collaboration Suite and Oracle Application Server components you want to manage.
If you install the Management Agent using a different user in a different operating system group, you may not be able to monitor certain performance metrics and you may not be able to discover some of the Oracle Collaboration Suite components.
Some of the instructions in this guide refer to local and remote monitoring of Oracle Collaboration Suite targets. The following sections provide more information about this concept:
After you install the Management Agent on your Oracle Collaboration Suite hosts, you can then use the instructions in this guide to create your Oracle Collaboration Suite targets and begin monitoring your Oracle Collaboration Suite environment.
Normally, to create a target, you navigate to the home page for the Management Agent on the host where the target exists and select the target type from the drop-down menu. This action allows the local Management Agent on a particular host to monitor the local targets on that host.
However, for some target types, you can monitor a target from a Management Agent installed on a remote host.
The following example describes how remote monitoring works. Suppose you install the Management Agent on two hosts, HOST1 and HOST2. Automatically, when you install the Management Agent on HOST1, it will discover and begin monitoring the host target, as well as the database and application server targets that are installed on HOST1. In fact, for target types such as hosts and databases, you must monitor the targets on HOST1 with the locally installed Management Agent on HOST1.
However, for some target types and in certain situations, you can monitor one or more targets on HOST1 from the Management Agent on HOST2. This process of managing a target remotely from another Management Agent can be useful in the following situations:
When the targets you want to manage are on a host computer (such as a Windows host) where the Management Agent is either not available or does not support the target type you want to manage.
When for any other reason, you cannot install the Management Agent on the target host computer, or it is more convenient to use a remote Management Agent to manage the targets on a particular host.
To remotely manage a target, simply create the target by navigating to the home page for the remote Management Agent. Use the drop-down menu on the remote Management Agent home page to create the target. As mentioned previously, not all target types can be monitored remotely so this process is only possible for certain types of targets.
The following sections provide recommendations for using specific features of Grid Control to create groups and subtabs to organize the Oracle Collaboration Suite targets. You can organize the Oracle Collaboration Suite targets to best meet the needs of your organization, but these sections describe some guidelines to consider:
Creating an Oracle Collaboration Suite Application Server Group
Creating an Oracle Collaboration Suite Subtab
|
Note: The following sections describe how to use the Groups and Preferences features of Grid Control to organize the Oracle Collaboration Suite targets so they are easier to monitor. For more information about these features, see the Grid Control online help. |
Create a group target for all the hosts that are running Collaboration Suite components. Name the group with an appropriate name, such as OCSHOSTS.
Grid Control includes these group targets: Groups, Database Groups, and Host Groups. For the Oracle Collaboration Suite hosts, you can create a Host Group target or a Group target.
If you create a Group target (as opposed to a Hosts Group target), you can specify a set of summary metrics. For example, Oracle recommends that, at a mimimum, you select the following summary metrics for the group target that has your Oracle Collaboration Suite hosts as members:
Load:CPU Utilization (%)
Load:Memory Utilization (%)
Load:Swap Utilization (%)
The resulting host group is convenient to use for monitoring overall CPU and memory for all your Oracle Collaboration Suite component hosts.
|
See Also: "Creating, Editing, and Viewing Groups" in the Grid Control online help. |
Create a group target for all the databases that support your Collaboration Suite deployment. Name the group an appropriate name, such as OCSDB.
Grid Control provides three types of group targets: Groups, Database Groups, and Host Groups. For the Oracle Collaboration Suite databases, you can create a Database Group target or a Group target.
If you create a Group target (as opposed to a Database Group target), you can specify a set of summary metrics. For example, Oracle recommends that, at a mimimum, you select the following summary metrics for the group target that has your Oracle Collaboration Suite databases as members:
Response:User Logon Time (msec)
Wait Bottlenecks:Wait Time (%)
Throughput:Physical Reads (per sec)
The resulting group is convenient to use for collectively monitoring all the databases in your Collaboration Suite deployment.
|
See Also: "Creating, Editing, and Viewing Groups" in the Grid Control online help. |
Create a group target for all the application servers that support your Collaboration Suite deployment. Name the group an appropriate name, such as OCSAS.
Add the following summary metrics to the group definition:
Resource Usage:CPU Usage (%)
Resource Usage: Memory Usage (MB)
The resulting group is convenient to use for collectively monitoring all the application servers in your Collaboration Suite deployement.
|
See Also: "Creating, Editing, and Viewing Groups" in the Grid Control online help. |
Create a group target for your Collaboration Suite deployment and name it an appropriate name, such as OCSGroup. Add the groups created above (OCSHOSTS, OCSDB, and OCSAS) to this group. You also use this group to collect all targets configured for OCS. After you have configured the targets for each Collaboration Suite application, you can add those new targets to this group.
|
See Also: "Creating, Editing, and Viewing Groups" in the Grid Control online help. |
After you create a new OCSGroup target, you can modify your Grid Control preferences so that the OCSGroup appears as a subtab on the Targets tab. This makes it easy to navigate to the OCSGroup home page, which summarizes the overall performance of your Oracle Collaboration Suite targets.
|
See Also: "Customizing Target Subtabs" in the Grid Control online help. |
