9 Monitoring Domain, Node, Service, and Server Performance

Use the Application Server Control to monitor Oracle Content DB domain, node, service, and server performance. You can use this information to get an overall picture of the performance of the domain, or to determine whether the configuration of the domain needs to be changed.

This chapter provides information about the following topics:

• Monitoring Domain Performance

• Monitoring Node Performance

• Monitoring Service Performance

• Monitoring Server Performance

• Viewing Logs

• Accessing Metrics and Monitoring Metric Alerts

Monitoring Domain Performance

You can use the Application Server Control to view different types of performance information for the Oracle Content DB domain. This section contains the following topics:

• About Oracle Content DB Performance Metrics

• Viewing Performance Information

• Configuring Performance Metrics

About Oracle Content DB Performance Metrics

There are three types of Oracle Content DB performance metrics: repository metrics, Dynamic Monitoring Service (DMS) metrics, and other metrics. See "Monitoring Server Performance" for information about DMS metrics.

Repository metrics are metrics that apply to the entire Oracle Content DB domain. These metrics include:

• Domain Response

• Documents

• Documents By MIME Type

• Users

• Users By Site

• Libraries By Site

• Nodes

• Sessions By Server (Node)

• Sessions By Server (Domain)

• All Sessions

Other Oracle Content DB performance metrics include:

• Response

• Resource Usage

• Processes

• Web Application URL Timing

• Records DB Application URL Timing

• Load Balanced Web Application URL Timing

• Load Balanced Records DB Application URL Timing

Some metrics must be configured for particular middle tiers. See "Configuring Performance Metrics" for more information.

Viewing Performance Information

You can view Oracle Content DB performance metrics in two ways:

• All Oracle Content DB metrics can be viewed from the All Metrics pages, as long as they are being collected on that middle tier.

• Repository metrics can also be viewed from the Domain Performance & Statistics pages, which provide information in a more graphical format than the All Metrics pages. These pages are not available on middle tiers where repository metrics are not being collected.

Using the All Metrics Link

All Oracle Content DB performance metrics that are being collected on a middle tier can be accessed from the All Metrics pages in the Application Server Control. To access these pages, from the Performance section of the Content DB Home page, click All Metrics.

To view information about a particular metric, click the metric name, then click Help on the resulting Metric Detail page.

Using the Domain Performance & Statistics Pages

The Domain Performance & Statistics pages in the Application Server Control provide tables and charts that present information about Oracle Content DB users, Libraries, documents, sessions, and overall usage patterns. This information can help you evaluate system performance and guide you in making changes to your configuration.

The Domain Performance & Statistics pages are only available on middle tiers that have been configured for repository metrics. See "Configuring Performance Metrics" for more information.

To view domain performance information:

1. On the Content DB Home page, click Domain Performance & Statistics.

   Figure 9-1 shows the Domain Performance & Statistics page.

   Figure 9-1 Domain Performance & Statistics Page

   
   Description of "Figure 9-1 Domain Performance & Statistics Page"
   
   

2. Select one of the four subtabs:

   • The Users and Libraries subtab provides information about the total number of users and the number of users for each Site, and provides information about Personal and Shared Libraries for each Site.

   • The Documents subtab provides systemwide information about documents.

   • The Sessions subtab lets you view the connected sessions by server type.

   • The Node Usage subtab lets you monitor sessions, threads, and memory by node and host.

3. To refresh the information for the Sessions or Node Usage subtabs, refresh your browser, or click the Refresh Data icon in the upper right portion of the page.

   Because data for the Users and Libraries and Documents subtabs is only collected at preset intervals, refreshing the page will not cause the data to be collected again. To see the last time the data was collected on these tabs, look at the Data Collection Time displayed in the upper left corner of the page.

4. To move between the table view and the chart view, make a selection from the Select a View list.

Table 9-1 lists the various charts, graphs, and tables, and shows you which subtab and view names you need to select to access the information.

Table 9-1 Reference to Statistical Information About the Domain and Nodes

Chart, Graph, or Table Name	Statistics or Information Displayed	Subtab	Select a View Item
Users	Total Number of Users Total Number of Users by Site	Users and Libraries	Not applicable
Libraries	Tabular display showing: Total number of Libraries for each Site Total allocated quota for each Site Total consumed quota for each Site Percentage of quota consumed for each Site These statistics are also available for Personal and Shared Libraries for each Site; click Show in the Details column to access this information.	Users and Libraries	Not applicable
Document Table	Document distribution and space consumption by MIME type.	Documents	Table
Document Distribution Chart	Space consumed, displayed by MIME type (displays a bar chart comparing quantities of the different types of documents stored in the system).	Documents	Distribution Chart
Document Consumption Chart	Space consumed, displayed by MIME type.	Documents	Consumption Chart
Sessions Table	Tabular display of the total number of connected sessions for each protocol server or agent.	Sessions	Table
Sessions Chart	Pie chart of total number of connected sessions for each protocol server or agent. The sessions for all the agents are displayed as a combined result.	Sessions	Chart
Node Usage Table	Tabular display of node name, host name and IP address, number of sessions, number of threads, and JVM total/free/used memory for each node.	Node Usage	Table
Node Usage Chart	Bar charts showing the same information as the Overall Usage Table.	Node Usage	Chart

