Configuring Connection Factory for outbound communication

Connection Factories

Outbound communication is handled via so-called connection factories, which you must configure in the application server.

At least you have to configure one connection factory for each EIS partner. However it is also possible to configure more than one connection factories for a EIS partner with different properties.

For each connection factory you specify the following in the application server:

• The resource type
  • For communication over OSI TP / LU6.2 the following resource types are relevant:
    • net.fsc.jca.communication.cci.BCOltpConnectionFactory
    • net.fsc.jca.communication.EISOltpConnectionFactory
  • For communication over UPIC the following resource types are relevant:
    • net.fsc.jca.communication.cci.BCUpicConnectionFactory
    • net.fsc.jca.communication.EISUpicConnectionFactory
• JNDI name:  This is necessary for deploying the EJB and serves to address the connection factory in the EJB.

• Configuration properties: These are the parameter that apply to the connection to the EIS partner (see Defining configuration properties for outbound communication). 

• Connection pooling: Connection pooling is a functionality of the application server. Its purpose is to enhance the performance when connection factories are used often.

• Security settings: These are the data, which are used for signing at the EIS partner, e.g. user id and password. If this data is coded directly in the EJB, this entry in the deployment decriptor can be omitted. (see Defining security settings (managing sign-on)).

• For outbound communication over OSII-TP / LU6.2 in the management console a outbound communication endpoint will be assigned to each connection factory.