WebSphere WebSphere Enterprise Service Bus, Version 6.0 Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Custom Mediation primitive

Use the Custom Mediation primitive to execute custom logic.

Introduction

The Custom Mediation primitive can call an external Service Component Architecture (SCA) component, that you create or provide.

The SCA component that is called by Custom Mediation, must be of type Java. The Custom Mediation primitive cannot call a mediation flow component. When using WebSphere Integration Developer you have to create a Java SCA component manually, using the assembly editor.

The Custom Mediation primitive has one input terminal and two output terminals. One output terminal is for successful output and one for failure output. The input terminal is wired to accept a message and the output terminals are wired to propagate a message. The input message is passed to the external SCA component, as the input parameter. If the operation returns successfully the response is propagated to the output terminal. If the operation returns unsuccessfully then the fail terminal propagates the original message, together with any exception information.

Usage

You can use the Custom Mediation primitive to do processing that is not covered by other mediation primitives. For example, you could write a custom SCA component to access the Message Logger database.

Properties

Service reference
The reference to the target SCA component. If the Custom Mediation primitive is generated through WebSphere Integration Developer using a bottom up action, then the Service reference is generated, by default. Otherwise, you must provide the Service reference. Generating a Custom Mediation primitive from the bottom up, means creating the implementation details before creating the mediation flow component.
Operation
The chosen operation, from the interface of the target SCA component. The interface of the target SCA component might specify a number of operations you can choose from.
Root
An XPath 1.0 expression representing the root of the SMO that is passed to the SCA component. You can specify / or /body. / refers to the complete SMO and /body refers to the body section of the SMO.
Table 1. Custom Mediation primitive properties
Property Valid Values Default
Service reference String null or reference generated
Operation String  
Root String: an XPath expression representing the root of the message that is passed to the SCA Component /body

Considerations

Consider the following when using the Custom Mediation primitive:


Reference topic

Terms of Use |

Last updated: 20 Nov 2005
http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp?topic=/com.ibm.wbit.help.medprim.doc\ref\rwesb_CustomSCAmediationprimitive.html

© Copyright IBM Corporation 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)