Oracle® Fusion Middleware Administrator's Guide 11g Release 1 (11.1.1) E10105-02 |
|
![]() Previous |
![]() Next |
This chapter describes procedures for starting and stopping Oracle Fusion Middleware.
It contains the following topics:
Oracle Fusion Middleware is a flexible product that you can start and stop in different ways, depending on your requirements. In most situations, you can use Fusion Middleware Control, Oracle WebLogic Server Administration Console, or the WLST or OPMN commands to start or stop Oracle Fusion Middleware components.
These tools are completely compatible and, in most cases, can be used interchangeably. For example, you can start a J2EE component using WLST and stop it using Fusion Middleware Control.
You can start Oracle WebLogic Server Administration Servers using the WLST command line. You can start and stop Managed Servers using the WLST command line, the WebLogic Server Administration Console, or Fusion Middleware Control. The following sections describe how to start and stop WebLogic Servers using the WLST command line, Fusion Middleware Control, or both.
You can start and stop Oracle WebLogic Server Administration Servers using the WLST command line. When you do stop the Administration Server, you also stop the processes running in the Administration Server, including the WebLogic Server Administration Console and Fusion Middleware Control.
To start an Administration Server, use the following script, which is based on WLST commands:
MW_HOME/user_projects/domains/domain_name/bin/startWebLogic.sh -Dweblogic.management.username=weblogic -Dweblogic.management.password=password -Dweblogic.system.StoreBootIdentity=true
To stop an Administration Server, use the following script, which is based on WLST commands:
MW_HOME/user_projects/domains/domain_name/bin/stopWeblogic.sh username password admin_url
You can use WLST to start and stop a WebLogic Server Managed Server.
To start a WebLogic Server Managed Server, use the following script, which is based on WLST commands:
(UNIX) MW_HOME/user_projects/domains/domain_name/bin/startManagedWebLogic.sh managed_server_name admin_url (Windows) MW_HOME\user_projects\domains\domain_name\bin\startManagedWebLogic.cmd managed_server_name admin_url
When prompted, enter your user name and password.
To stop a WebLogic Server Managed Server, use the following script, which is based on WLST commands:
(UNIX) MW_HOME/user_projects/domains/domain_name/bin/stopManagedWebLogic.sh managed_server_name admin_url username password (Windows) MW_HOME\user_projects\domains\domain_name\bin\stopManagedWebLogic.cmd managed_server_name admin_url username password
Fusion Middleware Control, as well as the Oracle WebLogic Server Administration Console, use Node Manager to start Managed Servers. If you are starting a Managed Server that does not contain Oracle Fusion Middleware products other than Oracle WebLogic Server, you can start the servers using the procedure in this section.
However, if the Managed Server contains other Oracle Fusion Middleware products, such as Oracle SOA Suite, Oracle WebCenter, or Oracle JRF, you must first configure Node Manager, as described in Section 4.2.4.
To start or stop a WebLogic Server Managed Server using Fusion Middleware Control:
From the navigation pane, expand the farm, then WebLogic Domain, and then the domain.
Select the Managed Server.
From the WebLogic Server menu, choose Control, then Start Up or Shut Down.
Alternatively, you can right-click on the server, then choose Control, then Start Up or Shut Down.
If a Managed Server contains other Oracle Fusion Middleware products, such as Oracle SOA Suite, Oracle WebCenter, or Oracle JRF, the Managed Servers environment must be configured to set the correct classpath and parameters. This environment information is provided through the start scripts, such as startWebLogic and setDomainEnv, that are located in the domain directory.
If the Managed Servers are started by Node Manager, (as is the case when the servers are started by the Oracle WebLogic Server Administration Console or Fusion Middleware Control) Node Manager must be instructed to use these start scripts so that the server environments are correctly configured. Specifically, Node Manager must be started with the property StartScriptEnabled=true
.
There are several ways to ensure that Node Manager starts with this property enabled. As a convenience, Oracle Fusion Middleware provides the following script, which adds the property StartScriptEnabled=true
to the nodemanager.properties file:
(UNIX) ORACLE_COMMON_HOME/common/bin/setNMProps.sh. (Windows) ORACLE_COMMON_HOME\common\bin\setNMProps.cmd
For example, on Linux, execute the setNMProps script and start Node Manager:
ORACLE_COMMON_HOME/common/bin/setNMProps.sh MW_HOME/wl_server_n/server/bin/startNodeManager.sh
When you start Node Manager, it reads the nodemanager.properties file with the StartScriptEnabled=true
property, and uses the start scripts when it subsequently starts Managed Servers. Note that you need to run the setNMProps script only once.
See Also: "Using Node Manager" in the Oracle Fusion Middleware Node Manager Administrator's Guide for Oracle WebLogic Server for other methods of configuring and starting Node Manager |
You can start and stop components using the command line, the WebLogic Server Administration Console, or Fusion Middleware Control, depending upon the component. The following sections describe how to start and stop components using the command line and Fusion Middleware Control.
If a component is a Java component, you use WLST commands to start and stop the component. If a component is a system component, you use opmnctl
commands to start and stop the components.
To start and stop Java components, use the WLST startApplication
and stopApplication
commands:
startApplication(appName, [options]) stopApplication(appName, [options])
For example, to start Oracle Directory Integration Platform, use the following command:
startApplication("DIP")
To start and stop system components, use the opmnctl
command-line tool. It is located in the following directory:
(UNIX) ORACLE_HOME/opmn/bin (Windows) ORACLE_HOME\opmn\bin
To start or stop OPMN and all system processes, such as Oracle HTTP Server:
opmnctl startall opmnctl stopall
To start, stop, or restart a component using opmnctl:
opmnctl startproc ias-component=component_name opmnctl stopproc ias-component=component_name opmnctl restartproc ias-component=component_name
For example, to start Oracle HTTP Server, ohs1:
opmnctl startproc ias-component=ohs1
To start, stop, or restart the subprocess of a component:
opmnctl stopproc process-type=process opmnctl startproc process-type=process opmnctl restartproc process-type=process
To start, stop, and restart components:
From the navigation pane, expand the farm, then navigate to the component.
Select the component, such as SoaInfra.
From the dynamic target menu, choose Control, then Start Up or Shut Down.
Note: If OPMN is not started, you cannot start system components such as Oracle HTTP Server or Oracle Internet Directory using Fusion Middleware Control. To start OPMN, use the following command:opmnctl start |
If Fusion Middleware Control is configured for a domain, it is automatically started when you start an Oracle WebLogic Server Administration Server, as described in Section 4.2.1.
If Fusion Middleware Control is configured for a domain, it is automatically stopped when you stop an Oracle WebLogic Server Administration Server, as described in Section 4.2.1.
Oracle Management Agent is designed specifically for monitoring particular Oracle Fusion Middleware components.
To start Oracle Management Agent, use the following command:
opmnctl startproc ias-component=EMAGENT
To stop Oracle Management Agent, use the following command:
opmnctl stopproc ias-component=EMAGENT
You can start and stop applications using WLST command line, the WebLogic Server Administration Console, or Fusion Middleware Control. The following sections describe how to start and stop applications using the command line and Fusion Middleware Control.
To start or stop applications with the WLST command line, use the following commands:
startApplication(appName, [options]) stopApplication(appName, [options])
The application must be fully configured and available in the domain. The startApplication
command returns a WLSTProgress object that you can access to check the status of the command. In the event of an error, the command returns a WLSTException. For more information about the WLSTProgress object, see "WLSTProgress Object" in the Oracle Fusion Middleware Oracle WebLogic Scripting Tool.
To start or stop a Java EE application using Fusion Middleware Control:
From the navigation pane, expand Application Deployments.
Select the application.
From the Application Deployment menu, choose Control, then Start Up or Shut Down.
To start or stop a SOA Composite application using Fusion Middleware Control:
From the navigation pane, expand the farm, then SOA, and then soa-infra.
Select the application.
On the SOA Composite page, click Start Up or Shut Down.
This section provides procedures for starting and stopping an Oracle Fusion Middleware environment. An environment can consist of Oracle WebLogic Server domain, an Administration Server, multiple Managed Servers, Java components, system components, including Identity Management components, and a database used as a repository for metadata. The components may be dependent on each other and it is important to start and stop them in the proper order.
You can follow these procedures when you need to completely shut down your Oracle Fusion Middleware environment. For example, when preparing to perform a complete backup of your environment, or apply a patch.
To start an Oracle Fusion Middleware environment:
Start any database-based repository:
Set the ORACLE_HOME environment variable to the Oracle home for the database.
Set the ORACLE_SID environment variable to the SID for the database (default is orcl
).
ORACLE_HOME/bin/lsnrctl start
Start the database instance:
ORACLE_HOME/bin/sqlplus /nolog
SQL> connect SYS as SYSDBA
SQL> startup
SQL> quit
Start Oracle Identity Management system components:
Set the ORACLE_HOME environment variable to the Oracle home for the Identity Management components.
Start OPMN and all system components:
opmnctl startall
Start the Oracle WebLogic Server Administration Server as described in Section 4.2.1.
Start the Oracle WebLogic Server Managed Servers as described in Section 4.2.2. Any applications deployed to the server are also started.
Start OPMN and all system components.
Set the ORACLE_HOME and ORACLE_INSTANCE environment variables to the Oracle home and Oracle instance for the system components.
Start OPMN and all system components in that Oracle instance:
opmnctl startall
If your environment includes components that are targets monitored by Oracle Management Agent, start Oracle Management Agent, as described in Section 4.5.
To stop an Oracle Fusion Middleware environment:
Stop system components, such as Oracle HTTP Server. You can stop them in any order.
Set the ORACLE_HOME and ORACLE_INSTANCE environment variables to the Oracle home and Oracle instance for the system components.
Stop OPMN and all system components in that Oracle instance:
opmnctl stopall
If your environment includes components that are targets monitored by Oracle Management Agent, stop Oracle Management Agent, as described in Section 4.5.
Stop the Oracle WebLogic Server Managed Servers as described in Section 4.2. Any applications deployed to the server are also stopped.
Stop Oracle Identity Management components:
Set the ORACLE_HOME environment variable to the Oracle home for the Identity Management components.
Stop OPMN and all system components:
opmnctl stopall
Stop the Administration Server as described in Section 4.2.1.
Stop any database-based repository:
Set the ORACLE_HOME environment variable to the Oracle home for the database.
Set the ORACLE_SID environment variable to the SID for the database (default is orcl
).
Stop the database instance:
ORACLE_HOME/bin/sqlplus /nolog
SQL> connect SYS as SYSDBA
SQL> shutdown
SQL> quit
Stop the Net Listener:
ORACLE_HOME/bin/lsnrctl stop
This section contains the following special topics about starting and stopping Oracle Fusion Middleware:
There are special considerations and procedures for starting and stopping High Availability environments, such as:
Oracle Fusion Middleware Cold Failover Cluster
Oracle Application Server Disaster Recovery
See: Oracle Fusion Middleware High Availability Guide for information about starting and stopping in high-availability environments |
If you find that the Oracle Database instance is taking a long time to shut down, you can use the following commands to force an immediate shutdown:
ORACLE_HOME/bin/sqlplus /nolog
SQL> connect SYS as SYSDBA
SQL> SHUTDOWN IMMEDIATE;
An immediate database shutdown proceeds with the following conditions:
No new connections are allowed, nor are new transactions allowed to be started, after the statement is issued.
Any uncommitted transactions are rolled back. (If long uncommitted transactions exist, this method of shutdown might not complete quickly, despite its name.)
Oracle does not wait for users currently connected to the database to disconnect. Oracle implicitly rolls back active transactions and disconnects all connected users.
The next startup of the database will not require any instance recovery procedures.
See Also: Oracle Database Administrator's Guide in the Oracle Database 11g documentation library |