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

Command environment: Windows systems

Set up the Windows environment to run IBM® Integration Bus commands.

On Windows systems, the components run as services, therefore they do not inherit the environment that is set for the command prompt from which you start them. The components run the mqsiprofile command when they start, which completes the environment initialization.

The mqsiprofile command is located in the directory install_dir\bin.

You must not change the location of the mqsiprofile command, or make user modifications to the command, because it might be replaced if you install service, or an update, to the product.

If you need to run your own settings, add one or more command files (with the file extension .cmd) to the directory work_path\Common\profiles, where work_path identifies the machine-wide IBM Integration Bus working directory.

To verify the machine-wide IBM Integration Bus working directory, enter the following command in a command console:

echo %MQSI_WORKPATH%

When mqsiprofile runs, it automatically calls any additional user-written scripts in this directory.

A typical reason for adding scripts is to configure access to databases from deployed message flows. For more information, see Running database setup scripts.

When you have configured any additional setup, you can use one of the following methods to initialize the runtime environment for components and commands:

If you have only one installation of the runtime product, open a command console by clicking Start > All Programs > IBM Integration Bus 9.0 > Command Console. The mqsiprofile command initializes the environment and invokes any additional scripts in the common\profiles directory.
If you have one or more installations of the runtime product, open a command prompt window. Locate and run the mqsiprofile.cmd script in the directory in which you installed the appropriate product. The mqsiprofile command initializes the environment and invokes any additional scripts in the common\profiles directory.

Check whether the following conditions apply to your environment:

If you have a previous version of the product on this system, ensure that you run the correct profile before using Version 9.0. The mqsiprofile command places the Version 9.0 commands and libraries at the front of your search path, and invokes any user profiles that you have supplied which can override any combination of PATH, CLASSPATH, or library PATH.
If you use the same user ID, and you run multiple profiles (from multiple different installations or versions), you might get unexpected results. Log off and log on again before you run the specific profile that you require.

Running database setup scripts

A broker might require access to databases from deployed message flows.

When you install a database product on Windows, the relevant settings are typically made to the system environment. However, some database managers provide a profile to perform this setup, or provide details of actions that you must take in their documentation. Always check the database product documentation for environment setup details; the information provided here is for general guidance only.

If a profile is provided for the database that you are using, complete the following steps:

If you can update the profile to provide permanent values for the details that are required (for example, the database server name or the installation directory):
1. Complete the changes to the database profile.
2. Copy the profile file to the directory work_path\Common\profiles.
If you cannot update the profile permanently, but need to make changes each time, you must run it independently of the mqsiprofile command before you start the component.

When your environment has been set up, see Working with databases for information about setting up your databases for use with the broker.

an26220_.htm |

Last updated Friday, 21 July 2017