SCA EIS Binding

Service Component Architecture (SCA) enterprise information system (EIS) bindings provide connectivity between SCA components and external systems. This communication is mediated by EIS exports and EIS imports.

Your SCA components may require data to be transferred to or form an external EIS. When you create SCA modules requiring such connectivity, in addition to your SCA component you will include EIS imports and/or EIS exports to communicate with specific external EISs. Details of how to develop EIS imports and exports are provided in the WebSphere Integration Developer Information Center.

Example

A typical SCA module named ContactSyncModule, synchronizes contact information between a Siebel system and a SAP system. The SCA component named ContactSync listens via an EIS Service Export named Siebel Contact for changes to Siebel contacts. The ContactSync SCA component itself makes use of an SAP service via an EIS Service Import in order to update the SAP contact information accordingly. Since the data structures used for storing contacts is different in Siebel and SAP systems, the ContactSync SCA must provide mapping.

The image shows how the sample SCA module ContactSyncModule synchronizes contact information between a Siebel system and a SAP system. At far left a Siebel system is shown, and at far right a SAP system is depicted. Between the two external systems a large rectangle is shown and is labelled ContactSyncModule. Within the module are three nodes, from left to right an Export called "Siebel Contact", an SCA component called "ContactSync" and an Import called "SAP Contact". A series of arrows shows data flowing from the Siebel system to the SCA component via the Export. The SCA component is wired to the Import which has an additional arrow out to the SAP system.
Related concepts
JMS bindings

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)