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

Moving from IBM Integration Bus on a distributed system to z/OS

Define resources for IBM® Integration Bus for z/OS® and move your message flows.

Read the following topics for guidance on what action you might want to take in moving part of your operations to z/OS:

After reviewing your requirements, re-create your broker on z/OS and deploy your message flows and integration servers to the broker on z/OS. If you have extended IBM Integration Bus in a distributed environment with user-defined parsers or message processing nodes, port them to run under z/OS.

Also consider the following points:

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 IBM Integration Bus. If these applications use the common subset of functionality of all IBM Integration Bus brokers, no migration is necessary. If you are using functionality that is available on some IBM Integration Bus systems only, for example message segmentation and WebSphere® MQ message groups, be aware that IBM Integration Bus for z/OS does not provide support for this migration.

ae19180_.htm |

Last updated Friday, 21 July 2017