3 Starting and Stopping

This chapter describes various procedures for starting and stopping Oracle Application Server and its components. It contains the following topics:

• Starting and Stopping Application Server Instances

• Starting and Stopping Components

• Enabling and Disabling Components

• Starting and Stopping an Oracle Application Server Environment

Oracle Application Server is a flexible product that you can start and stop in different ways, depending on your requirements.

3.1 Starting and Stopping Application Server Instances

This section describes how to start and stop application server instances. It contains the following topics:

• Starting OracleAS Infrastructure

• Stopping OracleAS Infrastructure

• Starting a Middle Tier Instance

• Stopping a Middle Tier Instance

Note: Oracle provides scripts that perform the procedures in this section. You can find them on the "OracleAS RepCA and Utilities" CD-ROM in the utilities/startup directory.

3.1.1 Starting OracleAS Infrastructure

This section describes how to start all processes in OracleAS Infrastructure. OracleAS Infrastructure can have the following components:

• OracleAS Metadata Repository

• Oracle Identity Management

Your infrastructure can have both or one of the components. If your infrastructure contains both the components, then start the OracleAS Metadata Repository first.

3.1.1.1 OracleAS Metadata Repository

You can start OracleAS Metadata Repository as follows:

1. Set the ORACLE_HOME environment variable to the OracleAS Infrastructure Oracle home.

2. Set the ORACLE_SID environment variable to OracleAS Metadata Repository SID (default is asdb).

3. Start the Net Listener:

   ORACLE_HOME/bin/lsnrctl start
   
   

4. Start OracleAS Metadata Repository instance:

   ORACLE_HOME/bin/sqlplus /nolog
   SQL> connect SYS as SYSDBA
   SQL> startup
   SQL> quit
   
   

3.1.1.2 Oracle Identity Management

You can start Oracle Identity Management as follows:

1. Start components:

   ORACLE_HOME/opmn/bin/opmnctl startall
   
   

   This command starts OPMN and all OPMN-managed processes such as DCM, Oracle HTTP Server, OC4J instances, and Oracle Internet Directory.

2. Start the Application Server Control Console:

   ORACLE_HOME/bin/emctl start iasconsole
   
   

3.1.2 Stopping OracleAS Infrastructure

This section describes how to stop all processes in an OracleAS Infrastructure.

OracleAS Infrastructure can have the following components:

• OracleAS Metadata Repository

• Oracle Identity Management

Your OracleAS Infrastructure can have both or one of the components.

3.1.2.1 OracleAS Metadata Repository

You can stop OracleAS Metadata Repository as follows:

1. Set the ORACLE_HOME environment variable to the OracleAS Infrastructure Oracle home.

2. Set the ORACLE_SID environment variable to OracleAS Metadata Repository SID (default is asdb).

3. Stop OracleAS Metadata Repository instance:

   ORACLE_HOME/bin/sqlplus /nolog
   SQL> connect SYS as SYSDBA
   SQL> shutdown
   SQL> quit
   
   

4. Stop the Net Listener:

   ORACLE_HOME/bin/lsnrctl stop
   
   

3.1.2.2 Oracle Identity Management

You can stop Oracle Identity Management as follows:

1. Stop the Application Server Control Console:

   ORACLE_HOME/bin/emctl stop iasconsole
   
   

2. Stop components:

   ORACLE_HOME/opmn/bin/opmnctl stopall
   
   

   This command stops OPMN and all OPMN-managed processes such as DCM, Oracle HTTP Server, OC4J instances, and Oracle Internet Directory.

3.1.3 Starting a Middle Tier Instance

This section describes how to start all processes in a Middle Tier instance. A middle tier can have the following instance types:

• J2EE and Web Cache

• Portal and Wireless

• Business Intelligence

You can start a Middle Tier instance as follows:

1. If the Middle Tier instance uses OracleAS Infrastructure services, such as Oracle Identity Management or a OracleAS Metadata Repository, then ensure they are started.

2. Start components:

   ORACLE_HOME/opmn/bin/opmnctl startall
   
   

   This command starts OPMN and all OPMN-managed processes such as DCM, Oracle HTTP Server, OC4J instances, and OracleAS Web Cache.

3. Start the Application Server Control Console:

   ORACLE_HOME/bin/emctl start iasconsole
   
   

3.1.4 Stopping a Middle Tier Instance

This section describes how to stop all processes in a Middle Tier instance. A middle tier can have the following instance types:

• J2EE and Web Cache

• Portal and Wireless

• Business Intelligence

You can stop a Middle Tier instance as follows:

1. Stop the Application Server Control Console:

   ORACLE_HOME/bin/emctl stop iasconsole
   
   

2. Stop components:

   ORACLE_HOME/opmn/bin/opmnctl stopall
   
   

   This command stops OPMN and all OPMN-managed processes such as DCM, Oracle HTTP Server, OC4J instances, and OracleAS Web Cache.

