Configuring the Initiator Default Host

You can enable or disable protocols, or edit protocol configurations for hosts using Protocols tab.

To create a host, see TIBCO BusinessConnect™ Container Edition Trading Partner Management, Creating a Host.

To configure the EZComm protocol of a host, perform the following steps:

Procedure
  1. On the Hosts page, click on the host name whose EZComm protocol you wish to configure.
  2. On the Edit Host page, select the EZComm business protocol and click Edit Configurations.
  3. In the General tab, select the AS2 identifier from the drop-down list. If there are no AS2 Identifiers found in the drop-down list, perform the following steps.
    Note: An identifier to use in the AS2-From header field of the HTTP message. This identifier should be mutually agreed upon between trading partners.
    1. To add new identifier, click add icon in the General tab.
    2. In the new dialog box, enter the following details in the Add New tab.
      Add New
      Fields Description
      Domain Type Select the type of the domain from the drop-down list.
      ID Enter an ID for the selected domain name.
    3. Click Add.

      The list of domains and their respective IDs are displayed in the Identifiers List tab. You can search or delete one or more identifiers from the list.

  4. In the General tab, after you have selected the AS2 identifier from the drop-down list, enter the host's email address in the Valid Email Address List field.
    Note: You can assign multiple email address list.
  5. Select the following check boxes:
    Option Description
    Allow override of filename via HTTP parameter If this check box is selected, and a file reference is being passed from the private process, then the name of the file is passed on to the Responder in an HTTP header called filename.

    Each partner has this check box. If it is selected and there is a fileName field in the HTTP message header or in QueryString (in that order), the message is written to a fileName file. This file is created in the shared directory located under the partner’s name directory. The file size is irrelevant in this case.

    Note: This feature is fully supported for the Notify and Asynchronous Request Response operations. For the Synchronous Request Response operations, only request can send the filename to the partner while the partner cannot send the filename on the response: a synchronous response cannot be written to the file that the partner wants.
    Duplicate Detection for Outbound If selected, all incoming private process messages and the outgoing responses are checked for duplicate detection.

    If a request is found to be a duplicate, the transaction is terminated and an error advisory is sent.

    Duplicate Detection for Inbound All incoming requests for Responder and Initiator are checked for duplicates.

    If any duplicates are found, the duplicate field in the private process message is set to true.

  6. Click Save.