5
Starting and Stopping the Application Server

This chapter describes how to start and stop application server instances, infrastructures, and customer databases. It also provides information about starting and stopping individual components.

It contains the following topics:

Introduction

An application server enterprise contains application server instances, infrastructures, and customer databases that can be started and stopped. Most commonly you will start and stop these pieces of your enterprise separately, for example, when rebooting a system. You may also want to start and stop your entire enterprise, for example, to reconfigure it or perform routine maintenance.

This section provides high-level information about starting and stopping an entire enterprise and its individual pieces. The rest of this chapter provides detailed procedures for starting and stopping application server instances and infrastructures, as well as starting and stopping individual components within instances.

Starting an Application Server Enterprise

The order in which to start the pieces of an application server enterprise is as follows:

Start the infrastructure.

If your enterprise contains more than one infrastructure, start the primary infrastructure first.
Start customer databases.

If your enterprise contains customer databases, you can start them using several methods, including SQL*Plus and Oracle Enterprise Manager Console.

See Also:
Oracle database administration guides and Oracle Enterprise Manager Administrator's Guide for more information about starting databases
Start application server instances.

You can start application server instances in any order. If instances are part of a cluster, start them as part of starting the cluster.

See Also:
Chapter 14, "Application Server Clustering" for information about clusters

Stopping an Application Server Enterprise

The order in which to stop the pieces of an application server enterprise is as follows:

Stop application server instances.

You can stop application server instances in any order. If instances are part of a cluster, stop them as part of stopping the cluster.

See Also:
Chapter 14, "Application Server Clustering" for information about clusters
Stop customer databases.

If your enterprise contains customer databases, you can stop them using several methods, including SQL*Plus and Oracle Enterprise Manager Console.

See Also:
Oracle database administration guides and Oracle Enterprise Manager Administrator's Guide for more information about starting databases
Stop the infrastructure.

If your enterprise contains more than one infrastructure, stop the primary infrastructure last.

Dependencies for Starting and Stopping Pieces of an Application Server Enterprise

You can start and stop individual pieces of an application server enterprise, for example, to reboot a system; however you must be aware of the dependencies between pieces as described in Table 5-1.

Table 5-1 Dependencies for Starting and Stopping Pieces of an Application Server

Piece	Prerequisites for Starting	Prerequisites for Stopping
Application Server Instance	Associated infrastructure, if any, must be started. Customer databases used by components within the application server instance must be started.	None.
Infrastructure	None.	Associated application server instances must be stopped.
Customer Database	None	Components that use the customer database must be stopped.

Piece

Prerequisites for Starting

Prerequisites for Stopping

Application Server Instance

Associated infrastructure, if any, must be started.

Customer databases used by components within the application server instance must be started.

None.

Infrastructure

None.

Associated application server instances must be stopped.

Customer Database

None

Components that use the customer database must be stopped.

Starting and Stopping Application Server Instances

This section describes how to start and stop application server instances using the Enterprise Manager Web site or command-line tools.

About the Enterprise Manager Web Site and Intelligent Agent

When starting and stopping application server instances, you should be aware of two host-wide processes:

Enterprise Manager Web Site (Required)

The first step before starting an application server instance is to ensure that the Enterprise Manager Web site is running on the host. The Web site provides underlying processes required to run an application server instance and must be running even if you intend to use command-line tools to start your instance.

Note:

Always ensure that the Enterprise Manager Web site is running on a host before starting an application server instance on that host. You must start the Enterprise Manager Web site after every system boot.

There is one Enterprise Manager Web site per host. It resides in the primary installation (or first installation) on that host. The primary installation can be an application server installation or an infrastructure. This Web site usually listens on port 1810 and provides services to all application server instances and infrastructures on that host.

To verify the status of the Enterprise Manager Web site, run the following command in the Oracle home of the primary installation:

(UNIX) ORACLE_HOME/bin/emctl status
(Windows) ORACLE_HOME\bin\emctl status

To start the Enterprise Manager Web site, run the following command in the Oracle home of the primary installation:

(UNIX) ORACLE_HOME/bin/emctl start
(Windows) ORACLE_HOME\bin\emctl start

You do not need to stop the Enterprise Manager Web site every time you stop an application server instance; however, if you need to stop the Web site, for example, to shut down the system, use the following commands:

(UNIX) ORACLE_HOME/bin/emctl stop
(Windows) ORACLE_HOME\bin\emctl stop

Intelligent Agent (Optional)

You only need to run the Intelligent Agent if you are using Oracle Management Server in your enterprise. In order for Oracle Management Server to detect application server installations on a host, you must make sure the Intelligent Agent is started. Note that one Intelligent Agent is started per host and must be started after every system boot.

