Integration Service REST API

Unable to Get Data using AVEVA Integration Service REST API - For Dabacon - When AVEVA Admin 2.1.1 is used to add AD user in the project.

Description: When you add an AVEVA Dabacon user using AVEVA Administrator to map a Dabacon user to a PDMS user, an unnamed ULOGID Element is created.

AVEVA Integration Service validates the REST API user making the request to get data from the Dabacon product is a valid ULOGID and mapped to a PDMS user. Because the ULOGID is unnamed, AVEVA Integration Service is unable to validate.

Resolution: You can manually modify the user's Name attribute of the ULOGID Element types to match their username in AVEVA Administrator.

REST application pool stops every time when you browse the REST API website.

Description: If you have connected AVEVA Integration Service on-premises (Local) with AVEVA Integration Service on Connect (AVEVA Integration Service Data API & AVEVA Integration Service Config API), and AVEVA Integration Service REST API Local cannot subscribe or create a publish/subscribe listener to AVEVA Integration Service Data API then RESTAPIPOOL automatically stops working. This is a Known issue. When this happens you may see the following errors in the application. RESTAPIPOOL Stopped in IIS.

Resolution:

• Delete the Connect Token already generated, to do that go to below folders and delete the token.

  • C:\Users\<username>\.aveva

  • C:\ProgramData\.aveva

• Check that the environment variable “AVEVA_SERVICE_AUTHENTICATION_TYPE” value is:

  • CONNECT if you are using “AVEVA Integration Service on Connect”

  • NTLM if you are not using “AVEVA Integration Service on Connect”.

    

• Configure all (Datasource Store URL, Data Store URL, REST URL, webadmin URL) the Endpoint and Start Service. Error should not appear again.

Unable to Get Data Using REST API - For Dabacon Product

Description: Unable to Get Data Using REST API - For Dabacon Product

Resolution: To Use REST API to get data from AVEVA Dabacon Platform based products like Engineering, E3D you should follow these steps.

1. Make sure the project is AD Authenticated.

2. Add Data source as Project User (Free User i.e., SYSTEM) and Change the Authentication Type to “User”.

3. Users who want to call the Rest API should be mapped to a PDMS user in AVEVA Administration.

4. Request REST API as shown below and provide Authorization Header [NTLM] and Project User request Header having mapped the PDMS user.

   

5. Use this base URL for REST API https://<AisServer>:8080/ais/odata/v3