2 Introduction to Administration Tools

2.1.1 Managing Oracle Application Server with Oracle Enterprise Manager 10g

The primary tool for managing Oracle Application Server—as well as your entire Oracle environment—is Oracle Enterprise Manager 10g.

With Enterprise Manager, you can use your Web browser to:

• Manage individual Oracle Application Server instances with Oracle Enterprise Manager 10g Application Server Control.

• Centrally manage all the components of your network and your enterprise with Oracle Enterprise Manager 10g Grid Control.

• Manage your Oracle Application Server Metadata Repository with the Oracle Enterprise Manager 10g Database Control.

When used together, Application Server Control, Grid Control, and Database Control provide a complete set of efficient tools to reduce the cost and complexity of managing your enterprise.

2.1.2 Managing Oracle Application Server from the Command Line

Oracle Application Server also provides command-line interfaces to several key management technologies. After you become familiar with the architecture and components of your application server, command-line tools can help you automate your management procedures with scripts and custom utilities.

The most important administration command-line tools are:

• runstartupconsole, which starts and stops Application Server instances. You can use runstartupconsole to:

  • Start and stop entire Application Server instances, including the Infrastructure, middle tier, and Enterprise Manager, at the same time when they are installed on the same host.

  • Start and stop either the Infrastructure or the middle tier.

  • Start and stop Enterprise Manager in the Infrastructure or middle-tier instances, or both at the same time.

  
  

  See Also: Section 3.2, "Starting and Stopping Application Server Instances"

  
  

• opmnctl, which provides a command-line interface to Oracle Process Manager and Notification Server (OPMN). You can use opmnctl to:

  • Start and stop components, instances, and OracleAS Clusters

  • Monitor processes

    
    

    See Also: Section 2.2.2, "About the Underlying Technologies" and Oracle Process Manager and Notification Server Administrator's Guide

    
    

• dcmctl, which provides a command-line interface to Distributed Configuration Management (DCM). You can use dcmctl to:

  • Create and remove OC4J instances and OracleAS Clusters

  • Deploy and undeploy OC4J applications

  • Archive and restore configuration information

  • Obtain configuration information

    
    

    See Also: Section 2.2.2, "About the Underlying Technologies" and Distributed Configuration Management Administrator's Guide

    
    

In addition to opmnctl and dcmctl, Oracle Application Server provides many other command-line tools for performing specific tasks.

2.1.3 Using Other Tools to Monitor the Built-In Performance Metrics

After you install and start Oracle Application Server, the application server automatically begins gathering a set of built-in performance metrics. These built-in performance metrics are measured continuously using performance instrumentation inserted into the implementations of Oracle Application Server components.

The Application Server Control Console presents a subset of these performance metrics in an organized fashion on the application server component home pages. For example, the Oracle HTTP Server metrics are presented as a series of charts on the Status Metrics page, which is available from the Oracle HTTP Server home page. You can also display all the metrics for a particular component by using the All Metrics page.

Alternatively, you may want to view the complete set of built-in performance metrics, or you may need to monitor a specific set of application server component metrics. Oracle Application Server provides a set of command-line and servlet-based tools to view the Oracle Application Server built-in performance metrics directly, outside of the Application Server Control Console.

2.2.1 Introducing the Enterprise Manager Home Pages

Oracle Application Server provides a wide variety of software solutions designed to help you run all aspects of your business. As a result, you will want to manage Oracle Application Server from different levels of detail.

At times, you may want to manage a single application server instance; or, you may find it efficient to combine multiple instances into an OracleAS Cluster. At other times, you will want to manage a specific application server component.

To support these multiple levels of management, Oracle introduces the Oracle Enterprise Manager home pages. Each home page provides the information you need to monitor the performance and availability of Oracle Application Server from a particular level of management detail. Selected home pages also provide tools for configuring your Oracle Application Server components.

From each home page, you can obtain high-level information or you can drill down to get more specific information about an instance, component, or application.

Consider the following pages that are available when you use the Application Server Control Console:

• Use the OracleAS Farm page to view a set of related application server instances on your network and to create OracleAS Clusters that speed up the configuration and deployment of your Web applications. See Section 2.3.4, "Using the Oracle Application Server Farm Page" for more information.

• Use the Application Server Home page to manage all aspects of an individual application server instance. See Section 2.3.3, "Using the Application Server Home Page" for more information.

