Configuration in the CICS

The following configuration activities have to be carried out in the CICS itself:

• Definition of a connection, used to specify the connection parameters. This definition contains the name of the logical unit (NETNAME parameter) of the CICS partner application.

• Definition of a session, used to specify the session parameters. This definition contains the name of the connection (CONNECTION parameter) and the name of the session mode (MODE parameter). The properties of a session are then defined via the mode.

The BeanConnect Management Console generates a text file that contains the definitions of CONNECTION and SESSION (see Configuring EIS partners of type CICS ).

In the case of a single proxy, the name of the generated input file is:

ProxyID.<p-id>.EisPartnerID.<e-id>.CICS.txt

In the case of a proxy in a cluster, the name of the generated input file is:

ClusterID.<c-id>.ProxyID.<p-id>.EisPartnerID.<e-id>.CICS.txt

<p-id>, <e-id> and <c-id> designate the IDs for the proxy, EIS partner and proxy cluster assigned by the Management Console.

BeanConnect does not transfer the file to the EIS platform. This file has to be transferred to the EIS partner host using common file transfer mechanisms and can be used by the CICS administrator to carry out the configuration activities.