Node and parser factory behavior

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:

Before the node factory is returned, the following functions are called:

  1. cniCreateNodeFactory

    This function creates a single instance of the node factory in the message broker.

  2. cndDefineNodeClass

    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:

  1. cpiCreateParserFactory

    This function creates a single instance of the named parser factory in the message broker.

  2. cpiDefineParserClass

    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.

See the following topics for information on these functions:
Related concepts
Planning user-defined extensions
Planning user-defined input nodes
Planning user-defined message processing nodes
Planning user-defined output nodes
Planning user-defined parsers
Designing user-defined extensions
User-defined extensions in the runtime environment
C user-defined input node life cycle
Java user-defined input node life cycle
User-defined input nodes
User-defined message processing nodes
User-defined output nodes
User-defined parsers
Related tasks
Creating an input node in C
Creating a message processing or output node in C
Creating a parser in C