Configuring environments without IBM Integration Bus installed

Install and run custom integration applications and other utilities on computers, when you are using a local ID only, on which you have not installed IBM® Integration Bus.

1. Ensure that the target computer has a compatible Java Runtime Environment (JRE).
   Because you are not installing IBM Integration Bus, which includes a JRE, you must use an alternative option.

   Note, that you must also set MQSI_JREPATH to the installation path of your JRE.

   Java support is defined in the IBM Integration Bus system requirements; see IBM Integration Bus system requirements.

2. Copy the following set of files from a computer that has IBM Integration Bus installed to the target computer:
   1. The IntegrationAPI.jar file from the install_dir/common/classes directory.
   2. All the .jar files from the install_dir/common/jetty/lib directory.
   3. All the .jar files from the install_dir/common/jackson/lib directory.
   4. Your custom integration applications and all configuration files, for example .broker files.
   5. If you want to run the integration node commands on the target computer, complete the following steps:
      1. Copy brokerutil.jar from the install_dirserver/classes directory.
      2. Copy the script files that start with mqsi, from the install_dirserver/bin directory. Scripts have a .bat extension on Windows or no extension on UNIX platforms.
         Note: Not all of these script files can be used to perform remote administration tasks. Check the documentation for the command that is associated with the script file to verify whether the command can be used remotely. For example, the command mqsibackupbroker can be used to administer only a local integration node.
   6. If you want to display integration node (BIP) messages in English environments other than US English, copy all BIPmsgs*.properties files from the messages directory.
3. On the target computer, use system facilities to update the CLASSPATH environment variable to include the following files:
   • The JAR file that contains the definitions of the IBM Integration API classes: IntegrationAPI.jar.
   • The JAR files that you copied from the install_dir/common/jetty/lib directory and the install_dir/common/jackson/lib directory.
   • Your applications that import the IBM Integration API classes.
   • The JAR files that contain the definitions of the IntegrationNodeConnectionParameters classes.
   • Any other required JAR files and directories. For example, if you require any of the available command utilities on the target computer, include brokerutil.jar; if you require the integration node (BIP) messages to be displayed in locales other than US English, include a directory that contains BIPmsgs*.properties.
4. Ensure that the user ID that the target computer uses has the following authorities:
   • Authority to connect to the queue manager that the integration node uses.
   • Authority to manipulate integration node objects.