(UNIX) You can run the following commands in the Oracle home of the primary installation (the first installation on the host) to get status and start the Intelligent Agent:

ORACLE_HOME/bin/agentctl status agent
ORACLE_HOME/bin/agentctl start agent

(Windows) You can check the status and start the Intelligent Agent using the Services control panel. The name of the service is in the following format:

OracleORACLE_HOMEAgent

start the Intelligent Agent in the Oracle home of the primary installation:

ORACLE_HOME/bin/agentctl start agent

Starting and Stopping Instances Using the Enterprise Manager Web Site

You can start, stop, and restart all types of application server instances using the Instance Home Page on the Enterprise Manager Web site. Figure 5-1 displays a sample Instance Home Page.

Figure 5-1 Instance Home Page

Text description of the illustration iastop.gif

Starting, stopping, and restarting an application server instance applies the chosen action to the components within the instance, as described in Table 5-2.

Table 5-2 Application Server Instance Start/Stop/Restart Actions

Performing this action on an application server instance:	Applies these actions to its components:
Start	Starts components that are stopped. Does not affect components that are already running.
Stop	Stops components that are running. Does not affect components that are stopped.
Restart	Restarts components that are running. Starts components that are stopped.

Performing this action on an application server instance:

Applies these actions to its components:

Start

Starts components that are stopped.

Does not affect components that are already running.

Stop

Stops components that are running.

Does not affect components that are stopped.

Restart

Restarts components that are running.

Starts components that are stopped.

To start, stop, or restart an application server instance:

Navigate to the Instance Home Page on the Enterprise Manager Web site.
In the General section of the Instance Home Page, click Start All, Stop All, or Restart All. In the System Components section, review the status of each component and confirm it was started or stopped.

See Also:
If the application server instance is part of a cluster, refer to "Managing the Cluster" for information on starting and stopping an instance as part of a cluster.

Starting and Stopping Instances Using Commands

You can start and stop a J2EE and Web Cache instance using command-line tools. J2EE and Web Cache is the only install type that has command-line tools for starting and stopping all of its components. You must start and stop all other install types using the Enterprise Manager Web site.

Starting a J2EE and Web Cache Instance Using Commands

To start a J2EE and Web Cache instance using command-line tools:

Start the Enterprise Manager Web site. Even though you are not using the Web site, this ensures that the processes to support the dcmctl command-line tool are started. To start the Web site, execute the following command in the Oracle home of the primary installation on your host:
```
(UNIX) ORACLE_HOME/bin/emctl start
(Windows) ORACLE_HOME\bin\emctl start
```
Start Oracle HTTP Server and OC4J (the rest of the commands in this section should be executed in the Oracle home of the J2EE and Web Cache instance):
```
(UNIX) ORACLE_HOME/dcm/bin/dcmctl start
(Windows) ORACLE_HOME\dcm\bin\dcmctl start
```

If Web Cache is configured, start Web Cache:

(UNIX) ORACLE_HOME/bin/webcachectl start
(Windows) ORACLE_HOME\bin\webcachectl start

Stopping a J2EE and Web Cache Instance Using Commands

To stop a J2EE and Web Cache instance using command-line tools:

If Web Cache is configured, stop Web Cache:

(UNIX) ORACLE_HOME/bin/webcachectl stop
(Windows) ORACLE_HOME\bin\webcachectl stop

Stop Oracle HTTP Server and OC4J:

(UNIX) ORACLE_HOME/dcm/bin/dcmctl stop
(Windows) ORACLE_HOME\dcm\bin\dcmctl stop

Starting and Stopping Components

You can start, stop, and restart individual components using the Instance Home Page or the component home page on the Enterprise Manager Web site. You can also start and stop some components using command-line tools.

Warning:

Starting or stopping an individual component can affect the behavior of other components in the application server instance. Before starting or stopping a component, review the information in "Dependencies for Starting and Stopping Components" .

Starting and Stopping Components Using the Instance Home Page

To start, stop, or restart a component from the Instance Home Page:

Navigate to the Instance Home Page on the Enterprise Manager Web site. Scroll to the System Components section.
Click the radio button in the Select column for the component.
Click the Start, Stop, or Restart button on the top right of the System Components section.

See Also:
The radio button in the Select column is disabled for some components. See "About Components that Cannot Be Started or Stopped" for more information.

Starting and Stopping Components Using the Component Home Page

To start, stop, or restart a component from the home page for the component:

Navigate to the Instance Home Page on the Enterprise Manager Web site. Scroll to the System Components section.
Select the component in the Name column. This opens the home page for the component.
On the component home page, click the Start, Stop, or Restart button in the General section.

See Also:
The home page for some components does not allow you to start, stop, and restart the component. See "About Components that Cannot Be Started or Stopped" for more information.

Starting and Stopping Components Using Commands

You can start and stop some components using command-line tools. Table 5-3 lists the commands for UNIX and Table 5-4 lists the commands for Windows.

Note that many components are started when their corresponding OC4J instance is started. Refer to "About Components that Cannot Be Started or Stopped".

Table 5-3 Starting and Stopping Components Using Command-Line Tools on UNIX

Component	Action	Command
Oracle HTTP Server	Start	`ORACLE_HOME``/dcm/bin/dcmctl start -ct ohs`
Oracle HTTP Server	Stop	`ORACLE_HOME``/dcm/bin/dcmctl stop -ct ohs`
Individual OC4J Instances	Start	`ORACLE_HOME``/dcm/bin/dcmctl start -co instance_name`
Individual OC4J Instances	Stop	`ORACLE_HOME``/dcm/bin/dcmctl stop -co instance_name`
All OC4J Instances	Start	`ORACLE_HOME``/dcm/bin/dcmctl start -ct oc4j`
All OC4J Instances	Stop	`ORACLE_HOME``/dcm/bin/dcmctl stop -ct oc4j`
Web Cache	Start	`ORACLE_HOME``/bin/webcachectl start`
Web Cache	Stop	`ORACLE_HOME``/bin/webcachectl stop`
Discoverer	Start	`ORACLE_HOME``/discoverer902/util/startall.sh`
Discoverer	Stop	`ORACLE_HOME``/discoverer902/util/stopall.sh`
Reports	Start	`ORACLE_HOME``/bin/rwserver.sh server=name`
Reports	Stop	`ORACLE_HOME``/bin/rwserver.sh server=name shutdown=yes`

Table 5-4 Starting and Stopping Components Using Command-Line Tools on Windows

Component	Action	Command
Oracle HTTP Server	Start	`ORACLE_HOME``\dcm\bin\dcmctl start -ct ohs`
Oracle HTTP Server	Stop	`ORACLE_HOME``\dcm\bin\dcmctl stop -ct ohs`
Individual OC4J Instances	Start	`ORACLE_HOME``\dcm\bin\dcmctl start -co instance_name`
Individual OC4J Instances	Stop	`ORACLE_HOME``\dcm\bin\dcmctl stop -co instance_name`
All OC4J Instances	Start	`ORACLE_HOME``\dcm\bin\dcmctl start -ct oc4j`
All OC4J Instances	Stop	`ORACLE_HOME``\dcm\bin\dcmctl stop -ct oc4j`
Web Cache	Start	`ORACLE_HOME``\bin\webcachectl start`
Web Cache	Stop	`ORACLE_HOME``\bin\webcachectl stop`
Reports	Start	`ORACLE_HOME``\bin\rwserver server=name`
Reports	Stop	`ORACLE_HOME``\bin\rwserver server=name shutdown=yes`

About Components that Cannot Be Started or Stopped

You cannot start or stop some components. The radio buttons in the Select column on the Instance Home Page are disabled for these components, and their component home pages do not have Start, Stop, or Restart buttons.

This section provides information about the following components, which cannot be started or stopped:

BC4J

Business Components for Java (BC4J) is a framework for building applications and is deployed to the OC4J_home instance. BC4J displays an up status if the OC4J_home instance is running and a down status if the OC4J_home instance is stopped.

Discoverer

Discoverer is provided by a servlet running in the OC4J_BI_Forms instance. Discoverer displays an up status if the OC4J_BI_Forms instance is running and a down status if the OC4J_BI_Forms instance is stopped.

Forms

The Forms service is provided by a servlet running in the OC4J_BI_Forms instance. Forms displays an up status if the OC4J_BI_Forms instance is running and a down status if the OC4J_BI_Forms instance is stopped.

Internet File System

Internet File System is supported by a servlet running in the OC4J_iFS instance. Internet File System displays an up status if the OC4J_iFS instance is running and a down status if the OC4J_iFS instance is stopped.

JServ

JServ is a Java servlet environment available in the HTTP Server. Jserv displays an up status if HTTP Server is running and a down status if HTTP Server is stopped.

Portal

Portal is supported by a servlet running in the OC4J_Portal instance. Portal displays an up status if the OC4J_Portal instance is running and a down status if the OC4J_Portal instance is stopped.

Single Sign-On

Single Sign-On service is accessible through HTTP Server. Single Sign-On displays an up status if HTTP Server is running and a down status if HTTP Server is stopped.

Dependencies for Starting and Stopping Components

There are many dependencies between components in an application server instance. Before you start or stop an individual component, you must understand the effect, if any, the action will have on other components.

You may need to make sure other components are started before starting a component. Stopping a component may disrupt the services of other components.

Table 5-5, describes the prerequisites for starting and the side-effects of stopping individual components.

Table 5-5 Dependencies for Starting and Stopping Components

Component	Prerequisites for Starting	Side-Effects of Stopping
Clickstream Collector	None	None
Clickstream	None	None
HTTP Server	None	All services that require access through the HTTP Server will be unavailable.
Internet Directory	Metadata Repository must be started.	All application server instances using the directory will be disrupted. The directory should only be stopped as part of an orderly infrastructure shutdown.
OC4J_BI_Forms	None	Forms, Reports, Clickstream, Personalization, and Discoverer become unavailable.
OC4J_DAS	HTTP Server and OC4J_home must be started.	Delegated Administration Service becomes unavailable.
OC4J_Demos	None	Demos that depend on OC4J_Demos will not work.
OC4J_home (OC4J default instance)	None	None
OC4J_iFS	None	Internet File System becomes unavailable.
OC4J_Portal	None	Portal becomes unavailable.
OC4J_UM	None	Unified Messaging becomes unavailable.
OC4J_Wireless	None	None.
Reports	None	None
Unified Messaging	HTTP Server and OC4J_home must be started.	None Note: Restarting causes Unified Messaging to reload operational settings. It does not stop and start the instance.
Web Cache	None	Portal will become unavailable.
Wireless	None	None

Starting an Infrastructure

This section contains the following procedures for starting an infrastructure:

No matter which procedure you use, starting an infrastructure involves performing the following steps in order:

Start the Metadata Repository
Start Oracle Internet Directory
Start the Enterprise Manager Web site.
Start Oracle HTTP Server
Start the OC4J_DAS instance
Start Web Cache (optional)
Start Oracle Management Server and Intelligent Agent (optional)

About Unused Component Instances in the Infrastructure

An infrastructure contains several component instances that are not required to run an infrastructure and incur unnecessary system overhead if started. When you start an infrastructure, you do not need to start these components:

OC4J_Demos: This OC4J instance is only required if you want to run demos.
OC4J_home: This OC4J instance is not required because applications are not deployed to an infrastructure.
BC4J: This component is only used by OC4J_home and is not required if OC4J_home is not started.
Clickstream Collector: This instance is only required to collect Clickstream data and is not necessary since applications are not deployed to an infrastructure.

Figure 5-2 shows the component statuses of a properly started infrastructure.

Figure 5-2 A Properly Started Infrastructure Instance

Text description of infraem.gif follows.

Text description of the illustration infraem.gif

Starting an Infrastructure Using Oracle Enterprise Manager on UNIX and Windows

This section describes how to start an infrastructure using Oracle Enterprise Manager on UNIX and Windows.

Start the metadata repository.
1. Start the metadata repository listener:
```
(UNIX) ORACLE_HOME/bin/lsnrctl start
(Windows) ORACLE_HOME\bin\lsnrctl start
```
2. Launch Oracle Enterprise Manager in standalone mode:
```
(UNIX) ORACLE_HOME/bin/oemapp dbastudio
(Windows) ORACLE_HOME\bin\oemapp dbastudio
```
  Select Launch Standalone and click OK.
3. Expand the Databases entry in the System Objects frame by clicking the plus sign (+) next to it.
4. Select the metadata repository entry.
5. In the toolbar, select Object -> Connect. Connect as a user with SYSDBA privileges.
6. In the toolbar, select Object -> Startup.

Start Oracle Internet Directory.

Set the ORACLE_SID is set to the metadata repository system identifier (default is iasdb).

Start the Oracle Internet Directory monitor:

(UNIX) ORACLE_HOME/bin/oidmon start
(Windows) ORACLE_HOME\bin\oidmon start

Start the Oracle Internet Directory server:

(UNIX) ORACLE_HOME/bin/oidctl server=oidldapd configset=0 instance=n 
start
(Windows) ORACLE_HOME\bin\oidctl server=oidldapd configset=0 instance=n 
start

where n is any instance number (1, 2, 3...) that is not in use. For example:

(UNIX) ORACLE_HOME/bin/oidctl server=oidldapd configset=0 instance=1 
start
(Windows) ORACLE_HOME\bin\oidctl server=oidldapd configset=0 instance=1 
start

Start the Enterprise Manager Web site. The Web site must be started after every system boot.

(UNIX) You can run the following commands in the Oracle home of the primary installation (the first installation on the host) to get status and start the Web site:
```
ORACLE_HOME/bin/emctl status
ORACLE_HOME/bin/emctl start
```
(Windows) You can check the status and start the Enterprise Manager Web site using the Services control panel. The name of the service is in the following format:
```
OracleORACLE_HOMEEMwebsite
```
Access the Infrastructure Instance Page on the Enterprise Manager Web site.

