Message flow porting
If you have configured a message
flow that runs on a broker on a distributed system, and you now want
to deploy it to a broker that runs on z/OS®,
you might have to take additional actions to port the flow successfully.
Consider the following resources and attributes:
- WebSphere® MQ queue manager and queue
names
- WebSphere MQ imposes some restrictions
for resource names on z/OS:
- The queue manager name cannot be greater than four characters.
- All queue names must be in uppercase. Although using quotation
marks preserves the case, certain WebSphere MQ activities
on z/OS cannot find the queue
names being referenced.
For more information about configuring on z/OS, refer to the Concepts
and Planning Guide section of the WebSphere MQ Version 7 product documentation online
- File system references
- File system references must reflect a UNIX file path. If you deploy a
message flow to z/OS that you
have previously run on Windows,
you might have to make changes. If you have previously deployed the
message flow to a UNIX system
(AIX®, Linux, Solaris, or HP-UX), you do not have to make any
changes.
- Databases
- If the message flow accesses one or more databases, it might be
subject to some restrictions based on the system on which the database
is defined. These restrictions are described in Database locations.