IBM Integration Bus, Version 9.0.0.8 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Configuring environments without the Integration Bus component installed

Install and run CMP applications and other utilities on computers, when you are using a local ID only, on which you have not installed the Integration Bus component.

You can run Java™ applications that use the CMP even where you have not installed the Integration Bus component. These CMP applications include your own applications, and the following command utilities:

mqsicreateexecutiongroup
mqsideleteexecutiongroup
mqsimode
mqsipackagebar
mqsireloadsecurity; the CMP application version of mqsireloadsecurity is called mqsireloadsecurityscript.
mqsistartmsgflow
mqsistopmsgflow

To install CMP applications in an environment that does not have the Integration Bus component installed, complete the following steps:

Ensure that the target computer has a compatible Java Runtime Environment (JRE). Because you are not installing the Integration Bus component, 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 Additional software requirements.
Copy the following set of files from a computer that has the Integration Bus component installed to the target computer:
1. ConfigManagerProxy.jar from the classes directory.
2. The WebSphere® MQ Classes for Java.
  - On Windows, these classes are located in the file com.ibm.mq.jar.
  - On other platforms, these classes are located in the component's installation image.
3. Your CMP application and all configuration files, for example .broker files.
4. If you want to run the broker commands on the target computer, complete the following steps:
  1. Copy brokerutil.jar from the classes directory.
  2. Copy the required utility bat files, or shell scripts, from the bin directory. Shell scripts have a .bat extension on Windows or no extension on UNIX platforms:
    - mqsicreateexecutiongroup or mqsicreateexecutiongroup.bat
    - mqsideleteexecutiongroup or mqsideleteexecutiongroup.bat
    - mqsimode or mqsimode.bat
    - mqsipackagebar or mqsipackagebar.bat
    - mqsireloadsecurity or mqsireloadsecurityscript.bat
    - mqsistartmsgflow or mqsistartmsgflow.bat
    - mqsistopmsgflow or mqsistopmsgflow.bat
5. If you want to display broker (BIP) messages in English environments other than US English, copy all BIPmsgs*.properties files from the messages directory.
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 CMP classes, ConfigManagerProxy.jar.
- Your applications that import the CMP classes.
- The WebSphere MQ Classes for Java, com.ibm.mq.jar, and any additional JAR files required by this package.
- 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 broker (BIP) messages to be displayed in locales other than US English, include a directory that contains BIPmsgs*.properties.
Ensure that the user ID that the target computer uses has the following authorities:
- Authority to connect to the queue manager that the broker uses.
- Authority to manipulate broker objects.

Next: You can run your CMP applications, and the specified command utilities, on the target computer.

ae33102_.htm |

Last updated Friday, 21 July 2017