Migrating a custom mediation primitive

Prior to WebSphere® Integration Developer v 6.0.2, a custom mediation primitive was implemented by invoking a Java™ component. Starting with WebSphere Integration Developer v 6.0.2, Java code is embedded in the custom mediation primitive. Follow these instructions to convert your custom mediation primitive's implementation to an embedded snippet.

In previous versions of WebSphere Integration Developer, mediation primitives that used custom Java code were created in a two stages. A service reference was created in the mediation flow component, and its mediate operation was used to invoke a Java component, which in turn invoked the custom Java code. Starting with WebSphere Integration Developer 6.0.2, this process is much simpler. Java code is now embedded directly in the custom mediation primitive, without the need for the intermediary service reference and Java component.

Custom mediation primitives created in prior versions will work in WebSphere Integration Developer 6.0.2, however the only change that you can make to the primitive's properties is to edit the Java or Visual snippet.

To upgrade your custom mediation primitive, perform the following tasks: Follow these steps to upgrade your custom mediation primitive.
  1. Select the custom mediation primitive on the canvas to view its properties. In the properties view, click the Details tab. The implementation is set to Java or Visual, and the custom code appears as a snippet in the embedded editor, as shown in the following image: Details view of custom mediation primitive from a previous version of WebSphere Integration Developer
  2. Click the Convert to Embedded Snippet button to convert the Java or Visual code to an embedded Java or Visual snippet. Save the changes.
  3. After conversion to a Java or Visual snippet, all the classes in the snippet need to be fully qualified. If you see errors in the Java snippet code indicating that an object cannot be resolved or is not a type, use code assist (crtl-space) to add the package qualifier.
  4. In the top section of the mediation flow editor, delete the service reference used by the old custom mediation primitive, if the reference is no longer used in the mediation flow. Save your changes.
  5. If you deleted the service reference in the mediation flow, you need to synchronize the references in mediation flow component. In the assembly editor, select the mediation flow component, right-click, and select Synchronize Interfaces and References > from Implementation.
  6. Delete the Java component, and save the changes in the assembly editor.
Related concepts
Tips for creating Custom mediation primitives
Related tasks
Creating Java code in a custom mediation primitive
Invoking an import or a Java component from a custom mediation primitive

Feedback
(C) Copyright IBM Corporation 2005, 2006. All Rights Reserved.