B Starting and Stopping the Oracle Stack

You must start and stop the components of the Oracle stack in a specific order.

This appendix describes that order and contains the following topics:

Note:

When executing the startManagedWebLogic and stopManagedWebLogic scripts described in the following topics:

  • The default value for DOMAIN_NAME is IDMDomain.

  • SERVER_NAME represents the name of the WebLogic Managed Server. The default value for the Oracle Directory Integration Platform and Oracle Directory Services Manager WebLogic Managed Server is wls_ods1. The default value for the Oracle Identity Federation WebLogic Managed Server is wls_oif1.

  • You will be prompted for values for USER_NAME and PASSWORD if you do not provide them as options when you execute the script.

  • The value for ADMIN_URL will be inherited if you do not provide it as an option when you execute the script.

B.1 Starting the Stack

Start the stack components in the following order:

Note:

You must start the Node Manager, the WebLogic Administration Server, and the Managed Servers with Java Secure Socket Extension (JSSE) enabled if you have applied the following Oracle WebLogic Server patches to your Middleware home:

  • 13964737 (YVDZ)

  • 14174803 (IMWL)

These patches are available from My Oracle Support.

For information on how to start the Node Manager with JSSE enabled, see the "Set the Node Manager Environment Variables" topic in the Node Manager Administrator's Guide for Oracle WebLogic Server.

After starting Node Manager with JSSE enabled, you must start the Administration Server and Managed Servers with JSSE enabled. For more information, see the "Using the JSSE-Enabled SSL Implementation" topic in Securing Oracle WebLogic Server.

  1. Start the WebLogic Administration Server by executing the following command:

    MW_HOME/user_projects/domains/DOMAIN_NAME/bin/startWebLogic.sh

  2. Ensure that the Node Manager is running. Oracle WebLogic Administration Server does not do this automatically. If the Node Manager is not running, start the Node Manager by executing the following command:

    WLS_HOME/server/bin/startNodeManager.sh

  3. Start system components, such as Oracle Internet Directory and Oracle Virtual Directory, by executing the following command:

    ORACLE_INSTANCE/bin/opmnctl startall

    You can verify that the system components have started by executing the following command:

    ORACLE_INSTANCE/bin/opmnctl status -l

  4. Start WebLogic managed components, such as Oracle Directory Integration Platform, Oracle Identity Federation, and Oracle Directory Services Manager, by executing the following command:

    MW_HOME/user_projects/domains/DOMAIN_NAME/bin/startManagedWebLogic.sh\
SERVER_NAME {ADMIN_URL}

    Note:

    You can view the status of WebLogic managed components with Fusion Middleware Control.

B.2 Stopping the Stack

Stop the stack components in the following order:

  1. Stop WebLogic managed components by executing the following command:

    MW_HOME/user_projects/domains/DOMAIN_NAME/bin/stopManagedWebLogic.sh \
{SERVER_NAME} {ADMIN_URL} {USER_NAME} {PASSWORD}

  2. Stop the WebLogic Administration Server by executing the following command:

    MW_HOME/user_projects/domains/DOMAIN_NAME/bin/stopWebLogic.sh

  3. Stop system components, such as Oracle Internet Directory and Oracle Virtual Directory, by executing the following command:

    ORACLE_INSTANCE/bin/opmnctl stopall

  4. If you want to stop the Node Manager, you can use the kill command:

    kill -9 PID