Point your browser to the Enterprise Manager Web site on your host using the following URL:
```
http://hostname:1810
```
Log in as ias_admin. This opens the Farm Page. Select the infrastructure instance in the Name column in the Standalone Instances section. This opens the Infrastructure Instance Page.

Note that you should not click Start All. This will start OC4J instances (OC4J_home and OC4J_Demos) that are not required and incur unnecessary overhead. Instead, follow the rest of these steps to start only the required components. Refer to "About Unused Component Instances in the Infrastructure" for more information.
Start Oracle HTTP Server.
1. On the Infrastructure Instance Page, in the System Components section, click the radio button in the Select column for HTTP Server.
2. Click the Start button on the top right of the System Components section.
Note that starting Oracle HTTP Server also makes Oracle9iAS Single Sign-On available.
Start the OC4J_DAS instance.
1. On the Infrastructure Instance Page, in the System Components section, click the radio button in the Select column for OC4J_DAS.
2. Click the Start button on the top right of the System Components section.
Note that the infrastructure instance contains other OC4J instances, such as OC4J_home and OC4J_Demos, but these do not need to be started; their services are not required and incur unnecessary overhead.
Start Web Cache (optional).

Web Cache is not configured in the infrastructure by default, but if you have configured it, start it as follows:
1. On the Infrastructure Instance Page, in the System Components section, click the radio button in the Select column for Web Cache.
2. Click the Start button on the top right of the System Components section.
Start Oracle Management Server and Intelligent Agent (optional).

Perform these steps only if you have configured Oracle Management Server.
1. Start Oracle Management Server:
```
(UNIX) ORACLE_HOME/bin/oemctl start oms
(Windows) ORACLE_HOME\bin\oemctl start oms
```
2. Start the Intelligent Agent.
  
  In order for Oracle Management Server to detect the infrastructure and any other application server installations on this host, you must make sure the Intelligent Agent is started. Note that one Intelligent Agent is started per host and must be started after every reboot.
  
  (UNIX) You can run the following commands in the Oracle home of the primary installation (the first installation on the host) to get status and start the Intelligent Agent:
```
ORACLE_HOME/bin/agentctl status agent
ORACLE_HOME/bin/agentctl start agent
```
  (Windows) You can check the status and start the Intelligent Agent using the Services control panel. The name of the service is in the following format:
```
OracleORACLE_HOMEAgent
```

Starting an Infrastructure Using Commands on UNIX

This section describes how to start an infrastructure using command-line tools on UNIX. Except where noted, all commands should be run in the Oracle home of the infrastructure.

Start the metadata repository.
1. Start the metadata repository listener:
```
ORACLE_HOME/bin/lsnrctl start
```
2. Set the ORACLE_SID environment variable to the metadata repository system identifier. The default ORACLE_SID is iasdb.
```
(Bourne or Korn shell) ORACLE_SID=iasdb; export ORACLE_SID
(C shell) setenv ORACLE_SID iasdb
```
3. Start the metadata repository instance using SQL*Plus:
```
ORACLE_HOME/bin/sqlplus /nolog
sql> connect sys/password_for_sys as sysdba
sql> startup
sql> quit
```
Start Oracle Internet Directory.
1. Make sure the ORACLE_SID is set to the metadata repository system identifier (refer to previous step).
2. Start the Oracle Internet Directory monitor:
```
ORACLE_HOME/bin/oidmon start
```
3. Start the Oracle Internet Directory server:
```
ORACLE_HOME/bin/oidctl server=oidldapd configset=0 instance=n start
```
  where n is any instance number (1, 2, 3...) that is not in use. For example:
```
ORACLE_HOME/bin/oidctl server=oidldapd configset=0 instance=1 start
```
Start the Enterprise Manager Web site.

Even though you are using command-line, the Web site is required because it provides underlying support for the command-line tools. The Web site must be started after every system boot.

You can run the following commands in the Oracle home of the primary installation (the first installation on the host) to get status and start the Web site:
```
ORACLE_HOME/bin/emctl status
ORACLE_HOME/bin/emctl start
```
Start Oracle HTTP Server.
```
ORACLE_HOME/dcm/bin/dcmctl start -ct ohs
```
Note that starting Oracle HTTP Server also makes Oracle9iAS Single Sign-On available.
Start the OC4J_DAS instance.
```
ORACLE_HOME/dcm/bin/dcmctl start -co OC4J_DAS
```
Note that the infrastructure instance contains other OC4J instances, such as OC4J_home and OC4J_Demos, but these do not need to be started; their services are not required and incur unnecessary overhead. Refer to "About Unused Component Instances in the Infrastructure" for more information.
Start Web Cache (optional).

Web Cache is not configured in the infrastructure by default, but if you have configured it, start it as follows:
```
ORACLE_HOME/bin/webcachectl start
```
Start Oracle Management Server and Intelligent Agent (optional).

