Time to Acknowledge
|
No |
The amount of time to wait for an MDN acknowledgment
before resending the original request. This attribute works in conjunction
with Retry Count. The units are in minutes. |
Limited to package or connection |
30 |
Retry
Count
|
No |
The number of times to send a request if an MDN
is not received. This attribute works in conjunction with Time to
Acknowledge.
For example, if this attribute is set to 3, the request can potentially
be sent four times (the initial time and then the three retries). |
Limited to package or connection |
3 |
AS
Compressed
|
No |
Compress the data. This attribute works in conjunction
with the AS Compress Before Sign attribute. |
Limited to package or connection |
No |
AS
Compress Before Sign
|
No |
Indicates whether AS compression should be applied
to both the payload and signature or only to the payload.
If you select Yes, the payload is compressed before the message
is signed. This attribute works in conjunction with the AS Compressed
attribute. |
Limited to package or connection |
Yes |
AS
Encrypted
|
No |
Indicates whether encryption should be performed.
Note: This is not the same as SSL encryption.
For the TO side of an exchange (when you are sending documents
to a partner), this specifies whether to encrypt the document.
For the FROM side of an exchange (when you are receiving documents
from a partner), if the attribute is set to Yes, an AS request sent from
the partner must be encrypted. If the attribute is set to No, the
document from the partner can be encrypted or un-encrypted.
Valid values are Yes or No.
- Yes
- Encryption is required.
- No
- Encryption is not required.
|
Limited to package or connection |
No |
AS
MDN Requested
|
No |
Specifies whether an MDN reply is required. If
set to Yes, this attribute causes the "transport Disposition-notification-to" header
to be filled in with the value from the AS MDN Email Address attribute.
Valid values are Yes and No.
- Yes
- Request an MDN.
- No
- Do not request an MDN.
|
Limited to package or connection |
Yes |
AS
MDN Email Address
|
Yes if the "AS MDN Asynchronous" attribute is
Yes and you are using AS1. |
Specifies the e-mail address for the partner
to use when sending an asynchronous MDN. This attribute is used
in conjunction with the AS MDN Requested attribute. The value of AS
MDN Email Address is used in the "Disposition-notification-to" field.
For AS1 only, this attribute works in conjunction with the AS
MDN Asynchronous attribute of the format mailto:xxx@company.com. |
Limited to package or connection |
|
AS
MDN Http Url |
Yes if the "AS MDN Asynchronous" attribute is
Yes and you are using AS2. |
This attribute applies to AS2 and is used
to specify the URL to which a partner should send an asynchronous
MDN. This attribute works in conjunction with the AS MDN Asynchronous
attribute. |
Limited to package or connection |
|
AS
MDN Asynchronous
|
No |
Specifies whether the MDN should be returned
synchronously or asynchronously. The value of this attribute affects
whether the AS MDN HTTP URL or AS MDN Email Address attribute is
used.
Valid values are Yes and No.
- Yes
- Asynchronous
- No
- Synchronous
If this attribute is Yes, the "receipt-delivery-option" field
is filled in based on the AS MDN HTTP URL attribute (for AS2) or
the AS MDN Email Address attribute (for AS1). |
Limited to package or connection |
Yes |
AS
MDN Signed |
No |
Indicates whether the request requires that
a signed MDN be returned. This attribute works in conjunction with
AS MDN Requested.
If the value is Yes, the "Disposition-notification-options:
signed-receipt-protocol" is filled in.
Valid values are Yes and No.
- Yes
- Signed MDN requested
- No
- Signed MDN is not requested
If this attribute is set to Yes, the MDN sent by the partner
has to be signed.
If this attribute is set to No, the MDN can be signed or unsigned. |
Limited to package or connection |
No |
AS Message Digest Algorithm |
No |
The message digest algorithm to use when signing.
This attribute is used in conjunction with the AS Signed and AS
MDN Signed attributes.
For signed MDNs, this value is used to fill in the "Disposition-notification-options:
signed-receipt-micalg" header. |
Limited to package or connection |
sha1 |
AS
Signed
|
No |
Specifies whether to sign the document.
For the TO side of an exchange (when you are sending documents
to a partner), this specifies whether to sign the document.
For the FROM side of the exchange (when you are receiving from
a partner) if the attribute is set to Yes, an AS request sent from the
partner must be signed. If the attribute is set to No, the document
from the partner can be signed or unsigned.
- Yes
- Sign the document
- No
- Signed document is not required
|
Limited to package or connection |
No |
AS
Business Id |
No |
The AS business ID to use in the "AS2-To" header.
If a value is not supplied, WebSphere Partner Gateway uses the recipient
business ID used in the source document.
Note: The "AS2-From" header will be
set from the original source document that came into WebSphere Partner
Gateway and that is being sent out as AS. |
Limited to package or connection |
|