AS2 IN
Basic setting
| Options | Description |
|---|---|
| Message | |
| Receive signed or signed-encrypted messages | Select to receive inbound AS2 messages that are either signed or signed-encrypted. If you select this option and the inbound messages are not signed or signed-encrypted, then an Insufficient message security error appears for those transactions in the Course of transaction section. This error also appears in the Message Disposition Notification (MDN) if the sender requests one. By default, Receive signed or signed-encrypted messages is disabled. |
| Receive encrypted or signed-encrypted messages | Select to receive inbound AS2 messages that are either encrypted or signed-encrypted. If you select this option and the inbound messages are not encrypted or signed-encrypted, then an Insufficient message security error appears for those transactions in the Course of transaction section. This error also appears in the MDN if the sender requests one. By default Receive encrypted or signed-encrypted messages is disabled.
Note: If both Receive signed or signed-encrypted messages and Receive encrypted or signed-encrypted messages are enabled, the channel receives inbound messages that are both signed and encrypted.
|
Advanced setting
Configure the settings to identify the Flat File inbound documents you receive through the AS2-IN channel.
| Field | Description |
|---|---|
| Add custom property | |
| Key | Select a valid key to identify the Flat File document type. For example, a file name. |
| Value | Select the corresponding value for the Key. For example, sample.txt. |
To add a custom property, you must select the Custom key in the Key field, and then add the values.
To ensure that webMethods B2B Integration identifies the EDI document as the custom document type when it is received through the corresponding AS2-IN channel, set set the Key to EDICustomDocument and the Value to custom document type. For example, when you add a value for EDICustomDocument as X12 4010 850_Custom, webMethods B2B Integration recognizes the incoming document as X12 4010 850_Custom.
To ensure that webMethods B2B Integration identifies the HIPAA document when it is received through the AS2-IN channel, set the Key to SubDocType and the Value toHIPAA.
Mapping the AS2-IN Channel with a Partner
To associate a partner with an inbound channel, see Associating or Mapping an Inbound Channel with a Partner.