Use the Custom Mediation primitive to execute custom logic.
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.
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.
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 |
Consider the following when using the Custom Mediation primitive: