Configuration steps for outbound and inbound communication

The procedure depends on whether you want to operate outbound communication via OSI-TP/ LU6.2, outbound communication via UPIC, and/or inbound communication. Each of these possibilities is presented separately below. However, different rules apply for multiple resource adapter and cluster operation.

In the case of outbound communication (OSI-TP / LU6.2 and UPIC), you must define resource references in ejb-jar.xml.

Procedure for outbound communication via OSI-TP / LU6.2

If you want to use BeanConnect for outbound communication via OSI-TP / LU6.2 in default mode (one proxy, one resource adapter, no cluster) then you must perform the following activities:

• Defining general properties in ra.xml

• Deploying an Enterprise JavaBean for OSI-TP / LU6.2

• Preparing resource adapter logging

Procedure for outbound communication via UPIC

If you want to use BeanConnect for communications via UPIC then you must perform the following activities:

• Deploying an Enterprise JavaBean for UPIC

• Preparing resource adapter logging

Procedure for inbound communication

If you want to use BeanConnect for inbound communication in default mode (one proxy, one resource adapter, no cluster) then you must perform the following activities:

• Defining general properties in ra.xml

• Configuring inbound communication

• Deploying Enterprise Java Beans

• Preparing resource adapter logging

Procedure with multiple resource adapters and in cluster operation

When working with multiple resource adapters or in cluster operation, additional settings must be made in the file ra.xml. For further details, see:

• Special characteristics in cluster operation

• Special characteristics of multiple resource adapter mode