Install user-defined extensions that you have developed yourself, or have acquired from an independent software vendor, with the minimum of user intervention.
Complete the following tasks:
You must install user-defined extensions on all appropriate IBM Integration Bus systems. If your extension is a user-defined message flow node that contains a custom compiler, you must install the compiled user-defined extension file and the user-defined node plug-in on the integration node to which you want to deploy the message flow node. 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.
If an extension writes messages to user trace, you must update the environment variable MQSI_CONSOLE_NLSPATH (Windows systems), or NLSPATH (all other systems), so that the mqsiformatlog command can find the message catalog.
Before installing a user-defined message flow node, check the version of IBM Integration Bus to which you are installing, because a specific version of the IBM Integration Bus might be a prerequisite of the user-defined extension, or it might require specific files to run.
To determine the version, see Detecting installed versions of IBM Integration Bus.
You might be required to detect the versions of IBM Integration Bus that are installed, to ensure that the correct LIL file is loaded by the correct level of the integration node. See Detecting installed versions of IBM Integration Bus.
To add .jar or .lil files to integration node installations on IBM Integration Bus Version 10.0 and later, see Installing user-defined extension runtime files on an integration node.
For more information, see mqsicreatebroker command and mqsichangebroker command.
Make this change by creating a custom environment script in the working directory:
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 must limit the scope to only appending the following variables:
On Windows: This
example shows the environment profile for MyExtension, which
is installed in C:\Program Files\MyExtension.
The script is called MyExtension.cmd and is stored in the working directory. The default location is C:\ProgramData\IBM\MQSI\common\profiles.
The Windows script contains the following content:
REM Added by MyExtension install, do not modify
set MQSI_LILPATH=%MQSI_LILPATH%;"C:\Program Files\MyExtension\bin"
On Linux and UNIX: This example shows the environment
profile for MyExtension, which is installed in /opt/MyExtension.
The script is called MyExtension.sh and
is stored in the working directory /var/mqsi/common/profiles/ (for
a shared installation) or $HOME/iibconfig/common/profiles/ (for
a single-user installation).
The Linux script contains the following content:
#!/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 runs only on a specific version of the integration node: