Command environment - Windows platforms

On Windows platforms the components run as services, so do not inherit your command prompt environment; however, the components run mqsiprofile before starting.

You must not change the location of the mqsiprofile command, or make user modifications to the command, as it might be replaced if you install service, or an update, to the product. If you need to run your own settings, add a script to the profiles directory as described below.

mqsiprofile can call additional user-written scripts for you, if you place any files called *.cmd in the specific location:
 <workpath>\common\profiles 
You might want to use this method to run database environment setup scripts.

To work with a broker, you need to set up the required environment for its databases and you are recommended to do this by running the vendor-provided profile for the database manager.

Note, that on Windows platforms, the relevant environment settings are normally made to the system environment when the database product is installed.

Once your environment is set, see Configuring component databases for information on setting up your databases for use with the broker.

Ensure that your database product settings are made in the system environment, or add them as a chained script in the common\profiles directory. You then have two options:
  1. Open a Command Console by clicking Start > IBM > WebSphere Message Brokers 6.0 > Command Console This works only if you have one installation of the runtime product.
  2. Start a normal command prompt. Locate and run the mqsiprofile.cmd script from the path where you installed the product. This applies even if you have multiple installations of the runtime components; the profile you run determines which code you use.
Note the following:
  • If you have a previous version of the product on the system, ensure that you run the correct profile before using Version 6.0. The mqsiprofile command places the Version 6.0 commands and libraries at the front of your search 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 you require.
Related tasks
Configuring component databases
Setting up a command environment
Command environment - UNIX systems and Linux
Related reference
Runtime commands