Skip Headers
Oracle® Fusion Middleware Installation Guide for Oracle Identity Management
11g Release 1 (11.1.1)

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

Go to previous page
Previous
Go to next page
Next
View PDF

E Starting or Stopping the Oracle Stack

You must start or 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:

E.1 Starting the Stack

After completing the installation and domain configuration, you must start the Administration Server and various Managed Servers to get your deployments up and running:

  1. To start the Administration Server, run the startWebLogic.sh (on UNIX operating systems) or startWebLogic.cmd (on Windows operating systems) script in the directory where you created your new domain.

    On UNIX systems:

    MW_HOME/user_projects/domains/domain_name/startWebLogic.sh
    

    On Windows systems:

    MW_HOME\user_projects\domains\domain_name\startWebLogic.cmd
    

    You entered the domain name and location on the Specify Domain Name and Location Screen in the Configuration Wizard.

  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. To start the Managed Servers, run the startManagedWebLogic.sh (on UNIX operating systems) or startManagedWebLogic.cmd (on Windows operating systems) script in the bin directory inside the directory where you created your domain. You must start these Managed Servers from the command line.

    This command also requires that you specify a server name. You must start the servers you created when configuring the domain, as shown in the following example:

    • oam_server1 (Oracle Access Manager Server)

    • oim_server1 (Oracle Identity Manager Server)

    For example, to start Oracle Access Manager Server on a UNIX system:

    MW_HOME/user_projects/domains/domain_name/bin/startManagedWebLogic.sh oam_server1
    

    On Windows systems:

    MW_HOME\user_projects\domains\domain_name\bin\startManagedWebLogic.cmd oam_server1 
    

    Before the Managed Server is started, you are prompted for the WebLogic Server user name and password. These were provided on the Configure Administrator Username and Password Screen in the Configuration Wizard.

    If your Administration Server is using a non-default port, or resides on a different host than your Managed Servers (in a distributed environment), you must also specify the URL to access your Administration Server.

    On UNIX systems:

    MW_HOME/user_projects/domains/domain_name/bin/startManagedWebLogic.sh oam_server1 http://host:admin_server_port
    

    On Windows systems:

    MW_HOME\user_projects\domains\domain_name\bin\startManagedWebLogic.cmd oam_server1 http://host:admin_server_port
    

    Instead of being prompted for the Administration Server user name and password, you can also specify them directly from the command lime.

    On UNIX systems:

    MW_HOME/user_projects/domains/domain_name/bin/startManagedWebLogic.sh oam_server1 http://host:admin_server_port -Dweblogic.management.username=user_name -Dweblogic.management.password=password
    

    On Windows systems:

    MW_HOME\user_projects\domains\domain_name\bin\startManagedWebLogic.cmd oam_server1 http://host:admin_server_port -Dweblogic.management.username=user_name -Dweblogic.management.password=password
    

Note:

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

If you do not know the names of the Managed Servers that should be started, you can view the contents of the following file on UNIX systems:

MW_HOME/user_projects/domains/domain_name/startManagedWebLogic_readme.txt

On Windows systems:

MW_HOME\user_projects\domains\domain_name\startManagedWebLogic_readme.txt

Or, you can access the Administration Server console at the following URL:

http://host:admin_server_port/console

Supply the user name and password that you specified on the Configure Administrator Username and Password Screen of the Configuration Wizard. Then, navigate to Environment > Servers to see the names of your Managed Servers.

E.2 Stopping the Stack

You can stop the Oracle WebLogic 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, perform the following steps:

  1. Stop WebLogic managed components, such as Oracle Directory Integration Platform, Oracle Identity Federation, Oracle Directory Services Manager, Oracle Access Manager, Oracle Identity Manager, and Oracle Adaptive Access Manager, by executing the following command:

    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 and Oracle Virtual Directory, by executing the following command:

    ORACLE_INSTANCE/bin/opmnctl stopall 
    
  3. Stop the Oracle WebLogic Administration Server by executing the following command:

    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
    

E.3 Restarting Servers

To restart the Administration Server or Managed Servers, you must stop the running Administration Server or Managed Servers first before starting them again. For more information, see Stopping the Stack and Starting the Stack.