• Drill down to a component home page to monitor or configure an individual component of the application server. For example, use the Oracle HTTP Server Home page to monitor the performance of your Web server, or use the Oracle Application Server Containers for J2EE (OC4J) home page to deploy a custom Web-based application. See Section 2.3.5, "Using an Oracle Application Server Component Home Page" for more information.

2.2.2 About the Underlying Technologies

The Application Server Control Console relies on various technologies to discover, monitor, and administer the Oracle Application Server environment. Table 2-1 provides a summary of the underlying technologies leveraged by the Application Server Control Console.

2.2.3 Managing Previous Versions of Oracle Application Server

Previous versions of Oracle Application Server (specifically, Oracle9i Application Server 9.0.2 and 9.0.3) included the Oracle Enterprise Manager Web site, a Web-based tool that offers management capabilities similar to those provided by the Application Server Control Console.

In fact, you can still use the Enterprise Manager Web site to manage Oracle9i Application Server 9.0.2 and 9.0.3 after you begin deploying Oracle Application Server 10g (10.1.2 or 9.0.4) and its Application Server Control.

However, if you are familiar with the Enterprise Manager Web site and you plan to continue managing previous versions of Oracle Application Server, you should be aware of several differences between the Enterprise Manager Web site and the Application Server Control. In particular, you should note the following:

• Oracle9i Application Server (9.0.2) and Oracle9i Application Server (9.0.3) used one Enterprise Manager Web site to manage all the application server instances on a host.

  You could navigate to individual Enterprise Manager home pages for each application server, but only one instance of the Enterprise Manager Web site was running on the host and you managed all the application server instances from one Enterprise Manager Web site URL. This approach to application server management was convenient, but it required all application server instances to be installed and managed by the same operating system user.

• The current version of Oracle Application Server provides one Application Server Control for each application server instance on a host.

  For example, if you install two application server instances on a single host, and you want to manage both instances, two separate instances of the Application Server Control—one for each application server instance—must be started on the host.

  As a result, each application server instance provides a unique URL (specifically, a unique HTTP Server listening port number) for accessing the Application Server Control Console.

• If you have Oracle9i Application Server (9.0.2 or 9.0.3) and Oracle Application Server 10g (10.1.2 or 9.0.4) instances on the same host, and you have to deinstall a 9.0.2 or 9.0.3 instance, you must apply a patch to ensure Oracle Enterprise Manager continues to work after the change. Refer to the section on deinstallation of 9.0.2 or 9.0.3 Oracle homes after you upgrade to Oracle Application Server 10g (10.1.2) in the Oracle Application Server Upgrade and Compatibility Guide.

2.2.4 Using the Application Server Control Console Online Help

At any time while using the Application Server Control Console, you can click Help at the top of the page to get more information. In most cases, the Help window displays a help topic about the current page. Click Contents in the Help window to browse the list of help topics, or click Search to search for a particular word or phrase.

2.3.1 Displaying the Application Server Control Console

The following sections describe how to display the Application Server Control Console and introduce you to the initial home pages you should see when you display the Application Server Control Console for the first time:

• Using the Application Server Control Console URL

• Displaying the Application Server Control Console from the Welcome Page

(UNIX) ORACLE_HOME/install/setupinfo.txt
(Windows) ORACLE_HOME\install\setupinfo.txt

http://mgmthost1.acme.com:1156

2.3.2 Understanding the Initial Application Server Control Console Home Page

When you first display the Application Server Control Console, the initial home page you see varies depending upon whether or not the instance belongs to an OracleAS Farm.

Table 2-2 describes the Enterprise Manager home pages that might be used as a starting point when you first browse to the Application Server Control Console.

2.3.3 Using the Application Server Home Page

From the Application Server Home page (Figure 2-1), you can start and stop the application server instance, monitor the overall performance of the server, and review the components of the server. You can also drill down and examine the performance of a particular component and configure the component.

Figure 2-1 Application Server Home Page

Description of "Figure 2-1 Application Server Home Page"

The Application Server Home page provides a table that lists the components of the application server. From this table, you can also get a snapshot of how each individual component is performing.

From the System Components table, you can display a home page for each component of the application server.

You can perform the following management functions from the Application Server Home page:

• Click Logs at the top of the page to locate and search the various Oracle Application Server log files, as well as the Oracle Application Server Log Repository.

