|
Oracle® Identity Management User Reference
10g Release 2 (10.1.2) B15883-01 |
|
 Previous |
 Next |
|
Oracle® Identity Management User Reference
10g Release 2 (10.1.2) B15883-01 |
|
|
Previous |
Next |
The Oracle Directory Integration Server Control Tool (odisrv) is used to start an Oracle Directory Integration and Provisioning server in a client-only installation, where the Oracle Internet Directory Monitor (oidmon) and Control (oidctl) tools are not available, and if the Oracle Directory Integration and Provisioning server is not used for high-availability purposes.
In a typical Oracle Internet Directory installation you should use the Oracle Internet Directory Monitor and Control utilities to start and stop the server. Oracle Corporation recommends that you use these utilities if available. This way, if the Oracle Directory Integration and Provisioning server unexpectedly terminates, the Oracle Internet Directory Monitor utility automatically restarts it. See "oidmon" and "oidctl" for more information.
odisrv host=hostname port=port_number [config=configuration_set_number] instance=instance_number [debug=debug_level] [refresh=interval_between_refresh] [maxprofiles=number_of_profiles] [sslauth=ssl_mode]
host=hostname
Required. The host name of the Oracle Internet Directory server. If not specified, then the default of localhost is used.
port=port_number
Required. The port number used to connect to the Oracle Internet Directory server. If not specified, then the default of 389 is used.
config=configuration_set_number
Optional. The configuration set number to be used when starting the server.
instance=instance_number
Required. The instance number to assign to the Oracle Directory Integration and Provisioning server. This instance number must be unique. OID Monitor verifies that the instance number is not already associated with a currently running instance of this server.
debug=debug_level
Optional. If not specified the default of 0 (not enabled) is used. Debug levels are additive. Add the numbers representing the functions that you want to activate, and use the sum of those in the command-line option. For example, to trace search filter processing (512) and active connection management (256), enter 768 as the debug level (512 + 256 = 768). Debug levels are as follows:
1 — Heavy trace debugging
128 — Debug packet handling
256 — Connection management, related to network activities
512 — Search filter processing
1024 — Entry parsing
2048 — Configuration file processing
8192 — Access control list processing
491520 — Log of communication with the database
524288 — Schema related operations
4194304 — Replication specific operations
8388608 — Log of entries, operations and results for each connection
16777216 — Trace function call arguments
67108864 — Number and identity of clients connected to this server
117440511 — All possible operations and data
refresh=interval_between_refresh
The number of minutes between server refreshes for any changes in Oracle Directory Integration and Provisioning profiles. If not specified, the default of 2 is used.
maxprofiles=number_of_profiles
The maximum number of Oracle Directory Integration and Provisioning profiles that can be executed concurrently for this server instance.
sslauth=ssl_mode
The number of the corresponding SSL mode. If not specified, the default of 0 is used. The modes are as follows:
0 — SSL is not used.
1 — SSL is used for encryption only, not for authentication.
2 — SSL is used for one-way authentication. With this mode you must also specify the complete path and file name of the server's Oracle Wallet.
Using the odisrv tool, you can perform the following task:
The following example shows how to start an Oracle Directory Integration and Provisioning server in a client-only installation:
Example:
odisrv host=host.company.com port=389 config=3 instance=1 debug=256 refresh=2 maxprofiles=3
