function selector

Notice that the response message for an import with JMS binding does not pass through the function selector.

JMS Function Selector -- Remember that we explained how we view the application receiving the JMS message as a service?

A function selector specifies the particular operation to invoke within the mediation modules interface.

To work around this issue, we've created a custom function selector that hard-codes the method to processAction, as shown in Listing 1.

Now that you've created the WBE_to_WESB export and the Business Events function selector, you need to define the binding for the export.

Click Select for Function selector as shown in Figure 23, similar to data transformation.

If the WBE_to_WESB interface is defined as described in the previous steps, the attached function selector will work without modifications.

This article helped you implement a custom data binding and custom function selector for adapters running in WebSphere Process Server.

Then select RESTFunctionSelector for the function selector class as shown in Figure 26.

Appendix B shows sample code for a custom Function Selector.

The Adapter base classes send the Adapter-specific Record object to the Function Selector.

Hence to invoke custom interface methods, the custom function selector is required.

Event method information is provided by the Function Selector.

The export will use the default JMS function selector class.

To use a custom Function Selector, edit the . import or the . export file.

This will be used in the function selector later.

So, no function selector is needed.

We can use the default Function Selector for data binding invocation or implement a custom Function Selector.

Listing 1 shows the function selector code.

This is what the function selector does.

Listing 1 shows an extract of the function selector code that comes with our example