2.1 Starting and Stopping Servers in Your Deployment

The Oracle Access Management Console is deployed on the WebLogic Administration Server (AdminServer) thus, Oracle Access Management Administrators can access it only when the AdminServer is running.

If the Oracle Access Management Console is protected by a WebGate, the OAM Server must also be running. And the Node Manager must be started before the other servers. The following sections have more details.

2.1.1 Starting Node Manager

You can use the Node Manager, a Java utility, to perform common operations tasks for a Managed Server, regardless of its location with respect to its Administration Server. Node Manager must run before you can start and stop the WebLogic AdminServer, or WebLogic managed servers hosting OAM Servers.

After installing and configuring Oracle Identity Manager, you need to configure the Node Manager for use with the WebLogic Administration Console (AdminServer) or Oracle Enterprise Manager Fusion Middleware Control. This configuration is done only once.

See "Configuring the Node Manager" in .

After you complete the configuration, you need to make sure that the Node Manager runs the startNodeManager.sh script. Oracle WebLogic Administration Server does not do this automatically.

$WLS_HOME/server/bin/startNodeManager.sh

See the Oracle WebLogic Server Administrator Guide.

To start Node Manager:

  1. Change to your $WLS_HOME/server/bin directory.
  2. Enable Start Scripts: Run setNMProps to start the stack and instruct Node Manager to enable the use of start scripts (StartScriptEnabled=true). 
    ./setNMProps.sh
  3. Start Node Manager. 
    ./startNodeManager.sh

2.1.2 Starting and Stopping WebLogic AdminServer

Starting the WebLogic AdminServer the first time can take 12-15 minutes or more. This process must not be interrupted or terminated as policy data might be corrupted.

The following procedure describes starting and stopping the WebLogic AdminServer using the scripts located in your $DOMAIN_HOME/bin directory.

  • Unix: startWebLogic.sh or stopWebLogic.sh

  • Windows: startWebLogic.cmd or stopWebLogic.cmd

WARNING:

If startWebLogic.cmd (Windows) or startWebLogic.sh (Linux) is stopped for any reason (whether accidently or because of a system crash or reboot), policy data might be corrupted. This would require removal and recreation of the domain and running the RCU again to recreate the OAM schema.

To start and stop WebLogic AdminServer:

  1. Navigate to your $DOMAIN_HOME/bin.
  2. Start AdminServer:

    • Unix: ./startWebLogic.sh

    • Windows: run startWebLogic.cmd

  3. Stop AdminServer:

    • Unix: ./stopWebLogic.sh

    • Windows: run stopWebLogic.cmd

2.1.3 Starting and Stopping Managed WebLogic Servers and Access Manager Servers

You can perform all start and stop operations for managed WebLogic Servers hosting Oracle Access Management Servers (OAM Servers) from either a command prompt, the Oracle WebLogic Server Administration Console, the OAM Policy Manager Console, or the Oracle Enterprise Manager Fusion Middleware Control.

When using the command line scripts (located in the $DOMAIN_HOME/bin directory), the Managed Server name and the AdminServer URL are required as input.

The Unix system scripts are startManagedWebLogic.sh and stopManagedWebLogic.sh, and the Windows system scripts are startManagedWebLogic.cmd and stopManagedWebLogic.cmd.

To start and stop Managed WebLogic servers and Access Manager servers:

  1. Navigate to $DOMAIN_HOME/bin.
  2. Start OAM Server:

    • Unix: ./startManagedWebLogic.sh MANAGED_SERVER_NAME ADMIN_SERVER_URL

    • Windows: run startManagedWebLogic.cmd MANAGED_SERVER_NAME ADMIN_SERVER_URL

    If the managed server is named oam_server1 and the AdminServer URL is http://examplewlsadminhost.example.com:7001, the start command run on a Unix system would be:

    startManagedWebLogic.sh oam_server1 http://examplewlsadminhost.example.com:7001
  3. Stop OAM Server:

    • Unix: ./stopManagedWebLogic.sh MANAGED_SERVER_NAME ADMIN_SERVER_URL

    • Windows: run stopManagedWebLogic.cmd MANAGED_SERVER_NAME ADMIN_SERVER_URL

    If the managed server is named oam_server1 and the AdminServer URL is http://examplewlsadminhost.example.com:7001, the stop command run on a Unix system would be:

    stopManagedWebLogic.sh oam_server1 http://examplewlsadminhost.example.com:7001