>>-CORBASERVER(name)--GROUP(groupname)--+-------------------+---> '-DESCRIPTION(text)-' .-AUTOPUBLISH(NO)--. >--+------------------+--+--------------------+-----------------> '-AUTOPUBLISH(YES)-' '-CERTIFICATE(label)-' >--+---------------------+--+--------------------+--------------> '-CIPHERS(cipherlist)-' '-DJARDIR(directory)-' >--HOST(hostname)--+--------------------+-----------------------> '-JNDIPREFIX(prefix)-' .-SESSBEANTIME(00,00,10)-. .-SHELF(/var/cicsts)-. >--+------------------------+--+--------------------+-----------> +-SESSBEANTIME(00,00,00)-+ '-SHELF(directory)---' '-SESSBEANTIME(dd,hh,mm)-' .-STATUS(ENABLED)--. >--+------------------+-----------------------------------------> '-STATUS(DISABLED)-' >--UNAUTH(tcpipservice)--+-----------------+--+--------------------------+->< '-ASSERTED(char8)-' +-CLIENTCERT(tcpipservice)-+ '-SSLUNAUTH(tcpipservice)--'
Specifying YES causes beans to be automatically published to the namespace when a DJAR is successfully installed. It does not cause beans to be automatically retracted when a DJAR is discarded.
Certificate labels can be up to 32 bytes long.
The distinguished name within the specified certificate provides inputs to the distinguished name user-replaceable program, DFHEJDNX.
You can reorder the cipher codes or remove them from the initial list. However, you cannot add cipher codes that are not in the default list for the specified encryption level. To reset the value to the default list of codes, delete all of the cipher suite codes and the field will automatically repopulate with the default list.
See Cipher suites for more information.
Acceptable characters:
Unless
you are using the CREATE command, any lowercase characters you enter are converted
to uppercase. |
Acceptable characters:
For information about entering mixed case information,
see Entering mixed case attributes. |
Acceptable characters:
For information about entering mixed case information,
see Entering mixed case attributes. |
If specified, DJARDIR must refer to a valid HFS directory to which the CICS region has at least read access.
The pickup directory is where you place deployed JAR files that you want to be installed into the CorbaServer by the CICS scanning mechanism. When the CORBASERVER definition is installed, CICS scans the pickup directory and automatically installs any deployed JAR files it finds there. (This automatic scan occurs regardless of whether the CorbaServer is installed in enabled or disabled state.)
CICS assumes that any files in the pickup directory that end in .jar and have a base filename of 1–32 characters are EJB deployed JAR files. It copies them to its shelf directory and dynamically creates and installs DJAR definitions for them. The name of the DJAR definition is the name of the deployed JAR file on HFS. For example, a deployed JAR file named /var/cicsts/pickup/TheThreeBears.jar results in a DJAR definition named TheThreeBears.
After the CorbaServer has been installed, you can also put updated versions of deployed JAR files into the pickup directory. When you issue a PERFORM CORBASERVER SCAN command (either explicitly or by means of the RM for enterprise beans), CICS detects that an update has occurred and updates both the LASTMODTIME, DATESTAMP, and TIMESTAMP attributes of the installed DJAR definition and the shelf copy of the deployed JAR file, to reflect the pickup directory change.
Acceptable characters:
Any
lower case characters you enter are converted to upper case. |
The GROUP name can be up to eight characters in length. Lowercase characters are treated as uppercase characters. Do not use group names beginning with DFH, because these characters are reserved for use by CICS.
Acceptable characters:
For information about entering mixed case information,
see Entering mixed case attributes. |
The host name is included in Interoperable Object References (IORs) exported for objects in this logical server. Clients must use this host name to access the CICS listener regions.
If you are using connection optimization by means of Domain Name System (DNS) registration, to balance client connections across the listener regions of your logical IIOP or EJB server, specify the generic host name to be quoted by client connection requests. (The generic host name is the DNSGROUP value defined in the TCPIPSERVICE resource definition, suffixed by the name of the domain or subdomain managed by the MVS™ system name server. This is established by your MVS TCP/IP system administrator.) See Java™ Applications in CICS for more information about using DNS with IIOP and enterprise beans.
Acceptable characters:
For information about entering mixed case information,
see Entering mixed case attributes. |
Publishing a bean means binding a reference to the home of the bean in a name space. The naming context in which the bean is bound is named, relative to the initial context defined for the CICS region, using a concatenation of the JNDIPREFIX attribute of the CorbaServer and the name of the bean. The JNDIPREFIX attribute must match the prefix specified by the client when it uses JNDI to obtain a reference to the home interface for a bean. For more information, see Java Applications in CICS.
CICS creates the sub-context specified on the JNDIPREFIX option (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 sub-context hierarchy from deletion, do not give CICS write access to the initial context node or directory. (This means that you must create the top-level node or directory of the sub-context manually. For information on how to do this with an LDAP name server, see Java Applications in CICS.)
CICS limits the use of the / character in the JNDI prefix field to prevent the use of empty atomic components, which are denoted by an empty string. The / character may not be the first or last character of the prefix. Also, two or more consecutive instances of the / character are not allowed anywhere in the prefix.
If this option is not specified, no prefix is added when publishing enterprise beans to JNDI.
Acceptable characters:
For information about entering mixed case information,
see Entering mixed case attributes. |
CICS regions into which the CORBASERVER definition is installed must have full permissions to the shelf directory—read, write, and the ability to create subdirectories.
A single shelf directory may be shared by multiple CICS regions and by multiple CORBASERVER definitions. Each CICS region uses a separate subdirectory to keep its files separate from those of other CICS regions. The subdirectories for CORBASERVER definitions are contained within the subdirectories of the CICS regions into which they are installed. After a CICS region performs a cold or initial start, it deletes its subdirectories from the shelf before trying to use the shelf.
You should not modify the contents of a shelf that is referred to by an installed CORBASERVER definition. If you do, the effects are unpredictable.
Acceptable characters:
Unless
you are using the CREATE command, any lowercase characters you enter are converted
to uppercase. |
Acceptable characters:
Unless
you are using the CREATE command, any lowercase characters you enter are converted
to uppercase. |
Note that you must specify a value for the UNAUTH attribute when you define a CORBASERVER, even if you intend that all inbound requests to this CORBASERVER should be authenticated. This is because the PORTNUMBER attribute of the TCPIPSERVICE is required in order to construct IORs that are exported from this logical server.