Skip Headers
Oracle® Fusion Middleware Quick Installation Guide for Oracle Identity and Access Management
11g Release 2 (11.1.2)

Part Number E27794-02
Go to Documentation Home
Home
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

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

B Starting or Stopping the Oracle Stack

You must start or stop the components of the Oracle stack in a specific order. Oracle stack refers to Administration Server for the WebLogic Server domain, the system components that are managed by Oracle Process Manager and Notification Server, and the Managed Servers, which are controlled by Node Manager.

This appendix describes that order and contains the following topics:

Note:

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

B.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 the 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
    

    domain_name is the name of the domain that you entered on the Specify Domain Name and Location Screen in the Configuration Wizard.

  2. Configure Node Manager to start the Managed Servers. If a Managed Server contains other Oracle Fusion Middleware products, such as Oracle SOA Suite, Oracle WebCenter, or Oracle JRF, the Managed Servers environment must be configured to set the correct classpath and parameters. This environment information is provided through the start scripts, such as startWebLogic and setDomainEnv, which are located in the domain directory.

    If the Managed Servers are started by Node Manager (as is the case when the servers are started by the Oracle WebLogic Server Administration Console or Fusion Middleware Control), Node Manager must be instructed to use these start scripts so that the server environments are correctly configured. Specifically, Node Manager must be started with the property StartScriptEnabled=true.

    There are several ways to ensure that Node Manager starts with this property enabled. As a convenience, Oracle Fusion Middleware provides the following script, which adds the property StartScriptEnabled=true to the nodemanager.properties file:

    On UNIX:

    1. Run the following script to add the property StartScriptEnabled=true to the nodemanager.properties file:

      ORACLE_COMMON_HOME/common/bin/setNMProps.sh

    2. Start the Node Manager by executing the following command:

      MW_HOME/WLS_HOME/server/bin/startNodeManager.sh

    On Windows:

    1. Run the following script to add the property StartScriptEnabled=true to the nodemanager.properties file:

      ORACLE_COMMON_HOME\common\bin\setNMProps.cmd

    2. Start the Node Manager by executing the following command:

      MW_HOME\WLS_HOME\server\bin\startNodeManager.cmd

    Note:

    When you start Node Manager, it reads the nodemanager.properties file with the StartScriptEnabled=true property, and uses the start scripts when it subsequently starts Managed Servers. Note that you need to run the setNMProps script only once.

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

    Note:

    If the Node Manager is not running, you can 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 the Administration Server is using a non-default port, or resides on a different host than the Managed Servers (in a distributed environment), you must also specify the URL to access the 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 -Dweblogic.system.StoreBootIdentity=true 
    

    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 -Dweblogic.system.StoreBootIdentity=true 
    

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.

B.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 Access Management, 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 the Oracle WebLogic Administration Server by executing the following command:

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

    kill -9 PID
    

B.3 Restarting Servers

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