Table of Contents
Advertisement
Problem Cause: The Connection Parse XML Failure error is generated due to the
following reason: The information from the incoming document is not sufficient for
parsing the connection.
Explanation: Hub should parse the incoming document for getting the attributes
required to find the connection for the incoming XML document. Either the
connection is not configured or the proper values are not present in the incoming
XML.
Solution: To solve this problem, do the following:
v Check whether the connection is configured properly.
v Check whether the incoming document contains all the required attributes for
Technical support: For further information on this error event, visit our technical
support site at: WebSphere Partner Gateway technical support site.
Detailed information about events: To view the details of the event, click on the
event code provided.
AS Viewer
Use the AS Viewer to view packaged B2B transactions and B2B process details that
use the Applicability Statement 1, 2, or 3 (AS1, AS2, or AS3) communication
protocol. You can view the choreography of the B2B process and associated
business documents, acknowledgment signals, process state, HTTP headers, and
contents of the transmitted documents.
Like its predecessor, AS1, which defines a standard for data transmissions using
SMTP, AS2 defines a standard for data transmissions using HTTP. AS3 is a
standard for data transmission using FTP.
AS2 and AS3 describe how to connect, deliver, validate, and reply to data. They do
not interact with the content of the document, only the transport. AS2 and AS3
create a wrapper around a document so that it can be transported over the Internet
using HTTP or HTTPS for AS2, or FTP for AS3. Together, the document and
wrapper are called a message. AS2 provides signing and encryption around the
data carried within HTTP packets. Similarly, AS3 does this for the data transported
using the FTP transport. AS2 and AS3 provide an encryption base with guaranteed
delivery. AS1, AS2 and AS3 provide signing and encryption functionality.
Compression functionality is also provided.
An important component of both AS2 and AS3 is the receipt mechanism, which is
referred to as a Message Disposition Notification (MDN). The MDN ensures the
sender of the document that the recipient has successfully received the document.
The sender specifies how the MDN is to be sent back (either synchronously or
asynchronously, and signed or unsigned).
Note: When the decryption fails for an incoming encrypted AS2 document, a
failure MDN is not sent on the same connection. To correct this issue, a partner
connection must be activated , whether used or not between the two partners. The
connection created must be a AS to None connection, that is, a connection by
activating the AS B2B capability on one partner and None B2B capability on the
other, thus creating a connection and activating it. Ensure that the source gateway
on the AS side is a SMTP gateway (in case of AS1) or HTTP destination (in case of
104
IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide
identifying the connection.
Advertisement
Table of Contents