3.2 Starting and Stopping Components

You can use the following tools to start, stop, restart, and view the status of components:

• opmnctl: a command-line tool

• Application Server Control Console: a Web-based tool

These tools are completely compatible as they both use OPMN as their underlying technology for managing processes. For example, you can start a component using the opmnctl command and stop it using the Application Server Control Console.

Although the two tools can be used interchangeably, they offer different features. The opmnctl command allows you to start and stop subprocesses within components, as well as the entire component. For example, you can start and stop Web Cache, or you can start and stop only the Web Cache Admin subprocess. The Application Server Control Console allows you to view components that cannot be started or stopped, but whose status depends on other components. For example, it displays the status of the Single Sign-On component, whose status depends on the HTTP_Server.

3.2.1 Starting and Stopping Using opmnctl

You can start, stop, or restart a component, using the following commands:

ORACLE_HOME/opmn/bin/opmnctl stopproc ias-component=component
ORACLE_HOME/opmn/bin/opmnctl startproc ias-component=component
ORACLE_HOME/opmn/bin/opmnctl restartproc ias-component=component

You can start, stop, or restart the subprocess of a component, using the following commands:

ORACLE_HOME/opmn/bin/opmnctl stopproc process-type=process
ORACLE_HOME/opmn/bin/opmnctl startproc process-type=process
ORACLE_HOME/opmn/bin/opmnctl restartproc process-type=process

You can check the status of components and processes, using the following command:

ORACLE_HOME/opmn/bin/opmnctl status

See Also: Oracle Process Manager and Notification Server Administrator's Guide.

3.2.2 Starting and Stopping Using the Application Server Control Console

You can start, stop, restart, and view status of components on the Application Server home page as follows:

1. Open the Application Server home page from the Application Server Control Console. Scroll to the System Components section.

2. Select the checkboxes in the Select column for the components you want to start, stop, or restart.

3. Click the Start, Stop, or Restart button on the top-right of the System Components section.

3.3 Enabling and Disabling Components

If you want a component to start every time the application server instance is started, then you must enable the component. On the other hand, if you disable a component, then it will no longer start when the application server instance is started.

You can enable and disable components using the Application Server Control Console. On the Application Server home page, click Enable/Disable Components. Components that are dependent on each other are grouped, and are all enabled or disabled together.

Note: If you use the backup and recovery procedures documented in this book, then you must run bkp_restore.pl -m config after you enable or disable components so that these are registered with the OracleAS Backup and Recovery Tool.

3.4 Starting and Stopping an Oracle Application Server Environment

This section provides procedures for starting and stopping an Oracle Application Server environment. An environment can consist of multiple Infrastructure and Middle Tier instances distributed across multiple hosts. These instances are dependent on each other and you must start and stop them in the proper order.

You can follow these procedures when you need to completely shut down your Oracle Application Server environment. For example, when preparing to perform a complete backup of your environment, or apply a patch.

3.4.1 Starting an Oracle Application Server Environment

You can start an Oracle Application Server environment as follows:

1. Start any OracleAS Infrastructure that contains only OracleAS Metadata Repository.

   If your environment has OracleAS Infrastructure installations that contain only OracleAS Metadata Repository, then start them in any order. For these installation types, you only need to start OracleAS Metadata Repository. You do not need to start any processes with opmnctl and you do not need to start the Application Server Control Console.

   
   

   See Also: Section 3.1.1, "Starting OracleAS Infrastructure"

   
   

2. Start the OracleAS Infrastructure that contains Oracle Identity Management.

   If your environment uses Oracle Identity Management, then start the OracleAS Infrastructure that contains Oracle Internet Directory.

   
   

   See Also: Section 3.1.1, "Starting OracleAS Infrastructure"

   
   

3. Start OracleAS Clusters.

   If your environment has Middle Tier instances that are part of OracleAS Cluster, then start the clusters in any order.

   
   

   See Also: Oracle Application Server 10g High Availability Guide

   
   

4. Start Middle Tier instances.

   If your environment contains Middle Tier instances that are not part of OracleAS Cluster, then start them in any order.

   
   

   See Also: Section 3.1.3, "Starting a Middle Tier Instance"

   
   

3.4.2 Stopping an Oracle Application Server Environment

You can stop all processes in an Oracle Application Server environment as follows:

1. Stop OracleAS Clusters.

2. Stop Middle Tier instances.

3. Stop the OracleAS Infrastructure that contains Oracle Identity Management.

4. Stop any OracleAS Infrastructure instances that contain only OracleAS Metadata Repository.

   
   

   See Also: Oracle Application Server 10g High Availability Guide Section 3.1.4, "Stopping a Middle Tier Instance" Section 3.1.2, "Stopping OracleAS Infrastructure"