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

Broker-specific command environment: Windows systems

Extend or change the Windows environment that is used when you run a specific broker.

If you want to run your own additional environment settings for a broker, add one or more command files (with the file extension .cmd) to the work_path\config\broker_name\profiles directory, where work_path is the machine-wide IBM® Integration Bus working directory, and broker_name is the name of your broker.

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

Ensure that the broker name, and any integration servers that you create, contain only characters that are valid on your file system. You might also have to create the required directory structure.

All files that are placed into the work_path\config\broker_name\profiles directory, and that have a .cmd extension, are processed when the broker starts.

Scripts in the work_path\config\broker_name\profiles directory are run after the mqsiprofile script, and any scripts in the work_path\Common\profiles directory have run.

To diagnose any problems, a log file is written that lists the profile scripts that have been read, and the environment that is used by this broker. The log file location is work_path\Common\log\broker_name.profilelog.

Integration server profile scripts are not removed automatically when an integration server is deleted. Therefore, if you have created any integration server profile files for this broker, you must delete these profile files manually if they are no longer required.

Broker profile scripts are not removed automatically when a broker is deleted. If you no longer need the profile files that you have created, delete them manually.


bh44525_.htm | Last updated Friday, 21 July 2017