A fix is available
APAR status
Closed as program error.
Error description
WMQ FTE Database Logger 7.0.4.2 is sending the message to the reject queue when the source agent of the transfer is a WebAgent. The reason for the rejection showed as: BFGDB0011W: The data value represented by "/transaction/originator/webUserID" could not be located in the message
Local fix
Problem summary
**************************************************************** USERS AFFECTED: This issue affects all users of WebSphere MQ File Transfer Edition and WebSphere MQ Managed File Transfer who use the Web Gateway. Platforms affected: MultiPlatform **************************************************************** PROBLEM DESCRIPTION: The user generated a file upload request using the Web Gateway. The transfer request completed successfully but when the database logger attempted to process one of the Transfer Log audit messages from this transfer request it was unable to process it and sent it to the reject queue. The reason for the rejection showed as: BFGDB0011W: The data value represented by "/transaction/originator/webUserID" could not be located in the message. This meant that a required field was either missing or in the wrong place in the Transfer Log XML message. The Web Gateway relies on knowing the user identifier of the user that initiated a transfer request. The user making the request must have been authenticated. If JEE application security was not operational then the user identifier was not provided to the Web Gateway because the user was not authentication. This meant that a null user identifier was associated with the managed transfer request and was not included in the Transfer Log publication message.
Problem conclusion
The product code has been modified to take the following two actions: 1. Ensure that a user identifier has been included on the HttpServletRequest object that is passed to the Web Gateway such that the user has been authenticated. If the user has not been authenticated such that the user identifier associated with the request is null, an exception is returned to the user and the managed transfer request not actioned. 2. Ensure that the Transfer Log XML messages conform to the relevant XML schema definition by changing the ordering of elements in the Transfer Log publications so that the element (which is a child of the element) is present before the element. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v7.0 7.0.4.5 v7.5 7.5.0.6 v8.0 8.0.0.3 The latest available FTE maintenance can be obtained from 'Fix List for WebSphere MQ File Transfer Edition 7.0' http://www-01.ibm.com/support/docview.wss?uid=swg27015313 The latest available MQ maintenance can be obtained from 'WebSphere MQ Recommended Fixes' http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037 If the maintenance level is not yet available information on its planned availability can be found in 'WebSphere MQ Planned Maintenance Release Dates' http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309 ---------------------------------------------------------------
Temporary fix
Comments
APAR Information
APAR number
IT06123
Reported component name
WMQ FILE TRANSF
Reported component ID
5724R1000
Reported release
704
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-12-18
Closed date
2015-02-22
Last modified date
2015-02-22
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WMQ FILE TRANSF
Fixed component ID
5724R1000
Applicable component levels
R704 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEP7X","label":"WebSphere MQ File Transfer Edition"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0.4","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
22 February 2015