Skip Headers
Oracle® Fusion Middleware Administrator's Guide for Oracle Directory Integration Platform
11g Release 1 (11.1.1)

Part Number E10031-06
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

D Starting and Stopping the Oracle Stack

You must start and stop the components of the Oracle stack in a specific order, which is described in this appendix.

D.1 Starting the Stack

Start the stack components in the following order.

  1. Start the Oracle Database

    1. In the Database ORACLE_HOME, set the ORACLE_SID, ORACLE_HOME and PATH environment variables to the appropriate values.

    2. Start the listener.

      ORACLE_HOME/bin/lsnrctl start 
      
    3. Start the database.

      ORACLE_HOME/bin/sqlplus "/as sysdba"
      startup
      
  2. Start the Oracle WebLogic Administration Server.

    Note:

    If you start the Oracle WebLogic Administration Server from the command line, it runs in the foreground and prints output to the screen.

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

    When executing these scripts:

    • The default value for DOMAIN_NAME is IDMDomain

    • SERVER_NAME represents the name of the Oracle WebLogic Managed Server. Its default value is wls_ods1.

    • 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.

  3. Ensure that the Node Manager is running. Normally, the Oracle WebLogic Administration Server starts the Node Manager. If, for some reason, the Node Manager is not running, start it.

    MW_HOME/user_projects/domains/DOMAIN_NAME/bin/startNodeManager.sh 
    
  4. Start system components, such as Oracle Internet Directory.

    ORACLE_INSTANCE/bin/opmnctl startall
    

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

    ORACLE_INSTANCE/bin/opmnctl status -l
    
  5. Start WebLogic managed components, such as Oracle Directory Integration Platform and Oracle Directory Services Manager.

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

    To start managed components in the background, you can use the Oracle WebLogic Administration Console. See Oracle Fusion Middleware Introduction to Oracle WebLogic Server for more information.

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

D.2 Stopping the Stack

You can stop the Administration Server and all the managed servers by using Oracle WebLogic Administration Console. See Oracle Fusion Middleware Introduction to Oracle WebLogic Server for more information.

To stop the stack components from the command line, issue the commands in the following order.

  1. Stop WebLogic managed components, such as Oracle Directory Integration Platform and Oracle Directory Services Manager.

    MW_HOME/user_projects/domains/DOMAIN_NAME/bin/stopManagedWebLogic.sh \
    {SERVER_NAME} {ADMIN_URL} {USER_NAME} {PASSWORD}
    
  2. Stop system components, such as Oracle Internet Directory.

    ORACLE_INSTANCE/bin/opmnctl stopall 
    
  3. Stop the WebLogic Administration Server.

    MW_HOME/user_projects/domains/DOMAIN_NAME/bin/stopWebLogic.sh
    
  4. If you want to stop the Node Manager, you can use the kill command.

    kill -9 pid
    
  5. Stop the Oracle Database.

    1. In the Database ORACLE_HOME, set the ORACLE_SID, ORACLE_HOME, and PATH environment variables to the appropriate values.

    2. Stop the database.

      ORACLE_HOME/bin/sqlplus "/as sysdba"
      shutdown immediate 
      
    3. Stop the listener.

      ORACLE_HOME/bin/lsnrctl stop