Configuring Performance Metrics

You can use the Application Server Control to select which Oracle Content DB performance metrics to configure on the current middle tier. For example, you can collect metrics related to Oracle Content DB Web application response time.

To configure performance metrics:

1. On the Content DB Home page, in the Performance section, click Metric Configuration.

2. You can collect repository metrics on this middle tier. To do this, select Run Repository Metric?, and provide the Oracle Content DB schema password and the database connect descriptor. If you do not know the database connect descriptor, you can copy it from the Content DB Home page.

   To avoid the potential performance impact of duplicate metric collection, only run repository metrics on one middle tier. Be aware that the Domain Performance & Statistics pages are only available from middle tiers on which repository metrics are collected.

3. You can collect metrics related to Oracle Content DB Web application response time on this middle tier.

   • To collect metrics related to the Oracle Content DB Web application URL for this middle tier, select Run Web Application Response Time Metric?, and provide the correct Oracle Content DB Web application URL for this middle tier.

   • To collect metrics related to the load-balanced URL for the Oracle Content DB Web application, select Run Load Balanced Web Application Response Time Metric?, and provide the correct Oracle Content DB load-balanced Web application URL.

4. You can collect metrics related to Oracle Records DB Web application response time on this middle tier.

   • To collect metrics related to the Oracle Records DB Web application URL for this middle tier, select Run Records DB Application Response Time Metric?, and provide the correct Oracle Records DB Web application URL for this middle tier.

   • To collect metrics related to the load-balanced URL for the Oracle Records DB Web application, select Run Load Balanced Records DB Application Response Time Metric?, and provide the correct Oracle Records DB load-balanced Web application URL.

   If Oracle Records DB was not enabled, these metrics will report that the Oracle Records DB Web application URLs are not available.

5. Click OK.

Monitoring Node Performance

You can use the Application Server Control to view performance information about both regular nodes and HTTP nodes, including JVM total, used, and free memory, JVM thread count, and default time zone and locale.

To view node performance information:

1. On the Content DB Home page, click the name of the node for which you want to view performance information.

2. On the Node page, click the Details link to display operating system and JVM information about that node.

   Figure 9-2 shows the Details page.

   Figure 9-2 Details Page for Selected Node

   
   Description of "Figure 9-2 Details Page for Selected Node"
   
   

Monitoring Service Performance

You can view real-time statistics for the Committed Data Cache, the Read-Only Connection Pool, and the Writable Connection Pool for each service. You can also reset the statistics.

1. On the Content DB Home page, click the node whose service you want to monitor.

2. On the Node page, click the service (for example, IfsDefaultService).

3. On the Service page, scroll to the Performance section.

4. Click the link to the statistics you want to view: Committed Data Cache Statistics or Connection Pool Statistics.

   Figure 9-3 shows the Committed Data Cache Statistics page.

   Figure 9-3 Committed Data Cache Statistics Page

   
   Description of "Figure 9-3 Committed Data Cache Statistics Page"
   
   

   Figure 9-4 shows the Connection Pool Statistics page.

   Figure 9-4 Connection Pool Statistics Page

   
   Description of "Figure 9-4 Connection Pool Statistics Page"
   
   

5. Click Reset Statistics in the Committed Data Cache, Read-Only Connection Pool, or Writeable Connection Pool areas to reset cache or connection pool statistics.

Logging Service Performance Information

The Statistics Agent captures the statistics for the Committed Data Cache, as well as the Read-Only and Writeable Connection Pools, and writes them to the node log and the application log. You can also configure this agent to write statistics to a document stored in the Oracle Content DB repository.

See "Viewing Logs" for information about the node log and application log. See "Statistics Agent" for information about the Statistics Agent.

Monitoring Server Performance

You can monitor server performance by viewing Dynamic Monitoring Service (DMS) metrics that were defined for some servers. DMS metrics are a special type of performance metric that can be defined in Oracle Application Server. DMS metrics for Oracle Content DB include:

• WebDAV Servers

• FTP Servers

• Servers

