The task described here is for users, for example for third-party vendors, who want to install user-defined extensions with the minimum of user intervention.
Before you start
Complete the following tasks:
You must install user-defined extensions on all appropriate broker computers, and, if the extension is a user-defined node, on the toolkit computers (user-defined parsers have no toolkit component). Components can be installed separately, or as part of one process. The components can be on different systems, therefore check that the installations are completed on all affected systems.
Before installing a user-defined node, establish the version of the toolkit you are installing to, because a specific version of the toolkit could be a prerequisite of the user-defined extension, or it might require specific files to run.
To determine the toolkit version, see Detecting installed versions of WebSphere Message Broker.
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 user-defined extension runtime files on a broker.
You cannot use the -l parameter to modify the user LILPATH for 64-bit extensions. Instead, append the directory containing the directory that holds the extension files to the environment variable MQSI_LILPATH64, as described below.
You can do this by creating a custom environment script in %ALLUSERSPROFILE%\Application Data\IBM\MQSI\common\profiles on Windows, or /var/mqsi/common/profiles on UNIX and Linux. You can give the environment script any name, but the file extension must be .cmd on Windows and .sh on all other platforms. The script can perform all the operations of a shell script, but you should limit the scope to only appending the following variables:
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: