Explanation: When you create files that define message
flow resources in the IBM Integration Toolkit,
the overall file path length of those files must not exceed 256 characters,
because of a Windows file system limitation. If you have a message flow that includes resource files that
have a path length that exceeds 256 characters, the message flow cannot
be compiled when you try to add it to a BAR file, and therefore cannot
be deployed.
You might also be affected by this restriction
when you use the Adapters Connection wizard; names discovered and
returned by the EIS can be very long. The Adapters Connection wizard
attempts to write these files to the message set on the local file
system, but their path exceeds the operating system limit, and the
files appear corrupted.