Issuing commands from a program after migration

If you have programs that issue WebSphere MQ Event Broker Version 2.1 commands, this topic describes how you can run these programs unchanged after you have migrated to WebSphere Business Integration Event Broker Version 5.0.

UNIX systems

The names of WebSphere MQ Event Broker commands start with the prefix "wmqps", not "mqsi". In addition, WebSphere MQ Event Broker commands are stored in a different directory to where WebSphere Business Integration Event Broker commands are stored. If you have programs, such as shell scripts, that issue WebSphere MQ Event Broker commands, you can continue to use these programs unchanged after migration by running the shell script migration.sh, which is supplied with WebSphere Business Integration Event Broker. migration.sh creates the required symbolic links to the WebSphere Business Integration Event Broker commands.

The following table displays the fully qualified path name of migration.sh for each platform:
Platform Fully qualified path name of migration.sh
AIX /usr/opt/mqsi/sample/migration/migration.sh

HP-UX
Solaris

/opt/mqsi/sample/migration/migration.sh

Because migration.sh works by creating symbolic links, you do not need to run it again after applying a maintenance update to WebSphere Business Integration Event Broker.

Windows systems

The names of WebSphere MQ Event Broker 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, you can continue to use these programs unchanged after migration by running the batch program migration.bat, which is supplied with WebSphere Business Integration Event Broker. migration.bat makes a copy of each WebSphere Business Integration 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 Business Integration Event Broker. You must run migration.bat from this directory.

Because migration.bat works by copying commands, you must run it again after every maintenance update you apply to WebSphere Business Integration Event Broker.

Related tasks
Migrating from WebSphere MQ Event Broker Version 2.1 to WebSphere Business Integration Event Broker Version 5.0