IBM Integration Bus, Version 10.0.0.0 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS


User-defined extensions execution model

The execution model is the system used to start message flows through a series of nodes.

When an integration server is initialized, the appropriate loadable implementation library (LIL) files and Plug-in Archive (PAR) files are made available to the runtime environment. The integration server runtime process starts, and creates a dedicated configuration thread. You are responsible for ensuring that a user-defined node is thread-safe. If a node updates a variable across multiple threads, appropriate locking must be in place. Do not compromise this threading model in your implementation of user-defined nodes. Consider the following points:

As an example, consider a message flow in which you use both user-defined nodes and parsers. You use a user-defined node to process messages, and a user-defined parser to parse messages; both the node and parser contain implementation functions. The integration node calls the implementation functions, or callback functions, when certain events occur:

The integration node invokes the user-defined parser on one of its implementation functions, for example cpiParseFirstChild. This function instructs the parser to build the parse tree. The parser builds the tree by invoking utility functions that create elements in the parse tree, for example cpiCreateElement. The parser can be called many times by the integration node.


as01540_.htm | Last updated 2015-03-27 19:27:16