An EIS import is a Service Component Architecture (SCA) import that allows components in the SCA module to use EIS services defined outside the SCA module. An EIS import, is used to transfer data from the SCA component to an external EIS.
The role of the EIS import is to bridge the gap between SCA components and external EIS systems. External services can be treated as an EIS export. In this case, the external service sends its data in the form of a periodic notification.
The EIS import provides SCA components with a uniform view of the services external to the module. This allows components to communicate with a variety of external EISs such as SAP, Siebel or PeopleSoft, using a consistent SCA model.
On the client side of the import, there is an interface, exposed by the EIS Import Service, with one or more methods, each taking Data Objects as arguments and return values. On the implementation side, there is a Common Client Interface (CCI) implemented by the Resource Adapter.
The runtime implementation of an EIS import connects the client-side interface and the CCI. The import maps the invocation of the method on the interface to the invocation on the CCI. Bindings are created at three levels, Interface Binding, using contained Method Bindings which in turn use Data Bindings.
The Interface Binding relates the interface of the import to the connection to the EIS system providing the service. This reflects the fact that the set of services, represented by the interface, is provided by the specific instance of the EIS and the connection provides access to this instance. The binding element contains properties with enough information to create the connection (these properties are part of the javax.resource.spi.ManagedConnectionFactory instance).
The Method Binding associates the method with the specific interaction with the EIS system. For J2C, the interaction is characterized by the set of properties of the javax.resource.cci.InteractionSpec interface implementation. The Interaction element of the Method Binding contains these properties, along with the name of the class thus providing enough information to perform the interaction. The Method Binding uses Data Bindings describing the mapping of the argument and result of the interface method to EIS representation.
The runtime scenario for an EIS import is as follows. The method on the import interface is invoked using the SCA programming model. The request, reaching the EIS import handler, contains the name of the method and its arguments. The handler first creates an interface binding implementation, then using data from the import file, a ConnectionFactory, and associates the two. That is, the handler calls setConnectionFactory on the interface binding. The next step is to create the Method Binding implementation matching the invoked method. The javax.resource.cci.InteractionSpec instance is created and populated, then Data Bindings are used to bind the method arguments to a format understood by the resource adapter. At this point, the CCI interface is used to perform the interaction. When the call returns, the Data Binding is used to create the result of the invocation, and return the result to the caller.
The adapter interaction style allows for the EIS Export binding to invoke the target component either asynchronously or synchronously. The default is asynchronously.
Last updated: Wed 06 Dec 2006 07:08:08
(c) Copyright IBM Corporation 2005, 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)