Some DMS metric information can be viewed on the Node page, and on the Server page for some servers. For example, the Servers section of the Node page shows the Last Start Time and Last Stop Time for each server, while the FTP Server page displays Requests Completed, Average Request Processing Time (seconds), Downloaded Content Size (MB), and Uploaded Content Size (MB).

DMS metrics can also be viewed using the dmstool utility and AggreSpy. For more information about DMS metrics and how to view them, see Oracle Application Server Performance Guide.

Viewing Logs

The following sections provide a list of Oracle Content DB logs, and information about how to view logs in the Application Server Control.

Oracle Content DB Logs

Logs are generated by each node. Because some logs can get very large, manage your log files to ensure that you do not run out of disk space.

You can set the level of logging for various loggers, such as the FTP server, repository, or Web application, from the Configure Loggers page in the Application Server Control. See "Configuring Node Loggers" for more information.

The Node Log

The node log records major state transitions (such as started, failed, or restarted) and provides centralized data on overall node health. This log is useful for troubleshooting protocol servers and agents. All errors are logged with stack traces. Log properties, such as Log Level and Rotation Interval, are specified in the node configuration of the node being monitored. The location of the node log cannot be changed. The node log is located in:

ORACLE_HOME/content/log/domain_name/node_name.log

You can also refer to the OPMN log for the regular node:

ORACLE_HOME/opmn/logs/Content~Node~1

The Application Log

The application log records additional information for HTTP nodes. This log is useful for troubleshooting the Oracle Content DB and Oracle Records DB applications and the WebDAV server. All errors are logged with stack traces. By default, application logs are located in:

ORACLE_HOME/j2ee/OC4J_Content/application-deployments/Content/OC4J_Content_
default_island_1/application.log

ORACLE_HOME/opmn/logs/Content~OC4J_Content~default_island~1

ORACLE_HOME/j2ee/OC4J_RM/application-deployments/rm/OC4J_RM_
default_island_1/application.log

ORACLE_HOME/opmn/logs/Content~OC4J_RM~default_island~1

Log for changehostname Script

When you run the changehostname script to change a middle-tier host name or IP address, a log is generated. This log is located in:

ORACLE_HOME/content/log/changehostname.log

Viewing Oracle Content DB Logs from the Application Server Control

You can view a variety of logs from the Application Server Control. This feature lets you view the logs without having to remember the individual log location.

To view log, click the Logs link in the upper-right corner of any Application Server Control page.

• The View Logs page provides a custom list of logs relevant to the component from where the link was clicked. For example, if you click Logs from any Oracle Content DB page, the View Logs page will display relevant Oracle Content DB logs, such as the node logs.

• You can also use Simple Search to locate logs. To do this, select the target that corresponds to the type of log you want to see from the Available Components list, and move it to the Selected Components list:

  • Select the Oracle Content DB instance (for example, Content) if you want to see the node log.

  • Select OC4J_Content or OC4J_RM to see the application log for Oracle Content DB or Oracle Records DB.

  • Select Enterprise Manager to see Application Server Control logs.

  Click Search to see the log names in the Results table.

Click the name of a log to see the log data. By default, the last 500 lines in the log appear in the log viewer. You can view up to 2000 lines. To download the contents of the entire log, click the log name at the top of the screen. If the log is large, the download may take several minutes.

Accessing Metrics and Monitoring Metric Alerts

You can access Oracle Content DB metrics from the Oracle Enterprise Manager 10g Grid Control. The following sections provide information about how to access the metrics and how to set up metric collection:

• Installing the Grid Control and Oracle Management Agent

• Setting the Management Agent Classpath

• Accessing the Grid Control

• Changing the Default Metric Collection Behavior

• Viewing Oracle Content DB Metrics in the Grid Control

• Metric Thresholds and Metric Collection Intervals

For more information about the metrics available for Oracle Content DB, click Help on any Grid Control Metrics page. For more information about the Grid Control, see Oracle Enterprise Manager Concepts.

Note: The Grid Control uses "Oracle Content Services," the previous product name for Oracle Content DB, as the display name for Oracle Content DB targets.

Installing the Grid Control and Oracle Management Agent

Before you begin configuring the Grid Control to manage Oracle Content DB, you must install and configure the Grid Control on at least one host computer on your network. You can only use Grid Control 10g (10.2.0.2) with Oracle Content DB.

Oracle recommends that you install the Grid Control components on their own host or hosts. For example, if the Oracle Content DB 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.

You must install the Grid Control Oracle Management Agent on every Oracle Content DB host that you want to manage with the Grid Control.

See Oracle Enterprise Manager Grid Control Installation and Basic Configuration for more information.

Setting the Management Agent Classpath

To manage Oracle Content DB with Grid Control, you must run a script that is installed with the Management Agent. This script configures the Management Agent classpath so that the Management Agent can monitor the Oracle Content DB component.

