WebSphere brand IBM WebSphere Telecom Web Services Server, Version 7.1

Integrating your custom mediation primitives with WebSphere Integration Developer (WID)

A reusable approach for creating custom mediation primitives is to package the mediation primitives so that they plug in to the Flow Editor palette. The palette is part of the Telecom Web Services Server plug-in for WebSphere® Integration Developer (WID).

To integrate your custom mediation primitives into the Flow Editor palette, you must create a JAR file that contains the mediation primitive runtime code. Then you must place that code within the class path for WebSphere Enterprise Service Bus.

Eclipse plug-in code is also needed, and an icon must be included for the Flow Editor palette. After they are installed into the WID Eclipse plug-in directory, these plug-ins are automatically populated into the palette when WID is started with the -clean option.

Mediation primitives that extend the Flow Editor palette can also have static properties that can be set. These properties are described within the Eclipse plug-in descriptor and appear within the Properties view below the Assembly Diagram canvas. Properties can be set on each primitive instance that is added into the canvas.

Property values can be set only within the Flow Editor and are stored within the EAR file that is generated from the flow artifacts. Because of this, custom mediation primitives should use properties only for static information, such as JNDI resource names or default properties. All other configuration information should be policy driven.

For more information about developing custom mediation primitives, refer to the topic Implementing custom mediation logic in the WebSphere Integration Developer information center.




Terms of use
(C) Copyright IBM Corporation 2009. All Rights Reserved.