Stop or Start WebLogic Servers

You can stop or start WebLogic Servers using WebLogic Scripting Tool (WLST) commands and the WebLogic Server Administration Console.

To stop the WebLogic servers:

To start the WebLogic servers:

Stop or Start the Managed Servers

You can stop or start the Managed Servers for an Oracle SOA Suite on Marketplace instance by using the WebLogic Server Administration Console for SOA Suite 12.2.1.4 or WebLogic Remote Console for SOA Suite 14.1.2.0.

To stop or start the Managed Servers:
  1. Open the management console for your Oracle SOA Suite release.
  2. Locate the servers in the console. In the WebLogic Server Administration Console, under Domain Structure, expand Environment, and then select Servers. In WebLogic Remote Console, use the equivalent server view.
  3. Note the state of the Administration Server and the Managed Servers.
  4. Select the server-control view.
  5. For each Managed Server, select the server and perform the required action.
    • To stop a server, select Shutdown, then select Force Shutdown Now or When Work Completes.
    • To start a server, select Start.
  6. Confirm the operation when prompted, then refresh the server view until the server state is SHUTDOWN or RUNNING, as applicable.

Stop or Start the Administration Server

You stop or start the Administration Server for an Oracle SOA Suite on Marketplace instance through the Node Manager by using WLST commands.

To stop or start the Administration Server:
  1. Use the ssh command to connect to the Administration Server VM (as the opc user):
    ssh -i private_key opc@AdminServerVM_IP_address
  2. Change to the oracle user:
    sudo su - oracle
  3. Check that the Node Manager is running:
    ps -ef | grep NodeManager
    You should receive messages showing that the Node Manager is running.
  4. Change the directory to the bin folder in DOMAIN_HOME.
    cd $DOMAIN_HOME/bin

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

  5. Set up the environment.
    . ./setDomainEnv.sh

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

  6. Start WLST:
    /u01/app/oracle/middleware/oracle_common/common/bin/wlst.sh

    Note:

    If you see exceptions while starting the command, ignore them and continue to next step.
  7. 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 instance.  
    password WebLogic Server password you specified when you created the 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, which is the name of the folder in /u01/data/domains/. OurServi_domain
    domainDir Path to the domain. 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','welcome','ourserviceinstance-wls-1','5556','OurServi_domain','/u01/data/domains/OurServi_domain','SSL')
  8. Stop or start the Administration Server:
    • To stop the Administration Server, follow the steps in Stop or Start the Managed Servers, selecting and shutting down the Administration Server. When you shut down the Administration Server, a message warns you that the browser session will end.
    • To start the Administration Server, use nmStart:
      nmStart ('server_name')

      For example:

      nmStart ('OurServi_adminserver')
  9. Exit WLST:
    exit()