Oracle® Fusion Applications Upgrade Guide 11g Release 7 (11.1.7) Part Number E35833-18 |
|
|
PDF · Mobi · ePub |
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"
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
.
Start the Oracle Web Tier by issuing the command:
opmnctl startall
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.
Start and stop Oracle Identity Manager and Oracle SOA Suite servers as follows:
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:
Select Environment - Servers from the Domain Structure menu.
Click the Control tab.
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.
Click the Start button.
Click Yes when asked to confirm that you want to start the server(s).
After WLS_SOA1 and/or WLS_SOA2 have started, select WLS_OIM1 and/or WLS_OIM2
Click Start.
Click Yes when asked to confirm that you want to start the server(s).
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:
Select Environment - Servers from the Domain Structure menu.
Click the Control tab.
Select OIM Servers (WLS_OIM1 and/or WLS_OIM2) and (WLS_SOA1 and/or WLS_SOA2).
Click the Shutdown button and select Force Shutdown now.
Click Yes when asked to confirm that you want to shutdown the server(s).
Start and stop Oracle Identity Federation Managed Servers as follows:
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:
Select Environment - Servers from the Domain Structure menu.
Click the Control tab.
Select OIF Servers (WLS_OIF1 and/or WLS_OIF2).
Click Start.
Click Yes when asked to confirm that you want to start the server(s).
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:
Select Environment - Servers from the Domain Structure menu.
Click the Control tab.
Select OIF Servers (WLS_OIF1 and/or WLS_OIF2).
Click Shutdown and select Force Shutdown now.
Click Yes when asked to confirm that you want to shut down the server(s).
Restart the server by following the previous Stop and Start procedures.
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
Start and stop Oracle Access Manager Managed Servers as follows:
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.
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:
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 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
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 that you want to shut down the server(s).
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.
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
To stop the Administration Server, 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 AdminServer(admin).
Click Shutdown and select Force Shutdown now.
Click Yes when asked to confirm that you want to shut down the Administration Server.
Start and stop Oracle Virtual Directory as follows.
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
Start and stop Oracle Internet Directory as follows.
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
Start and stop the Node Manager as follows:
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
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.