• Click Topology to view the Topology Viewer, which provides a graphical view of the application server processes managed by OPMN.

  
  

  See Also: Section 2.4.1, "Reviewing the Application Server Component Topology"

  
  

• Click J2EE Applications to display a list of the applications deployed across all the OC4J instances within this Oracle Application Server.

• Click Ports to view a list of all the ports currently in use by the various Oracle Application Server components. You can also modify many of the port assignments when necessary.

• Click Infrastructure to configure Identity Management, Grid Control Management, or OracleAS Farm Repository Management.

• Click Backup/Recovery to perform backup and recovery operations for the selected Oracle Application Server instance.

  
  

  See Also: Part V, "Backup and Recovery" and the Enterprise Manager online help for more information about backup and recovery procedures.

  
  

• Click Enable/Disable Components to control whether or not the selected components appears in the list of system components and whether or not the component is affected by server-wide actions, such as Start All or Restart All. When a component is disabled, it does not consume any system resources and you can always enable it later.

  
  

  See Also: Section 3.4, "Enabling and Disabling Components"

  
  

For more information, click Help after selecting an option on the Application Server Home page.

2.3.4 Using the Oracle Application Server Farm Page

If your application server instance is part of an OracleAS Farm, your start page for the Application Server Control Console is the OracleAS Farm page (Figure 2-2).

The OracleAS Farm page displays a list of the standalone application server instances and OracleAS Clusters associated with your OracleAS Infrastructure 10g. Standalone instances are application server instances that are not part of an OracleAS Cluster.

You can configure your application server instance to use OracleAS Infrastructure 10g by clicking Infrastructure on the Application Server Home page. For more information, see the Enterprise Manager online help.

Using the Farm page, you can perform the following tasks:

• View multiple application server instances on multiple hosts

• Drill down to the Application Server Home page for each instance

• Create and manage OracleAS Clusters

  
  

  See Also: Oracle Application Server High Availability Guide for more information about using OracleAS Clusters

  
  

Figure 2-2 OracleAS Farm Home Page

Description of "Figure 2-2 OracleAS Farm Home Page"

2.3.5 Using an Oracle Application Server Component Home Page

Component home pages vary from one component to another because each component has different monitoring and configuration requirements. However, most of the component home pages have the following common elements:

• A general information section that includes an icon to indicate the current state of the component and buttons for starting and stopping the component (if applicable)

• Status information, including CPU and memory usage information, so you can get a snapshot of how the component is performing

• Component-specific information, such as a virtual hosts tab on the HTTP Server home page or a list of deployed applications on the OC4J home page

• Links to administrative functions where appropriate, so you can modify the configuration of selected components. In many cases, this means you can use a graphical user interface to modify configuration files.

2.4.1 Reviewing the Application Server Component Topology

Click Topology at the top of any page in Application Server Control Console to display the Topology Viewer (Figure 2-3). The Topology Viewer provides a graphical, real-time representation of application server processes managed by Oracle Process Manager and Notification Server (OPMN).

The Topology Viewer identifies each component of the application server with an icon. The position of each icon on the page and the connections between the icons represent the relationships between each component. Visual clues in the Topology Viewer help you quickly identify components that are down or performing poorly.

If you are managing multiple application servers as part of an OracleAS Farm, the viewer also shows the relationships between the application server instances, including any OracleAS Clusters you have created.

From the Topology Viewer, you can perform the following tasks:

• View the status of components

• Start, stop, or restart processes

• Monitor performance across the application server environment

• Drill down to component home pages for details

Figure 2-3 Topology Viewer

Description of "Figure 2-3 Topology Viewer"

2.4.2 Reviewing General Information and Resource Usage

The Application Server Home page provides general information about the status of your server, including the name, location, and application server availability. The home page also provides high-level information about CPU and memory usage. When reviewing the home page, review the CPU Usage and Memory Usage charts for excessive CPU or memory usage by the application server (Figure 2-4).

Figure 2-4 General Section of the Application Server Home Page

Description of "Figure 2-4 General Section of the Application Server Home Page"

If you suspect that the application server is using too many resources, review the list of components to review the resource usage of each component (Figure 2-5).

Figure 2-5 System Components Table on the Application Server Home Page

Description of "Figure 2-5 System Components Table on the Application Server Home Page"

Consider disabling any components that you are not currently using as part of this application server instance. Disabled components are not started when you start the application server and as a result do not consume system resources. You can always enable a disabled application server component at a later time.

