The user-defined node implements a function interface for the message broker to invoke during runtime execution. This includes functions to create a local context whenever a node instance is created, functions to set and retrieve attribute values, the function to actually perform the processing of the node itself, and functions to examine messages.
These implementation functions are called by the broker and implemented by the node.
For certain implementation functions, it might be necessary to specify the name of a parser supplied with WebSphere Business Integration Message Broker. When doing so you must use the correct class name of the parser. The following table provides a summary of the parsers, root element names, and class names for different headers.
Parser | Root element name | Class name |
---|---|---|
BLOB | BLOB | NONE |
IDOC | IDOC | IDOC |
JMSMap | JMSMap | JMS_MAP |
JMSStream | JMSStream | JMS_STREAM |
MQCFH | MQPCF | MQPCF |
MQCIH | MQCIH | MQCICS |
MQDLH | MQDLH | MQDEAD |
MQIIH | MQIIH | MQIMS |
MQMD | MQMD | MQHMD |
MQMDE | MQMDE | MQHMDE |
MQRFH | MQRFH | MQHRF |
MQRFH2 | MQRFH2 | MQHRF2 |
MQRMH | MQRMH | MQHREF |
MQSAPH | MQSAPH | MQHSAP |
MQWIH | MQWIH | MQHWIH |
MRM | MRM | MRM |
Properties | Properties | PropertyParser |
SMQ_BMH | SMQ_BMH | SMQBAD |
XML | XML | XML |
XMLNS | XMLNS | XMLNS |
This section covers the following functions:
Related concepts
Planning user-defined extensions
Designing user-defined extensions
User-defined Input nodes
User-defined message processing nodes
User-defined output nodes
Related tasks
Creating an input node in C
Creating a message processing node in C
Related reference
C language node utility functions
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
as07410_ |