WebSphere Message Broker, Version 8.0.0.7 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Execution group-specific command environment: Windows systems

Extend or change the Windows environment that is used when running a specific WebSphere® Message Broker.

To enable function that becomes available in WebSphere Message Broker fix packs, use the -f parameter on the mqsichangebroker command. For more information, see mqsichangebroker command.

To run your own additional environment settings for a broker, add a script (or scripts) in the %MQSI_WORKPATH%\config\<my_broker_name>\<my_eg_label>\profiles directory.

Ensure that the broker name, and any execution groups 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 placed into the %MQSI_WORKPATH%\config\<my_broker_name>\<my_eg_label>\profiles directory that have a .cmd extension, are processed when the execution group <my_eg_label> on broker <my_broker_name> starts.

Scripts in the %MQSI_WORKPATH%\config\<my_broker_name>\<my_eg_label>\profiles directory are run after the mqsiprofile script, and any scripts placed in the common\profiles directory have been run.

To diagnose any problems, a log file is written that lists the profile scripts that have been read, and the environment used by this broker. The log file location is under the work path of the broker and is located at %MQSI_WORKPATH%\common\log\<my_broker_name>.<my_eg_label>.profilelog

Execution group profile scripts are not removed automatically when an execution group is deleted. If you no longer need the profile files that you have created, delete them manually.

Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2016Copyright IBM Corporation 1999, 2016.

        
        Last updated:
        
        Last updated: 2016-05-23 14:48:13


Task topicTask topic | Version 8.0.0.7 | bh44535_