Fixes are available
7.5.1.1: IBM Integration Designer V7.5.1 Fix Pack 1 for Windows
7.5.1.1: IBM Integration Designer V7.5.1 Fix Pack 1 for Linux
Version 8.0 Refresh Pack 1 for the IBM Business Process Manager products
8.0.1: IBM Integration Designer V8.0 Refresh Pack 1 for Windows
8.0.1: IBM Integration Designer V8.0 Refresh Pack 1 for Linux
APAR status
Closed as fixed if next.
Error description
USER AFFECTED: User migrating a mediation module from v6.x to v7.5.1 or later where the module contains maps that reference RPC style WSDL PROBLEM DETAILED DESCRIPTION: When migrating a mediation module from v6.x to v7.5.1 or later a migration error can occur which will leave dangling transforms in the migrated .map files. The inputs and outputs of the map will show in the source and target tree, but the transform wires will be broken due to the fact that the input and output paths were incorrectly migrated. This only happens when the maps are referencing complex types in RPC style WSDL files. Instead of the element name being used in the path, the name of the complex type is used and thus the wiring is broken in the resulting map file. The problem will be seen in map files that meet the above criteria after the migration wizard has finished executing.
Local fix
Problem summary
Fix planned for next V7.5.1 cumulative maintenance deliverable, targetting 3Q 2012. USER AFFECTED: User migrating a mediation module from v6.x to v7.5.1 or later where the module contains maps that reference RPC style WSDL PROBLEM SUMMARY: XML Map SMO path migration fails for RPC style WSDL complex types PROBLEM DETAILED DESCRIPTION: When migrating a mediation module from v6.x to v7.5.1 or later a migration error can occur which will leave dangling transforms in the migrated .map files. The inputs and outputs of the map will show in the source and target tree, but the transform wires will be broken due to the fact that the input and output paths were incorrectly migrated. This only happens when the maps are referencing complex types in RPC style WSDL files. Instead of the element name being used in the path, the name of the complex type is used and thus the wiring is broken in the resulting map file. The problem will be seen in map files that meet the above criteria after the migration wizard has finished executing. PROBLEM CONCLUSION: The problem will be fixed to ensure that the post migration paths properly reference the desired mapping inputs and outputs.
Problem conclusion
Temporary fix
Comments
APAR Information
APAR number
JR43763
Reported component name
INTEGRATION DES
Reported component ID
5725C9702
Reported release
751
Status
CLOSED FIN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-08-14
Closed date
2012-09-20
Last modified date
2012-09-20
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
R751 PSY
UP
R800 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSTLXK","label":"IBM Integration Designer"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5.1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
20 September 2012