Perform these steps only if you have configured Oracle Management Server.
1. Start Oracle Management Server:
```
ORACLE_HOME/bin/oemctl start oms
```
2. Start the Intelligent Agent.
  
  In order for Oracle Management Server to detect the infrastructure and any other application server installations on this host, you must make sure the Intelligent Agent is started. Note that one Intelligent Agent is started per host and must be started after every reboot.
  
  You can run the following commands in the Oracle home of the primary installation (the first installation on the host) to get status and start the Intelligent Agent:
```
ORACLE_HOME/bin/agentctl status agent
ORACLE_HOME/bin/agentctl start agent
```

Starting an Infrastructure Using Commands on Windows

This section describes how to start an infrastructure using command-line tools on Windows. Except where noted, all commands should be run in the Oracle home of the infrastructure.

Start the metadata repository.
1. Start the metadata repository listener:
```
ORACLE_HOME\bin\lsnrctl start
```
2. Set the ORACLE_SID environment variable to the metadata repository system identifier (default is iasdb).
  
  You can set the ORACLE_SID system variable using the System Properties control panel.
3. Start the metadata repository instance using SQL*Plus:
```
ORACLE_HOME\bin\sqlplus /nolog
sql> connect sys/password_for_sys as sysdba
sql> startup
sql> quit
```
Start Oracle Internet Directory.
1. Make sure the ORACLE_SID is set to the metadata repository system identifier (refer to previous step).
2. Start the Oracle Internet Directory monitor:
```
ORACLE_HOME\bin\oidmon start
```
3. Start the Oracle Internet Directory server:
```
ORACLE_HOME\bin\oidctl server=oidldapd configset=0 instance=n start
```
  where n is any instance number (1, 2, 3...) that is not in use. For example:
```
ORACLE_HOME\bin\oidctl server=oidldapd configset=0 instance=1 start
```
Start the Enterprise Manager Web site.

Even though you are using command-line, the Web site is required because it provides underlying support for the command-line tools. The Web site must be started after every system boot.

You can check the status and start the Enterprise Manager Web site using the Services control panel. The name of the service is in the following format:
```
OracleORACLE_HOMEEMwebsite
```
You can also start the service using the following command line:
```
net start WEB_SITE_SERVICE_NAME
```
Start Oracle HTTP Server.
```
ORACLE_HOME\dcm\bin\dcmctl start -ct ohs
```
Note that starting Oracle HTTP Server also makes Oracle9iAS Single Sign-On available.
Start the OC4J_DAS instance.
```
ORACLE_HOME\dcm\bin\dcmctl start -co OC4J_DAS
```
Note that the infrastructure instance contains other OC4J instances, such as OC4J_home and OC4J_Demos, but these do not need to be started; their services are not required and incur unnecessary overhead. Refer to "About Unused Component Instances in the Infrastructure" for more information.
Start Web Cache (optional).

Web Cache is not configured in the infrastructure by default, but if you have configured it, start it as follows:
```
ORACLE_HOME\bin\webcachectl start
```
Start Oracle Management Server and Intelligent Agent (optional).

Perform these steps only if you have configured Oracle Management Server.
1. Start Oracle Management Server:
```
ORACLE_HOME\bin\oemctl start oms
```
2. Start the Intelligent Agent.
  
  In order for Oracle Management Server to detect the infrastructure and any other application server installations on this host, you must make sure the Intelligent Agent is started. Note that one Intelligent Agent is started per host and must be started after every reboot.
  
  You can check the status and start the Intelligent Agent using the Services control panel. The name of the service is in the following format:
```
OracleORACLE_HOMEAgent
```

Stopping an Infrastructure

This section contains the following procedures for stopping an infrastructure:

No matter which procedure you use, stopping an infrastructure involves performing the following steps in order:

Stop all middle-tier application server instances that use the infrastructure.
Stop Oracle Management Server and Intelligent Agent (optional)
Stop Web Cache (optional)
Stop OC4J instances
Stop Oracle HTTP Server
Stop Oracle Internet Directory
Stop the Metadata Repository

Stopping an Infrastructure Using Oracle Enterprise Manager on UNIX and Windows

This section describes how to stop an infrastructure using Oracle Enterprise Manager on UNIX and Windows.

Stop all middle-tier application server instances that use the infrastructure.
Stop Oracle Management Server and Intelligent Agent (optional).

Perform these steps only if you have configured Oracle Management Server.
1. Stop Oracle Management Server:
```
(UNIX) ORACLE_HOME/bin/oemctl stop oms
(Windows) ORACLE_HOME\bin\oemctl stop oms
```
2. Stop the Intelligent Agent (for system shutdown only).
  
  If you are preparing to shut down your system, stop the Intelligent Agent on this host.
  
  (UNIX) You can run the following commands in the Oracle home of the primary installation (the first installation on the host) to get status and stop the Intelligent Agent:
