How To Create An Instance Specific Configuration Entry In OID (Doc ID 2571508.1)

Last updated on DECEMBER 14, 2020

Applies to:

Goal

Oracle Internet Directory (OID) stores and utilizes runtime parameters such as the LDAP listen ports, TLS/SSL settings, OID process tuning parameters and more, in instance-specific configuration entries, multiple of which can be stored and referenced during process start. These are known as Fusion Middleware system components, or simply 'components' ('configsets' prior to 10.1.4.3.0). Installation creates the first instance-specific configuration containing default ports and other settings in the form of the 'oid1' component ('configset0' prior to 11g).

Whereas the existing components can be adjusted and modified, it can be advantageous to create additional components to tailor for a specific class of clients. Examples include configuring additional listen ports, segregating client traffic from applications traffic such as for OID Replication Server or Directory Integration Platform (DIP), or settings to require certificate based authentication on some connections.

The configuration entries are maintained in the subtree specified by the subConfigsubEntry attribute of the directory-specific entry (DSE), which itself resides in the associated directory information base (DIB) against which the servers are started. Starting with OID 10.1.4.3.0, configuration information for an OID instance resides in an instance-specific configuration entry, which has a DN of the form:

cn=componentname,cn=osdldapd,cn=subconfigsubentry

where componentname is the name of a Oracle Fusion Middleware system component of Type=OID, such as oid1 or oid2.

Prior to OID 10.1.4.3.0,  instance-specific configuration information is maintained in a Configuration Set entry, which has a DN of the form:

cn=configset0,cn=osdldapd,cn=subconfigsubentry

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.