|
Oracle® Application Server Quick Administration Guide
10g Release 2 (10.1.2) B14126-02 |
|
 Previous |
 Next |
|
Oracle® Application Server Quick Administration Guide
10g Release 2 (10.1.2) B14126-02 |
|
|
Previous |
Next |
This chapter describes the Oracle Application Server administration tools for managing Oracle Application Server. It contains the following topics:
The primary tool for managing Oracle Application Server, as well as your entire Oracle environment, is Oracle Enterprise Manager 10g (Enterprise Manager).
Enterprise Manager has two main components:
Oracle Enterprise Manager 10g Application Server Control
You can manage individual Oracle Application Server instances with Oracle Enterprise Manager 10g Application Server Control.
Oracle Enterprise Manager 10g Grid Control
You can centrally manage all the components of your network and your enterprise with Oracle Enterprise Manager 10g Grid Control .
When used together, Application Server Control and Grid Control provide a complete set of efficient tools to reduce the cost and complexity of managing your enterprise.
|
Note: If you select the OracleAS Metadata Repository-only installation type, the Application Server Control is installed, but not configured. This installation type does not need the Application Server Control Console.See Section 2.4, "Managing the OracleAS Metadata Repository Database with Database Control" for more information about managing OracleAS Metadata Repository. |
Application Server Control is installed with every instance of Oracle Application Server and you can manage your application server and its components from your Web browser.
The Application Server Control consists of:
Application Server Control Console organizes a wide variety of performance data and administrative functions into distinct, Web-based home pages for each application server component. You can monitor and administer a single Oracle Application Server instance, a farm of application server instances, or OracleAS Cluster.
The Web-based home pages, called the Enterprise Manager home pages, help you to locate commonly used administrative functions, using your Web browser. Enterprise Manager home pages provide you with a high-level view of your Oracle Application Server environment.
Oracle Application Server provides a wide variety of software solutions designed to help you run all aspects of your business. As a result, you may want to manage Oracle Application Server from different levels of detail.
For example, 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, use the 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. Enterprise Manager home pages also provide tools for configuring your Oracle Application Server components.
The following home pages 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 clusters that speed up the configuration and deployment of your Web applications. See Section 2.3.3, "Using the Oracle Application Server Farm Home Page" for more information.
Use the Application Server Home page to manage all aspects of an individual application server instance. See Section 2.3.2, "Using the Application Server Home Page" for more information.
Use 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. Similarly, use the Oracle Containers for J2EE (OC4J) Home page to deploy a custom Web-based application. See Section 2.3.4, "Using an Oracle Application Server Component Home Page" for more information.
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.
Table 2-1 Summary of the Application Server Control Underlying Technologies
| Technology | Description |
|---|---|
|
The Application Server Control Console uses DMS to gather performance data about your Oracle Application Server components. |
|
|
OPMN manages Oracle HTTP Server, OC4J, and other Oracle Application Server processes. It channels all events from different component instances to all components interested in receiving them. Refer to Section 1.4.1.1, "Oracle Process Manager and Notification Server (OPMN)". |
|
|
The Application Server Control Console uses DCM to make configuration changes and to propagate configuration changes and deployed applications across the cluster. Refer to Section 1.4.1.2, "Distributed Configuration Management (DCM)". |
|
|
A local version of the Oracle Management Agent designed specifically to monitor and administer your application server components. |
|
|
The Management Watchdog Process monitors the Management Agent and the Application Server Control Console to ensure both processes are running and available at all times. |
If you have an environment that includes other Oracle products and applications in addition to Oracle Application Server, then consider using Oracle Enterprise Manager 10g Grid Control.
Grid Control, when used with Application Server Control, provides a wider view of your Oracle environment beyond the application server. From a central location, you can use the Grid Control Console to manage databases, application servers, and Oracle applications across your entire network.
The Grid Control Console offers advanced management features, such as a Notification system to notify administrators of changes in your environment and a Job system to automate standard and repetitive tasks, such as executing a SQL script or executing an operating system command.
Grid Control is installed separately from the Oracle Enterprise Manager 10g installation CD-ROM. The Grid Control Console provides a wider view of your network so you can manage multiple Oracle Application Server instances. In addition, the Grid Control Console provides a robust feature set designed to help you manage all aspects of your enterprise, including your Oracle databases, hosts, listeners, and other components.
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.
opmnctl, which provides a command-line interface to Oracle Process Management Notification (OPMN). You can use opmnctl to:
Start and stop components, instances, and OracleAS Clusters
Monitor processes
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
In addition to these commands, Oracle Application Server provides many other command-line tools for performing specific tasks.
|
Note: Oracle Application Server also 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. These built-in performance metrics are measured continuously using performance instrumentation inserted into the implementations of Oracle Application Server components. |
Application Server Control Console provides Web-based management capabilities for Oracle Application Server. Using the Application Server Control Console, you can monitor, diagnose, and configure the components of your application server. You can deploy applications, manage security, and create and manage OracleAS Clusters.
This section describes how to use the Application Server Control Console. It contains the following topics:
The following sections describe how to display the Application Server Control Console and introduce you to the initial Home pages that you should see when you display the Application Server Control Console for the first time:
The URL for the Application Server Control Console is included in the text file that displays at the end of the Oracle Application Server installation procedure. This text file is saved in the following location after you install the application server:
(UNIX) ORACLE_HOME/install/setupinfo.txt (Windows) ORACLE_HOME\install\setupinfo.txt
The Application Server Control Console URL typically includes the name of the host computer and the port number assigned to the Application Server Control Console during the installation. For example, on UNIX:
http://mgmthost1.acme.com:1156
|
Note: The default port for the Application Server Control Console is usually 1156 on UNIX. However, if that port is in use, the installation will assign another port. Refer to thesetupinfo.txt file for the exact port for your installation of Oracle Application Server.
|
When you first display the Application Server Control Console, the initial home page you see varies depending upon whether or not the instance uses an OracleAS Metadata Repository (belongs to a farm).
|
See Also: Oracle Application Server Installation Guide for your platform |
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.
Table 2-2 Enterprise Manager Home Pages for Managing Oracle Application Server
| Home Page | Description |
|---|---|
|
Use this home page to monitor and configure a single application server instance. The Application Server Home page is the first page you see if you have installed a single application server instance that does not use an OracleAS Metadata Repository. See Section 2.3.2, "Using the Application Server Home Page" for more information. |
|
|
Use this home page to view a list of all the application server instances that use a common OracleAS Metadata Repository. The Farm Home page is the first page you see if you have installed one or more application server instances that use a common set of Infrastructure Services or more specifically, a common OracleAS Metadata Repository. See Section 2.3.3, "Using the Oracle Application Server Farm Home Page" for more information. |
From the Application Server Home page, shown in 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 configure individual components and examine their performance.
The page contains a System Components table that lists the components of the application server. This table provides a snapshot of how each individual component is performing. You can also display a home page for each component of the application server.
You can perform the following management functions from the instance 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.
Click J2EE Applications to display a list of the applications deployed on this instance of 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 use Identity Management, Central Management, or the cluster capabilities of Oracle Application Server.
Click Backup/Recovery to perform backup and recovery operations for the selected Oracle Application Server instance.
|
See Also: Chapter 9, "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 are started automatically or affected by server-wide actions, such as Start All or Restart All.
For more information, click Help after selecting an option on the Application Server Home page.
If your application server instance uses an OracleAS Metadata Repository, then your start page for the Application Server Control Console is the OracleAS Farm page as shown in Figure 2-2.
|
See Also: Oracle Application Server Installation Guide for your platform for information about installing an OracleAS Metadata Repository |
The Oracle Application Server Farm Home page displays a list of the standalone application server instances and OracleAS Clusters associated with your Infrastructure Services. Standalone instances are application server instances that are not part of an OracleAS Cluster.
You can configure your application server instance to use Infrastructure Services by clicking Infrastructure on the Application Server Home page. For more information, refer to the Enterprise Manager online help.
Using the Oracle Application Server Farm Home 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 |
Component home pages vary from one component to another because each component has different monitoring and configuration requirements. However, most 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 complex configuration files.
The Application Server Control Console is designed to encourage a top-down approach to your monitoring and diagnostic activities. For example, you can start by reviewing the basic characteristics of your application server on the Application Server Home page and then drill down to examine the performance of individual components of the server.
The following sections provide an outline of this monitoring methodology:
You can click Topology at the top of any page in Application Server Control Console to display Topology Viewer (Figure 2-3). The Topology Viewer provides a graphical, real-time representation of application server processes managed by OPMN. You can use this viewer to better understand the component relationships of the application server.
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, then the viewer also shows the relationships between the application server instances, including any OracleAS Cluster you have created.
From 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
|
See Also: 'About Topology Viewer" in the Enterprise Manager online help |
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.
If you suspect that the application server is using too many resources, then review the resource usage by each component.
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.
|
See Also: "Disabling and Enabling Components" in the Enterprise Manager online help |
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.
|
See Also: "About Memory Usage" in the Enterprise Manager online help for information about how Enterprise Manager calculates the memory usage for your application server. |
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, then 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.
After you review the high-level performance metrics and the resources available on the application server host computer, you can 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.
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. Click J2EE Applications on the Application Server Home page to display a list of the applications deployed from this application server instance.
From this list of J2EE applications, you can navigate quickly to the OC4J instance or application page for information about the performance and availability of each application you have deployed.
|
See Also: For more complete information about monitoring, refer to the Application Server Control Console online help and the Oracle Application Server Performance Guide. |
Many features of Oracle Application Server depend upon the OracleAS Metadata Repository, which uses an Oracle database to contain the OracleAS Metadata Repository. When you install the OracleAS Metadata Repository, you can choose to install a preconfigured instance of Oracle Database 10g for the OracleAS Metadata Repository.
If you have installed and deployed Oracle Enterprise Manager 10g Grid Control, then you can use the Grid Control Console to manage the OracleAS Metadata Repository.
However, if you are not centrally managing your environment with Grid Control, the OracleAS Metadata Repository database comes with Oracle Enterprise Manager 10g Database Control, which is provided with Oracle Database 10g.
To display the Database Control:
Use a Web browser to access the Database Control URL:
http://hostname.domain:port/em
In this example:
hostname is the name of the computer on which you installed Oracle Database.
port is the port number reserved for the Database Control during installation.
If you do not know the correct port number, then look for the following line in the portlist.ini file, which is stored in the install directory of your OracleAS Metadata Repository Oracle home:
Enterprise Manager Console HTTP Port (db_name) = 5500
The installation reserves the first available port from the range 5500 to 5519. For example, if you installed Oracle Database on host mgmt42, and the Database Control uses port 5500, then enter the following URL:
http://mgmt42.acme.com:5500/em
Oracle Enterprise Manager displays the Database Control login page.
Log in to the database using the user name SYS and connect as SYSDBA.
Use the password that you specified for the SYS account during the installation.
Enterprise Manager displays the Database Home page.
From the Database Home page, you can review the current state of your database and access a wide range of monitoring and administration features.
|
See Also: Oracle 2 Day DBA in the Oracle Database 10g documentation library for an introduction to database management with the Database Control Console |
