Access Token for SAP
Configure an access token to connect to SAP.
Background and Setup
Good to Know
- The values in this access token must match the values you entered in the
SAP Connector.
For more information, refer to Configure the SAP AgileConnector.
- In most cases, you can use a global access token or
an application level access token:
- Global access tokens are shared across all users and applications. If you want all process designers and runtime app users in your AgilePoint NX tenant to be able to connect to an external data source, use a global access token. An example is a SharePoint site on an intranet that all employees in a company can access.
- Application level access tokens are shared with all processes in a process-based app, or restricted to use within a form-based app. Use application level access tokens if only process designers or runtime app users for a particular application should access an external system — for example, a Google Drive account that is only used to share files within a small team.
- Access tokens are collections of credentials that are used to authenticate communication directly between AgilePoint NX and an external system. Because it is the AgilePoint NX system that uses these credentials, rather than an app, there is no difference between
design time
and
runtime
access tokens. Access tokens are never checked in or published, and they do not use version control. If you change an access token in the App Builder or Manage Center, the access token changes immediately everywhere the access token is used. Changes to application level access tokens apply to all versions of an application, including running application instances. Changes to global access tokens apply everywhere they are used in AgilePoint NX. You can not roll back an access token to a previous version.
For more information, refer to What Data Is Deleted When I Delete an App or Application Resource?
- Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation, and it is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business uses cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, and other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?
How to Start
There are several ways to create an access token for SAP. How to create the access token depends on where you want to use it.
Global (Manage Center)
You can use a global access token in any application in your AgilePoint NX tenant. Use a global access token if you want any user in your environment to be able to connect to the same external system.
- Click Manage
.
- Click App Builder
> Global Access Tokens.
- On the Global Access Tokens screen,
click Add Token
.
- On the Add Global Access Tokens screen, select SAP
.
Application Level (App Builder)
Create an access token to use in any process activity or form control in an application.
- Click Build Apps .
- .
- Click New
.
- On the New App Token screen, select
SAP .
Process Activities and Form Controls
Different access token types can be created in context and used in different process activities, form controls, or applications. The App Builder shows shortcut buttons in any place you can create an access token.
You can create an application level access token for SAP here:
- Process Builder
- Any activity on the SAP Integration tab
- Any activity on the SAP Integration
Fields
| Field Name | Definition |
|---|---|
Token Name |
|
Description |
|
Connector |
|
Server |
|
Pool ID |
|
Client |
|
Language |
|
User Name |
|
Password |
|
Test Connection |
|
Encrypt |
|