Oracle® Identity Management Integration Guide
10g Release 2 (10.1.2) B14085-02 |
|
Previous |
Next |
This section tells you how to start, stop, and restart the Oracle directory integration and provisioning server. It contains these topics:
Starting the Oracle Directory Integration and Provisioning Server
Stopping the Oracle Directory Integration and Provisioning Server
Restarting the Oracle Directory Integration and Provisioning Server
Note: When the Oracle directory integration and provisioning server is invoked in the default mode, it supports only the Oracle Provisioning Service, and not the Oracle Directory Synchronization Service. |
Oracle Directory Integration and Provisioning can be installed as a component of Oracle Internet Directory or as a standalone installation. How you start the Oracle directory integration and provisioning server depends on whether you install Oracle Directory Integration and Provisioning as a component of Oracle Internet Directory as a standalone installation.
To start Oracle Directory Integration and Provisioning as a component of Oracle Internet Directory, you use the Oracle Internet Directory Monitor (oidmon
) and the Oracle Internet Directory Control Utility (oidctl
). You can start both utilities at the same time by using the Oracle Process Manager and Notification Server Control Utility (opmnctl
). When you install Oracle Directory Integration and Provisioning as a component of Oracle Internet Directory, an instance of the Oracle directory integration and provisioning server is started that only processes provisioning requests. To start an additional instance of Oracle directory integration and provisioning server that performs synchronization, you must use the Oracle Internet Directory Control Utility (oidctl
). The oidmon
, oidctl
, and opmnctl
utilities are documented in the Oracle Identity Management server administration tools chapter of the Oracle Identity Management User Reference.
To start a standalone installation of Oracle Directory Integration and Provisioning, use the Oracle Directory Integration Server Control Tool (odisrv
), which is also documented in the Oracle Identity Management server administration tools chapter of the Oracle Identity Management User Reference. In a standalone installation of Oracle Directory Integration and Provisioning, the Oracle directory integration and provisioning server instance starts by default if no other Oracle directory integration and provisioning server instance is running within the same Oracle Application Server infrastructure.
WARNING: If you attempt to manually stop then start the server within 30 seconds, the old server instance may not shut down before the new instance starts. This is because the Oracle Directory Integration and Provisioning server determines whether to shut down by polling the registration entry stored under |
How you stop the directory integration and provisioning server depends on the utility you used to start it. If you started the server with either the oidctl
or the opmnctl
utilities, then you must the oidctl
utility to stop it. If you used the odisrv
utility to start the server, you must use the stopodiserver.sh
command to stop it. You can also use opmnctl
command to stop all running Oracle Internet Directory instances on a particular node, including directory servers, directory replication server, and directory integration and provisioning server. The oidctl
, and opmnctl
, odisrv
, and stopodiserver.sh
utilities are documented in the Oracle Identity Management server administration tools chapter of the Oracle Identity Management User Reference.
To restart the Oracle directory integration and provisioning server, first stop the server using the procedures described in "Stopping the Oracle Directory Integration and Provisioning Server", wait 30 seconds, then start the server again using the procedures described in "Starting the Oracle Directory Integration and Provisioning Server". You need to wait 30 seconds because the Oracle Directory Integration and Provisioning server determines whether to shut down by polling the registration entry stored under cn=odisrv,cn=subregistrysubentry
at 30 second intervals. If you start the server before the next polling interval, the first instance of the server will not be stopped, resulting in two running instances.