Top tip when planning a migration from WebSphere MQ File Transfer Edition V7.0.4
firstname.lastname@example.org 12000048MT Visits (2209)
With the WebS
WebSphere MQ File Transfer Edition Fix Packs added a number of enhancements and new pieces of functionality to the product (such as the ability to transfer a 100MB file to a single message, and prioritize existing managed transfers over new transfer requests). Details of these enhancements and new functionality can be found here. The new function and behaviour was disabled by default, and could be enabled by adding the entry:
to the inst
These enhancements and pieces of new function have been integrated into the WebSphere MQ V7.5 (and later) Managed File Transfer component, and have become the expected behaviour. In some cases, this has caused agents which have been migrated from WebSphere MQ File Transfer Edition V7.0.4 to behave in a slightly different way to the way they worked before. This has impacted the time taken to migrate these agents to the new release. A good example of this can be found in APAR IT12728.
If you are planning a migration from WebSphere MQ File Transfer Edition V7.0.4, then it is worth enabling the new functionality on your V7.0.4 agents first, by adding the entry:
to the installation properties file for your installation, to ensure that they work as expected. If they do, then the migration to the new release should be relatively smooth. However, if the agent starts behaving unexpectedly, then you should allow a bit longer for your migration in order to get the issues resolved.