E Stopping and Starting Identity Management Related Servers

This appendix describes how to start, stop and restart the various components of the Oracle Enterprise Deployment for Identity Management.

This appendix contains the following topics.

• Section E.1, "Starting, Stopping, and Restarting Oracle HTTP Server"

• Section E.2, "Starting, Stopping, and Restarting Oracle Identity Manager"

• Section E.3, "Starting and Stopping Oracle Identity Federation Managed Servers"

• Section E.4, "Starting, Stopping, and Restarting Oracle Access Manager Managed Servers"

• Section E.5, "Starting, Stopping, and Restarting WebLogic Administration Server"

• Section E.6, "Starting and Stopping Oracle Virtual Directory"

• Section E.7, "Starting and Stopping Oracle Internet Directory"

• Section E.8, "Starting and Stopping Node Manager"

E.1 Starting, Stopping, and Restarting Oracle HTTP Server

Prior to starting/stopping the Oracle HTTP server:

• Set ORACLE_INSTANCE to WEB_ORACLE_INSTANCE.

• Set ORACLE_HOME to WEB_ORACLE_HOME.

• Ensure that the ORACLE_HOME/opmn/bin appears in the PATH.

E.1.1 Starting Oracle HTTP Server

Start the Oracle Web Tier by issuing the command:

opmnctl startall

E.1.2 Stopping Oracle HTTP Server

Stop the Web Tier by issuing the command

opmnctl stopall 

to stop the entire Web Tier or

opmnctl stoproc process-type=OHS  

to stop Oracle HTTP Server only.

E.1.3 Restarting Oracle HTTP Server

You can restart the Web Tier by issuing a Stop followed by a Start as described in the previous sections.

To restart the Oracle HTTP server only, use the following command.

opmnctl restartproc process-type=OHS

E.2 Starting, Stopping, and Restarting Oracle Identity Manager

Start and stop Oracle Identity Manager and Oracle SOA Suite servers as follows:

E.2.1 Starting Oracle Identity Manager

To start the Oracle Identity Manager Managed Server(s), log in to the WebLogic console at: http://ADMIN.mycompany.com/oamconsole

Then proceed as follows:

1. Select Environment - Servers from the Domain Structure menu.

2. Click the Control tab.

3. Select SOA Servers (WLS_SOA1 and/or WLS_SOA2).

   Note:

   You can start the Oracle Identity Manager and Oracle SOA Suite servers independently of each other. There is no dependency in their start order. However, the SOA server must be up and running for all of the Oracle Identity Manager functionality to be available.

4. Click the Start button.

5. Click Yes when asked to confirm that you want to start the server(s).

6. After WLS_SOA1 and/or WLS_SOA2 have started, select WLS_OIM1 and/or WLS_OIM2

7. Click Start.

8. Click Yes when asked to confirm that you want to start the server(s).

E.2.2 Stopping Oracle Identity Manager

To stop the Oracle Identity Manager Managed Server(s), log in to the WebLogic console at: http://ADMIN.mycompany.com/oamconsole

Then proceed as follows:

1. Select Environment - Servers from the Domain Structure menu.

2. Click the Control tab.

3. Select OIM Servers (WLS_OIM1 and/or WLS_OIM2) and (WLS_SOA1 and/or WLS_SOA2).

4. Click the Shutdown button and select Force Shutdown now.

5. Click Yes when asked to confirm that you want to shutdown the server(s).

E.2.3 Restarting Oracle Identity Manager

Restart the server by following the Stop and Start procedures in the previous sections.

E.3 Starting and Stopping Oracle Identity Federation Managed Servers

Start and stop Oracle Identity Federation Managed Servers as follows:

E.3.1 Starting Oracle Identity Federation

To start the Oracle Identity Federation Managed Server(s), log in to the WebLogic console at: http://ADMIN.mycompany.com/oamconsole

Then proceed as follows:

1. Select Environment - Servers from the Domain Structure menu.

2. Click the Control tab.

3. Select OIF Servers (WLS_OIF1 and/or WLS_OIF2).

4. Click Start.

5. Click Yes when asked to confirm that you want to start the server(s).

E.3.2 Stopping Oracle Identity Federation

To stop the Oracle Identity Federation Managed Server(s), log in to the WebLogic console at: http://ADMIN.mycompany.com/oamconsole

Then proceed as follows:

1. Select Environment - Servers from the Domain Structure menu.

2. Click the Control tab.

3. Select OIF Servers (WLS_OIF1 and/or WLS_OIF2).

4. Click Shutdown and select Force Shutdown now.

5. Click Yes when asked to confirm that you want to shut down the server(s).

E.3.3 Restarting Oracle Identity Federation

Restart the server by following the previous Stop and Start procedures.

E.3.4 Starting the EMAgent

Start the EMAgent by executing the following command:

ORACLE_INSTANCE/bin/opmnctl startall

You can verify that the instance started successfully by executing:

ORACLE_INSTANCE/bin/opmnctl status -l

E.3.5 Stopping the Oracle Identity Federation Instances and EMAgent

Stop the Oracle Identity Federation Instance and EMAgent by executing the following command:

OIF_ORACLE_INSTANCE/bin/opmnctl stopall 

E.4 Starting, Stopping, and Restarting Oracle Access Manager Managed Servers

Start and stop Oracle Access Manager Managed Servers as follows:

E.4.1 Starting an Access Manager Managed Server When None is Running

