Shut Down and Start Server Processes

You can shut down and start WebLogic Server processes, including the Administration Server, within your Oracle Java Cloud Service instance.

You can shut down WebLogic Server processes without stopping the nodes on which the servers are running. You might shut down a server process for routine maintenance or testing, or to address CPU and memory resource contention. This approach shuts down the server processes only, while other processes you might have running on the nodes continue to run.

Topics

• Use the WebLogic Server Administration Console to Shut Down Servers

• Use WLST Commands to Start the Administration Server

• Use the WebLogic Server Administration Console to Start Managed Servers

Use the WebLogic Server Administration Console to Shut Down Servers

Use the WebLogic Server Administration Console to shut down the server processes for your Oracle Java Cloud Service instance. A WebLogic Server domain includes an administration server and one or more managed servers.

To use the WebLogic Server Console to shut down servers:

1. Access the Oracle Java Cloud Service console.
2. Click Manage this instance for the desired service instance, and then select Open WebLogic Server Administration Console.
3. Enter the WebLogic Server administrator user name and password you provided when you created the service instance.
4. From the WebLogic Server Administration Console, under Domain Structure, expand Environment.
5. Click Servers.
   From the Configuration tab of the Summary of Servers page, notice that the state of the Administration Server and Managed Servers is RUNNING.
6. Click the Control tab.
7. Click the check box to the left of each server.
8. Click Shutdown, and then select Force Shutdown Now or When Work Completes.
   When you shut down the administration server, a message warns you that the browser session will end.

Use WLST Commands to Start the Administration Server

You start the Administration Server in an Oracle Java Cloud Service instance through the Node Manager by using WLST commands.

Prior to running WLST, identify the public IP address of the Administration Server node and connect to it with a secure shell (SSH) client.

1. After connecting to the node, switch to the oracle user:

   sudo su - oracle

2. Verify that the Node Manager is running:

   ps -ef | grep NodeManager

   You should receive messages showing that the Node Manager is running.
3. Change the directory to the bin folder in DOMAIN_HOME.

   cd $DOMAIN_HOME/bin

   For example, /u01/data/domains/OurServi_domain/bin

4. Set up the environment.

   . ./setDomainEnv.sh

   You must use the . to ensure that the environment variables are set in the current shell.

5. Start WLST:

   $COMMON_COMPONENTS_HOME/common/bin/wlst.sh

6. To connect to the Node Manager, use the WLST nmConnect command:

   nmConnect ('username','password','host','nmPort','domainName','domainDir','nmType')

   Parameter	Description	Example
   username	WebLogic Server username you specified when you created the service instance.
   password	WebLogic Server password you specified when you created the service instance.
   host	The host name of the Node Manager. This is typically of the format <instanceName>-wls-1.	ourserviceinstance-wls-1
   nmPort	Port number of the node manager. .	5556
   domainName	Name of the domain. You can find the domain name on the Oracle Java Cloud Service Instance Overview page.	OurServi_domain
   domainDir	Path to the domain. In Oracle Java Cloud Service, the domain directory is /u01/data/domains/<domainName>.	/u01/data/domains/OurServi_domain
   nmType	Use SSL for Java-based SSL implementation.	SSL

   For example:

   nmConnect ('weblogic','password','ourserviceinstance-wls-1','5556','OurServi_domain','/u01/data/domains/OurServi_domain','SSL')

7. Use the nmStart command to start the Administration Server:

   nmStart (server_name)

   For example:

   nmStart ('OurServi_adminserver')

8. Exit WLST:

   exit()

9. Exit the oracle session.

   exit

10. Exit the command window:

    exit

11. Access the Oracle Java Cloud Service console.
12. Click Manage this instance for the desired service instance, and then select Open WebLogic Server Administration Console.
13. When the console login page appears, enter the WebLogic Server administrator user name and password you provided when you created the service instance.
14. From the WebLogic Server Administration Console, under Domain Structure, expand Environment.
15. Click Servers.
16. On the Configuration page, check that the Administration Server state is RUNNING.

For more information about nmConnect parameters, see:

• For Oracle Fusion Middleware 12.2.1.4: nmConnect in WLST Command Reference for WebLogic Server

• For Oracle Fusion Middleware 12.2.1.3: nmConnect in WLST Command Reference for WebLogic Server

• For Oracle Fusion Middleware 11.1.1.7: nmConnect in WLST Scripting Tool Command Reference

Use the WebLogic Server Administration Console to Start Managed Servers

After the Administration Server is running in your Oracle Java Cloud Service instance, you can start the Managed Servers by using the WebLogic Server Administration Console.

1. Access the Oracle Java Cloud Service console.
2. Click Manage this instance for the desired service instance, and then select Open WebLogic Server Administration Console.
3. Enter the WebLogic Server administrator user name and password that you provided when you created the service instance.
4. Under Domain Structure, expand Environment.
5. Click Servers.
   On the Configuration page, notice that the Administration Server state is RUNNING, and the Managed Server state is SHUTDOWN.
6. Click the Control tab.
7. Click the check box to the left of each Managed Server name.
8. Click Start.
9. When prompted for confirmation, click Yes.
   The server state changes to STARTING.
10. Periodically click the Refresh icon until the server state changes to RUNNING.