A naming context (also known as a
directory suffix) is a DN that identifies the top
entry in a locally held
directory hierarchy.
A new naming context can be created using ODSM, the OUD gui admin console, as described in http://docs.oracle.com/cd/E29407_01/admin.111200/e22648/server_config.htm#CBDGCJGF
It can also be created using the dsconfig command lione as described below: Creation of a new naming context consists in 3 steps:
First create a Local Backend Workflow element (myNewDb in this exemple) , responsible for the naming context base dn, e.g o=example.
dsconfig create-workflow-element \
--set base-dn:o=example \
--set enabled:true \
--type db-local-backend \
--element-name myNewDb \
--hostname <your host> \
--port <admin port> \
--bindDN cn=Directory\ Manager \
--bindPasswordFile ****** \
--no-prompt
Second, create a Workflow element (workFlowForMyNewDb in this exemple) associated with the Local Backend Workflow element. WorkFlow elements are used
to route LDAP requests
to the appropriate database, based on the target base dn.
dsconfig create-workflow \
--set base-dn:o=example \
--set enabled:true \
--set workflow-element:myNewDb \
--type generic \
--workflow-name workFlowForMyNewDb \
--hostname <your host name> \
--port <admin port>\
--bindDN cn=Directory\ Manager \
--bindPasswordFile ****** \
--no-prompt
Then, the workflow element must be made visible outside of the
directory, i.e added
to the internal "routing table". This is done by adding the Workflow
to the appropriate Network Group. A Network group is used
to classify incoming client connections and route requests
to workflows.
dsconfig set-network-group-prop \
--group-name network-group \
--add workflow:workFlowForMyNewDb \
--hostname <your hostname> \
--port <admin port>\
--bindDN cn=Directory\ Manager \
--bindPasswordFile ****** \
--no-prompt
At that stage, it is possible
to import entries
to the new naming context o=example.
