This section contains details on how to implement a user-defined node or parser to enhance the functionality of WebSphere Message Broker.
The files you create and then distribute are:
On Windows systems, a dynamic link library (DLL), named with a file type of '.lil'.
On Linux systems, a shared object, again with a file type of '.lil'.
On UNIX systems, a shared object, again with a file type of '.lil'.
On z/OS, a shared object, with a file type of '.lil'.
For Java nodes, a Java Archive file (JAR), with a file type of '.jar'.
A C user-defined extension implements a node or parser factory that can support multiple nodes or parser types. For more information refer to node and parser factory behavior. Java users do not need to write a node factory.
The system loads the user-defined extension when the broker initializes. This invokes the registration functions in the user-defined extension so that the broker understands what nodes or parsers the user-defined extension supports.
For user-defined nodes only, the developer needs to create a workbench plug-in as well as the runtime LIL or JAR file. This adds the user-defined node to the node palette in the Message Flow editor, and allows the new node to be used in message flows. See Creating the user interface representation of a user-defined node in the workbench for more details. This step is not needed for user-defined parsers.
The following table shows the topics that you must read based on the type of user-defined extension that you want to create:
Action | Topics to view |
---|---|
To use one of the Java sample nodes: | |
To use one of the C sample nodes: | |
To use the sample parser: | |
To create your own Java node using the workbench: | |
To create your own C node: |
|
To create your own parser: |
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
as09940_ |