2.4.3 Reviewing the Resources of the Application Server Host

Many performance or configuration issues are directly related to a lack of available resources on the host. Before you drill down to analyze the performance and resource usage of the individual application server components, review the resources and characteristics of the application server host.

Click the host name in the General section of the Application Server home page to display the Host home page. The Host home page provides a summary of the operating system, memory, and disk capacity. The Load section of the page provides a CPU chart that breaks down the CPU usage into categories of usage; the load metrics beneath the chart provide details about system memory usage (Figure 2-6).

Figure 2-6 General Information and Load Statistics on the Host Home Page

Description of "Figure 2-6 General Information and Load Statistics on the Host Home Page"

Scroll to the bottom of the page to view a set of links to real-time performance metrics. If you are concerned about the CPU and memory usage on the system, click Top Processes to display tables listing the processes that are using the most resources on the host.

Click Filesystems to display a bar chart that reveals the amount of disk space available on the application server host (Figure 2-7).

Figure 2-7 Disk Space Usage Chart Available from the Host Home Page

Description of "Figure 2-7 Disk Space Usage Chart Available from the Host Home Page"

2.4.4 Monitoring Application Server Components

After you review the high-level performance metrics and the resources available on the application server host computer, you can then begin to look for potential issues within the individual application server components.

To diagnose problems with individual application server components, click the component name in the System Components table on the Application Server home page. This technique of "drilling down" to obtain more detail can help you isolate problems in a particular component or area of the application server.

2.4.5 Displaying the All Metrics Page for the Application Server or an Application Server Component

The Application Server Control Console provides you with selected performance metrics that you can use to determine the overall performance of your application server. In some cases, the metrics are shown as performance charts; in other cases, you can monitor the real-time value of the metrics in numeric format.

For a comprehensive list of the metrics that are monitored by Enterprise Manager, you can view the All Metrics page. The All Metrics page is available from the Application Server Home page and from each of the component Home pages.

For example, to view All Metrics page for an application server instance:

1. Navigate to the Application Server Home page.

2. Click All Metrics in the Related Links section of the page.

   Enterprise Manager displays the All Metrics page for the application server.

3. Click Expand All to see all the application server metrics in each of the metric categories.

   Figure 2-8 shows the Application Server All Metrics page after you have expanded all the metric categories.

4. Click the name of metric to display the Metric detail page.

5. Click Help to display information about the metric.

Figure 2-8 Application Server All Metrics Page

Description of "Figure 2-8 Application Server All Metrics Page"

To view the All Metrics page for a component, such as Oracle HTTP Server:

1. Navigate to the component Home page.

2. Click All Metrics in the Related Links section of the page.

   Enterprise Manager displays the All Metrics page for the selected component.

2.4.6 Monitoring J2EE Applications

The J2EE applications you deploy and maintain with Oracle Application Server represent the most important aspects of your application server deployments. As a result, Enterprise Manager also provides a shortcut you can use to review the performance of your J2EE applications. Simply click J2EE Applications on the Application Server home page to display a list of the applications deployed from this application server instance (Figure 2-9).

Figure 2-9 List of Applications on the J2EE Applications Page

Description of "Figure 2-9 List of Applications on the J2EE Applications Page"

From this list of J2EE applications, you can navigate quickly to the OC4J instance or application page for information on the performance and availability of each application you have deployed.

2.4.7 Obtaining More Information About Monitoring Oracle Application Server

For more complete information about monitoring Oracle Application Server, refer to the Application Server Control Console online help and the Oracle Application Server Performance Guide.

2.6.1 About the Components of Grid Control

When you centrally manage your enterprise, including your Oracle Application Server instances, you take advantage of the Enterprise Manager three-tier architecture:

• The Grid Control Console provides a Web-based graphical interface you can use to manage all aspects of your enterprise.

• The Oracle Management Service and Management Repository provide a scalable middle tier for storing crucial management data and processing system management tasks.

  Note that the Management Repository is a separate repository from the OracleAS Metadata Repository. The Management Repository is designed specifically for Enterprise Manager.

• The Oracle Management Agent, which you install on each host computer on which there are services to be monitored, monitors the host services and executes tasks from the Management Service.

  
  

  See Also: Oracle Enterprise Manager Concepts for more information about the Oracle Enterprise Manager 10g components and architecture

  
  

