See information about the latest product version
Installing user-defined extension runtime files on a broker
Install the compiled runtime files for your user-defined extension on the broker on which you want to test its function. If your user-defined node uses a custom compiler, install the user-defined node plug-in to the broker on which you want to deploy the node.
- Create and compile your user-defined extension using the procedure
described in Compiling a Java user-defined node or Compiling a C user-defined extension.
- The files that have been created for extension created in C depend
on the underlying broker operating system:
A dynamic link library (DLL), named with a file type of .lil.
A shared object, again with a file type of .lil.
A shared object, again with a file type of .lil.
A shared object, with a file type of .lil.
- For Java nodes, a Java Archive file (JAR), with a file type of .jar (on all operating systems).
- The files that have been created for extension created in C depend
on the underlying broker operating system:
- If you have created a user-defined node, you must also complete the task Creating the user interface representation of a user-defined node in the WebSphere Message Broker Toolkit.
- If your user-defined node contains a custom compiler, you must package your user-defined node project; see Packaging and distributing a user-defined node project.
This task instructs you to stop and restart brokers. This action is required in all but the two circumstances described in step 4 later in this section, although if you do stop and restart the broker, you can ensure that anyone with an interest in a particular execution group is made aware that recent changes have been made.
This task is applicable to user-defined nodes written in Java or C only. If your user-defined node contains a custom compiler, you must install the compiled runtime files and the user-defined node plug-in to the broker. If your user-defined node does not contain a custom compiler, install only the compiled runtime files to the broker.
To install runtime and user-defined node plug-in files on the broker:
The broker loads the user-defined extension files during initialization. After loading the files, the broker calls the registration functions in the user-defined extension and records what nodes or parsers the user-defined extension supports.
A C user-defined extension implements a node or parser factory that can support multiple nodes or parser types. For more information, see Node and parser factory behavior. Java users are not required to write a node factory.