IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Services and service-related functions > Access external services with adapters > Configure and using adapters > IBM WebSphere Adapters > Adapter Toolkit > Implementing code from the IBM WebSphere Adapter Toolkit > Outbound support > Implementing outbound support

WBIManagedConnectionFactory

A javax.resource.spi.ManagedConnectionFactory instance manages the creation and configuration of physical connections to the underlying EIS. Specifically, WBIManagedConnectionFactory implements the ManagedConnectionFactory and javax.resource.spi.ResourceAdapterAssiociation interfaces.


Configuration Properties

EIS-specific subclasses should specify boxed JavaBeans-compliant accessor pairs (for example, setValue(Integer i) rather than setValue(int i)). The accessor pairs get and set EIS-specific outbound configuration properties and logic. This is the means by which property change events reach property change listeners with corresponding updates to the ResourceAdapter (RA) deployment descriptor, thereby making the JCA container aware of available properties. Properties defined in this class are generally intended for use by the WBIManagedConnection implementation when connecting to the EIS.

Support for the ResourceAdapterAssociation interface, which cannot be used in unmanaged environments, is optional for the JCA container. Accordingly, when defining properties, assume that ManagedConnectionFactory will not have access to the ResourceAdapter bean or any properties defined at the ResourceAdapter level. While the ManagedConnectionFactory can check for and use properties at the ResourceAdapter level as defaults when available, any properties defined at the ResourceAdapter level and used by the ManagedConnectionFactory should be optional, contain default values embedded in the ManagedConnectionFactory, or exposed in the ManagedConnectionFactory so that users can specify values if the ResourceAdapter bean is not available.


Subclass methods to implement

  1. Object createConnectionFactory(ConnectionManager)

    This method is called by the JCA container to enable the CCI clients to generate handles to the physical EIS connection. EIS-specific subclasses should implement this method to return an EIS-specific factory instance which is a subclass of WBIManagedConnectionFactory.

    public Object createConnectionFactory(ConnectionManager cm)
    			throws ResourceException {
    		return new EISSAConnectionFactory(cm, this);	
    	}
  2. ManagedConnection createManagedConnection(Subject, ConnectionRequestInfo)

    This method is used by the JCA container to acquire a physical connection to the EIS instance. Subclass implementation should return a EIS-specific ManagedConnection instance which is a subclass of WBIManagedConnection.

    public ManagedConnection createManagedConnection(Subject subject, 			ConnectionRequestInfo connRequestInfo)
    throws ResourceException {
            EISSAManagedConnection conn = 
    new EISSAManagedConnection(this,subject, (WBIConnectionRequestInfo)connRequestInfo);
            return conn;
    	}

Implementing outbound support


Related concepts:

WBIManagedConnection

WBIConnectionFactory

WBIConnection

javax.resource.cci.ConnectionSpec

WBIInteraction

WBIInteractionSpec

WBIConnectionRequestInfo

javax.resource.cci.ConnectionMetadata