Configuration fields - HxGN EAM - 12.2.1 - Feature Briefs - Hexagon

HxGN EAM SDx Integration Configuration
ft:locale
en-US
Product
HxGN EAM
Search by Category
Feature Briefs
HxGN EAM Version
12.2.1

The SDx Integration Configuration screen will be used to define the configuration and connection details for the integration between EAM and SDx.

SDx1

Token parameters

  • SDx Token Server URL: The URL for server to which token requests are sent.

  • Client ID: Public identifier of the external application.

  • Client Secret: The confidential identifier used for authentication known only to the OAuth application and the authorization server.

  • Scope: Enter the permission that is set on the token to further define the type of protected resources that the connected application can access.

  • User Name: Enter the user ID credential for an access token. This field is optional.

  • Password: Enter the user's password credential for an access token. This field is optional.

  • Resource: Enter the identifier of the Web API to be accessed.

    The Resource parameter is used if SDx1 is using Smart API Manager authorization server in an on-prem configuration. The Resource parameter is ignored by the Okta authorization server if using SDx1 in Smart Cloud. Also, the resource parameter is ignored by the Okta authorization server if using SDx2 in Clipper cloud.

SDx entity display parameters

  • Tag Infomap Server URL: The Tag Infomap URL to which requests are redirected after the authorization is complete. This URL includes parameters for the EAM position (SDx Tag) and Organization (SDx Plant). This field value should follow the format of https://<ServerName>/<WebClientSiteName>/#/launch/infomap;config=<PLANT>;objectObid=<TAG_ID>.

  • Document Viewer URL: The Document Viewer URL to which requests are redirected after the authorization is complete. This URL includes parameters for the EAM position (SDx Tag) and Organization (SDx Plant). This field has been allocated for future development to support Document display and is not currently used for integration.

  • Document Infomap URL: The Document Infomap URL to which requests are redirected after the authorization is complete. This URL includes parameters for the EAM position (SDx Tag) and Organization (SDx Plant). This field has been allocated for future development to support Document display and is not currently used for integration.

  • URL to request the OBID for a Position: The URL to which object ID requests are made for Positions. This URL includes a parameter for the EAM position (SDx Tag). This field value should follow the format of https://<ServerName>/<SiteName>/api/v2/sda/Tags?$filter=Name eq '<POSITION>'

  • URL to request Documents for a Position: The URL to which document requests are made for Positions. This URL includes a parameter for the EAM position (SDx Tag). This field has been allocated for future development to support Document display and is not currently used for integration.

Position sync interface parameters

  • URL for Position Sync Response: Populate a valid URL for this field. This field has been allocated for future development for Functional Locations and is not currently used for integration.

    For all URLs the parameter names must be capitalized.