Tracelink University
## Breadcrumb
1. [Home](/)
2. [Resources](/resources/resource-center)
3. [TraceLink University](/resources/tracelink-university)
# Add B2B connections in XTT Link Actions
- [Download PDF](/node/632061/pdf)
- [Share](#)
- [ LinkedIn ](https://www.linkedin.com/shareArticle?mini=true&url=https://www.tracelink.com/resources/tracelink-university/add-b2b-connections-xtt-link-actions&title=Add B2B connections in XTT Link Actions&summary=Application Administrators can add and update Opus B2B connections via Extensible TraceLink Transfer Link Actions (JavaScript snippets), which allows the exchange of files between TraceLink and customer's external ERP system, e.g. &source=TraceLink "LinkedIn")
- [ Facebook ](https://www.facebook.com/share.php?u=https://www.tracelink.com/resources/tracelink-university/add-b2b-connections-xtt-link-actions&t=Add B2B connections in XTT Link Actions "Facebook")
- [ Mail ](mailto:?subject=Add B2B connections in XTT Link Actions+|+TraceLink&body=https://www.tracelink.com/resources/tracelink-university/add-b2b-connections-xtt-link-actions "Mail")
- [ Twitter ](https://twitter.com/intent/tweet?text=Add B2B connections in XTT Link Actions https://www.tracelink.com/resources/tracelink-university/add-b2b-connections-xtt-link-actions&via=TraceLink "Twitter")
#### Table of contents
Application Administrators can add and update Opus B2B connections via Extensible TraceLink Transfer Link Actions (JavaScript snippets), which allows the exchange of files between TraceLink and customer's external ERP system, e.g. NetSuite, Microsoft Dynamics (MS Dynamics), etc. Application Administrators must create an Link Action using Integration Catalog before creating the B2B connection via XTT Link Actions.
 XTT LA fetches and executes the Link Actions form Integration Catalog. For more information, see the [Integration Catalog help center](https://opus.tracelink.com/documentation/prod/en-US/integration_catalog/Content/global_topics/landing_page.htm).
Opus B2B connections do not affect existing Track & Trace Services (TTS) B2B connections. TTS apps that are available to OPUS users via Opus iFrame can continue to use their existing TTS B2B connections. Apps built on the OPUS cannot use TTS B2B connections and must create a new Opus B2B connection via XTT Link Actions.
## Add and update B2B connections
[Add and configure a General B2B connection](#)Use the General connection whenever an integration does not require custom attributes.
1. Select the Main Menu  icon.
2. Select Extensible Tracelink Transfer Link Actions.
3. Select B2B Connections in the side menu.
4. Select General.
5. Select the Add  icon. The General Connection page displays.
6. In the **General** section, fill in the following information:
- Connection Name field – Required. The unique name of the B2B connection.  All letters in the Connection Name must be in uppercase.
- Authentication Type drop-down – The type of authentication used to protect the company against unauthorized access to data. Currently, only the OAuth2 authentication type is supported.
- Token Authentication Method drop-down – The method used to authenticate the token.
-
- Body Parameters – Sends the Client Identifier and Client Secret as parameters in the token request body.
- HTTP Basic Auth – Sends the Client Identifier and Client Secret in the HTTP Basic Authorization header when calling the token endpoint.
7. Token URL field – Required. The specific endpoint provided by the ERP system where XTT Link Actions exchanges an authorization grant for an access token.
8. JWT Issuer field – Required. The ID of the entity issuing the JSON Web Token (JWT).
9. JWT Scope field – Refers to the scope claim in the JWT that specifies the permissions or operations the token allows XTT Link Actions to perform.
10. JWT Subject field – A unique identifier that authenticates XTT Link Actions.
11. JWT Audience field – Refers to the intended recipient of the token of the ERP system.
12. JWT Signing Algorithm field – Refers to the cryptographic algorithm used to sign a JWT's header and determines the token's integrity and authenticity.
13. Key Identifier field – Refers to the Key ID claim that indicates which key was used to sign the JWT. The Key ID allows XTT Link Actions to quickly identify and retrieve the correct key for signature validation.
14. Client Identifier field – Required. The unique identifier assigned to XTT Link Actions, enabling recognition and authentication during interactions with the ERP system.
15. Client Secret field – The confidential key used by XTT Link Actions to authenticate with the ERP system within the secure OAuth 2.0 framework.
16. URL field – The URL that connects with the instance of the ERP system.
17. Select the Add  icon in the JWT Custom Header Attributes section to configure non-standard attributes fields included in the header section of a JSON Web Token (JWT).
18. Fill the following fields in the JWT Custom Header Attributes side panel:
- Name field – Name of the customized attribute.
- Value field – The corresponding value of the customized attribute.
19. Select Apply to save the configuration.
20. Select the Add  icon in the JWT Custom Request Params section to configure additional, non-standard parameters included in the JWT request.
21. Fill the following fields in the JWT Custom Request Params side panel:
- Name field – Name of the customized attribute.
- Value field – The corresponding value of the customized attribute.
22. Select Apply to save the configuration.
23. Select the Add  icon in the JWT Custom Claims section to configure additional claims to the JWT.
24. Fill the following fields in the JWT Custom Claims side panel:
- Name field – Name of the customized attribute.
- Value field – The corresponding value of the customized attribute.
25. Select Apply to save the configuration.
26. Select the Add  icon in the Inbound Link Actions section to configure inbound link actions.
27. Fill the following fields in the Add Inbound Entry side panel:
- B2B Transaction Type field – Required. The type of document exchanged, (e.g. Purchase Order).
- Catalog Access Type drop-down – Required. The access type of XTT Link Actions catalog,(e.g. Marketplace, Company).
- Link Action Version field – The version of the link action.
- Polling Interval (Minutes) field – Required. The frequency at which XTT Link Actions polls data from the ERP system.
28. Select Apply to save the configuration.
29. Select the Add  icon in the Outbound Link Actions section to configure outbound link actions.
30. Fill the following fields in the Add Outbound Entry side panel:
- B2B Transaction Type field – Required. The type of document exchanged, e.g. Purchase Order.
- Catalog Access Type drop-down – Required. The access type of XTT Link Actions catalog,(e.g. Marketplace, Company).
- Link Action Version field – Required. The version of the link action.
- Number of Retries field – Required. The number of retries XTT Link Actions attempts after a failure to send the B2B message to the ERP system.
31. Select Apply to save the configuration.
32. Select the Save  icon.
#### Tips
- Contact TraceLink Support for assistance in associating a link action from Integration Catalog with the B2B connection.
[Add and configure a NetSuite B2B connection](#)1. Select the Main Menu  icon.
2. Select Extensible Tracelink Transfer Link Actions.
3. Select B2B Connections in the side menu.
4. Select NetSuite.
5. Select the Add  icon. The New NetSuite Connection page displays.
6. In the **General** section, fill in the following information:
- Connection Name field – Required. The unique name of the B2B connection.  All letters in the Connection Name must be in uppercase.
- Authentication Type drop-down – The type of authentication used to protect the company against unauthorized access to data. Currently, only the OAuth2 authentication type is supported.
-
- Token Authentication Method drop-down – The method used to authenticate the token.
-
- Body Parameters – Sends the Client Identifier and Client Secret as parameters in the token request body.
- HTTP Basic Auth – Sends the Client Identifier and Client Secret in the HTTP Basic Authorization header when calling the token endpoint.
7. Token URL field – Required. The specific endpoint provided by the NetSuite Server where XTT Link Actions exchanges an authorization grant for an access token.
8. JWT Issuer field – Required. The ID of the entity issuing the JSON Web Token (JWT).
9. Client Identifier field – Required. The unique identifier assigned to XTT Link Actions, enabling recognition and authentication during interactions with NetSuite.
10. Client Secret field – The confidential key used by XTT Link Actions to authenticate with NetSuite within the secure OAuth 2.0 framework.
11. Connection URL field – The entry point for XTT Link Actions to communicate with NetSuite.
12. SuiteQL Url field – The endpoint used by XTT Link Actions to execute SuiteQL queries, enabling the querying and extraction of NetSuite records in a structured, efficient manner.
13. Date Format field – The date format set by the NetSuite administrator during system setup.
14. Time Format field – The time format set by the NetSuite administrator during system setup.
15. Date Time Format field – The date and time format set by the NetSuite administrator during system setup.
16. Select the Add  icon in the Inbound Link Actions section to configure inbound link actions.
17.  The Link Actions are created in the Integration Manager app. For more information about how to create the Link Action see the [Integration Manager help center](https://opus.tracelink.com/documentation/prod/en-US/integration_catalog/Content/global_topics/landing_page.htm).
18. Fill the following fields in the Add Inbound Entry side panel:
- B2B Transaction Type field – Required. The type of document exchanged, (e.g. Purchase Order).
- Catalog Access Type drop-down – Required. The access type of XTT Link Actions catalog,(e.g. Marketplace, Company).
- Link Action Version field – The version of the link action.
- Polling Interval (Minutes) field – Required. The frequency at which XTT Link Actions polls data from the NetSuite application.
19. Select Apply to save the configuration.
20. Select the Add  icon in the Outbound Link Actions section to configure outbound link actions.
21.  The Link Actions are created in the Integration Manager app. For more information about how to create the Link Action see the [Integration Manager help center](https://opus.tracelink.com/documentation/prod/en-US/integration_catalog/Content/global_topics/landing_page.htm).
22. Fill the following fields in the Add Outbound Entry side panel:
- B2B Transaction Type field – Required. The type of document exchanged, e.g. Purchase Order.
- Catalog Access Type drop-down – Required. The access type of XTT Link Actions catalog,(e.g. Marketplace, Company).
- Link Action Version field – Required. The version of the link action.
- Number of Retries field – Required. The number of retries XTT Link Actions attempts after a failure to send the B2B message to the NetSuite application.
23. Select Apply to save the configuration.
24. Select the Save  icon.
#### Tips
- Contact TraceLink Support for assistance in associating a link action from Integration Catalog with the B2B connection.
[Add and configure an MS Dynamics B2B connection](#)1. Select the Main Menu  icon.
2. Select Extensible Tracelink Transfer Link Actions.
3. Select B2B Connections in the side menu.
4. Select MS Dynamics.
5. Select the Add  icon. The New MS Dynamics Connection page displays.
6. In the **General** section, fill in the following information:
- Connection Name field – Required. The unique name of the B2B connection.  All letters in the Connection Name must be in uppercase.
- Authentication Type drop-down – The type of authentication used to protect the company against unauthorized access to data. Currently, only the OAuth2 authentication type is supported.
-
- Token Authentication Method drop-down – The method used to authenticate the token.
-
- Body Parameters – Sends the Client Identifier and Client Secret as parameters in the token request body.
- HTTP Basic Auth – Sends the Client Identifier and Client Secret in the HTTP Basic Authorization header when calling the token endpoint.
7. Token URL field – Required. The specific endpoint provided by the MS Dynamics Server where XTT Link Actions exchanges an authorization grant for an access token. The value of in the Token URL must be same as the Tenant ID value, e.g. `https://login.microsoftonline.com//oauth2/v2.0/token`.
8. JWT Issuer field – Required. The ID of the entity issuing the JSON Web Token (JWT).
9. JWT Scope field – Refers to the scope claim in the JWT that specifies the permissions or operations the token allows XTT Link Actions to perform.
10. JWT Subject field – A unique identifier that authenticates XTT Link Actions.
11. JWT Audience field – Refers to the intended recipient of the token of the MS Dynamics server.
12. JWT Signing Algorithm field – Refers to the cryptographic algorithm used to sign a JWT's header and determines the token's integrity and authenticity.
13. Key Identifier field – Refers to the Key ID claim that indicates which key was used to sign the JWT. The Key ID allows XTT Link Actions to quickly identify and retrieve the correct key for signature validation.
14. Client Identifier field – Required. The unique identifier assigned to XTT Link Actions, enabling recognition and authentication during interactions with MS Dynamics.
15. Client Secret field – The confidential key used by XTT Link Actions to authenticate with MS Dynamics within the secure OAuth 2.0 framework.
16. URL field – The URL that connects with the instance of MS Dynamics ERP system.
17. Tenant ID field – The global unique identifier that identifies the instance of the MS Dynamics ERP in the Microsoft cloud.
18. Select the Add  icon in the JWT Custom Header Attributes section to configure non-standard attributes fields included in the header section of a JSON Web Token (JWT).
19. Fill the following fields in the JWT Custom Header Attributes side panel:
- Name field – Name of the customized attribute.
- Value field – The corresponding value of the customized attribute.
20. Select Apply to save the configuration.
21. Select the Add  icon in the JWT Custom Request Params section to configure additional, non-standard parameters included in the JWT request.
22. Fill the following fields in the JWT Custom Request Params side panel:
- Name field – Name of the customized attribute.
- Value field – The corresponding value of the customized attribute.
23. Select Apply to save the configuration.
24. Select the Add  icon in the JWT Custom Claims section to configure additional claims to the JWT.
25. Fill the following fields in the JWT Custom Claims side panel:
- Name field – Name of the customized attribute.
- Value field – The corresponding value of the customized attribute.
26. Select Apply to save the configuration.
27. Click the Add  icon in the Inbound Link Actions section to configure inbound link actions.
28. Fill the following fields in the Add Inbound Entry side panel:
- B2B Transaction Type field – Required. The type of document exchanged, (e.g. Purchase Order).
- Catalog Access Type drop-down – Required. The access type of XTT Link Actions catalog,(e.g. Marketplace, Company).
- Link Action Version field – The version of the link action.
- Polling Interval (Minutes) field – Required. The frequency at which XTT Link Actions polls data from the MS Dynamics application.
29. Select Apply to save the configuration.
30. Select the Add  icon in the Outbound Link Actions section to configure outbound link actions.
31. Fill the following fields in the Add Outbound Entry side panel:
- B2B Transaction Type field – Required. The type of document exchanged, e.g. Purchase Order.
- Catalog Access Type drop-down – Required. The access type of XTT Link Actions catalog,(e.g. Marketplace, Company).
- Link Action Version field – Required. The version of the link action.
- Number of Retries field – Required. The number of retries XTT Link Actions attempts after a failure to send the B2B message to the MS Dynamics application.
32. Select Apply to save the configuration.
33. Select the Save  icon.
#### Tips
- Contact TraceLink Support for assistance in associating a link action from Integration Catalog with the B2B connection.
[Add and configure a JD Edwards B2B connection](#)1. Select the Main Menu  icon.
2. Select Extensible Tracelink Transfer Link Actions.
3. Select B2B Connections in the side menu.
4. Select JD Edwards.
5. Select the Add  icon. The New JD Edwards Connection page displays.
6. In the **General** section, fill in the following information:
- Connection Name field – Required. The unique name of the B2B connection.  All letters in the Connection Name must be in uppercase.
- Authentication Type drop-down – The type of authentication used to protect the company against unauthorized access to data. Currently, only the OAuth2 authentication type is supported.
-
- Token Authentication Method drop-down – The method used to authenticate the token.
-
- Body Parameters – Sends the Client Identifier and Client Secret as parameters in the token request body.
- HTTP Basic Auth – Sends the Client Identifier and Client Secret in the HTTP Basic Authorization header when calling the token endpoint.
7. Token URL field – Required. The specific endpoint provided by the JD Edwards Server where XTT Link Actions exchanges an authorization grant for an access token.
8. JWT Issuer field – Required. The ID of the entity issuing the JSON Web Token (JWT).
9. JWT Scope field – Refers to the scope claim in the JWT that specifies the permissions or operations the token allows XTT Link Actions to perform.
10. JWT Subject field – A unique identifier that authenticates XTT Link Actions.
11. JWT Audience field – Refers to the intended recipient of the token of the JD Edwards server.
12. JWT Signing Algorithm field – Refers to the cryptographic algorithm used to sign a JWT's header and determines the token's integrity and authenticity.
13. Key Identifier field – Refers to the Key ID claim that indicates which key was used to sign the JWT. The Key ID allows XTT Link Actions to quickly identify and retrieve the correct key for signature validation.
14. Client Identifier field – Required. The unique identifier assigned to XTT Link Actions, enabling recognition and authentication during interactions with JD Edwards.
15. Client Secret field – The confidential key used by XTT Link Actions to authenticate with JD Edwards within the secure OAuth 2.0 framework.
16. URL field – The URL that connects with the instance of JD Edwards ERP system.
17. Select the Add  icon in the JWT Custom Header Attributes section to configure non-standard attributes fields included in the header section of a JSON Web Token (JWT).
18. Fill the following fields in the JWT Custom Header Attributes side panel:
- Name field – Name of the customized attribute.
- Value field – The corresponding value of the customized attribute.
19. Select Apply to save the configuration.
20. Select the Add  icon in the JWT Custom Request Params section to configure additional, non-standard parameters included in the JWT request.
21. Fill the following fields in the JWT Custom Request Params side panel:
- Name field – Name of the customized attribute.
- Value field – The corresponding value of the customized attribute.
22. Select Apply to save the configuration.
23. Select the Add  icon in the JWT Custom Claims section to configure additional claims to the JWT.
24. Fill the following fields in the JWT Custom Claims side panel:
- Name field – Name of the customized attribute.
- Value field – The corresponding value of the customized attribute.
25. Select Apply to save the configuration.
26. Select the Add  icon in the Inbound Link Actions section to configure inbound link actions.
27. Fill the following fields in the Add Inbound Entry side panel:
- B2B Transaction Type field – Required. The type of document exchanged, (e.g. Purchase Order).
- Catalog Access Type drop-down – Required. The access type of XTT Link Actions catalog,(e.g. Marketplace, Company).
- Link Action Version field – The version of the link action.
- Polling Interval (Minutes) field – Required. The frequency at which XTT Link Actions polls data from the JD Edwards application.
28. Select Apply to save the configuration.
29. Select the Add  icon in the Outbound Link Actions section to configure outbound link actions.
30. Fill the following fields in the Add Outbound Entry side panel:
- B2B Transaction Type field – Required. The type of document exchanged, e.g. Purchase Order.
- Catalog Access Type drop-down – Required. The access type of XTT Link Actions catalog,(e.g. Marketplace, Company).
- Link Action Version field – Required. The version of the link action.
- Number of Retries field – Required. The number of retries XTT Link Actions attempts after a failure to send the B2B message to the JD Edwards application.
31. Select Apply to save the configuration.
32. Select the Save  icon.
#### Tips
- Contact TraceLink Support for assistance in associating a link action from Integration Catalog with the B2B connection.
[](#)[Add and configure a Creatio B2B connection](#)1. Select the Main Menu  icon.
2. Select Extensible Tracelink Transfer Link Actions.
3. Select B2B Connections in the side menu.
4. Select Creatio.
5. Select the Add  icon. The New Creatio Connection page displays.
6. In the **General** section, fill in the following information:
- Connection Name field – Required. The unique name of the B2B connection.  All letters in the Connection Name must be in uppercase.
- Authentication Type drop-down – The type of authentication used to protect the company against unauthorized access to data. Currently, only the OAuth2 authentication type is supported.
-
- Token Authentication Method drop-down – The method used to authenticate the token.
-
- Body Parameters – Sends the Client Identifier and Client Secret as parameters in the token request body.
- HTTP Basic Auth – Sends the Client Identifier and Client Secret in the HTTP Basic Authorization header when calling the token endpoint.
7. Token URL field – Required. The specific endpoint provided by the Creatio Server where XTT Link Actions exchanges an authorization grant for an access token.
8. JWT Issuer field – Required. The ID of the entity issuing the JSON Web Token (JWT).
9. JWT Scope field – Refers to the scope claim in the JWT that specifies the permissions or operations the token allows XTT Link Actions to perform.
10. JWT Subject field – A unique identifier that authenticates XTT Link Actions.
11. JWT Audience field – Refers to the intended recipient of the token of the Creatio server.
12. JWT Signing Algorithm field – Refers to the cryptographic algorithm used to sign a JWT's header and determines the token's integrity and authenticity.
13. Key Identifier field – Refers to the Key ID claim that indicates which key was used to sign the JWT. The Key ID allows XTT Link Actions to quickly identify and retrieve the correct key for signature validation.
14. Client Identifier field – Required. The unique identifier assigned to XTT Link Actions, enabling recognition and authentication during interactions with Creatio.
15. Client Secret field – The confidential key used by XTT Link Actions to authenticate with Creatio within the secure OAuth 2.0 framework.
16. URL field – The URL that connects with the instance of Creatio ERP system.
17. Select the Add  icon in the JWT Custom Header Attributes section to configure non-standard attributes fields included in the header section of a JSON Web Token (JWT).
18. Fill the following fields in the JWT Custom Header Attributes side panel:
- Name field – Name of the customized attribute.
- Value field – The corresponding value of the customized attribute.
19. Select Apply to save the configuration.
20. Select the Add  icon in the JWT Custom Request Params section to configure additional, non-standard parameters included in the JWT request.
21. Fill the following fields in the JWT Custom Request Params side panel:
- Name field – Name of the customized attribute.
- Value field – The corresponding value of the customized attribute.
22. Select Apply to save the configuration.
23. Select the Add  icon in the JWT Custom Claims section to configure additional claims to the JWT.
24. Fill the following fields in the JWT Custom Claims side panel:
- Name field – Name of the customized attribute.
- Value field – The corresponding value of the customized attribute.
25. Select Apply to save the configuration.
26. Select the Add  icon in the Inbound Link Actions section to configure inbound link actions.
27. Fill the following fields in the Add Inbound Entry side panel:
- B2B Transaction Type field – Required. The type of document exchanged, (e.g. Purchase Order).
- Catalog Access Type drop-down – Required. The access type of XTT Link Actions catalog,(e.g. Marketplace, Company).
- Link Action Version field – The version of the link action.
- Polling Interval (Minutes) field – Required. The frequency at which XTT Link Actions polls data from the Creatio application.
28. Select Apply to save the configuration.
29. Select the Add  icon in the Outbound Link Actions section to configure outbound link actions.
30. Fill the following fields in the Add Outbound Entry side panel:
- B2B Transaction Type field – Required. The type of document exchanged, e.g. Purchase Order.
- Catalog Access Type drop-down – Required. The access type of XTT Link Actions catalog,(e.g. Marketplace, Company).
- Link Action Version field – Required. The version of the link action.
- Number of Retries field – Required. The number of retries XTT Link Actions attempts after a failure to send the B2B message to the Creatio application.
31. Select Apply to save the configuration.
32. Select the Save  icon.
#### Tips
- Contact TraceLink Support for assistance in associating a link action from Integration Catalog with the B2B connection.
[Add and configure a SAP S/4Hana B2B connection](#)1. Select the Main Menu  icon.
2. Select Extensible Tracelink Transfer Link Actions.
3. Select B2B Connections in the side menu.
4. Select SAP S/4Hana.
5. Select the Add  icon. The SAP S/4Hana Connection page displays.
6. In the **General** section, fill in the following information:
- Connection Name field – Required. The unique name of the B2B connection.  All letters in the Connection Name must be in uppercase.
- Authentication Type drop-down – The type of authentication used to protect the company against unauthorized access to data. Currently, only the OAuth2 authentication type is supported.
- Token Authentication Method drop-down – The method used to authenticate the token.
-
- Body Parameters – Sends the Client Identifier and Client Secret as parameters in the token request body.
- HTTP Basic Auth – Sends the Client Identifier and Client Secret in the HTTP Basic Authorization header when calling the token endpoint.
7. Token URL field – Required. The specific endpoint provided by SAP S/4Hana where XTT Link Actions exchanges an authorization grant for an access token.
8. JWT Issuer field – Required. The ID of the entity issuing the JSON Web Token (JWT).
9. JWT Scope field – Refers to the scope claim in the JWT that specifies the permissions or operations the token allows XTT Link Actions to perform.
10. JWT Subject field – A unique identifier that authenticates XTT Link Actions.
11. JWT Audience field – Refers to the intended recipient of the token of the SAP S/4Hana system.
12. JWT Signing Algorithm field – Refers to the cryptographic algorithm used to sign a JWT's header and determines the token's integrity and authenticity.
13. Key Identifier field – Refers to the Key ID claim that indicates which key was used to sign the JWT. The Key ID allows XTT Link Actions to quickly identify and retrieve the correct key for signature validation.
14. Client Identifier field – Required. The unique identifier assigned to XTT Link Actions, enabling recognition and authentication during interactions with the SAP S/4Hana system.
15. Client Secret field – The confidential key used by XTT Link Actions to authenticate with the SAP S/4Hana system within the secure OAuth 2.0 framework.
16. URL field – The URL that connects with the instance of the SAP S/4Hana system.
17. Select the Add  icon in the JWT Custom Header Attributes section to configure non-standard attributes fields included in the header section of a JSON Web Token (JWT).
18. Fill the following fields in the JWT Custom Header Attributes side panel:
- Name field – Name of the customized attribute.
- Value field – The corresponding value of the customized attribute.
19. Select Apply to save the configuration.
20. Select the Add  icon in the JWT Custom Request Params section to configure additional, non-standard parameters included in the JWT request.
21. Fill the following fields in the JWT Custom Request Params side panel:
- Name field – Name of the customized attribute.
- Value field – The corresponding value of the customized attribute.
22. Select Apply to save the configuration.
23. Select the Add  icon in the JWT Custom Claims section to configure additional claims to the JWT.
24. Fill the following fields in the JWT Custom Claims side panel:
- Name field – Name of the customized attribute.
- Value field – The corresponding value of the customized attribute.
25. Select Apply to save the configuration.
26. Select the Add  icon in the Inbound Link Actions section to configure inbound link actions.
27. Fill the following fields in the Add Inbound Entry side panel:
- B2B Transaction Type field – Required. The type of document exchanged, (e.g. Purchase Order).
- Catalog Access Type drop-down – Required. The access type of XTT Link Actions catalog,(e.g. Marketplace, Company).
- Link Action Version field – The version of the link action.
- Polling Interval (Minutes) field – Required. The frequency at which XTT Link Actions polls data from the SAP S/4Hana system.
28. Select Apply to save the configuration.
29. Select the Add  icon in the Outbound Link Actions section to configure outbound link actions.
30. Fill the following fields in the Add Outbound Entry side panel:
- B2B Transaction Type field – Required. The type of document exchanged, e.g. Purchase Order.
- Catalog Access Type drop-down – Required. The access type of XTT Link Actions catalog,(e.g. Marketplace, Company).
- Link Action Version field – Required. The version of the link action.
- Number of Retries field – Required. The number of retries XTT Link Actions attempts after a failure to send the B2B message to the SAP S/4Hana system.
31. Select Apply to save the configuration.
32. Select the Save  icon.
#### Tips
- Contact TraceLink Support for assistance in associating a link action from Integration Catalog with the B2B connection.
## View B2B connections
[View a list of General B2B connections](#)1. Select the Main Menu  icon.
2. Select Extensible Tracelink Transfer Link Actions.
3. Select B2B Connection in the side menu.
4. Select General.
[See the information that displays for each B2B connection](#)
- Connection Name – The name given to a General connection.
- Authentication Type – The type of authentication used to protect the company against unauthorized access to data.
- Date Created – The date and time the General connection is created.
- Last Updated – The date and time the General connection is updated.
- Created By – The name of the Application Administrator who created the General connection.
- Updated By – The name of the Application Administrator who updated the General connection.
[View a General connection](#)1. Select the Main Menu  icon.
2. Select Extensible Tracelink Transfer Link Actions.
3. Select B2B Connection in the side menu.
4. Select General.
5. Select the link for the connection name from the results table. Select Apply.
6. The View / Edit General Connection Details screen displays.
[The following fields are editable while viewing the General section:](#)- Connection Name field – Required. The name of the B2B connection.
- Authentication Type drop-down – The type of authentication used to protect the company against unauthorized access to data. Currently, only OAuth 2.0 authentication type is supported.
-
- Token Authentication Method drop-down – The method used to authenticate the token.
-
- Body Parameters – Sends the Client Identifier and Client Secret as parameters in the token request body.
- HTTP Basic Auth – Sends the Client Identifier and Client Secret in the HTTP Basic Authorization header when calling the token endpoint.
2. Token URL field – Required. The specific endpoint provided by the ERP system where XTT Link Actions exchanges an authorization grant for an access token.
3. JWT Issuer field – Required. The ID of the entity issuing the JSON Web Token (JWT).
4. Client Identifier field – Required. The unique identifier assigned to XTT Link Actions, enabling recognition and authentication during interactions with the ERP system.
5. Client Secret field – The confidential key used by XTT Link Actions to authenticate with ERP system within the secure OAuth 2.0 framework.
In the **Link Action Configuration** section, view the following fields:
7. Connection URL field – The entry point for XTT Link Actions to communicate with the ERP system.
8. SuiteQL Url field – The endpoint used by XTT Link Actions to execute SuiteQL queries, enabling the querying and extraction of ERP system records in a structured, efficient manner.
9. Date Format field – The date format set by the ERP system administrator during system setup.
10. Time Format field – The time format set by the ERP system administrator during system setup.
11. Date Time Format field – The date and time format set by the ERP system administrator during system setup.
[The following fields are editable while viewing the Inbound Link Actions section:](#)- B2B Transaction Type field – Required. The type of document exchanged, (e.g. Purchase Order).
- Catalog Access Type drop-down – Required. The access type of XTT Link Actions catalog,(e.g. Marketplace, Company).
- Link Action Version field – The version of the link action.
- Polling Interval (Minutes) field – Required. The frequency at which XTT Link Actions polls data from the ERP system.
[The following fields are editable while viewing the Outbound Link Actions section:](#)- B2B Transaction Type field – Required. The type of document exchanged, (e.g. Purchase Order).
- Catalog Access Type drop-down – Required. The access type of XTT Link Actions catalog,(e.g. Marketplace, Company).
- Link Action Version field – The version of the link action.
- Number of Retries field – Required. The number of retries XTT Link Actions attempts after a failure to send the B2B message to the ERP system.
[View a list of NetSuite B2B connections](#)1. Select the Main Menu  icon.
2. Select Extensible Tracelink Transfer Link Actions.
3. Select B2B Connection in the side menu.
4. Select NetSuite.
[See the information that displays for each B2B connection](#)
- Connection Name – The name given to a NetSuite connection.
- Authentication Type – The type of authentication used to protect the company against unauthorized access to data.
- Date Created – The date and time the NetSuite connection is created.
- Last Updated – The date and time the NetSuite connection is updated.
- Created By – The name of the Application Administrator who created the NetSuite connection.
- Updated By – The name of the Application Administrator who updated the NetSuite connection.
[View a NetSuite connection](#)1. Select the Main Menu  icon.
2. Select Extensible Tracelink Transfer Link Actions.
3. Select B2B Connection in the side menu.
4. Select NetSuite.
5. Select the link for the connection name from the results table. Select Apply.
6. The View / Edit NetSuite Connection Details screen displays.
[The following fields are editable while viewing the General section:](#)- Connection Name field – Required. The name of the B2B connection.
- Authentication Type drop-down – The type of authentication used to protect the company against unauthorized access to data. Currently, only OAuth 2.0 authentication type is supported.
-
- Token Authentication Method drop-down – The method used to authenticate the token.
-
- Body Parameters – Sends the Client Identifier and Client Secret as parameters in the token request body.
- HTTP Basic Auth – Sends the Client Identifier and Client Secret in the HTTP Basic Authorization header when calling the token endpoint.
2. Token URL field – Required. The specific endpoint provided by the NetSuite Server where XTT Link Actions exchanges an authorization grant for an access token.
3. JWT Issuer field – Required. The ID of the entity issuing the JSON Web Token (JWT).
4. Client Identifier field – Required. The unique identifier assigned to XTT Link Actions, enabling recognition and authentication during interactions with NetSuite.
5. Client Secret field – The confidential key used by XTT Link Actions to authenticate with NetSuite within the secure OAuth 2.0 framework.
In the **Link Action Configuration** section, view the following fields:
7. Connection URL field – The entry point for XTT Link Actions to communicate with NetSuite.
8. SuiteQL Url field – The endpoint used by XTT Link Actions to execute SuiteQL queries, enabling the querying and extraction of NetSuite records in a structured, efficient manner.
9. Date Format field – The date format set by the NetSuite administrator during system setup.
10. Time Format field – The time format set by the NetSuite administrator during system setup.
11. Date Time Format field – The date and time format set by the NetSuite administrator during system setup.
[The following fields are editable while viewing the Inbound Link Actions section:](#)- B2B Transaction Type field – Required. The type of document exchanged, (e.g. Purchase Order).
- Catalog Access Type drop-down – Required. The access type of XTT Link Actions catalog,(e.g. Marketplace, Company).
- Link Action Version field – The version of the link action.
- Polling Interval (Minutes) field – Required. The frequency at which XTT Link Actions polls data from the NetSuite application.
[The following fields are editable while viewing the Outbound Link Actions section:](#)- B2B Transaction Type field – Required. The type of document exchanged, (e.g. Purchase Order).
- Catalog Access Type drop-down – Required. The access type of XTT Link Actions catalog,(e.g. Marketplace, Company).
- Link Action Version field – The version of the link action.
- Number of Retries field – Required. The number of retries XTT Link Actions attempts after a failure to send the B2B message to the NetSuite application.
[View a list of MS Dynamics B2B connections](#)1. Select the Main Menu  icon.
2. Select Extensible Tracelink Transfer Link Actions.
3. Select B2B Connection in the side menu.
4. Select MS Dynamics.
[See the information that displays for each B2B connection:](#)
- Connection Name – The name given to a MS Dynamics connection.
- Authentication Type – The type of authentication used to protect the company against unauthorized access to data.
- Date Created – The date and time the MS Dynamics connection is created.
- Last Updated – The date and time the MS Dynamics connection is updated.
- Created By – The name of the Application Administrator who created the MS Dynamics connection.
- Updated By – The name of the Application Administrator who updated the MS Dynamics connection.
[View an MS Dynamics connection](#)1. Select the Main Menu  icon.
2. Select Extensible Tracelink Transfer Link Actions.
3. Select B2B Connection in the side menu.
4. Select MS Dynamics.
5. Select the link for the connection name from the results table.
6. Select Apply.
The View / Edit MS Dynamics Connection Details screen displays.
[The following fields are editable while viewing the General section:](#)- In the **General** section, fill in the following fields:
- Connection Name field – Required. The unique name of the B2B connection.  All letters in the Connection Name must be in uppercase.
- Authentication Type drop-down – The type of authentication used to protect the company against unauthorized access to data. Currently, only the OAuth2 authentication type is supported.
-
- Token Authentication Method drop-down – The method used to authenticate the token.
-
- Body Parameters – Sends the Client Identifier and Client Secret as parameters in the token request body.
- HTTP Basic Auth – Sends the Client Identifier and Client Secret in the HTTP Basic Authorization header when calling the token endpoint.
- Token URL field – Required. The specific endpoint provided by the MS Dynamics Server where XTT Link Actions exchanges an authorization grant for an access token. The value of in the Token URL must be same as the Tenant ID value. E.g. `https://login.microsoftonline.com//oauth2/v2.0/token`.
- JWT Issuer field – Required. The ID of the entity issuing the JSON Web Token (JWT).
- JWT Scope field – Refers to the scope claim in the JWT that specifies the permissions or operations the token allows XTT Link Actions to perform.
- JWT Subject field – A unique identifier that authenticates XTT Link Actions.
- JWT Audience field – Refers to the intended recipient of the token of the MS Dynamics server.
- JWT Signing Algorithm field – Refers to the cryptographic algorithm used to sign a JWT's header and determines the token's integrity and authenticity.
- Key Identifier field – Refers to the Key ID claim that indicates which key was used to sign the JWT. The Key ID allows XTT Link Actions to quickly identify and retrieve the correct key for signature validation.
- Client Identifier field – Required. The unique identifier assigned to XTT Link Actions, enabling recognition and authentication during interactions with MS Dynamics.
- Client Secret field – The confidential key used by XTT Link Actions to authenticate with MS Dynamics within the secure OAuth 2.0 framework.
- URL field – The URL that connects with the instance of MS Dynamics ERP system.
- Tenant ID field – The global unique identifier that identifies the instance of the MS Dynamics ERP in the Microsoft cloud.
[The following fields are editable while viewing the JWT Custom Header Attributes section:](#)- Name field – Name of the customized attribute.
- Value field – The corresponding value of the customized attribute.
[The following fields are editable while viewing the JWT Custom Request Params section:](#)- Name field – Name of the customized attribute.
- Value field – The corresponding value of the customized attribute.
[Following are the fields that can be edited when viewed in the JWT Custom Claims section:](#)- Name field – Name of the customized attribute.
- Value field – The corresponding value of the customized attribute.
[The following fields are editable while viewing the Inbound Link Actions section:](#)- B2B Transaction Type field – Required. The type of document exchanged, (e.g. Purchase Order).
- Catalog Access Type drop-down – Required. The access type of XTT Link Actions catalog,(e.g. Marketplace, Company).
- Link Action Version field – The version of the link action.
- Polling Interval (Minutes) field – Required. The frequency at which XTT Link Actions polls data from the MS Dynamics application.
[The following fields are editable while viewing the Outbound Link Actions section:](#)- B2B Transaction Type field – Required. The type of document exchanged, (e.g. Purchase Order).
- Catalog Access Type drop-down – Required. The access type of XTT Link Actions catalog,(e.g. Marketplace, Company).
- Link Action Version field – The version of the link action.
- Number of Retries field – Required. The number of retries XTT Link Actions attempts after a failure to send the B2B message to the MS Dynamics application.
[View a list of JD Edwards B2B connections](#)1. Select the Main Menu  icon.
2. Select Extensible Tracelink Transfer Link Actions.
3. Select B2B Connection in the side menu.
4. Select JD Edwards.
[See the information that displays for each B2B connection:](#)
- Connection Name – The name given to a JD Edwards connection.
- Authentication Type – The type of authentication used to protect the company against unauthorized access to data.
- Date Created – The date and time the JD Edwards connection is created.
- Last Updated – The date and time the JD Edwards connection is updated.
- Created By – The name of the Application Administrator who created the JD Edwards connection.
- Updated By – The name of the Application Administrator who updated the JD Edwards connection.
[View a JD Edwards connection](#)1. Select the Main Menu  icon.
2. Select Extensible Tracelink Transfer Link Actions.
3. Select B2B Connection in the side menu.
4. Select JD Edwards.
5. Select the link for the connection name from the results table.
6. Select Apply.
The View / Edit JD Edwards Connection Details screen displays.
[The following fields are editable while viewing the General section:](#)- In the **General** section, fill in the following fields:
- Connection Name field – Required. The unique name of the B2B connection.  All letters in the Connection Name must be in uppercase.
- Authentication Type drop-down – The type of authentication used to protect the company against unauthorized access to data. Currently, only the OAuth2 authentication type is supported.
-
- Token Authentication Method drop-down – The method used to authenticate the token.
-
- Body Parameters – Sends the Client Identifier and Client Secret as parameters in the token request body.
- HTTP Basic Auth – Sends the Client Identifier and Client Secret in the HTTP Basic Authorization header when calling the token endpoint.
- Token URL field – Required. The specific endpoint provided by the JD Edwards Server where XTT Link Actions exchanges an authorization grant for an access token.
- JWT Issuer field – Required. The ID of the entity issuing the JSON Web Token (JWT).
- JWT Scope field – Refers to the scope claim in the JWT that specifies the permissions or operations the token allows XTT Link Actions to perform.
- JWT Subject field – A unique identifier that authenticates XTT Link Actions.
- JWT Audience field – Refers to the intended recipient of the token of the JD Edwards server.
- JWT Signing Algorithm field – Refers to the cryptographic algorithm used to sign a JWT's header and determines the token's integrity and authenticity.
- Key Identifier field – Refers to the Key ID claim that indicates which key was used to sign the JWT. The Key ID allows XTT Link Actions to quickly identify and retrieve the correct key for signature validation.
- Client Identifier field – Required. The unique identifier assigned to XTT Link Actions, enabling recognition and authentication during interactions with JD Edwards.
- Client Secret field – The confidential key used by XTT Link Actions to authenticate with JD Edwards within the secure OAuth 2.0 framework.
- URL field – The URL that connects with the instance of JD Edwards ERP system.
[The following fields are editable while viewing the JWT Custom Header Attributes section:](#)- Name field – Name of the customized attribute.
- Value field – The corresponding value of the customized attribute.
[The following fields are editable while viewing the JWT Custom Request Params section:](#)- Name field – Name of the customized attribute.
- Value field – The corresponding value of the customized attribute.
[Following are the fields that can be edited when viewed in the JWT Custom Claims section:](#)- Name field – Name of the customized attribute.
- Value field – The corresponding value of the customized attribute.
[The following fields are editable while viewing the Inbound Link Actions section:](#)- B2B Transaction Type field – Required. The type of document exchanged, (e.g. Purchase Order).
- Catalog Access Type drop-down – Required. The access type of XTT Link Actions catalog,(e.g. Marketplace, Company).
- Link Action Version field – The version of the link action.
- Polling Interval (Minutes) field – Required. The frequency at which XTT Link Actions polls data from the JD Edwards application.
[The following fields are editable while viewing the Outbound Link Actions section:](#)- B2B Transaction Type field – Required. The type of document exchanged, (e.g. Purchase Order).
- Catalog Access Type drop-down – Required. The access type of XTT Link Actions catalog,(e.g. Marketplace, Company).
- Link Action Version field – The version of the link action.
- Number of Retries field – Required. The number of retries XTT Link Actions attempts after a failure to send the B2B message to the JD Edwards application.
[](#)[View a list of Creatio B2B connections](#)1. Select the Main Menu  icon.
2. Select Extensible Tracelink Transfer Link Actions.
3. Select B2B Connection in the side menu.
4. Select Creatio.
[See the information that displays for each B2B connection:](#)
- Connection Name – The name given to a Creatio connection.
- Authentication Type – The type of authentication used to protect the company against unauthorized access to data.
- Date Created – The date and time the Creatio connection is created.
- Last Updated – The date and time the Creatio connection is updated.
- Created By – The name of the Application Administrator who created the Creatio connection.
- Updated By – The name of the Application Administrator who updated the Creatio connection.
[View a Creatio connection](#)1. Select the Main Menu  icon.
2. Select Extensible Tracelink Transfer Link Actions.
3. Select B2B Connection in the side menu.
4. Select Creatio.
5. Select the link for the connection name from the results table.
6. Select Apply.
The View / Edit Creatio Connection Details screen displays.
[The following fields are editable while viewing the Creatio section:](#)- In the **General** section, fill in the following fields:
- Connection Name field – Required. The unique name of the B2B connection.  All letters in the Connection Name must be in uppercase.
- Authentication Type drop-down – The type of authentication used to protect the company against unauthorized access to data. Currently, only the OAuth2 authentication type is supported.
-
- Token Authentication Method drop-down – The method used to authenticate the token.
-
- Body Parameters – Sends the Client Identifier and Client Secret as parameters in the token request body.
- HTTP Basic Auth – Sends the Client Identifier and Client Secret in the HTTP Basic Authorization header when calling the token endpoint.
- Token URL field – Required. The specific endpoint provided by the Creatio Server where XTT Link Actions exchanges an authorization grant for an access token.
- JWT Issuer field – Required. The ID of the entity issuing the JSON Web Token (JWT).
- JWT Scope field – Refers to the scope claim in the JWT that specifies the permissions or operations the token allows XTT Link Actions to perform.
- JWT Subject field – A unique identifier that authenticates XTT Link Actions.
- JWT Audience field – Refers to the intended recipient of the token of the Creatio server.
- JWT Signing Algorithm field – Refers to the cryptographic algorithm used to sign a JWT's header and determines the token's integrity and authenticity.
- Key Identifier field – Refers to the Key ID claim that indicates which key was used to sign the JWT. The Key ID allows XTT Link Actions to quickly identify and retrieve the correct key for signature validation.
- Client Identifier field – Required. The unique identifier assigned to XTT Link Actions, enabling recognition and authentication during interactions with Creatio.
- Client Secret field – The confidential key used by XTT Link Actions to authenticate with Creatio within the secure OAuth 2.0 framework.
- URL field – The URL that connects with the instance of the Creatio system.
[The following fields are editable while viewing the JWT Custom Header Attributes section:](#)- Name field – Name of the customized attribute.
- Value field – The corresponding value of the customized attribute.
[The following fields are editable while viewing the JWT Custom Request Params section:](#)- Name field – Name of the customized attribute.
- Value field – The corresponding value of the customized attribute.
[Following are the fields that can be edited when viewed in the JWT Custom Claims section:](#)- Name field – Name of the customized attribute.
- Value field – The corresponding value of the customized attribute.
[The following fields are editable while viewing the Inbound Link Actions section:](#)- B2B Transaction Type field – Required. The type of document exchanged, (e.g. Purchase Order).
- Catalog Access Type drop-down – Required. The access type of XTT Link Actions catalog,(e.g. Marketplace, Company).
- Link Action Version field – The version of the link action.
- Polling Interval (Minutes) field – Required. The frequency at which XTT Link Actions polls data from the Creatio application.
[The following fields are editable while viewing the Outbound Link Actions section:](#)- B2B Transaction Type field – Required. The type of document exchanged, (e.g. Purchase Order).
- Catalog Access Type drop-down – Required. The access type of XTT Link Actions catalog,(e.g. Marketplace, Company).
- Link Action Version field – The version of the link action.
- Number of Retries field – Required. The number of retries XTT Link Actions attempts after a failure to send the B2B message to the Creatio application.
[View a list of SAP S/4Hana B2B connections](#)1. Select the Main Menu  icon.
2. Select Extensible Tracelink Transfer Link Actions.
3. Select B2B Connection in the side menu.
4. Select SAP S/4Hana.
[See the information that displays for each SAP S/4Hana B2B connection](#)
- Connection Name – The name given to a SAP S/4Hana connection.
- Authentication Type – The type of authentication used to protect the company against unauthorized access to data.
- Date Created – The date and time the SAP S/4Hana connection is created.
- Last Updated – The date and time the SAP S/4Hana connection is updated.
- Created By – The name of the Application Administrator who created the SAP S/4Hana connection.
- Updated By – The name of the Application Administrator who updated the SAP S/4Hana connection.
[View a SAP S/4Hana connection](#)1. Select the Main Menu  icon.
2. Select Extensible Tracelink Transfer Link Actions.
3. Select B2B Connection in the side menu.
4. Select SAP S/4Hana.
5. Select the link for the connection name from the results table. Select Apply.
6. The View / Edit SAP S/4Hana Connection Details screen displays.
[The following fields are editable while viewing the General section:](#)- Connection Name field – Required. The name of the B2B connection.
- Authentication Type drop-down – The type of authentication used to protect the company against unauthorized access to data. Currently, only OAuth 2.0 authentication type is supported.
-
- Token Authentication Method drop-down – The method used to authenticate the token.
-
- Body Parameters – Sends the Client Identifier and Client Secret as parameters in the token request body.
- HTTP Basic Auth – Sends the Client Identifier and Client Secret in the HTTP Basic Authorization header when calling the token endpoint.
2. Token URL field – Required. The specific endpoint provided by the SAP S/4Hana system where XTT Link Actions exchanges an authorization grant for an access token.
3. JWT Issuer field – Required. The ID of the entity issuing the JSON Web Token (JWT).
4. Client Identifier field – Required. The unique identifier assigned to XTT Link Actions, enabling recognition and authentication during interactions with the SAP S/4Hana system.
5. Client Secret field – The confidential key used by XTT Link Actions to authenticate with SAP S/4Hana system within the secure OAuth 2.0 framework.
In the **Link Action Configuration** section, view the following fields:
7. Connection URL field – The entry point for XTT Link Actions to communicate with the SAP S/4Hana system.
8. Date Format field – The date format set by the SAP S/4Hana system administrator during system setup.
9. Time Format field – The time format set by the SAP S/4Hana system administrator during system setup.
10. Date Time Format field – The date and time format set by the SAP S/4Hana system administrator during system setup.
[The following fields are editable while viewing the Inbound Link Actions section:](#)- B2B Transaction Type field – Required. The type of document exchanged, (e.g. Purchase Order).
- Catalog Access Type drop-down – Required. The access type of XTT Link Actions catalog,(e.g. Marketplace, Company).
- Link Action Version field – The version of the link action.
- Polling Interval (Minutes) field – Required. The frequency at which XTT Link Actions polls data from the SAP S/4Hana system.
[The following fields are editable while viewing the Outbound Link Actions section:](#)- B2B Transaction Type field – Required. The type of document exchanged, (e.g. Purchase Order).
- Catalog Access Type drop-down – Required. The access type of XTT Link Actions catalog,(e.g. Marketplace, Company).
- Link Action Version field – The version of the link action.
- Number of Retries field – Required. The number of retries XTT Link Actions attempts after a failure to send the B2B message to the SAP S/4Hana system.
#### Table of contents
##### Related Content
[  ](/resources/tracelink-university/add-b2b-connections)
##### Add B2B connections
Application Administrators can create and update OPUS B2B connections using AS2, SFTP, and SMTP protocols.
[View More](/resources/tracelink-university/add-b2b-connections)
[  ](/resources/tracelink-university/view-b2b-messages)
##### View B2B messages
Application Administrators and members with standard access can filter and view the B2B messages for AS2 and SFTP .
[View More](/resources/tracelink-university/view-b2b-messages)