Domains

A domain contains a number of servers. In WebSphere Application Server for z/OS, each server has a node below legacyRoot, for example a server called BBOSV1 would have a name ibm-wsnName=BBOSV1,ibm-wsnName=PLEX2 relative to the legacy root, and the objects it publishes would be below this node.

When CICS is configured to use the same LDAP server as WebSphere, each CICS CorbaServer has a node directly below legacyRoot. So if a CorbaServer has a JNDI prefix of CICS1, there will be a node ibm-wsnName=CICS1 relative to the legacy root, and CICS publishes the CorbaServer's objects below this node. When a new InitialContext is created in WebSphere Application Server for z/OS, or in CICS configured as above, the InitialContext will be based on the legacyRoot node. This makes it easy for enterprise beans in CICS to look up objects published by WebSphere, and for enterprise beans or servlets in WebSphere to look up objects published by CICS.

Note: Any JNDI sub-context below a CICS region's initial JNDI context (which is typically the legacyRoot node) may be transient. This is the case if CICS has write access to the initial context node.

A CorbaServer's JNDI sub-context is specified on the JNDIPREFIX option of the CORBASERVER definition. CICS creates the sub-context (if it has the necessary write permission and the sub-context does not already exist in the name space structure) when an enterprise bean is published from the CorbaServer. However, if all the enterprise beans in the CorbaServer are retracted, CICS may delete the sub-context from the name space structure. Where multiple CorbaServers share part of a prefix hierarchy, CICS never removes contexts that are still in use by any of them. But if the contexts in the prefix are empty they are removed, as far back as the initial context.

If you want to protect the top-level node of the sub-context hierarchy from deletion, do not give CICS write access to the initial context node. (This means that you must create the top-level node of the sub-context manually.) If you want to protect several higher levels of the sub-context hierarchy, give CICS write permission only to the lower levels. (This means that you must create the higher-level nodes of the sub-context manually.) For more information, see Security at the CICS region level.

Versions of WebSphere Application Server for distributed platforms have a similar concept of domain, but that concept does not relate to a sysplex.