IT13795: DATAPOWER WEBSERVICE PROXY WITH MQ FSH REQUEST MATCHING LOGIC MIGHT STRUGGLE WITH AMBIGUOUS RESULTS ALSO VISIBLE IN LOGS
Fixes are available
Fix packs for DataPower Service Gateway version 7.0
Fix packs for DataPower B2B Appliance version 7.0
Fix packs for DataPower Integration Appliance version 7.0
Fix packs for DataPower Gateway version 7.1
Fix packs for DataPower Gateway version 7.2
Fix packs for DataPower Gateway version 7.5
Fix packs for DataPower Gateway version 7.5.1
Closed as program error.
The user observed problems with DataPower WebService Proxy having MQ Front side Handler. In certain scenarios, the logs showed request matching attempts to an unrelated WSP MQ FSH in another application domain. In some situations, the match to the actual target WSP (or any other WSP) even failed, due to missed match criteria.
MQ Web Service Proxy requests result in a Port value of 0. If all other unique identifiers such as URL IP and Operation are the same the request may go to the first compiled WSDL.
Fix is available in 126.96.36.199, 188.8.131.52, 184.108.40.206 and 220.127.116.11 For a list of the latest fix packs available, please see: http://www-01.ibm.com/support/docview.wss?uid=swg21237631
Create another unique identifier if using MQ for a Front Side Handler on a Web Service Proxy
Reported component name
Reported component ID
NoSpecatt / Xsystem
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
Fixed component ID
Applicable component levels