|
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 various procedures for starting and stopping Oracle Application Server and its components. It contains the following topics:
Oracle Application Server is a flexible product that you can start and stop in different ways, depending on your requirements.
This section describes how to start and stop application server instances. It contains the following topics:
To start an entire application server instance, including the Infrastructure and the middle tier, such as when you have restarted your host, you can use the runstartupconsole command.
If the Infrastructure and middle tier is installed on the same host, run the following command from the middle-tier Oracle home:
(UNIX) ORACLE_HOME/bin/runstartupconsole.sh start all (Windows) ORACLE_HOME\bin\runstartupconsole.bat start all
The command starts the following in the Infrastructure Oracle home:
The OracleAS Metadata Repository instance
OracleAS Infrastructure processes such as Oracle Identity Management components, Oracle Internet Directory, OC4J_Security, DCM, and OPMN
Enterprise Manager, including Application Server Control Console and Database Control
The command starts the following in the middle-tier Oracle home:
OPMN and all OPMN-managed processes such as DCM, Oracle HTTP Server, OC4J instances, and OracleAS Web Cache, OracleAS Forms Services, and OracleAS Reports Services
Enterprise Manager Application Server Control Console
If you want to start the Infrastructure and middle tier, but not Enterprise Manager, run the following command from the middle-tier Oracle home:
(UNIX) ORACLE_HOME/bin/runstartupconsole.sh start allas (Windows) ORACLE_HOME\bin\runstartupconsole.bat start allas
If you want to start only Enterprise Manager, but in both the Infrastructure and middle tier, run the following command from the middle-tier Oracle home:
(UNIX) ORACLE_HOME/bin/runstartupconsole.sh start allem (Windows) ORACLE_HOME\bin\runstartupconsole.bat start allem
If the Infrastructure and middle tier are installed on separate hosts, see Section 3.1.3, "Starting OracleAS Infrastructure" and Section 3.1.5, "Starting a Middle-Tier Instance".
To stop an entire application server instance, including the Infrastructure and the middle tier, such as when you are preparing to shut down your host, you can use the runstartupconsole command.
If the Infrastructure and middle tier is installed on the same host, run the following command from the middle-tier Oracle home:
(UNIX) ORACLE_HOME/bin/runstartupconsole.sh stop all (Windows) ORACLE_HOME\bin\runstartupconsole.bat stop all
The command stops the following in the Infrastructure Oracle home:
The OracleAS Metadata Repository instance
OracleAS Infrastructure processes such as Oracle Identity Management components, Oracle Internet Directory, OC4J_Security, DCM, and OPMN
Enterprise Manager, including Application Server Control Console and Database Control
The command stops the following in the middle-tier Oracle home:
OPMN and all OPMN-managed processes such as DCM, Oracle HTTP Server, OC4J instances, and OracleAS Web Cache, OracleAS Forms Services, and OracleAS Reports Services
Enterprise Manager Application Server Control Console
If you want to stop the Infrastructure and middle tier, but not Enterprise Manager, run the following command from the middle-tier Oracle home:
(UNIX) ORACLE_HOME/bin/runstartupconsole.sh stop allas (Windows) ORACLE_HOME\bin\runstartupconsole.bat stop allas
If you want to stop only Enterprise Manager, but in both the Infrastructure and middle tier, run the following command from the middle-tier Oracle home:
(UNIX) ORACLE_HOME/bin/runstartupconsole.sh stop allem (Windows) ORACLE_HOME\bin\runstartupconsole.bat stop allem
If the Infrastructure and middle tier are installed on separate hosts, see Section 3.1.4, "Stopping OracleAS Infrastructure" and Section 3.1.6, "Stopping a Middle-Tier Instance".
To start all processes in an OracleAS Infrastructure, such as when you have restarted your host, use the following command:
(UNIX) ORACLE_HOME/bin/runstartupconsole.sh start (Windows) ORACLE_HOME\bin\runstartupconsole.bat start
When you run this command in the Infrastructure home, it starts the following:
The OracleAS Metadata Repository instance
OracleAS Infrastructure processes such as Oracle Identity Management components, Oracle Internet Directory, OC4J_Security, DCM, and OPMN
Oracle Enterprise Manager 10g, including Application Server Control Console and Database Control
Alternatively, on Windows, you can start the Infrastructure from the Programs menu: Start > Programs > Oracle Application Server Infrastructure - Infra_name > Start instanceName.
To stop all processes in an OracleAS Infrastructure, such as when you are preparing to shut down the host, use the following command:
(UNIX) ORACLE_HOME/bin/runstartupconsole.sh stop (Windows) ORACLE_HOME\bin\runstartupconsole.bat stop
When you run this command in the Infrastructure home, it stops the following:
The OracleAS Metadata Repository instance
OracleAS Infrastructure processes such as Oracle Identity Management components, Oracle Internet Directory, OC4J_Security, DCM, and OPMN
Oracle Enterprise Manager 10g, including Application Server Control Console and Database Control
Alternatively, on Windows, you can stop the Infrastructure from the Programs menu: Start > Programs > Oracle Application Server Infrastructure - Infra_name > Stop instanceName.
To start all processes in a middle-tier instance, take the following steps:
If the middle-tier instance uses OracleAS Infrastructure services, such as Oracle Identity Management or OracleAS Metadata Repository, make sure they are started.
If they are not started, use the command described in Section 3.1.3, "Starting OracleAS Infrastructure", or start both the middle-tier instance and its associated Infrastructure, using the procedure described in Section 3.1.1, "Starting an Application Server Instance".
Start the middle-tier instance by using the following command:
(UNIX) ORACLE_HOME/bin/runstartupconsole.sh start (Windows) ORACLE_HOME\bin\runstartupconsole.bat start
When you run this command in a middle-tier Oracle home, it starts the following:
OPMN and all OPMN-managed processes such as DCM, Oracle HTTP Server, OC4J instances, and OracleAS Web Cache, OracleAS Forms Services, and OracleAS Reports Services
Oracle Enterprise Manager 10g Application Server Control Console
Alternatively, on Windows, you can start the middle tier from the Programs menu: Start > Programs > Oracle Application Server - Oracle_Home > Start > instanceName.
To stop all processes in a middle-tier instance, use the following command:
(UNIX) ORACLE_HOME/bin/runstartupconsole.sh stop (Windows) ORACLE_HOME\bin\runstartupconsole.bat stop
When you run this command in a middle-tier Oracle home, it stops the following:
OPMN and all OPMN-managed processes such as DCM, Oracle HTTP Server, OC4J instances, and OracleAS Web Cache, OracleAS Forms Services, and OracleAS Reports Services
Oracle Enterprise Manager 10g Application Server Control Console
Alternatively, on Windows, you can stop the middle tier from the Programs menu: Start > Programs > Oracle Application Server - Oracle_Home > Stop > instanceName.
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. With the opmnctl command, you can start and stop subprocesses within components, as well as the entire component. For example, you can start and stop OracleAS Web Cache, or you can start and stop only the OracleAS Web Cache Admin subprocess. With the Application Server Control Console, you can 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.
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
The commands are shown in UNIX format. For Windows, invert the slashes.
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
The commands are shown in UNIX format. For Windows, invert the slashes.
You can check the status of components and processes, using the following command:
ORACLE_HOME/opmn/bin/opmnctl status
You can start, stop, restart, and view status of components on the Application Server Home page as follows:
Open the Application Server Home page from the Application Server Control Console. Scroll to the System Components section.
Select the checkboxes in the Select column for the components you want to start, stop, or restart.
Click the Start, Stop, or Restart button on the top-right of the System Components section.
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, 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 runbkp_restore.pl -m config after you enable or disable components so that these are registered with the OracleAS Backup and Recovery Tool.
|
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 to apply a patch.
You can start an Oracle Application Server environment as follows:
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 Section 3.1.3, "Starting OracleAS Infrastructure" for more information.
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 Section 3.1.3, "Starting OracleAS Infrastructure" for more information.
Start OracleAS Clusters.
If your environment has middle-tier instances that are part of OracleAS Cluster, then start the clusters in any order.
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 Section 3.1.5, "Starting a Middle-Tier Instance" for more information.
You can stop all processes in an Oracle Application Server environment as follows:
Stop OracleAS Clusters.
Stop middle-tier instances. See Section 3.1.6, "Stopping a Middle-Tier Instance" for more information.
Stop the OracleAS Infrastructure that contains Oracle Identity Management. See Section 3.1.4, "Stopping OracleAS Infrastructure" for more information.
Stop any OracleAS Infrastructure instances that contain only OracleAS Metadata Repository.
