If the nameserver that you have chosen for use by CICS® has already been configured for WebSphere/390, there is likely to be very little configuration needed to enable CICS to use it.
Correct operation of the EJB support in CICS requires the chosen LDAP namespace to be configured with a WebSphere System Namespace - the publish and retract mechanisms of CICS both attempt to operate within a System Namespace structure. However, once inside an EJB method or if executing a regular Java™ transaction in CICS, you can communicate with any LDAP namespace regardless of whether it supports a System Name Space.
When you use an LDAP server that is not configured with a WebSphere System Namespace, use an alternative directory service, such as the SUN LDAP service supplied as part of the IBM® Developer Kit for the Java Platform 1.4.2 base, rather than the WebSphere context factory supplied with CICS. See SUN LDAP Context Factory for details of using the SUN LDAP factory.
An understanding of the WebSphere naming structure that exists on the LDAP server (see The LDAP namespace structure) makes it easier for you or your LDAP administrator to determine suitable values for the six key properties a CICS region needs to know: These are described in the CICS System Definition Guide. The three security properties are only necessary if the LDAP namespace is setup in a secure manner. On some LDAP servers it may be the case that all users have write access and neither the principal or credentials properties need to be set for the CICS region.
If the structure laid out in the namespace by WebSphere is suitable for your needs, no further configuration is necessary.
The values for nameserver, containerdn and noderootrdn can be obtained by understanding the System Name Space structure and observing the structure in place on your chosen LDAP server, the final part of this section discusses how to determine the property values if you are browsing an existing namespace.