Shutting Down and Starting Server Processes

You can shut down and start WebLogic Servers (including Administration Servers) employed in your Oracle Java Cloud Service instance.

The topics in this section describe how to shut down and start server processes only. The server VMs remain running. For information about how to shut down Managed Server and Administration Server VMs, see Stopping and Starting an Oracle Java Cloud Service Instance and Individual Nodes.

Using the WebLogic Server Administration Console to Shut Down Servers Without Stopping VMs

Use the WebLogic Server Administration Console to shut down servers employed by your Oracle Java Cloud Service instance: the Administration server and one or more managed servers. Do not attempt to shut down servers through the Oracle Traffic Director.

This topic only presents how to shut down servers without stopping the VMs on which the servers are running. This procedure enables you to shut down servers for any reason, such as periodic shutdown, or to address CPU and memory resource contention. This approach shuts down the server processes only, leaving other processes you might have running on the nodes to continue to run. For more information about stopping server nodes, see Stopping and Starting an Oracle Java Cloud Service Instance and Individual VMs.

To use the WebLogic Server Console to shut down servers:
  1. Navigate to the Oracle Java Cloud Service Console.
  2. Click menu icon for the desired service instance and select Open WebLogic Server Console.
  3. When the console login page appears, enter the WebLogic username and password you provided when you created the service instance.
  4. On the Administration Console, under Domain Structure, expand Environment.
  5. Select Servers.
  6. On the Configuration tab of the Summary of Servers page, notice that the state of the Administration server and managed servers is RUNNING.
  7. Click the Control tab.
  8. Click the check box to the left of each server.
  9. Select Shutdown, then Force Shutdown Now or When Work Completes.
    The servers are shut down. A Server Shutdown message appears. The message you receive will be different based on whether you are shutting down the administration server or the managed servers. When you shut down the administration server, the message warns you that the browser session will end.
You have now shut down the servers.

Using WLST Commands to Start the Administration Server

You start the Administration Server through the Node Manager by using WLST commands.

Prior to running WLST, identify the public IP address of the Administration Server VM and connect to it with SSH, as described in Accessing a VM Through a Secure Shell (SSH).

  1. After connecting to the VM, switch to the oracle user:
    sudo su - oracle
  2. Check to see 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 where environment setup is located:
    cd /u01/data/domains/domain_name/bin

    For example:

    cd /u01/data/domains/OurServi_domain/bin
  4. Set up the environment.
    . ./setDomainEnv.sh
  5. Start WLST:
    java weblogic.WLST
  6. To connect to the Node Manager, use the WLST nmConnect command:
    nmConnect (username,password,host,nmPort,domainName,domainDir,nmType)
    Parameter Description Example
    username Username you specified when you created the service instance. weblogic
    password Password you specified when you created the service instance. welcome1
    host The host name of the Node Manager. Instance name in all lower case, followed by a dash, followed by wls, followed by a dash, followed by 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','welcome1','ourserviceinstance-wls-1','5556','OurServi_domain','/u01/data/domains/OurServi_domain','SSL')
    For more information about nmConnect parameters, see:
    • For Oracle Fusion Middleware 12.2.1: nmConnect in WLST Command Reference for WebLogic Server

    • For Oracle Fusion Middleware 12.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

  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. Open a browser window.
  12. Navigate to the Oracle Java Cloud Service Console.
  13. Click menu icon for the desired service instance and select Open WebLogic Server Console.
  14. When the console login page appears, enter the WebLogic username and password you provided when you created the service instance.
    If the Administration Console opens, you know that the Administration Server is running. We will also verify that it is running by using the Administration Console.
  15. On the Administration Console, under Domain Structure, expand Environment.
  16. Select Servers.
  17. On the Configuration page, check that the Administration Server state is RUNNING.
You have now started the Administration Server through the Node Manager by using WLST commands.

Using the WebLogic Server Administration Console to Start Managed Servers

After you have started the Administration Server through the Node Manager by using WLST commands, you can start the Managed Servers through theWebLogic Server Administration Console.

To start Managed Servers:
  1. Navigate to the Oracle Java Cloud Service Console.
  2. Click menu icon for the desired service instance and select Open WebLogic Server Console.
  3. When the console login page appears, enter the WebLogic username and password you provided when you created the service instance.
  4. Under Domain Structure, expand Environment.
  5. Select Servers.
  6. On the Configuration page, notice that the Administration Server state is RUNNING, and the Managed Server state is SHUTDOWN.
  7. Select the Control tab.
  8. Click the check box to the left of each Managed Server name.
  9. Click Start.
  10. On the Server Life Cycle Assistant, click Yes.
    The server state changes to STARTING.
  11. Click the Refresh icon.
    The server state changes to RUNNING.
You have now started the Managed Servers.