```
ORACLE_HOME/bin/agentctl status agent
ORACLE_HOME/bin/agentctl stop agent
```
  (Windows) You can check the status and start the Intelligent Agent using the Services control panel. The name of the service is in the following format:
```
OracleORACLE_HOMEAgent
```
Access the Infrastructure Instance Page on the Enterprise Manager Web site.

Point your browser to the Enterprise Manager Web site on your host using the following URL:
```
http://hostname:1810
```
Log in as ias_admin. This opens the Farm Page. Select the infrastructure instance in the Name column in the Standalone Instances section. This opens the Infrastructure Instance Page.

Note that you should not click Stop All. Instead, follow the rest of these steps to stop components in the proper order.
Stop Web Cache (optional).

Web Cache is not configured in the infrastructure by default, but if you have configured it, stop it as follows:
1. On the Infrastructure Instance Page, in the System Components section, click the radio button in the Select column for Web Cache.
2. Click the Stop button on the top right of the System Components section.
Stop the OC4J instances.

Stop all running OC4J instances (OC4J_DAS, OC4J_home, OC4J_Demos) by performing these steps on each one.
1. On the Infrastructure Instance Page, in the System Components section, click the radio button in the Select column for the OC4J instance.
2. Click the Stop button on the top right of the System Components section.
Stop Oracle HTTP Server.
1. On the Infrastructure Instance Page, in the System Components section, click the radio button in the Select column for HTTP Server.
2. Click the Stop button on the top right of the System Components section.
Note that stopping Oracle HTTP Server also makes Oracle9iAS Single Sign-On unavailable.
Stop Oracle Internet Directory.
1. On the Infrastructure Instance Page, in the System Components section, click the radio button in the Select column for Internet Directory.
2. Click the Stop button on the top right of the System Components section.
Stop the metadata repository.
1. Launch Oracle Enterprise Manager in standalone mode:
```
(UNIX) ORACLE_HOME/bin/oemapp dbastudio
(Windows) ORACLE_HOME\bin\oemapp dbastudio
```
  Select Launch Standalone and click OK.
2. Expand the Databases entry in the System Objects frame by clicking the plus sign (+) next to it.
3. Select the metadata repository entry.
4. In the toolbar, select Object -> Connect. Connect as a user with SYSDBA privileges.
5. In the toolbar, select Object -> Shutdown.
6. Stop the metadata repository listener:
```
(UNIX) ORACLE_HOME/bin/lsnrctl stop
(Windows) ORACLE_HOME\bin\lsnrctl stop
```
Stop the Enterprise Manager Web site (system shutdown only).

If you are preparing to shut down your system, stop the Enterprise Manager Web site.

(UNIX) You can run the following commands in the Oracle home of the primary installation (the first installation on the host) to get status and stop the Web site:
```
ORACLE_HOME/bin/emctl status
ORACLE_HOME/bin/emctl stop
```
(Windows) You can check the status and stop the Enterprise Manager Web site using the Services control panel. The name of the service is in the following format:
```
OracleORACLE_HOMEEMwebsite
```

Stopping an Infrastructure Using Commands on UNIX

This section describes how to stop an infrastructure using command-line tools on UNIX. Except where noted, all commands should be run in the Oracle home of the infrastructure.

Stop all middle-tier application server instances that use the infrastructure.
Stop Oracle Management Server and Intelligent Agent (optional).

Perform these steps only if you have configured Oracle Management Server.
1. Stop Oracle Management Server:
  
  If you have configured Oracle Management Server, stop it as follows:
```
ORACLE_HOME/bin/oemctl stop oms
```
2. Stop the Intelligent Agent (for system shutdown only).
  
  If you are preparing to shut down your system, stop the Intelligent Agent on this host.
  
  You can run the following commands in the Oracle home of the primary installation (the first installation on the host) to get status and stop the Intelligent Agent:
```
ORACLE_HOME/bin/agentctl status agent
ORACLE_HOME/bin/agentctl stop agent
```
Stop the Enterprise Manager Web site (for system shutdown only).

If you are preparing to shut down your system, stop the Enterprise Manager Web site by running the following command in the Oracle home of the primary installation (the first installation on the host):
```
ORACLE_HOME/bin/emctl stop
```
Stop Web Cache (optional).

Web Cache is not configured in the infrastructure by default, but if you have configured it, stop it as follows:
```
ORACLE_HOME/bin/webcachectl stop
```
Stop OC4J instances and Oracle HTTP Server.

