Thing Templates
|
Description
|
||
---|---|---|---|
Generic Connector Connection Settings
|
• Refresh Interval (minutes): Specify the interval for refreshing the endpoint cache. The default is 60 minutes.
• Authentication Type: Enter one of the following:
◦ None
◦ Fixed
This authentication type requires a service account on the back-end application. This account is not an actual user; its purpose is to enable access to another application. All access from the ThingWorx applications uses this service account on the back-end application.
◦ SSO
For more information, see Single Sign-on Authentication.
• Authorization Server ID: For SSO authentication type only.
Enter the ID of the authorization server to which you want to connect.
The ID is assigned by a server administrator when ThingWorx is configured for SSO. To retrieve this value, refer to the <authServerId> variable used by the authServerId.clientID setting in the sso-settings.json file where ThingWorx is installed. You can contact your Apache Tomcat server administrator to request the authorization server ID.
For more information, refer to the topic Configure sso-settings.json.
|
||
HTTP Connector Connection Settings: For Fixed authentication type only.
|
• Enter values in the following fields:
◦ Username
◦ Password
◦ Confirm Password
Service route URLs for the OData back-end system. Enter multiple rows if you have multiple domains. If you enter a Relative URL below, that URL is used as part of the path.
For example, if the Relative URL is /servlet/odata and the Service Route URLs are /ProdMgmt and /DataAdmin, then the effective service URLs relative to the base URL will be /servlet/odata/ProdMgmt and /servlet/odata/DataAdmin. These service route URLs specify one or more OData specs. For each service route URL, the /$metadata path is appended, and the resource is requested to retrieve the OData spec.
• For all authentication types, enter information in the following URL fields. If a default value was provided by the Thing Template, do not change the value. For example, Relative URL and Connection URL are provided for the SAPODataConnector. They point to a catalog service that finds the related specifications.
◦ Base URL: The base URL is required to access the back-end system. This includes the host, port, and application of the back-end system.
For SSO, enter a URL that supports OAuth. For more information, see Working with Scopes.
◦ Relative URL: The URL on which the API is served, which is relative to the Base URL.
◦ Connection URL: The URL used to verify the connection, which is relative to the Base URL.
|
||
OData Connector Connection Settings: For ODataConnector only
|
|||
SAPODataConnector
|
|||
Swagger Connector Connection Settings
|
• Relative URL Of Swagger Specification: The URL used to obtain the Swagger specification from the back-end system. It is relative to the Base URL.
|
|
The connection status information is available from Monitoring the Status of the Integration Connectors.
> > . For more information, see |