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

When deploying an EJB which is designed to use BeanConnect for outbound communication, you must link the EJB to the BeanConnect deployment. The following files are relevant for deploying an EJB:

• Code file of the EJB (.java or .class file)

• Standardized deployment descriptor of the EJB (ejb-jar.xml) or Java annotations

• Application server-specific deployment descriptor of the EJB if necessary

• Application server-specific configuration file or deployment descriptor for the resource adapter if necessary

When an EJB is deployed, the resource reference used by the Bean developer is made known to the application server in the deployment descriptor of the EJB. In addition, a resource type is assigned to the resource reference.

BeanConnect supports the following resource types, which represent the different types of connections that can be used:

• For OSI-TP or LU6.2 communication using the BeanConnect interface:
  net.fsc.jca.communication.EISOltpConnectionFactory

• For OSI-TP or LU6.2 communication using the CCI interface:
  net.fsc.jca.communication.cci.BCOltpConnectionFactory

You must specify the resource type in the following files:

• ejb-ra.xml with the <res-type> tag

The sections of the code file of the EJB as well as of the file ejb-jar.xml that are relevant for the deployment of the EJB are described in detail below.

• Code file of the EJB (.java or .class file)

  The JNDI lookup for the ConnectionFactory object via a resource reference (coded name) takes place here. In the following example, the resource reference used is

  eis/Part1Dial.
  ...
  cf=(EISConnectionFactory)
           ic.lookup("java:comp/env/eis/Part1Dial")
  ... 
  

• Deployment descriptor of the EJB (ejb-jar.xml)

  Here the resource reference (ConnectionFactory object) which the EJB accesses is specified. In addition, a resource type is assigned to the resource reference. In the following example net.fsc.jca.communication.EISOltpConnectionFactory is used as the resource type.

  <session>
    <ejb-name>SimpleBeanConnect</ejb-name>
    ...
    <resource-ref>
      <res-ref-name>eis/Part1Dial</res-ref-name>
      <res-type>
        net.fsc.jca.communication.EISOltpConnectionFactory
      </res-type>
      <res-sharing-scope>Unshareable</res-sharing-scope>
     ...
    </resource-ref>
  </session>
  

  Please note that for <res-sharing-scope> you must always specify Unshareable.

• Application server-specific deployment descriptor of the EJB if necessary
  Here, application server JNDI names may be assigned to the EJB name and the resource references that are defined in the file ejb-jar.xml.

• Application server-specific configuration file or deployment descriptor for the resource adapter in which the connection factory is defined, if necessary

An additional configuration step is required on the proxy. For each outbound communication endpoint name, you must configure a corresponding outbound communication endpoint of the same name in the proxy. The outbound communication endpoint definition maps the symbolic service name onto a real service name in the EIS partner application. You can carry out configuration of an outbound communication endpoint using the Management Console (see Configuring outbound communication endpoints).