Configure J2C connection factories

 

+

Search Tips   |   Advanced Search

 

The terms J2C and JCA both refer to J2EE Connector Architecture and they are used here interchangeably.

Application components such as EJBs have <resource-ref> descriptors that refer to the connection factory, not the resource adapter. The connection factory is just a holder of a list of connection configuration properties. In addition to the arbitrary set of configuration properties defined by the vendor of the resource adapter, there are several standard configuration properties that apply to the connection factory. These standard properties are used by the connection pool manager in the appserver run time and are not used by the vendor supplied resource adapter code.

To create a J2C connection factory...

  1. Select...

      Resources | J2C connection factories

    You will see a list of J2C connection factories at the selected scope.

  2. Click New to create a new connection factory, or select an existing one to modify the connection factory properties.

    The J2C Connection Factory Configuration page...

    The general properties are:

    Name Type an administrative name for the J2C connection factory.
    JNDI name Connection factory name to be registered in the appserver's name space, including any naming subcontext.

    When installing an application that contains modules with J2C resource references, the resources defined by the deployment descriptor of the module need to be bound to the JNDI name of the resource.

    As a convention, use the value of the Name property prefixed with eis/, for example,

      eis/<ConnectionFactoryName>

    Description Optional description of the J2C connection factory, for your administrative records.
    Connection factory interface Name of the connection factory interfaces supported by the resource adapter.
    Category Specify a category that use to classify or group the connection factory.
    Component-managed authentication alias This authentication alias is used for component-managed sign-on to the resource.

    Deprecated in V6.1: The following security settings are deprecated:

    • Container managed authentication alias
    • Authentication preference
    • Mapping configuration alias

    Resource authentication settings should be used instead.

  3. Click Apply. The links under the Additional Properties section for connection pool, advanced connection factory, and custom properties become active.

    The connection pool properties are configured the same as for a JDBC data source.

    The advanced connection factory properties...

    Log missing transaction context Log if there is a missing transaction context in the activity log when the connection is obtained.
    Manage cached handles When you call the getConnection() method to access a database, you get a connection handle returned. The handle is not the physical connection, but a representation of a physical connection. The physical connection is managed by the connection manager. A cached handle is a connection handle held across transaction and method boundaries by an application.

    This setting specifies whether cached handles should be tracked by the container. This can cause overhead and only should be used in specific situations.

    Next