This topic provides information on the role of the node factory and parser factory for declaring a node to the broker or defining a parser.
Each LIL has one node factory, or one parser factory, or has both. A node factory can identify many nodes, and a parser factory can identify many parsers.
When the broker loads the LIL, the following functions are called:
The initialization function, bipGetMessageflowNodeFactory, is called by the broker after the LIL has been loaded and initialized by the operating system. The bipGetMessageflowNodeFactory function calls the utility function cniCreateNodeFactory, which passes back a factory name (or group name) for all the nodes that your LIL supports.
The initialization function, bipgetparserfactory, is called by the broker after the LIL has been loaded and initialized by the operating system. The bipgetparserfactory function defines the name of the factory that the user-defined parser supports and the classes of objects, or shared object, supported by the factory. bipgetparserfactory calls the utility function cpiCreateParserFactory, which passes back a factory name (or group name) for all the parsers that your LIL supports.
Before the node factory is returned, the following functions are called:
This function creates a single instance of the node factory in the message broker.
This function defines the name of a node class that is supported by a node factory, and identifies the nodes that the node factory can create.
Before the parser factory is returned, the following functions are called:
This function creates a single instance of the named parser factory in the message broker.
This function defines the name of a parser class that is supported by a parser factory, and identifies the parsers that the factory can create.
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
as24984_ |