Open topic with navigation

TIBCO BusinessConnect™ Container Edition 1.2.0

# Setting Up HTTP/S for a Trading Partner

To make a transport available for a trading partner, perform the following tasks:

1. Configuring HTTP/S for a Trading Partner.
2. Select this transport for the partner in the Primary Transport field on the Business Agreements > Edit Business Agreement > Bind Protocol > Available Protocols > Edit Configurations > Transports.

## Configuring HTTP/S for a Trading Partner

To configure HTTP/S for a trading partner, perform the following steps:

Note: The following steps are only for Transport tabs in EZComm protocol and X12 protocol.

Procedure
1. On the Partner Management tile, click Partners> partner’s name.
2. In the Edit Partner window, select EZComm and click Edit Configurations.
3. On the protocol configurations page, enter the following fields for General tab:

   Configuring HTTP/S for a Trading Partner: General Tab
   Field | Description
   --- | ---
   AS2 Identifier | Add a new AS2 Identifier or select from the list.
   Valid Email Address List | This email address list can be a list of email addresses for this participant, separated by semicolon or by a comma. For an outbound document sent to the trading partner through SMTP transport, the first email address is used in the From header. For incoming email from the mail server, the To email address from the email is matched to one of the email addresses in this list. This only applies when using AS1, AS2, or Email transport.
   Allow override of fileName via HTTP parameter | This option only applies to the HTTP and HTTPS transports for the TIBCO BusinessConnect Container Edition -Services Plug-in. This option does not apply to the AS2 and AS1 Email transports. For more information, see TIBCO BusinessConnect Container Edition -Services Plug-in, User Guide.

4. To add the transport for the partner, click partner name > protocol link > Transport > Add Outbound Transport or transport link respectively and configure the options listed in the following table:
   Note: The fields described in the following table are applicable for all the protocols.

   Configuring HTTP/S for a Trading Partner: Transports Tab
   Field | Description
   --- | ---
   Transport Name | An identifier for these transport settings.
   Transport Type | Select the transport type from the drop-down list: HTTP or HTTPs.
   URL | The URL of the trading partner.
   HTTP 1.0 Compatible | Whether to exclude "Expect: 100 continue" in the HTTP header of the outbound HTTP/S request when the request is sent to the server of the trading partner.
   Server Certificate (HTTPS only) | The participant’s certificate used to encrypt communication.Note: You must configure the credentials in advance, before creating this transport.
   Use HTTP Basic Authentication | Enable basic authentication at the trading partner. The user name and password supplied in those fields are provided when accessing the trading partner. The trading partner will service requests only if it can validate the supplied user name and password. Note that the password is passed in plain text across the network.
   Username | Specify a user name for authenticating the host on the partner HTTP/S service.
   Password | Specify a password for authenticating the host on the partner HTTP/S service.
   Retry Count | The maximum number of times BusinessConnect Container Edition attempts to reconnect to the remote HTTP server, in case of failures.
   Retry Interval | The interval BusinessConnect Container Edition waits before another re-connect is attempted.
   Socket Timeout (seconds) | The amount of time a socket blocks on a read operation. Note: If you want to receive the timeout error when no response is received from your partner, the value in this field must be less than the value set in the Response Wait Time field in the Configuration tab of the SendRequest activity.
   Cipher Suite Grade (HTTPS only) | Select the cipher grade (strength) from the list. The following options are available: All Only Stronger Than Export Only 128-Bit and Stronger Only stronger Than 128-Bit Only 256-Bit and Stronger All ciphers are listed in TIBCO BusinessConnect Container Edition Security Guidelines, Cipher Suites.
   Can Use TLS (HTTPS only) | TLS protocol is supported. If you select this check box, TLS protocol is used to establish connection to the trading partner server.
   TLS Version (HTTPS only) | Select the version of TLS protocol. TLS protocol versions 1.0, 1.1, 1.2, and 1.3 are supported. Note: If you select TLS version 1.1 or 1.2, you have to select SUN or IBM as the security vendor for inbound and outbound socket operations.
   Can Use SSLv3 (HTTPS only) | SSL protocol version 3.0 is supported. If you select this check box, SSL protocol version 3.0 is used to establish connection to the trading partner server.
   GISB/NAESB
   GISB/NAESB Package | Select this check box to package outbound messages in the NAESB Internet ET format. By default, this check box is cleared.
   GISB/NAESB Version | Specify the GISB/NAESB version. The default value is 2.0.
   Receipt Signature Required (X12 Protocol only) | Select this check box to support the receipt signature. When you select this check box, the outbound NAESB message contains a "receipt-security-selection" data element that instructs the responder to sign the receipt (including the synchronous receipt and asynchronous error notification) that is sent back. By default, this check box is cleared.
   PGP Encrypt (X12 Protocol only) | Select this check box to enable PGP encryption. By default, this check box is selected. PGP encryption in ASCII Armor format is mandatory for requests. This setting takes effect only for a regular outbound request and not for an outbound Error Notification, which is never encrypted according to the NAESB standard.
   PGP Sign (X12 Protocol only) | Select this check box to support PGP signature. This is optional. By default, this check box is cleared. This setting takes effect only for a regular outbound request and not for an outbound Error Notification. The "receipt-security-selection" data element in the original inbound NAESB message defines whether an error notification is signed. Note that other PGP features, such as Compression and Compression Algorithm, are not configured since NAESB messages are not compressed.

5. Click Add > Save.

# Configuring Gateway Services for HTTP

To configure the Gateway services for HTTP perform the following tasks:

Procedure
1. On the System Settings tile, click Inbound Protocols
2. On the Inbound page, select HTTP protocol and click Configure Service.
3. On the Gateway Service Configurations page, click http or the Add icon to create new gateway service.
4. In the Edit Gateway Service dialog box, enter the information in the fields displayed. For more information about the fields, see TIBCO BusinessConnect Container Edition Administration Guide, Configuring Gateway Services.

Did you find this helpful?

Yes No
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO BusinessConnect™ Container Edition

Copyright © 2001-2022. TIBCO Software Inc. All Rights Reserved.