Before you start
You must have a compiled user-defined extension, which was compiled using the procedure described in Compiling a Java user-defined node, or Compiling a C user-defined extension.
You must put a copy of your compiled or packaged user-defined extension file on every broker system from which you intend to use it. If all your brokers are on the same machine type, you can build the file once and distribute it to each of your systems (see Distributing a user-defined node for details of how to do this). If you have a cluster that consists of one AIX, one Solaris, and one Windows broker, you need to build the files separately on each machine type.
You can save your user-defined extension file in a directory of your choice. You must specify this directory using the mqsichangebroker or mqsicreatebroker command. If you do not specify a directory, the default location is used, as shown in the following tables.
For C user-defined extensions, store a copy of the .lil file, and it is recommended that you also store the .pdb file corresponding to the .lil file, in the following directory:
Platform | Location |
---|---|
Windows |
install_dir\bin |
UNIX platforms |
install_dir/lil |
z/OS |
install_dir/lil |
The .pdb file provides symbolic information that WebSphere Business Integration Message Broker uses when displaying stack diagnostic information in the event of access violations or other software malfunctions. This is useful when debugging any problems with your own user-defined extensions and also of use to IBM service personnel.
For Java user-defined nodes, store a copy of the .jar file in the following directory:
Platform | Location |
---|---|
Windows |
install_dir\jplugin |
UNIX platforms |
install_dir/jplugin |
z/OS |
install_dir/lil |
These directories are created during installation of WebSphere Business Integration Message Broker.
You must stop and restart each broker so that it can detect the existence of the new file.
On z/OS, also update the LILPATH variable in the mqsicompcif file with the name of the library containing the new .lil files, otherwise the LILPATH value will be reset next time you recustomize. The .lil file may require other executables, such as .dll files. These are loaded from the directory specified in the LIBPATH variable. If the LIBPATH value needs to be updated, you must change it in mqsicompcif and recustomize.
Once you have installed a node, it is referred to by its schema and name, just like a message flow.
Related concepts
User-defined extensions
Related tasks
Developing user-defined extensions
Creating the user interface representation of a user-defined node in the workbench
Testing a user-defined node
Distributing a user-defined node
Related reference
User-defined extensions
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
as10004_ |