Add B2B connections
Application Administrators can add and update Opus B2B connections via XTT 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), JD Edwards ERP application. Application Administrators must create an XTT Link Actions Catalog Item before creating the B2B connection via XTT Link Actions.
Contact the TraceLink implementation team for assistance in performing the one-time task of creating and associating an XTT Link Actions Catalog Item with the B2B connection.
Opus B2B connections do not affect existing Track & Trace Services (TTS) B2B connections. TTS apps that are available to Opus Platform users via Opus iFrame can continue to use their existing TTS B2B connections. Apps built on the Opus Platform cannot use TTS B2B connections and must create a new Opus B2B connection via XTT Link Actions.
Add and update B2B connections
Currently, TraceLink only supports connecting to NetSuite and Enterprise Resource Planning, Microsoft Dynamics Customer Relationship Management systems, and JD Edwards ERP application.
-
Select the Main Menu icon.
-
Select Extensible Tracelink Transfer Link Actions.
-
Select B2B Connections in the side menu.
-
Select NetSuite.
-
Select the Add icon. The New NetSuite Connection page displays.
-
In the General section, fill in the following information:
All letters in the Connection Name must be in uppercase.
field – Required. The unique name of the B2B connection. Currently, only the OAuth2 authentication type is supported.
drop-down – The type of authentication used to protect the company against unauthorized access to data.- field – Required. The specific endpoint provided by the NetSuite Server where XTT Link Actions exchanges an authorization grant for an access token.
- field – Required. The ID of the entity issuing the JSON Web Token (JWT).
- field – Required. The unique identifier assigned to XTT Link Actions, enabling recognition and authentication during interactions with NetSuite.
- field – The confidential key used by XTT Link Actions to authenticate with NetSuite within the secure OAuth 2.0 framework.
- field – The entry point for XTT Link Actions to communicate with NetSuite.
- 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.
- field – The date format set by the NetSuite administrator during system setup.
- field – The time format set by the NetSuite administrator during system setup.
- field – The date and time format set by the NetSuite administrator during system setup.
-
Click the Add icon in the Inbound Link Actions section to configure inbound link actions.
-
Fill the following fields in the Add Inbound Entry side panel:
- field – Required. The type of document exchanged, (e.g. Purchase Order).
- drop-down – Required. The access type of XTT Link Actions catalog,(e.g. Marketplace, Company).
- field – The version of the link action.
- field – Required. The frequency at which XTT Link Actions polls data from the NetSuite application.
-
Click
to save the configuration. -
Click the Add icon in the Outbound Link Actions section to configure outbound link actions.
-
Fill the following fields in the Add Outbound Entry side panel:
- field – Required. The type of document exchanged, e.g. Purchase Order.
- drop-down – Required. The access type of XTT Link Actions catalog,(e.g. Marketplace, Company).
- field – Required. The version of the link action.
- field – Required. The number of retries XTT Link Actions attempts after a failure to send the B2B message to the NetSuite application.
-
Click
to save the configuration. -
Click the Save icon.
Tips
-
Contact the TraceLink Support for assistance in associating a link action from the Catalog Manager with the B2B connection.
-
Select the Main Menu icon.
-
Select Extensible Tracelink Transfer Link Actions.
-
Select B2B Connections in the side menu.
-
Select MS Dynamics.
-
Select the Add icon. The New MS Dynamics Connection page displays.
-
In the General section, fill in the following information:
All letters in the Connection Name must be in uppercase.
field – Required. The unique name of the B2B connection. Currently, only the OAuth2 authentication type is supported.
drop-down – The type of authentication used to protect the company against unauthorized access to data.- Tenant ID value, e.g.
https://login.microsoftonline.com/<Tenant ID>/oauth2/v2.0/token
. 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 <Tenant ID> in the Token URL must be same as the - field – Required. The ID of the entity issuing the JSON Web Token (JWT).
- field – Refers to the scope claim in the JWT that specifies the permissions or operations the token allows XTT Link Actions to perform.
- field – A unique identifier that authenticates XTT Link Actions.
- field – Refers to the intended recipient of the token of the MS Dynamics server.
- field – Refers to the cryptographic algorithm used to sign a JWT's header and determines the token's integrity and authenticity.
- 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.
- field – Required. The unique identifier assigned to XTT Link Actions, enabling recognition and authentication during interactions with MS Dynamics.
- field – The confidential key used by XTT Link Actions to authenticate with MS Dynamics within the secure OAuth 2.0 framework.
- field – The URL that connects with the instance of MS Dynamics ERP system.
- field – The global unique identifier that identifies the instance of the MS Dynamics ERP in the Microsoft cloud.
-
Click 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).
-
Fill the following fields in the JWT Custom Header Attributes side panel:
- field – Name of the customized attribute.
- field – The corresponding value of the customized attribute.
-
Click
to save the configuration. -
Click the Add icon in the JWT Custom Request Params section to configure additional, non-standard parameters included in the JWT request.
-
Fill the following fields in the JWT Custom Request Params side panel:
- field – Name of the customized attribute.
- field – The corresponding value of the customized attribute.
-
Click
to save the configuration. -
Click the Add icon in the JWT Custom Claims section to configure additional claims to the JWT.
-
Fill the following fields in the JWT Custom Claims side panel:
- field – Name of the customized attribute.
- field – The corresponding value of the customized attribute.
-
Click
to save the configuration. -
Click the Add icon in the Inbound Link Actions section to configure inbound link actions.
-
Fill the following fields in the Add Inbound Entry side panel:
- field – Required. The type of document exchanged, (e.g. Purchase Order).
- drop-down – Required. The access type of XTT Link Actions catalog,(e.g. Marketplace, Company).
- field – The version of the link action.
- field – Required. The frequency at which XTT Link Actions polls data from the MS Dynamics application.
-
Click
to save the configuration. -
Click the Add icon in the Outbound Link Actions section to configure outbound link actions.
-
Fill the following fields in the Add Outbound Entry side panel:
- field – Required. The type of document exchanged, e.g. Purchase Order.
- drop-down – Required. The access type of XTT Link Actions catalog,(e.g. Marketplace, Company).
- field – Required. The version of the link action.
- field – Required. The number of retries XTT Link Actions attempts after a failure to send the B2B message to the MS Dynamics application.
-
Click
to save the configuration. -
Click the Save icon.
Tips
-
Contact the TraceLink Support for assistance in associating a link action from the Catalog Manager with the B2B connection.
-
Select the Main Menu icon.
-
Select Extensible Tracelink Transfer Link Actions.
-
Select B2B Connections in the side menu.
-
Select JD Edwards.
-
Select the Add icon. The New JD Edwards Connection page displays.
-
In the General section, fill in the following information:
All letters in the Connection Name must be in uppercase.
field – Required. The unique name of the B2B connection. Currently, only the OAuth2 authentication type is supported.
drop-down – The type of authentication used to protect the company against unauthorized access to data.- field – Required. The specific endpoint provided by the JD Edwards Server where XTT Link Actions exchanges an authorization grant for an access token.
- field – Required. The ID of the entity issuing the JSON Web Token (JWT).
- field – Refers to the scope claim in the JWT that specifies the permissions or operations the token allows XTT Link Actions to perform.
- field – A unique identifier that authenticates XTT Link Actions.
- field – Refers to the intended recipient of the token of the JD Edwards server.
- field – Refers to the cryptographic algorithm used to sign a JWT's header and determines the token's integrity and authenticity.
- 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.
- field – Required. The unique identifier assigned to XTT Link Actions, enabling recognition and authentication during interactions with JD Edwards.
- field – The confidential key used by XTT Link Actions to authenticate with JD Edwards within the secure OAuth 2.0 framework.
- field – The URL that connects with the instance of JD Edwards ERP system.
-
Click 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).
-
Fill the following fields in the JWT Custom Header Attributes side panel:
- field – Name of the customized attribute.
- field – The corresponding value of the customized attribute.
-
Click
to save the configuration. -
Click the Add icon in the JWT Custom Request Params section to configure additional, non-standard parameters included in the JWT request.
-
Fill the following fields in the JWT Custom Request Params side panel:
- field – Name of the customized attribute.
- field – The corresponding value of the customized attribute.
-
Click
to save the configuration. -
Click the Add icon in the JWT Custom Claims section to configure additional claims to the JWT.
-
Fill the following fields in the JWT Custom Claims side panel:
- field – Name of the customized attribute.
- field – The corresponding value of the customized attribute.
-
Click
to save the configuration. -
Click the Add icon in the Inbound Link Actions section to configure inbound link actions.
-
Fill the following fields in the Add Inbound Entry side panel:
- field – Required. The type of document exchanged, (e.g. Purchase Order).
- drop-down – Required. The access type of XTT Link Actions catalog,(e.g. Marketplace, Company).
- field – The version of the link action.
- field – Required. The frequency at which XTT Link Actions polls data from the JD Edwards application.
-
Click
to save the configuration. -
Click the Add icon in the Outbound Link Actions section to configure outbound link actions.
-
Fill the following fields in the Add Outbound Entry side panel:
- field – Required. The type of document exchanged, e.g. Purchase Order.
- drop-down – Required. The access type of XTT Link Actions catalog,(e.g. Marketplace, Company).
- field – Required. The version of the link action.
- field – Required. The number of retries XTT Link Actions attempts after a failure to send the B2B message to the JD Edwards application.
-
Click
to save the configuration. -
Click the Save icon.
Tips
-
Contact the TraceLink Support for assistance in associating a link action from the Catalog Manager with the B2B connection.
View B2B connections
-
Select the Main Menu icon .
-
Select Extensible Tracelink Transfer Link Actions.
-
Select B2B Connection in the side menu.
-
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.
-
Select the Main Menu icon .
-
Select Extensible Tracelink Transfer Link Actions.
-
Select B2B Connection in the side menu.
-
Select NetSuite.
- Select the link for the connection name from the results table. Select .
-
The View / Edit NetSuite Connection Details screen displays.
- field – Required. The name of the B2B connection.
Currently, only OAuth 2.0 authentication type is supported.
drop-down – The type of authentication used to protect the company against unauthorized access to data.- field – Required. The specific endpoint provided by the NetSuite Server where XTT Link Actions exchanges an authorization grant for an access token.
- field – Required. The ID of the entity issuing the JSON Web Token (JWT).
- field – Required. The unique identifier assigned to XTT Link Actions, enabling recognition and authentication during interactions with NetSuite.
- field – The confidential key used by XTT Link Actions to authenticate with NetSuite within the secure OAuth 2.0 framework.
- field – The entry point for XTT Link Actions to communicate with NetSuite.
- 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.
- field – The date format set by the NetSuite administrator during system setup.
- field – The time format set by the NetSuite administrator during system setup.
- field – The date and time format set by the NetSuite administrator during system setup.
In the Link Action Configuration section, view the following fields:
- field – Required. The type of document exchanged, (e.g. Purchase Order).
- drop-down – Required. The access type of XTT Link Actions catalog,(e.g. Marketplace, Company).
- field – The version of the link action.
- field – Required. The frequency at which XTT Link Actions polls data from the NetSuite application.
- field – Required. The type of document exchanged, (e.g. Purchase Order).
- drop-down – Required. The access type of XTT Link Actions catalog,(e.g. Marketplace, Company).
- field – The version of the link action.
- field – Required. The number of retries XTT Link Actions attempts after a failure to send the B2B message to the NetSuite application.
-
Select the Main Menu icon .
-
Select Extensible Tracelink Transfer Link Actions.
-
Select B2B Connection in the side menu.
-
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.
-
Select the Main Menu icon .
-
Select Extensible Tracelink Transfer Link Actions.
-
Select B2B Connection in the side menu.
-
Select MS Dynamics.
- Select the link for the connection name from the results table.
- Select .
The View / Edit MS Dynamics Connection Details screen displays.
-
In the General section, fill in the following fields:
All letters in the Connection Name must be in uppercase.
field – Required. The unique name of the B2B connection. Currently, only the OAuth2 authentication type is supported.
drop-down – The type of authentication used to protect the company against unauthorized access to data.- Tenant ID value. E.g.
https://login.microsoftonline.com/<Tenant ID>/oauth2/v2.0/token
. 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 <Tenant ID> in the Token URL must be same as the - field – Required. The ID of the entity issuing the JSON Web Token (JWT).
- field – Refers to the scope claim in the JWT that specifies the permissions or operations the token allows XTT Link Actions to perform.
- field – A unique identifier that authenticates XTT Link Actions.
- field – Refers to the intended recipient of the token of the MS Dynamics server.
- field – Refers to the cryptographic algorithm used to sign a JWT's header and determines the token's integrity and authenticity.
- 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.
- field – Required. The unique identifier assigned to XTT Link Actions, enabling recognition and authentication during interactions with MS Dynamics.
- field – The confidential key used by XTT Link Actions to authenticate with MS Dynamics within the secure OAuth 2.0 framework.
- field – The URL that connects with the instance of MS Dynamics ERP system.
- field – The global unique identifier that identifies the instance of the MS Dynamics ERP in the Microsoft cloud.
- field – Name of the customized attribute.
- field – The corresponding value of the customized attribute.
- field – Name of the customized attribute.
- field – The corresponding value of the customized attribute.
- field – Name of the customized attribute.
- field – The corresponding value of the customized attribute.
- field – Required. The type of document exchanged, (e.g. Purchase Order).
- drop-down – Required. The access type of XTT Link Actions catalog,(e.g. Marketplace, Company).
- field – The version of the link action.
- field – Required. The frequency at which XTT Link Actions polls data from the MS Dynamics application.
- field – Required. The type of document exchanged, (e.g. Purchase Order).
- drop-down – Required. The access type of XTT Link Actions catalog,(e.g. Marketplace, Company).
- field – The version of the link action.
- field – Required. The number of retries XTT Link Actions attempts after a failure to send the B2B message to the MS Dynamics application.
-
Select the Main Menu icon .
-
Select Extensible Tracelink Transfer Link Actions.
-
Select B2B Connection in the side menu.
-
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.
-
Select the Main Menu icon .
-
Select Extensible Tracelink Transfer Link Actions.
-
Select B2B Connection in the side menu.
-
Select JD Edwards.
- Select the link for the connection name from the results table.
- Select .
The View / Edit JD Edwards Connection Details screen displays.
-
In the General section, fill in the following fields:
All letters in the Connection Name must be in uppercase.
field – Required. The unique name of the B2B connection. Currently, only the OAuth2 authentication type is supported.
drop-down – The type of authentication used to protect the company against unauthorized access to data.- field – Required. The specific endpoint provided by the JD Edwards Server where XTT Link Actions exchanges an authorization grant for an access token.
- field – Required. The ID of the entity issuing the JSON Web Token (JWT).
- field – Refers to the scope claim in the JWT that specifies the permissions or operations the token allows XTT Link Actions to perform.
- field – A unique identifier that authenticates XTT Link Actions.
- field – Refers to the intended recipient of the token of the JD Edwards server.
- field – Refers to the cryptographic algorithm used to sign a JWT's header and determines the token's integrity and authenticity.
- 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.
- field – Required. The unique identifier assigned to XTT Link Actions, enabling recognition and authentication during interactions with JD Edwards.
- field – The confidential key used by XTT Link Actions to authenticate with JD Edwards within the secure OAuth 2.0 framework.
- field – The URL that connects with the instance of JD Edwards ERP system.
- field – Name of the customized attribute.
- field – The corresponding value of the customized attribute.
- field – Name of the customized attribute.
- field – The corresponding value of the customized attribute.
- field – Name of the customized attribute.
- field – The corresponding value of the customized attribute.
- field – Required. The type of document exchanged, (e.g. Purchase Order).
- drop-down – Required. The access type of XTT Link Actions catalog,(e.g. Marketplace, Company).
- field – The version of the link action.
- field – Required. The frequency at which XTT Link Actions polls data from the JD Edwards application.
- field – Required. The type of document exchanged, (e.g. Purchase Order).
- drop-down – Required. The access type of XTT Link Actions catalog,(e.g. Marketplace, Company).
- field – The version of the link action.
- field – Required. The number of retries XTT Link Actions attempts after a failure to send the B2B message to the JD Edwards application.