Normally, you start Access Manager managed servers by using the WebLogic console. After you have enabled Single Sign-On for the administration consoles, however, you must have at least one Access Manager Server running in order to access a console. If no Access Manager server is running, the only way you can start one is from the command line.

To start WLS_OAM1 manually, use the command:

MSERVER_HOME/bin/startManagedWeblogic.sh WLS_OAM1 t3://ADMINVHN:7001

where 7001 is WLS_ADMIN_PORT in Section A.3.

E.4.2 Starting an Oracle Access Manager Managed Server When Another is Running

To start an Oracle Access Manager Managed Server when you already have another one running, log in to the WebLogic console at: http://ADMIN.mycompany.com/oamconsole

Then proceed as follows:

1. Select Environment - Servers from the Domain Structure menu.

2. Click the Control tab.

3. Select OAM Servers (WLS_OAM1 and/or WLS_OAM2).

4. Click the Start button.

5. Click Yes when asked to confirm that you want to start the server(s).

   Note:

   After you have enabled single sign-on for the administration consoles, ensure that at least one Oracle Access Manager Server is running to enable console access.

   If you have used the Oracle WebLogic console to shut down all of the Oracle Access Manager Managed Servers, then restart one of those Managed Servers manually before using the console again.

   To start WLS_OAM1 manually, use the command:

   MSERVER_HOME/bin/startManagedWeblogic.sh WLS_OAM1 t3://ADMINVHN:7001
   

E.4.3 Stopping Oracle Access Manager Managed Servers

To stop the Oracle Access Manager Managed Server(s), log in to the WebLogic console at: http://ADMIN.mycompany.com/oamconsole

Then proceed as follows:

1. Select Environment - Servers from the Domain Structure menu.

2. Click the Control tab.

3. Select OAM Servers (WLS_OAM1 and/or WLS_OAM2).

4. Click the Shutdown button and select Force Shutdown now.

5. Click Yes when asked to confirm that you want to shut down the server(s).

E.4.4 Restarting Oracle Access Manager Managed Servers

Restart the server by following the Stop and Start procedures in the previous sections.

E.5 Starting, Stopping, and Restarting WebLogic Administration Server

Start and stop the WebLogic Administration Server as described in the following sections.

Note:

Admin_user and Admin_Password are only used to authenticate connections between Node Manager and clients. They are independent from the server administration ID and password and are stored in the ASERVER_HOME/config/nodemanager/nm_password.properties file.

E.5.1 Starting WebLogic Administration Server

The recommended way to start the Administration server is to use WLST and connect to Node Manager:

cd ORACLE_COMMON_HOME/common/bin 
./wlst.sh

Once in WLST shell, execute

nmConnect('Admin_User','Admin_Password','ADMINHOST1','5556', 'IDMDomain','ASERVER_HOME')
nmStart('AdminServer')

Alternatively, you can start the Administration server by using the command:

DOMAIN_HOME/bin/startWeblogic.sh

E.5.2 Stopping WebLogic Administration Server

To stop the Administration Server, log in to the WebLogic console at: http://ADMIN.mycompany.com/oamconsole

Then proceed as follows:

1. Select Environment - Servers from the Domain Structure menu.

2. Click the Control tab.

3. Select AdminServer(admin).

4. Click Shutdown and select Force Shutdown now.

5. Click Yes when asked to confirm that you want to shut down the Administration Server.

E.5.3 Restarting WebLogic Administration Server

Restart the server by following the Stop and Start procedures in the previous sections.

E.6 Starting and Stopping Oracle Virtual Directory

Start and stop Oracle Virtual Directory as follows.

E.6.1 Starting Oracle Virtual Directory

Start system components such as Oracle Virtual Directory by typing:

ORACLE_INSTANCE/bin/opmnctl startall

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

ORACLE_INSTANCE/bin/opmnctl status -l

E.6.2 Stopping Oracle Virtual Directory

Stop system components such as Oracle Virtual Directory by executing the following command:

ORACLE_INSTANCE/bin/opmnctl stopall 

E.7 Starting and Stopping Oracle Internet Directory

Start and stop Oracle Internet Directory as follows.

E.7.1 Starting Oracle Internet Directory

Start system components such as Oracle Internet Directory by typing

ORACLE_INSTANCE/bin/opmnctl startall

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

ORACLE_INSTANCE/bin/opmnctl status -l

E.7.2 Stopping Oracle Internet Directory

Stop system components such as Oracle Internet Directory by executing the following command:

ORACLE_INSTANCE/bin/opmnctl stopall 

E.8 Starting and Stopping Node Manager

Start and stop the Node Manager as follows:

E.8.1 Starting Node Manager

If the Node Manager being started is the one that controls the Administration Server (IDMHOST1 or IDMHOST2), then prior to starting the Node Manager, set JAVA_OPTIONS to -DDomainRegistrationEnabled=true and issue the commands:

cd IAM_MW_HOME/wlserver_10.3/server/bin
./startNodeManager.sh

E.8.2 Stopping Node Manager

To stop Node Manager, kill the process started in the previous section.

E.8.3 Starting Node Manager for an Administration Server

Set the environment variable JAVA_OPTIONS to -DDomainRegistrationEnabled=true and issue the commands:

cd IAM_MW_HOME/wlserver_10.3/server/bin
./startNodeManager.sh

Note:

It is important to set -DDomainRegistrationEnabled=true whenever you start a Node Manager that manages the Administration Server.