Managing Components Basic Tasks for Configuring and Managing Oracle Fusion Middleware

4 Starting and Stopping Oracle Fusion Middleware 4-1 4 Starting and Stopping Oracle Fusion Middleware This chapter describes procedures for starting and stopping Oracle Fusion Middleware. It contains the following topics: ■ Overview of Starting and Stopping Procedures ■ Starting and Stopping Oracle WebLogic Server Instances ■ Starting and Stopping Components ■ Starting and Stopping Fusion Middleware Control ■ Starting and Stopping Oracle Management Agent ■ Starting and Stopping Applications ■ Starting and Stopping Your Oracle Fusion Middleware Environment ■ Starting and Stopping: Special Topics

4.1 Overview of Starting and Stopping Procedures

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.

4.2 Starting and Stopping Oracle WebLogic Server Instances

You can start Oracle WebLogic Server Administration Servers using the WLST command line. You can start and stop Managed Servers using scripts, 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: Note: For information about starting and stopping servers for IBM Websphere, see Starting and Stopping Servers on IBM WebSphere in the Oracle Fusion Middleware Third-Party Application Server Guide. 4-2 Oracle Fusion Middleware Administrators Guide ■ Starting and Stopping Administration Servers ■ Starting and Stopping Managed Servers ■ Enabling Servers to Start Without Supplying Credentials ■ Configuring Node Manager to Start Managed Servers

4.2.1 Starting and Stopping Administration Servers

You can start and stop Oracle WebLogic Server Administration Servers using the WLST command line or a script. When you start or stop the Administration Server, you also start or stop the processes running in the Administration Server, including the WebLogic Server Administration Console and Fusion Middleware Control. For example, to start an Administration Server, use the following script: MW_HOMEuser_projectsdomainsdomain_namebinstartWebLogic.sh -Dweblogic.management.username=weblogic -Dweblogic.management.password=password -Dweblogic.system.StoreBootIdentity=true To stop an Administration Server, use the following script: MW_HOMEuser_projectsdomainsdomain_namebinstopWeblogic.sh username password [admin_url]

4.2.2 Starting and Stopping Managed Servers

You can start and stop Managed Servers using Fusion Middleware Control or WLST commands and scripts, as described in the following topics: ■ Starting and Stopping Managed Servers Using Fusion Middleware Control ■ Starting and Stopping Managed Servers Using WLST

4.2.2.1 Starting and Stopping Managed Servers Using Fusion Middleware Control

Fusion Middleware Control and 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: 1. From the navigation pane, expand the farm, then WebLogic Domain, and then the domain. 2. Select the Managed Server. 3. From the WebLogic Server menu, choose Control, then Start Up or Shut Down. Alternatively, you can right-click the server, then choose Control, then Start Up or Shut Down.

4.2.2.2 Starting and Stopping Managed Servers Using WLST

You can use a script or WLST to start and stop a WebLogic Server Managed Server. For example, to start a WebLogic Server Managed Server, use the following script: Starting and Stopping Oracle Fusion Middleware 4-3 UNIX MW_HOMEuser_projectsdomainsdomain_namebinstartManagedWebLogic.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: UNIX MW_HOMEuser_projectsdomainsdomain_namebinstopManagedWebLogic.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

4.2.3 Enabling Servers to Start Without Supplying Credentials

You can enable the Administration Server and Managed Servers to start without prompting you for the administrator user name and password. 1. For the Administration Server, create a boot.properties file: a. Create the following directory: MW_HOMEuser_ projectsdomainsdomain_nameserversAdminServersecurity b. Use a text editor to create a file called boot.properties in the security directory created in the previous step, and enter the following lines in the file: username=adminuser password=password 2. For each Managed Server: a. Create the following directory: MW_HOMEuser_ projectsdomainsdomain_nameserversserver_namesecurity b. Copy the boot.properties file you created for the Administration Server to the security directory you created in the previous step. 3. Restart the Administration Server and Managed Servers, as described in Section 4.2.1 and Section 4.2.2 .

4.2.4 Configuring Node Manager to Start Managed Servers

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 Note: When you start the Administration Server or Managed Server, the user name and password entries in the file are encrypted. For security reasons, minimize the time the entries in the file are left unencrypted. After you edit the file, start the server as soon as possible in order for the entries to be encrypted. See Also: Boot Identity Files in the Oracle Fusion Middleware Managing Server Startup and Shutdown for Oracle WebLogic Server for more information