APAR status
Closed as program error.
Error description
After attempting to start an IBM MQ v8 Managed File Transfer (MFT) protocol bridge agent that has been migrated from WebSphere MQ File Transfer Edition using the fteMigrateAgent command, the following exception is thrown: 0000001 XMLFileLoader E BFGPR0045E: A problem has occurred while parsing the E: \mqm\mqft\config\...\agents\....\ProtocolBridg ePropert ies.xml XML file. The internal MQMFT data has not been updated. The details of the error are: cvc-complex-type.2.4.a: Invalid content was found starting with element 'tns:credentialsFile'. One of '{"http: //wmqfte.ibm.com/ProtocolBridgeProperties":ftpServer, "http://wmqfte. ibm.com/ProtocolBridgeProperties":sftpServer, "http://wmqfte.ibm. com/ProtocolBridgeProperties":ftpsServer, "http://wmqfte.ibm. com/ProtocolBridgeProperties":ftpsfgServer, "http://wmqfte.ibm. com/ProtocolBridgeProperties":ftpssfgServer}' is expected. [10/06/2015 11:58:24:037 BST] 00000001 BridgeManager E BFGBR0167E: The ProtocolBridgeProperties.xml file is invalid. [10/06/2015 11:58:24:037 BST] 00000001 AgentRuntime E BFGAG0171E: The agent has ended abnormally with return code 78.
Local fix
Manually edit the ProtocolBridgeProperties.xml file for the migrated protocol bridge agent such that the tns:credentialsFile element comes before any server definition elements (tns:ftpServer, tns:ftpsServer or tns:sftpServer), as per the documented protocol bridge properties file format: http://www-01.ibm.com/support/knowledgecenter/SSFKSJ_8.0.0/com.i bm.wmqfte.doc/protocol_bridge_properties_format.htm For example, if the following incorrect ProtocolBridgeProperties.xml was output from the fteMigrateAgent command: ?xml version="1.0" encoding="UTF-8"?> then it should be manually edited to: ?xml version="1.0" encoding="UTF-8"?>
Problem summary
**************************************************************** USERS AFFECTED: This issue affects all users of the fteMigrateAgent command who migrate a WebSphere MQ File Transfer Edition (FTE) protocol bridge agent to IBM MQ v8 Managed File Transfer, and the ProtocolBridgeProperties.xml file for the agent being migrated does not contain a "tns:defaultServer" element. Platforms affected: MultiPlatform **************************************************************** PROBLEM DESCRIPTION: When using the fteMigrateAgent command in IBM MQ v8 to migrate a protocol bridge agent, the command attempted to convert the WebSphere MQ File Transfer Edition (FTE) version of the ProtocolBridgeProperties.xml file to the format defined in IBM MQ v8 Managed File Transfer. This included inserting a new "tns:credentialsFile" XML element in the output ProtocolBridgeProperties.xml file for the migrated protocol bridge agent. The XML schema ProtocolBridgeProperties.xsd defines that the tns:credentialsFile element, which is used to specify the path to a file containing credentials to be used when connecting to defined servers, must occur directly before the "tns:defaultServer" XML element, should it exists. As such, the fteMigrateAgent code attempted to locate a tns:defaultServer element in the existing WebSphere MQ FTE ProtocolBridgeProperties.xml file and used this to determine the position to insert the tns:credentialsFile element. However, the tns:defaultServer element is defined as an optional element. If it did not exist in the ProtocolBridgeProperties.xml file being migrated, then the new tns:credentialsFile element was inserted as the last child element of the tns:serverProperties XML element (before the final closing XML tag). This resulted in the tns:credentialsFile element being written to the output ProtocolBridgeProperties.xml file after all of the server definitions, which is not valid according to the schema for the file. As an example, consider the following WebSphere MQ FTE version of a valid ProtocolBridgeProperties.xml file that does not contain a tns:defaultServer element: ?xml version="1.0" encoding="UTF-8"?> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://wmqfte.ibm.com/ProtocolBridgeProperti es ProtocolBridgeProperties.xsd"> timeZone="Europe/London" locale="en-GB" fileEncoding="UTF-8" listFormat="unix" limitedWrite="false" /> fileEncoding="UTF-8" limitedWrite="false"> When invoking the fteMigrateAgent command to migrate the protocol bridge that uses this ProtocolBridgeProperties.xml file, the output IBM MQ v8 Managed File Transfer version of the file is as follows: ?xml version="1.0" encoding="UTF-8"?> Due to the fteMigrateAgent command inserting the tns:credentialsFile element in an invalid location, the migrated protocol bridge agent could not parse the ProtocolBridgeProperties.xml file upon starting.
Problem conclusion
The IBM MQ v8 Managed File Transfer code for the fteMigrateAgent command has been updated such that, for a protocol bridge agent, the tns:credentialsFile XML element is written to the migrated ProtocolBridgeProperties.xml in the correct position according to the schema for this file (ProtocolBridgeProperties.xsd). --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v8.0 8.0.0.4 The latest available 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
IT09574
Reported component name
WMQ BASE MULTIP
Reported component ID
5724H7251
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2015-06-24
Closed date
2015-07-31
Last modified date
2015-07-31
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 BASE MULTIP
Fixed component ID
5724H7251
Applicable component levels
R800 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0.0.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
31 July 2015