This section describes how to start, stop, and restart the various components of the Oracle Enterprise Deployment for Identity Management. The following topics are discussed:
Prior to starting or stopping the Oracle HTTP server, perform the following steps:
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.
Start the Oracle Web Tier by issuing the following command:
opmnctl startall
opmnctl stopall
opmnctl stoproc process-type=OHS
Start and stop Oracle Identity Manager and Oracle SOA Suite servers as described in the following sections:
To start the Oracle Identity Manager Managed Server(s), log in to the WebLogic console at: http://ADMIN.mycompany.com/console, then proceed as follows:
To stop the Oracle Identity Manager Managed Server(s), log in to the WebLogic console at: http://ADMIN.mycompany.com/oamconsole, and then proceed as follows:
Restart the server by following the Stop and Start procedures in the previous sections.
To start and stop all IDM components on a particular host in IDM provisioned environments, you can use the start/stop scripts as described in Starting and Stopping Servers in the Oracle Fusion Applications Installation Guide. Ensure the order is maintained when starting/stopping the servers in distributed nodes.
An IDM provisioned environment refers to the Type 1 environment and to the Type 2 only after migration or upgrade are run on it. For more information, see Upgrade Type I IDM Environments and Upgrade Type II IDM Environments.
Start and stop Oracle Identity Federation Managed Servers as described in the following sections:
To start the Oracle Identity Federation Managed Server(s), log in to the WebLogic console at: http://ADMIN.mycompany.com/oamconsole, and then proceed as follows:
To stop the Oracle Identity Federation Managed Server(s), log in to the WebLogic console at: http://ADMIN.mycompany.com/oamconsole, and then proceed as follows:
To start and stop the EMAgent, perform the following steps:
Start the EMAgent by executing the following command:
ORACLE_INSTANCE/bin/emctl start all
It is possible to verify that the instance started successfully by executing the following command:
ORACLE_INSTANCE/bin/emctl status -l
Stop the EMAgent by executing the following command:
ORACLE_INSTANCE/bin/emctl stop all
Start and stop Oracle Access Manager Managed Servers as described in the following sections:
Normally, Access Manager managed servers are started by using the WebLogic console. After enabling Single Sign-On for the administration consoles. However, there must be at least one Access Manager Server running in order to access a console. If no Access Manager server is running, the only way to start one is from the command line.
To start WLS_OAM1 manually, use the following command:
MSERVER_HOME/bin/startManagedWeblogic.sh WLS_OAM1 t3://ADMINVHN:7001
where 7001 is WLS_ADMIN_PORT in Section 8.3.
To start an Oracle Access Manager Managed Server when there is another already one running, log in to the WebLogic console at: http://ADMIN.mycompany.com/oamconsole
Then proceed as follows:
Select Environment - Servers from the Domain Structure menu.
Click the Control tab.
Select OAM Servers (WLS_OAM1 and/or WLS_OAM2).
Click the Start button.
Click Yes when asked to confirm the start of the server(s).
After enabling single sign-on for the administration consoles, ensure that at least one Oracle Access Manager Server is running to enable console access.
If the Oracle WebLogic console was used 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
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:
Select Environment - Servers from the Domain Structure menu.
Click the Control tab.
Select OAM Servers (WLS_OAM1 and/or WLS_OAM2).
Click the Shutdown button and select Force Shutdown now.
Click Yes when asked to confirm the shutdown of the server(s).
Start and stop the WebLogic Administration Server as described in the following sections:
Admin_user and Admin_Password are only used to authenticate connections between Node Manager and clients. These are independent from the server administration ID and password and are stored in the ASERVER_HOME/config/nodemanager/nm_password.properties file.
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 the WLST shell, execute
nmConnect('Admin_User','Admin_Password','ADMINHOST1','5556', 'IDMDomain','ASERVER_HOME')
nmStart('AdminServer')
Alternatively, it is possible to start the Administration server by using the command:
DOMAIN_HOME/bin/startWeblogic.sh
To stop the Administration Server, log in to the WebLogic console at: http://ADMIN.mycompany.com/oamconsole, and then proceed as follows:
Start and stop Oracle Internet Directory as described in the following sections:
Start system components such as Oracle Internet Directory by executing the following command:
ORACLE_INSTANCE/bin/opmnctl startall
To verify that the system components have started, execute the following command:
ORACLE_INSTANCE/bin/opmnctl status -l
Start and stop the Node Manager as described in the following sections:
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 following commands:
cd IAM_MW_HOME/wlserver_10.3/server/bin
./startNodeManager.sh
Set the environment variable JAVA_OPTIONS to -DDomainRegistrationEnabled=true and issue the following commands:
cd IAM_MW_HOME/wlserver_10.3/server/bin
./startNodeManager.sh
It is important to set -DDomainRegistrationEnabled=true whenever starting a Node Manager that manages the Administration Server.