Starting and Stopping Components Using Fusion Middleware Control

4-6 Oracle Fusion Middleware Administrators Guide

4.6 Starting and Stopping Applications

You can start and stop applications using Fusion Middleware Control, the WebLogic Server Administration Console, or the WLST command line. The following topics describe how to start and stop applications using Fusion Middleware Control and the command line: ■ Starting and Stopping Java EE Applications Using Fusion Middleware Control ■ Starting and Stopping Java EE Applications Using WLST

4.6.1 Starting and Stopping Java EE Applications Using Fusion Middleware Control

To start or stop a Java EE application using Fusion Middleware Control: 1. From the navigation pane, expand Application Deployments. 2. Select the application. 3. 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: 1. From the navigation pane, expand the farm, then SOA, and then soa-infra. 2. Select the application. 3. On the SOA Composite page, click Start Up or Shut Down.

4.6.2 Starting and Stopping Java EE Applications Using WLST

To start or stop a Java EE application with the WLST command line, use the following commands: startApplicationappName, [options] stopApplicationappName, [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.

4.7 Starting and Stopping Your Oracle Fusion Middleware Environment

This section provides procedures for starting and stopping an Oracle Fusion Middleware environment. An environment can consist of an 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. Therefore, 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.

4.7.1 Starting an Oracle Fusion Middleware Environment

To start an Oracle Fusion Middleware environment: Starting and Stopping Oracle Fusion Middleware 4-7 1. Start any database-based repository: a. Set the ORACLE_HOME environment variable to the Oracle home for the database. b. Set the ORACLE_SID environment variable to the SID for the database default is orcl. c. Start the Net Listener: ORACLE_HOMEbinlsnrctl start d. Start the database instance: ORACLE_HOMEbinsqlplus nolog SQL connect SYS as SYSDBA SQL startup SQL quit 2. Start the Oracle WebLogic Server Administration Server as described in Section 4.2.1 . 3. If you have not already done so, configure Node Manager, as described in Section 4.2.4 . 4. Ensure Node Manager is running. If Node Manager is not running, start it by executing the following command: MW_HOMEuser_projectsdomainsDOMAIN_NAMEbinstartNodeManager.sh 5. Start Oracle Identity Management system components: a. Set the ORACLE_HOME environment variable to the Oracle home and ORACLE_INSTANCE environment variables for the Identity Management components. b. Start OPMN and all system components: opmnctl startall 6. Start the Oracle WebLogic Server Managed Servers as described in Section 4.2.2.2 . Any applications deployed to the server are also started. 7. Start OPMN and all other system components, such as Oracle HTTP Server. a. Set the ORACLE_HOME and ORACLE_INSTANCE environment variables to the Oracle home and Oracle instance for the system components. b. Start OPMN and all system components in that Oracle instance: opmnctl startall 8. If your environment includes components that are targets monitored by Oracle Management Agent, start Oracle Management Agent, as described in Section 4.5 .

4.7.2 Stopping an Oracle Fusion Middleware Environment

To stop an Oracle Fusion Middleware environment: 1. Stop system components, such as Oracle HTTP Server. You can stop them in any order. a. Set the ORACLE_HOME and ORACLE_INSTANCE environment variables to the Oracle home and Oracle instance for the system components.