To modify the Management Agent classpath:

1. Stop the Management Agent, if it has been started:

   • UNIX: AGENT_HOME/bin/emctl stop agent

   • Windows: AGENT_HOME\bin\emctl stop agent

2. Run the following command:

   • UNIX: AGENT_HOME/files/emagent/bin/ifsemchgtarget

   • Windows: AGENT_HOME\files\emagent\bin\ifsemchgtarget

3. When prompted, choose 4. Oracle Content Services Release 10.1.2.

   (Oracle Content Services was the former product name for Oracle Content DB.)

4. Start the Management Agent:

   • UNIX: AGENT_HOME/bin/emctl start agent

   • Windows: AGENT_HOME\bin\emctl start agent

Accessing the Grid Control

To access the Grid Control, perform the following steps:

1. Use the following URL to access the Grid Control from a Web browser:

   http://host_name:port/em
   
   

   or

   https://host_name:port/em
   

   
   

   Note: 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 installation ORACLE_HOME/install/portlist.ini on the Management Service computer

   
   

2. Log in as sysman, using the password you created during Oracle Enterprise Manager 10g installation. Or, log in as another Grid Control user with administrator privileges.

Changing the Default Metric Collection Behavior

You may want to enable or disable an Oracle Content DB metric for a middle-tier host after initial configuration. For example, you may want to enable the Load Balanced Application URL Timing metric on a middle tier because a load balancer has been recently added to the system, or you may want to disable the Application URL Timing metric on a middle tier because the HTTP node has been removed from that middle tier.

To change the default metric collection behavior, reconfigure the Oracle Content DB (oracle_files) targets for the given Oracle Content DB domain in the Grid Control.

Note: In the following section, wherever you see "Oracle Content DB," the Grid Control displays "Oracle Content Services," the previous product name for Oracle Content DB.

Reconfiguring Oracle Content DB (oracle_files) Targets in the Grid Control

Follow these steps to change the default metric collection behavior of Oracle Content DB targets:

1. From the Grid Control Home page, click the Targets tab, then click the All Targets subtab. A list of all the discovered targets across the network appears.

2. Locate the Oracle Content DB target for the given middle tier. You can perform a quick search by entering the schema name in the Search field and clicking Go.

3. Select the Oracle Content DB target and click Configure.

4. Set the following values to TRUE or FALSE to enable or disable metric collection. The values must be in upper case.

   • Run Repository Metric?

     The default is TRUE for the first middle tier to be configured. For any additional Oracle Content DB middle tiers, the default is FALSE.

   • Run Web Application Response Time Metric?

     The default is TRUE. If you set this parameter to TRUE, specify a valid value for Web Application URL. If you sent this parameter to FALSE, enter NULL for Web Application URL.

   • Run Load Balanced Web Application Response Time Metric?

     The default is FALSE. If you set this parameter to TRUE, specify a valid value for Load Balanced Web Application URL. If you sent this parameter to FALSE, enter NULL for Load Balanced Web Application URL.

   • Run RM Application Response Time Metric?

     The default is TRUE. If you set this parameter to TRUE, specify a valid value for RM Application URL (in other words, the URL for the Oracle Records DB application). If you sent this parameter to FALSE, enter NULL for RM Application URL.

   • Run Load Balanced RM Application Response Time Metric?

     The default is FALSE. If you set this parameter to TRUE, specify a valid value for Load Balanced RM Application URL (in other words, the load-balanced URL for the Oracle Records DB application). If you sent this parameter to FALSE, enter NULL for Load Balanced RM Application URL.

   For more information about these parameters, click the Help link.

5. Click OK.

Viewing Oracle Content DB Metrics in the Grid Control

After you have logged in to the Grid Control, you can use the search function to navigate to the pages that show Oracle Content DB metrics.

To access Oracle Content DB metrics using the search function, follow these steps:

1. Click the Targets tab.

2. Click the All Targets subtab. A list of targets appears.

3. Type the name of your Oracle Content DB host in the Search field and click Go.

4. Click the name of your Oracle Content DB instance.

5. Click All Metrics to see a list of Oracle Content DB metrics.

Metric Thresholds and Metric Collection Intervals

You can use the Grid Control to edit the thresholds for Grid Control metrics. When you edit the thresholds, a customized collection file will be created in the following directory:

AGENT_HOME/sysman/emd/collection

For more information, see Oracle Enterprise Manager Concepts.

Metric Collection Intervals

You cannot use the Grid Control to update the metric collection intervals. If you must change the default intervals, you can manually edit the customized collection file described in the previous section. Do not specify a collection rate higher than once every minute, or it will have a negative impact on the performance of your entire system.