IBM E02HRLL-G - WebSphere Partner Gateway Express, Administration Manual

Page: 123 / 268

To re-send a failed In document, select In document and click Resend . The
document is resubmitted either from DAE or BPE based on the failure location. For
example,
In document failures can occur in DAE in the following cases:
v
Received document size is more than the maximum size limit.
v
Non-repudiation of the received document failed.
v
Failed sending the document to BPE.
In document failures can occur in BPE in the following cases:
v Fixed inbound workflow failures
–
While unpackaging, the message failures can occur while decrypting the
message or verifying the signature. This can be caused by incorrect
configuration of certificates at the partner or hub.
– B2B capabilities are not configured for the partner.
v
Variable workflow failures
– Validation maps are not configured.
– Invalid Translation maps are configured.
Note: Documents that fail in the Receiver are resubmitted when the administrator
resolves the problem.
To re-send failed Out documents, select the Out document and click Resend . The
document is resubmitted either from BPE or Delivery Manager.
Out
document failures can occur in the following cases:
v
For a BPE failure resubmitting the Out document itself does not make sense, so
in a BPE failure the In document should be resubmitted. This ensures that
anything that was incorrect in the BPE flow that was corrected will get picked
up. An example of a correction may be in the transformation.
Out document
failures in BPE can be Fixed outbound workflow failures. Packaging of the
message can fail while encrypting or signing the message because of incorrect
certificate configurations for partner or hub.
v
For a Delivery Manager failure:
– If the problem was because of an error in the BPE flow, the In document
should be resubmitted. This ensures that any corrections in the BPE flow will
get picked up. For example, if the destination information was incorrect.
– If the failure was caused by something else, for example, the destination
transport was down, then a resubmit of the Out document can be done,
although the In document can also be resubmitted.
There is an underlying assumption that nothing has changed that would break a
re-send, especially from the DAE or BPE. For example, if the
In document is
encrypted, the certificates required to decrypt the document should not have been
changed from the certificates that were used to encrypt the document. The
administrator has to be aware of any potential consequences of the re-send.
When re-sending the In document, the document goes through the complete
workflow processing steps. For example, if a document is an AS2 Request from the
partner and an MDN is required, then an MDN is sent to the partner even though
an MDN might have already been sent the first time the document was processed.
Also duplicate document ID checking is bypassed. However, depending on the
business protocol, a
″
duplicate document ID is detected
″
warning might still be
issued.
Chapter 11. Viewing events and documents
117