Installing CorbaServer definitions

The EJB request streams directory file, DFHEJDIR, must be defined, installed, and available before you can install a CORBASERVER definition.

When you install a CORBASERVER, CICS® checks related resources for consistency:
  • At the end of GROUPLIST installation during CICS initialization.
  • After a group containing a CORBASERVER is installed. In this case, related TCPIPSERVICEs must either be installed before the group containing the CORBASERVER, or as part of the same group.
  • After a CORBASERVER is installed as an individual resource. In this case, related TCPIPSERVICEs must be installed before the CORBASERVER.

You can install a CorbaServer in either enabled or disabled state.

When you install a CORBASERVER, it is not available for use immediately, even if you have chosen to install it in enabled state; instead CICS starts a task which completes the steps necessary to make it usable:
  1. Related resources (such as TCPIPSERVICE and DJAR) are checked for consistency with the CORBASERVER.
  2. The shelf directory is created if necessary, or emptied if it already exists.
  3. If a deployed JAR file directory has been specified, it is scanned for deployed JAR files. (This automatic scan occurs regardless of whether the CorbaServer is installed in enabled or disabled state.) CICS assumes that a file is a deployed JAR if:
    1. It has a suffix of .jar (in lowercase).
    2. Its base filename is between 1 and 32 characters long. By “base filename” we mean the part of the filename before the suffix, and excluding any file path. For example, the base filename of the file djardir\myDeployedJar.jar is myDeployedJar.
  4. If there are any deployed JAR files in the DJARDIR directory, they are copied to the shelf directory, and DJAR resource definitions are dynamically created for them.
If step 1 or step 2 fails, CICS puts the CORBASERVER in DISABLED state, and issues a message indicating the cause of the problem. If this happens, and the problem lies with the associated resources, you must:
  • Make the necessary corrections to the associated resources, re-installing the resource definitions as necessary.
  • If required, enable the CorbaServer by issuing an EXEC CICS or CEMT SET CORBASERVER ENABLED command.
If the problem lies with the CORBASERVER definition, you must:
  • Discard the installed CORBASERVER definition.
  • Make the necessary corrections to the CORBASERVER definition.
  • Reinstall the CORBASERVER definition.

Any work which is directed to a newly-installed CORBASERVER is suspended until the CORBASERVER is ready for use—that is, in ENABLED state.

To determine the state of a CORBASERVER, use the INQUIRE CORBASERVER command, or CEMT INQUIRE CORBASERVER.

You can install more than one CORBASERVER definition in the same CICS region. It is recommended that you divide your enterprise beans and CORBA stateless objects between CorbaServers based on their:
  • Functionality
  • Maintenance requirements
  • Availability requirements
That is, sets of beans or CORBA stateless objects that have distinct functionality, maintenance requirements, or availability requirements, should be installed in distinct CorbaServers.

If you replace an existing CORBASERVER definition by installing another of the same name, you must first discard the existing definition.