2.6.2 Installing the Grid Control Components

You install Oracle Enterprise Manager 10g Grid Control from a separate CD-ROM.

To centrally manage your enterprise, you typically perform the following steps:

1. Install the Management Service and the Management Repository on a host computer.

2. Install the Oracle Management Agent on each of the computers that you want to manage from the Grid Control Console.

   
   

   Note: You install the Oracle Management Agent into its own Oracle home directory on each managed hosts.

   
   

   On each host, the Management Agent gathers information about the various targets on the host. A target is a software component (such as Oracle Application Server), a host computer, and or other service that you manage with Oracle Enterprise Manager 10g.

   Specifically, information about the targets on a host are discovered by the Management Agent during the Management Agent installation. When a target is discovered, information about the target is added to the Management Repository and the target displayed in the list of managed targets in the Grid Control Console.

   If you later install additional application servers on a managed host, you can add them to the Grid Control Console later. To add additional application server targets, click Add on the Application Servers page in the Grid Control Console, or use the Grid Control Management section of the Infrastructure page in the Application Server Control Console.

   
   

   See Also: Oracle Enterprise Manager Grid Control Installation and Basic Configuration for complete instructions about installing Grid Control and starting and stopping the Grid Control components Oracle Enterprise Manager Advanced Configuration for information about common configurations when installing the Grid Control components "Configuring Your Application Server for Grid Control Management" in the Application Server Control Console online help

   
   

2.6.3 Logging In to the Grid Control Console

After you have configured and started Oracle Management Service, you can log in to the Grid Control Console by entering the following URL in your Web browser:

http://grid_control_hostname.domain:port/em

For example:

http://mgmthost2.acme.com:7777/em

If you are uncertain about the port number, you can refer to one of the following files in the install directory of the Management Service Oracle home after you install the Management Service:

• The setupinfo.txt, which includes information displayed by the Oracle Universal Installer at the end of the Grid Control install

• The portlist.ini, which describes the ports assigned during the Management Service installation

When the Grid Control login page appears, enter the username and password for the Super administrator SYSMAN account, which you defined during the Grid Control installation.

After you log in, Enterprise Manager displays the Grid Control Console Home page (Figure 2-11).

Figure 2-11 Grid Control Console Home Page

Description of "Figure 2-11 Grid Control Console Home Page"

2.6.4 Viewing a List of Application Servers in the Grid Control Console

From the Grid Control Console home page, click the Targets tab and then click Application Servers in the horizontal navigation bar. Enterprise Manager displays the Application Servers page (Figure 2-12), which lists all the application servers currently being monitored by Oracle Management Agents in your enterprise.

Figure 2-12 List of Application Servers in the Grid Control Console

Description of "Figure 2-12 List of Application Servers in the Grid Control Console"

This list provides you with a snapshot of the availability, number of alerts, and the CPU and memory usage of each application server target.

2.6.5 Overview of Grid Control Monitoring Tasks

After you have installed the Management Agent on the Oracle Application Server hosts and have identified your application server targets in the Grid Control Console, you can perform a variety of monitoring tasks. For example, you can:

• Set and adjust a set of default metric thresholds for the application servers that you monitor. You can then configure Enterprise Manager so you are notified automatically when a particular application server metric reaches its threshold.

• Organize your application server targets into groups so you can monitor them as a single unit; groups also allow you to compare the performance of the application servers you monitor and to perform administration tasks, such as blackouts, on the group.

• Review historical data and analyze trends in the performance of your application server components and J2EE applications. For example, you can:

  • Emulate and monitor the client experience from remote locations.

  • Measure real end-user performance against a Web application.

  • Trace Web site transactions through the application stack, Oracle HTTP Server, OC4J, and the back-end Oracle database.

  • Correlate application performance across components to rapidly isolate problems.

• Use Application Service Level Management to measure the performance and availability of your J2EE Web applications.

• Perform configuration management tasks, such as software and hardware inventory tracking, cloning, and patching.

2.6.6 Obtaining More Information About Grid Control

For information about starting, configuring, and using Grid Control, see the following documentation:

• Oracle Enterprise Manager Grid Control Installation and Basic Configuration

• Oracle Enterprise Manager Concepts

• Oracle Enterprise Manager Advanced Configuration

The Grid Control Console also provides extensive online help. To display the Grid Control Console online help, click Help at the top of any of the Grid Control Console pages.