If you are preparing to shutdown your system, stop all running OC4J instances, Oracle HTTP Server, and OPMN as follows:
```
ORACLE_HOME/dcm/bin/dcmctl shutdown
```
Otherwise, if you are not preparing to shut down your system, stop all running OC4J instances and Oracle HTTP Server (leave OPMN running):
```
ORACLE_HOME/dcm/bin/dcmctl stop
```
Note that stopping Oracle HTTP Server also makes Oracle9iAS Single Sign-On unavailable.
Stop Oracle Internet Directory.
1. Make sure the ORACLE_SID is set to the metadata repository system identifier (refer to the next step).
2. Stop the Oracle Internet Directory server:
```
ORACLE_HOME/bin/oidctl server=oidldapd configset=0 instance=n stop
```
  where n is the instance number that was used to start the server (1, 2, 3...). For example:
```
ORACLE_HOME\bin\oidctl server=oidldapd configset=0 instance=1 stop
```
3. Stop the Oracle Internet Directory monitor:
```
ORACLE_HOME/bin/oidmon stop
```
Stop the metadata repository.
1. Set the ORACLE_SID environment variable to the metadata repository system identifier. The default ORACLE_SID is iasdb.
```
(Bourne or Korn shell) ORACLE_SID=iasdb; export ORACLE_SID
(C shell) setenv ORACLE_SID iasdb
```
2. Stop the metadata repository instance using SQL*Plus:
```
ORACLE_HOME/bin/sqlplus /nolog
sql> connect sys/password_for_sys as sysdba
sql> shutdown
sql> quit
```
3. Stop the metadata repository listener:
```
ORACLE_HOME/bin/lsnrctl sto
```

Stopping an Infrastructure Using Commands on Windows

This section describes how to stop an infrastructure using command-line tools on Windows. Except where noted, all commands should be run in the Oracle home of the infrastructure.

Stop all middle-tier application server instances that use the infrastructure.
Stop Oracle Management Server and Intelligent Agent (optional).

Perform these steps only if you have configured Oracle Management Server.
1. Stop Oracle Management Server.
```
ORACLE_HOME\bin\oemctl stop oms
```
2. Stop the Intelligent Agent (for system shutdown only).
  
  If you are preparing to shut down your system, stop the Intelligent Agent on this host.
  
  The name of the service is in the following format:
```
OracleORACLE_HOMEAgent
```
  For example:
```
OracleOraHome902Agent
```
  The Services control panel shows you the status of the service and indicates the method used to stop the service. You can then select the service name and use the controls on the Services window to stop the service.
Stop the Enterprise Manager Web site (for system shutdown only).

If you are preparing to shut down your system, stop the Enterprise Manager Web site.

You can check the status and stop the Enterprise Manager Web site using the Services control panel. The name of the service is in the following format:
```
OracleORACLE_HOMEEMwebsite
```
For example, if the name of the Oracle home is OraHome902, the service name is:
```
OracleOraHome902EMWebsite
```
Stop Web Cache (optional).

Web Cache is not configured in the infrastructure by default, but if you have configured it, stop it as follows:
```
ORACLE_HOME\bin\webcachectl stop
```
Stop OC4J instances and Oracle HTTP Server

If you are preparing to shutdown your system, stop all running OC4J instances, Oracle HTTP Server, and OPMN as follows:
```
ORACLE_HOME\dcm\bin\dcmctl shutdown
```
Otherwise, if you are not preparing to shut down your system, stop all running OC4J instances and Oracle HTTP Server (leave OPMN running):
```
ORACLE_HOME\dcm\bin\dcmctl stop
```
Note that stopping Oracle HTTP Server also makes Oracle9iAS Single Sign-On unavailable.
Stop Oracle Internet Directory.
1. Make sure the ORACLE_SID is set to the metadata repository system identifier (refer to next step).
2. Stop the Oracle Internet Directory server:
```
ORACLE_HOME\bin\oidctl server=oidldapd configset=0 instance=n stop
```
  where n is the instance number that was used to start the server (1, 2, 3...). For example:
```
ORACLE_HOME\bin\oidctl server=oidldapd configset=0 instance=1 stop
```
3. Stop the Oracle Internet Directory monitor:
```
ORACLE_HOME\bin\oidmon stop
```
Stop the metadata repository.
1. Set the ORACLE_SID environment variable to the metadata repository system identifier. The default ORACLE_SID is iasdb.
  
  You can set the ORACLE_SID system variable using the System Properties control panel.
2. Stop the metadata repository instance using SQL*Plus:
```
ORACLE_HOME\bin\sqlplus /nolog
sql> connect sys/password_for_sys as sysdba
sql> shutdown
sql> quit
```
3. Stop the metadata repository listener:
```
ORACLE_HOME\bin\lsnrctl stop
```

5 Starting and Stopping the Application Server