WebSphere Process Server can send messages to, or receive messages from, external clients using EIS bindings.
An external client, for example a web portal or an EIS needs to send a message to an SCA module in WebSphere Process Server or needs to be invoked by a component from within WebSphere Process Server.
The client invokes the EIS Import as any other Service, using either the Dynamic Invocation Interface (DII) or Java™ interface.
First, the external client creates instance of the ServiceManager and looks up the EIS Import using its reference name. The result of the lookup is a Service interface implementation. Next, the client creates an input argument, a generic DataObject, created dynamically using the data object schema. This step is done using Service Data Object's (SDO's) DataFactory interface implementation. In the last step, the external client invokes EIS and obtains the required results.
Alternatively, the client can invoke EIS Import using the Java interface. First, the client creates instance of the ServiceManager and looks up the EIS Import using its reference name. The result of the lookup is a Java interface of the EIS Import. Next, the client creates an input argument, a typed DataObject and finally invokes EIS and obtains the required results.
The EIS Export interface defines the interface of the exported SCA component that is available to the external EIS Services. This interface can be thought of as the interface that external service like SAP or PeopleSoft will invoke (through the implementation of the EIS Export Service runtime). The export uses EISExportBinding to bind exported Services to the external EIS Service, it allows you to subscribe a Service contained in your SCA module to listen for EIS service requests. The EIS Export Binding specifies the mapping between the definition of inbound events as it is understood by the Resource Adapter (using J2EE Connector Architecture interfaces) and the invocation of SCA operations. The EISExportBinding requires external EIS Services to be based on J2EE Connector Architecture 1.5 inbound contracts. The EISExportBinding requires that a DataBinding be specified either at the binding level, or the method level.
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)