See information about the latest product version
Moving from WebSphere Message Broker on a distributed system to z/OS
Define resources for WebSphere® Message Broker for z/OS® and move your message flows.
After reviewing your requirements, re-create your broker on z/OS and deploy your message flows and execution groups to the broker on z/OS. If you have extended WebSphere Message Broker in a distributed environment with user-defined parsers or message processing nodes, port them to run under z/OS.
- Floating point conversion: z/OS runs under z/OS floating point format, so floating point operations on z/OS run in a different range and accuracy from distributed systems.
- Administration commands are partially implemented as console commands and partially as JCL commands. Some commands provide both options.
- Event log messages: All address spaces have a JOBLOG where messages appear. In addition to this, all messages appear on the SYSLOG, with important operator messages being filtered to the console through MPF (Message Processing Facility).
For information about message flow transactionality, see Message flow transactions.
Moving user applications
You can write your own applications to work with WebSphere Message Broker. If these applications use the common subset of functionality of all WebSphere Message Broker brokers, no migration is necessary. If you are using functionality that is available on some WebSphere Message Broker systems only, for example message segmentation and WebSphere MQ message groups, be aware that WebSphere Message Broker for z/OS does not provide support for this migration.