The names of WebSphere MQ Event Broker Version 2.1 commands start with the prefix "wmqps", not "mqsi". In addition, WebSphere MQ Event Broker commands are stored in a different directory to where WebSphere Event Broker commands are stored. If you have programs, such as shell scripts, that issue WebSphere MQ Event Broker commands, continue to use these programs unchanged after migration by running the shell script migration.sh, which is supplied with WebSphere Event Broker. migration.sh creates the required symbolic links to the WebSphere Event Broker commands.
Operating system | Fully qualified path name of migration.sh |
---|---|
AIX | /usr/opt/mqsi/sample/migration/migration.sh |
HP-UX |
/opt/mqsi/sample/migration/migration.sh |
migration.sh works by creating symbolic links, so you do not need to run it again after applying a maintenance update to WebSphere Event Broker.
The names of WebSphere MQ Event Broker Version 2.1 commands start with the prefix "wmqps", not "mqsi". If you have programs, such as batch programs (or batch files), that issue WebSphere MQ Event Broker commands, continue to use these programs unchanged after migration by running the batch program migration.bat, which is supplied with WebSphere Event Broker. migration.bat makes a copy of each WebSphere Event Broker command that has an equivalent WebSphere MQ Event Broker command and gives the copied command its WebSphere MQ Event Broker name.
migration.bat is in the directory WBIEB\sample\migration, where WBIEB is the fully qualified path name of the directory where you have installed WebSphere Event Broker. You must run migration.bat from this directory.
migration.bat works by copying commands, so you must run it again after every maintenance update you apply to WebSphere Event Broker.
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ah18660_ |