Tuesday, June 16, 2009

Use interface maps to facilitate the wiring between two SCA compo

Component Implementation

Websphere Integration Developer v612

Contact us...  

  
 

Use Interface maps to facilitate the wiring between two SCA components

SCA components can only communicate with one another if they have matching interfaces.  If they don't, then they cannot communicate.
 
An interface map resolves differences between the interfaces of interacting components to enable them to communicate with one another.
 
Differences between interfaces in components that need to interact with one another are common. These differences arise because in WebSphere® Integration Developer you are often assembling components that were created for different applications. Reusing them to create a new application is one of WebSphere Integration Developer's strengths, since otherwise you would be recoding similar components. But you typically must make some adjustments.

Creating interfaces

Interfaces are the means of exchanging data between components. In this section, you will learn about the relationship between interfaces and implementations, the parts of an interface, different ways of starting the interface editor and developing an interface, and see some tutorials and samples about interfaces.
 
  1. Interfaces
    An interface provides the input and output of a component. It is created independent of the internal implementation of the component.
  2. Interface editor
    You create interfaces with the interface editor. How you use the interface editor to create interfaces and work with interfaces is discussed in this section.
  3. Developing interfaces: top-down
    Top-down development means building the entire interface yourself, meaning you have no initial interface.
  4. Developing interfaces: bottom-up
    Bottom-up development means starting with an interface that was created outside of WebSphere® Integration Developer, importing it into a module and then, if necessary, modifying it in the interface editor.
  5. Developing interfaces: meet-in-the-middle
    Meet-in-the-middle development means taking an already created interface and adding it to a component that has been implemented but has no interface.
  6. Inline schemas
    Inline schemas are a way of including the schema within a WSDL file rather than specifying that it be imported.

Mapping interfaces

An interface provides the means to interact with a component. It is independent of the internal implementation of the component. In WebSphere Integration Developer, you can use the interface mapping editor to resolve and reconcile the differences between the interfaces of interacting components.
 
Note:
Interface maps can be used only in modules for business services, not for mediation services.
 
The following topics provide the conceptual information about and step-by-step instructions for mapping interfaces:
 
  1. Interface maps
    Interface maps are created in the interface mapping editor to resolve and reconcile differences between the interfaces of interacting components.
  2. Interface mapping editor
    With the interface mapping editor, you can build and edit interface maps in a graphical mode.
  3. Operation mappings
    Each operation mapping maps one operation in the source interface to one operation in the target interface.
  4. Parameter mappings
    Parameter mappings map parameters in the source operation to parameters in the target operation.
  5. Creating interface maps
    Using the interface mapping editor, you can establish correspondence between the operations and parameters of interfaces, thereby permitting the exchange of data between them, by creating interface maps.
  6. Adding event monitoring to interface maps
    The event monitor generates and monitors events. Event monitoring can be set for operation mappings and parameter mappings in interface maps.
  7. Hints and tips for the interface mapping editor
    This topic provides troubleshooting tips and other helpful information to consider when using the interface mapping editor.

Related links

 

 

No comments: