Starting and Stopping Oracle WebLogic Server Managed Servers Configuring Node Manager to Start Managed Servers

3-12 Oracle Fusion Middleware 2 Day Administration Guide -Dweblogic.management.username=weblogic -Dweblogic.management.password=password -Dweblogic.system.StoreBootIdentity=true To stop an Oracle WebLogic Server Administration Server, use the following script: MW_HOME user_projectsdomainsdomain_namebinstopWeblogic.sh username password [admin_url]

3.4.2 Starting and Stopping Oracle WebLogic Server Managed Servers

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 3.4.3 . To start or stop a 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, select Control, then Start Up or Shut Down.

3.4.3 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 environment information is provided through the start scripts, such as startWebLogic and setDomainEnv, which 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: See Also: Oracle Fusion Middleware Oracle WebLogic Scripting Tool WLST Scripts: To start a Managed Server: MW_HOME user_projectsdomainsdomain_namebinstartManagedWebLogic.sh server_name admin_url username password To stop a Managed Server: MW_HOME user_projectsdomainsdomain_namebinstopManagedWeblogic.sh username password admin_url Installing and Configuring Oracle Fusion Middleware 3-13 UNIX ORACLE_COMMON_HOMEcommonbinsetNMProps.sh. Windows ORACLE_COMMON_HOME\common\bin\setNMProps.cmd For example, on Linux, execute the setNMProps script and start Node Manager: ORACLE_COMMON_HOME commonbinsetNMProps.sh MW_HOME wlserver_nserverbinstartNodeManager.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.

3.4.4 Starting and Stopping Components