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 the general properties of the resource adapter in weblogic- ra.xml and Defining general and connection-specific properties for OSI-TP / LU6.2 in weblogic-ra.xml .
Pack the file
weblogic-ra.xmlunder the META-INF sub-directory of the BeanConnect RAR archive before deployment.
Procedure for outbound communication via UPIC
If you want to use BeanConnect for communications via UPIC then you must perform the following activities:
Defining the general properties of the resource adapter in weblogic- ra.xml and Defining general and connection-specific properties for OSI-TP / LU6.2 in weblogic-ra.xml .
Before deployment, insert the file
weblogic-ra.xmlin the sub-directory META-INF of the BeanConnect RAR archive.
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 the general properties of the resource adapter in weblogic- ra.xml
Before deployment, insert the file
weblogic-ra.xmlin the subdirectory META-INF of the BeanConnect RAR archive
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: