C node implementation functions

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:
Mandatory function
cniCreateNodeContext
Optional and conditional functions

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 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
MIME MIME MIME
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
XMLNSC XMLNSC xmlnsC
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 or output node in C
Related reference
C node utility functions