Before you start
This topic is for third-party users who want to install to WebSphere Message Broker with the least possible user intervention.
In order to install a user-defined extension, the extension needs to be installed to the runtime and to the toolkit. Components can be installed to separately, or as part of one process. The components could be on different systems, so you should ensure that the end-user runs the installations on all affected systems.
To determine the toolkit version, see Detecting Installed versions of WebSphere Message Broker.
If the product is shell-sharing with another product, the installation path will be that of whichever RAD program was installed first. Use the following steps to determine the location of the toolkit.
To determine the location of the toolkit installation, you need to look at the cdi_ref.properties file, as set up by RAD. This file is installed by the Message Brokers Toolkit and by Rational Version 6.x products: The first time one of these products is installed the file is created. It is shared by all subsequent installations. If all Message Brokers Toolkit and Rational Version 6.x products are uninstalled, the file is removed when the last product is uninstalled.
Note that the value of c_wb.b_wb.location might not be the same as the value of c_wmbt_specifc.b_wmbt_specific.location. This can happen if another RAD product has been installed before WebSphere Message Broker.
If cdi_ref.properties does not exist, there are no Rational products installed, and the Message Brokers Toolkit is not installed.
To set up Message Brokers Toolkit with icons and options for a new user-defined node, you should set up a new Eclipse link file pointing to the directory containing the Eclipse plug-in files. The link file should contain one line, which is the full path of the target directory. When you create the Eclipse link file, place it in <c.wb.b_wb.location>/eclipse/links/. For example:
The file named opt/ibm/MessageBrokerToolkit/6.0/Myextension might contain the line path=/opt/My/Extension/Nodes. The directory pointed to in that line should contain the plugin fragments you have assembled using the instructions in Distributing a user-defined extension.
When you have installed the extension, restart the target workbench with the -clean option. You can do this from the command line, or by modifying the menu shortcut. You should use the -clean option whenever any changes are made to user-defined extensions, to make sure the changes are picked up by the message flow node palette. When the workbench has restarted, the new category of nodes appears on the palette of the flow editor.
You might need to detect the version of the runtime that is installed, to ensure that the correct .lil file is loaded by the correct level of the broker. See Detecting Installed versions of WebSphere Message Broker.
To add .jar or .lil files to runtime installations on WebSphere Business Integration Message Broker Version 5.0 or later, see Installing a user-defined extension on a broker domain
. For Version 2 brokers, add the plugin to <WebSphere Brokers Install Dir>/lil/ and restart the broker.
REM Added by MyExtension install, do not modify set MQSI_LILPATH=%MQSI_LILPATH%;"C:\Program Files\MyExtension\bin"
#!/bin/ksh # Added by MyExtension install, do not modify export MQSI_LILPATH=/opt/MyExtension/lil${MQSI_LILPATH:+":"${MQSI_LILPATH}}
You can test the following variables in the profile script, for example if you want to ensure that a user-defined extension only runs on a specific version of the broker.
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
as04540_ |