General

Specify the interchange qualifier and ID to use for this trading partner.

• For outbound documents, the qualifier and ID are specified as the interchange receiver qualifier and ID in the interchange header.
• For inbound documents, the interchange sender qualifier and ID are used to identify the sender. To add a default interchange qualifier ID:

1. Click the Add New Identifier icon.
2. Click the Add New tab.
3. Select a qualifier from the Identifiers List.
4. Enter the mandatory domain name. This is mapped to the Interchange Qualifier used by the trading partner.
5. Enter the mandatory identity for the partner in the ID field. This is mapped to the partner’s Interchange ID. For example, 123456789 is the fictitious D-U-N-S number used in the tutorial.
6. Click Add.
7. Select the new Interchange Qualifier ID from the list.

Specify an identifier to use in the AS2-To header field of the HTTP message. This identifier must be mutually agreed upon between trading partners. This identifier can be an interchange ID. This only applies when using AS2 Transport. Add New To use a new AS2 identifier:

1. Click the Add New Identifier icon.

2. Click the Add New tab.

3. Enter a name of the AS2 identity.

4. Select the new AS2 identifier from the list.

Specify the common code identifier to use in the "to" data element of the outbound NAESB packaged HTTP message. It must also be identical to the "from" data element of the inbound NAESB packaged HTTP message from this partner. This identifier must be mutually agreed upon between trading partners who use NAESB packaging. DUNS numbers are used for common code identifiers.

To add a common code identifier:

1. Click the Add New Identifier icon.
2. Click the Add New tab.

3. Enter a DUNS number of the DUNS identity.

4. Click Add.

Select this check box to validate inbound EDI documents before TIBCO BusinessConnect Container Edition converts and forwards them to the private process. This involves using the guidelines configured in the configuration store to validate inbound EDI data.

By default, this check box is selected.

Select this check box to disable EDI to XML conversion of inbound documents. The validation of inbound X12 documents occur using the guidelines configured in the configuration store. However, the XML file corresponding to the inbound X12 data is not generated. The ResponderRequest message is still sent to the private process. However, the request attribute of the ResponderRequest message is not populated.

This option must be used when XML conversion of the EDI data is not required. Using this option reduces memory utilization and improves performance.

By default, this check box is cleared.

Select this check box to enable detection for duplicate inbound transactions.

By default, this check box is cleared.

When you select this check box, all inbound transactions that are received from the trading partner are checked to see whether a duplicate is received and appropriately marked in the RESPONDER.REQUEST PP message. The duplicate attribute in ResponderRequest is marked as true if the same message is received from the trading partner.

X12 has the following attributes: Trading Partner Name, operationID, transactionName, whole transaction (only the ST to SE segments for X12), host initiates flag, interchange control number, group control number, and transaction control number.

Specify a list of interchange qualifiers and identifiers supported for this trading partner.

Normally, only interchanges with the qualifier and identifier specified in the Default Interchange Qualifier - ID field are supported for a trading partner. When a trading partner uses multiple interchange qualifiers and IDs, the additional qualifiers and IDs to be supported can be specified in this field. To specify the allowable list of identities, follow the following syntax: Qualifier:ID[;Qualifier:ID]

Select one item from the list to specify what kind of messages that you expect from this partner for this particular transaction set.

In the list, the following options are available:

• None
• Plain Text Only
• Signed Only
• Encrypted Only
• Signed And Encrypted

For example, if you expect only signed messages for this particular transaction set from a partner, but the partner, or someone posing as the partner, sends this particular transaction set in a plain text message, TIBCO BusinessConnect Container Edition rejects the message. If a message is rejected, it is logged as an ERROR transaction, and an error advisory is published. The rejected message is not published to the Responder private process.

Specify the type of encoding for inbound EDI data.

• If inbound EDI data contains the BOM header, such as UTF-8 and UTF-16 encoding, TIBCO BusinessConnect Container Edition - EDI Protocol powered by Instream gets the encoding from the BOM header regardless of what value you set in this field.

• If inbound EDI data does not contain the BOM header, such as ISO-8859-1 and US-ASCII encoding, TIBCO BusinessConnect Container Edition - EDI Protocol powered by Instream checks whether the value in this field is set.

— If you set a value in this field, TIBCO BusinessConnect Container Edition - EDI Protocol powered by Instream uses the specified encoding type to process inbound EDI data.

— If no value is set in this field, TIBCO BusinessConnect Container Edition - EDI Protocol powered by Instream uses the system encoding of the TIBCO BusinessConnect Container Edition Interior Server engine to process inbound EDI data.

Select this check box to validate outbound EDI documents before TIBCO BusinessConnect Container Edition converts and forwards them to the trading partner. This involves using the guidelines configured in the configuration store to validate outbound EDI data.

By default, this check box is cleared.

When you select this check box:

• For the XML payload sent from private processes, both transaction values are validated as well as the envelope information.
• For EDI payload sent from private processes, the whole EDI document with envelope is validated.
• For Publish Information to Insight Reporting to take effect, you must select this check box.

Select one item from the list to specify how duplicate documents from private processes are handled. All attributes contribute to detect whether a message is as duplicate or not.

None No outbound duplicate detection is performed.

Allow to TP If a duplicate document is sent, the message is marked as duplicate and returned to the private process through an attribute in the InitiatorResponse message. The message is sent to the trading partner.

Deny to TP If a duplicate document is sent, the message is marked as duplicate and returned to the private process through an attribute in the InitiatorResponse message. The message is not sent to the trading partner.

Specify the type of encoding for outbound XML to EDI data.

This field is mandatory.

The default value is US-ASCII.

Select this check box to add the BOM for UTF encoding.

By default, this check box is selected.