You might need to proceed with LDAP server configuration, even though
the server is already configured for WebSphere/390, for any of the following
reasons:
- The security configuration needs changing to cope with the CICS regions
being introduced. See The LDAP namespace structure and Security considerations for
further information about the LDAP structure and security issues.
- CICS needs to run in a separate domain from WebSphere.
If you are building a new, separate, domain, WebSphere/390 and CICS will
not easily be able to locate each other's enterprise beans. However, if
you just intend to build a new domain the only configuration steps you need
to execute are Step 4. “Build the legacyRoot node” and Step 5. “Apply security at CICS region level”.
- CICS needs to run in an entirely different system name space structure
on the LDAP server. That is, CICS needs to have a containerdn that
points to somewhere other than the existing namespace root location on the
server. In this case, start the configuration procedure at Step 2. “Add a new suffix”. In
this case, it is not possible for CICS and WebSphere/390 systems working with
the differing containerdn settings to locate each other's Enterprise Beans.