IBM Integration Bus - When you write Java™ code for a JavaCompute node, you can include references to other Java projects and JAR files.

To complete this task, you must have completed the following tasks:

• Add a JavaCompute node to your message flow.
• Create Java code for a JavaCompute node.

The Java code in a JavaCompute node might contain references to other Java projects in the Eclipse workspace (internal dependencies), or to external JAR files, for example the JavaMail API (external dependencies), or a set of JAXB Java object classes (internal or external). If other JAR files are referenced, you must add the files to the project class path.
See Using JAXB with a JavaCompute node for an example of a project using Java objects generated by the JAXB binding compiler.

1. Right-click the project folder for the project on which you are working, and click Properties.
2. Click Java Build Path in the left pane.
3. Click the Libraries tab.
4. Complete one of the following steps:

• To add an internal dependency, click Add JARs, select the JAR file that you want to add, then click OK.
• To add an external dependency, click Add External JARs, select the JAR file that you want to add, then click Open. Copy the JAR file to the shared-classes directory required. For more details of the shared-classes directories available and the effects of each, see Java shared classloader. If you do not copy the JAR file to a valid shared-classes directory, ClassNotFoundException exceptions are generated at run time.

You have now added a code dependency.

Reference: https://www.ibm.com/support/knowledgecenter/en/SSMKHH_9.0.0/com.ibm.etools.mft.doc/ac30280_.htm

Loads all the JAR files located within the shared-classes directories.

Loads all the JAR files located within the shared-classes directories. The precedence order of loading is dictated by the directories the JAR files are located in.

Determine the integration node workpath to use by running the mqsireportbroker command as follows:

mqsireportbroker integrationNodeName

JAR files are loaded in the following precedence order:

• For Windows
• workpath\config\<my_int_node_name>\<my_int_server_label>\shared-classes
• For Linux, UNIX, and z/OS
• workpath/config/<my_int_node_name>/<my_int_server_label>/shared-classes

• For Windows
• workpath\config\<my_int_node_name>\shared-classes

• For Linux, UNIX, and z/OS
• workpath/config/<my_int_node_name>/shared-classes
• For Windows
• workpath\shared-classes
• For Linux, UNIX and z/OS
• workpath/shared-classes

IBM Integration Bus - Filter Node

Filter Node
The “Filter” node is the simplest of the routing nodes and provides a simple “If-Then-Else” routing mechanism within a Message Flow. The “Filter” node is an ESQL node. The ESQL executed in this node must terminate with an ESQL RETURN statement. This statement must return a Boolean value. The route taken from this node depends upon the value of the RETURN statement.
This node has four output terminals. These terminals are:

•  Failure (A failure in the ESQL code)
• True (ESQL code returns a “True” value)
• False (ESQL code returns a “False” value)
• Unknown (ESQL code returns a “NULL” value or does not “RETURN” a boolean)

Note: The “Filter” node propagates an unchanged input message to an output terminal. If you are referring to the input message to interrogate its contents in a Database or Filter node, use correlation name Body to refer to the start of the message. Body is equivalent to Root followed by the parser name (for example, Root.XMLNS), which you can use if you prefer. You cannot use the Body correlation name in a DatabaseInput node.

You must use these different correlation names because there is only one message to which to refer in a Database or Filter node; you cannot create an output message in these nodes. Use a Compute node to create an output message.

Example:

CREATE FILTER MODULE HTTPInputMessageFlow_Filter

    CREATE FUNCTION Main() RETURNS BOOLEAN

    BEGIN

        

        DECLARE space1 NAMESPACE 'namespace1';

        IF Body.space1:root.space1:example = 'ABCDE' THEN

            RETURN TRUE;

        ELSE

            RETURN FALSE;

        END IF;

    END;

END MODULE;