Add B2B connections
Extensible TraceLink Transfer Exchanges (XTT Exchanges) app is an enterprise solution available in TraceLink's Opus Ensemble release. XTT Exchanges bridges the gap between the TraceLink Network and external exchange platforms (e.g. SAP Ariba) without requiring additional integrations. Companies can continue to work with Partners on different networks while maintaining a single integration with TraceLink. This approach:
-
Maintains secure data exchange
-
Enables end-to-end transaction tracking
-
Preserves the TraceLink integrate once model
Add and update B2B connections
-
Select the Main Menu
icon. -
Select Extensible Tracelink Transfer Exchanges.
-
Select B2B Connections in the side menu.
-
Select SAP Ariba.
-
Select the Add
icon. The General Connection page displays. -
In the General section, fill in the following information:
- field – Required. The unique name of the B2B connection.
- field – Auto-populated. The OPUS URL where SAP Ariba can send inbound messages to TraceLink. This field is auto generated after the connection is created.
- field – SAP Ariba URL for XTT Exchanges to send outbound messages.
-
In the Ariba Certificatessection, fill in the following information:
- field – Required. The Privacy Enhanced Mail (PEM) server certificate chain that includes the leaf, intermediate certificates, and the root certificate.
Self-signed leaf certificates are not supported. Use certificates signed by a trusted Certificate Authority (CA). - field – A brief description to label the certificate for internal tracking.
- field – Required. The Privacy Enhanced Mail (PEM) server certificate chain that includes the leaf, intermediate certificates, and the root certificate.
-
In the Customer Certificatessection, fill in the following information:
- field – The private key or encrypted private key.
- field – The password if the private key is encrypted.
- field – Required. The Privacy Enhanced Mail (PEM) server certificate chain that includes the leaf, intermediate certificates, and the root certificate.
Self-signed leaf certificates are not supported. Use certificates signed by a trusted Certificate Authority (CA). - field – A brief description to label the certificate for internal tracking.
- field – Auto-populated. The ID of the certificate.
- field – Auto-populated. A unique identifier of the the certificate used for tracking and managing certificates.
- field – The date and time from which the certificate is considered valid. Transactions that rely on the certificate should not occur before this date.
- field – The date and time until which the certificate remains valid. After this date, the certificate is no longer considered trustworthy, and transactions relying on the certificate must cease.
View B2B connections
-
Select the Main Menu
icon. -
Select Extensible Tracelink Transfer Exchanges.
-
Select B2B Connections in the side menu.
-
Select SAP Ariba.
See the information that displays for each B2B connection
- Connection Name – The unique name of the B2B connection.
- Inbound Ariba Endpoint – The OPUS URL where SAP Ariba can send inbound messages to TraceLink.
- Outbound Ariba Endpoint – SAP Ariba URL for XTT Exchanges to send outbound messages.
- Last Updated By – The name of the Application Administrator who updated the SAP Ariba connection.
- Last Updated – The date and time the SAP Ariba connection is updated.
-
Select the Main Menu
icon. -
Select Extensible Tracelink Transfer Exchanges.
-
Select B2B Connections in the side menu.
-
Select SAP Ariba.
- Select the link for the connection name from the results table. Select .
-
The View/Edit SAP Ariba B2B Connection screen displays.
- field – Required. The unique name of the B2B connection.
- field – The OPUS URL where SAP Ariba can send inbound messages to TraceLink. This field is auto generated after the connection is created.
- field – SAP Ariba URL for XTT Exchanges to send outbound messages.
- field – Required. The Privacy Enhances Mail (PEM) server certificate chain that includes the leaf, intermediate certificates, and the root certificate.
Self-signed leaf certificates are not supported. Use certificates signed by a trusted Certificate Authority (CA). - field – A brief description to label the certificate for internal tracking.
- field – The private key or encrypted private key.
- field – The password if the private key is encrypted.
- field – Required. The Privacy Enhances Mail (PEM) server certificate chain that includes the leaf, intermediate certificates, and the root certificate.
Self-signed leaf certificates are not supported. Use certificates signed by a trusted Certificate Authority (CA). - field – A brief description to label the certificate for internal tracking.
- field – Auto-populated. The ID of the certificate.
- field – Auto-populated. A unique identifier assigned by the issuing Certificate Authority (CA).
- field – The start of the certificate validity period.
- field – The end of the certificate validity period.


