CorbaServer definition attributes

The CorbaServer resource definition attribute descriptions are:

ASSERTED
specifies the 8-character name of a TCPIPSERVICE that defines the characteristics of the port which is used for inbound IIOP with asserted identity authentication.
AUTOPUBLISH({NO|YES})
specifies whether the contents of a deployed JAR file should be automatically published to the namespace when the DJAR definition is successfully installed into this CorbaServer. "Successfully installed" means that the DJAR is INSERVICE. The default is NO.

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
specifies the label of an X.509 certificate that is used as a client certificate during the SSL handshake for outbound IIOP connections. If this attribute is omitted, the default certificate defined in the key ring for the CICS® region user ID is used.

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.

Start of changeCiphersEnd of change
Start of change(Optional) Specifies a value up to 28 cipher suites, in the form of hexadecimal pairs. Any hexadecimal can be specified, but currently the only recognized values are 01, 02, 03, 04, 05, 09, 0A, 2F, and 35. Additional values can be added at a later time. No separating characters are necessary between each pair.

The default is blank.

Ciphers is valid only on CICS Transaction Server 3.1 and later systems .

End of change
ClientCert
specifies the 8-character name of a TCPIPSERVICE that defines the characteristics of the port which is used for inbound IIOP with SSL client certificate authentication. This attribute is optional.
DJARDIR(directoryname)
specifies the 1-255 character fully-qualified name of the deployed JAR file directory (also known as the pickup directory) on HFS. The acceptable characters are A-Z a-z 0-9 . _ /.For information about entering mixed case information, see CICS Resource Definition Guide.

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. (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.)

After the CorbaServer has been installed, you can add more deployed JAR files to the pickup directory. CICS installs them:

or

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.

Notes:
  1. If you use the scanning mechanism in a production region, be aware of the security implications: specifically, the possibility of CICS command security on DJAR definitions being circumvented. To guard against this, we recommend that user IDs given write access to the HFS deployed JAR file directory should be restricted to those given RACF® authority to create and update DJAR and CORBASERVER definitions.
  2. If you do not specify a value for DJARDIR, no automatic scan takes place on installation of the CorbaServer. PERFORM CORBASERVER SCAN commands (whether explicit or issued by the RM for enterprise beans) will fail.
  3. The installation of the CorbaServer fails if the value of DJARDIR is not blank but does not refer to a valid HFS directory to which the CICS region has read access.
  4. Different CorbaServers may share the same DJARDIR directory. Typically, all the AORs in a multi-region EJB server would share the same DJARDIR directory.
  5. CICS ignores any deployed JAR files in the pickup directory that have the same name and the same date and time stamps as currently-installed DJAR resources. A deployed JAR file with the same name but a later date-and-time stamp than an installed DJAR is treated as an update.
  6. Deleting a previously-installed deployed JAR file from the pickup directory does not remove the DJAR resource from CICS; its beans are still available. To make the beans unavailable, you must discard the DJAR resource.
  7. An invalid deployed JAR file is not detected early (when the pickup directory is scanned), but when the EJB environment attempts to open it. The DJAR resource for an invalid JAR file becomes UNRESOLVED. CICS outputs a message to indicate what is wrong with the JAR file. The message is sent to the CICS log and to the "EJB event" user-replaceable program.
  8. After every scan of the pickup directory, CICS outputs a message indicating the number of new and the number of updated deployed JAR files found during the scan.
Host
specifies the TCP/IP host name, or a string containing the dotted-decimal TCP/IP address, of this logical EJB/CORBA server.

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.

JNDIPrefix
specifies a JNDI prefix of up to 255 characters which is used when enterprise beans are published to the Java™ Naming and Directory Interface (JNDI). The acceptable characters are A-Z a-z 0-9 . _ /.
For information about entering mixed case information, see CICS Resource Definition Guide.

Publishing a bean means binding a reference to the home of the bean in a namespace. 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 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.

Name
The 1-4 character name of a CorbaServer.
Port
This attribute is obsolete, but is supported to provide compatibility with earlier releases of CICS. If this attribute is present in the CORBASERVER definition, the following attributes must be blank:

If you define a CORBASERVER with this attribute, you can only install it on CICS Transaction Server for z/OS®, Version 2 Release 1. See CICS Resource Definition Guide for more information.

RESGROUP
(Optional.) Specify the name of an existing resource group to which the definition is to be automatically added.
Sessbeantime
specifies, in days, hours, and minutes, the period of inactivity after which a session bean may be discarded by CICS.
00,00,00
Session beans will not be timed out.
00,00,10
Session beans may be discarded after ten minutes of inactivity. This is the default value.
dd,hh,mm
Session beans may be discarded after the specified period of inactivity. The maximum value you can specify is 99 days, 23 hours, and 59 minutes.
Shelf
specifies the 1-255 character fully-qualified name of a directory (a shelf, primarily for deployed JAR files) on HFS. The acceptable characters are A-Z a-z 0-9 . _ /. For information about entering mixed case information, see CICS Resource Definition Guide.

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.

SSL
This attribute is obsolete, but is supported to provide compatibility with earlier releases of CICS. If this attribute is present in the CORBASERVER definition, the following attributes must be blank:

If you define a CORBASERVER with this attribute, you can only install it on CICS Transaction Server for z/OS, Version 2 Release 1. See CICS Resource Definition Guide for more information.

SSLPort
This attribute is obsolete, but is supported to provide compatibility with earlier releases of CICS. If this attribute is present in the CORBASERVER definition, the following attributes must be blank:

If you define a CORBASERVER with this attribute, you can only install it on CICS Transaction Server for z/OS, Version 2 Release 1. See CICS Resource Definition Guide for more information.

SSLUnauth
specifies the 8-character name of a TCPIPSERVICE that defines the characteristics of the port which is used for inbound IIOP with SSL but no client authentication. This attribute is optional.
Unauth
specifies the 8-character name of a TCPIPSERVICE that defines the characteristics of the port which is used for inbound IIOP with no authentication.

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.

User data
(Optional.) Three 8-character fields provided for any site-specific data related to the file key segments. CICSPlex® SM makes no use of this user data.
Version
(Optional.) Specify an integer in the range 1 through 15. Specify 0 or leave blank for CICSPlex SM to assign the first available version id in the range 1 through 15.

Related concepts
CorbaServer definitions
CICS Resource Definition Guide
Related tasks
Accessing BAS CorbaServer definitions
Working with the EJCODEF view
Defining CorbaServers using BAS
Installing BAS CorbaServer definitions
[[ Contents Previous Page | Next Page Index ]]