Configure AVEVA Integration Service Standalone Installation Server

To configure AVEVA Integration Service Standalone Installation server only, follow these steps:

1. Authentication & License Setup

   1. Click on Authentication & License Setup node.

      

   2. Select Yes or No in CONNECT Login Required?.

      Notes:

   • Select Yes to generate an interactive CONNECT token for AVEVA Product License type LaaS.

   • You will see below screen, if No is selected for CONNECT Login Required?.

     

     3. CONNECT Authority URL https://signin.connect.aveva.com is used when you select Yes.

        

     4. Select Service Authentication Type as NTLM.

     5. Specify the Encryption Password. The password provided is used to encrypt the datasources. This password is required if you wish to migrate the datasources in future.

        Note: The password must be at least 12 characters long and contain at least one uppercase letter, one lowercase letter, one numeric and one special character.

        Important: Ensure that the Encryption Password is saved securely at the time of configuration. This password is used to encrypt your datasources and is required when migrating datasources to a later version of AIS in the future. Loss of this password may result in the inability to migrate your datasources. AVEVA cannot recover this password on your behalf.

     6. Click Configure.

     7. Click Yes.

        

     Note: You can view, messages in Configuration Messages.

2. Database & Logging Settings

   8. Click on Database & Log Settings.

   9. Browse to the database Location. Specify a path for db files or use the default working folder. Browse to select a folder path.

      AVEVA Integration Service moves the files AISDatasource.db and AISDataStore.db files to a different location on the local drive, or a secured network location.

   10. Set a secure Database Password to protect db file.

   11. Confirm Password.

       AVEVA Integration Service protects the database with password and stores it in AVEVA Platform Common Service (PCS) system securely for AIS APIs to read.

   12. Browse to the log file Location. AVEVA Integration Service stores logs in the entered location. Browse to a folder path.

       

   13. Click Configure.

3. AIS APIs Settings

   14. Click on AIS APIs Settings.

   15. Select Security & Certificate tab.

   16. Click on Select Certificate.

       

   17. Select a certificate.

       

   18. Click Open.

       You can either browse a certificate issued by your IT department or generate a self-signed certificate (not recommended for production use).

   19. Select API Identity Management tab.

   20. Enter Host Machine Name.

   21. Enter Identity UserName along with domain for AIS APIs site binding.

   22. Enter Identity Password for AIS IIS Application Pools Identity.

       This configures the identity credentials for the API application pool. This account is used to authenticate and manage API operations on the specified host machine.

   23. Click Save & Apply.

       

   24. Select API Port Settings tab.

   25. Enter Port Number for Config API.

   26. Click Apply.

       

   27. Enter Port Number for Data API.

   28. Click Apply.

       

   29. Enter Port Number for REST API.

   30. Click Apply.

       

   31. Enter Port Number for Web Administration URI.

   32. Click Apply.

       

   33. Click Configure.

       

4. API Access Control

   34. Select API Access Control.

       In AVEVA Integration Service (AIS) 4.1 and later, the default API Access Control restricts access to only the user account under which AIS is installed and the identity running the Application Pools. All other users must be explicitly granted access via Allow Rules.

   35. Select Config API tab.

   36. Click Add Allow Rule

       

   37. Click Add Allow Rule and select the Specified roles or user groups: radio button and add "your group name" and click the OK button.

       Note: Your group name is allowed to access AIS APIs.

       

   38. You select each tab DataAPI, RESTAPI, Web Administration and follow the steps accordingly to provide permission.

       Notes:

       • AIS API APP Pool Identity must be given access to all the APIs (ConfigAPI, DataAPI, RESTAPI, Web Administration).

       • You can manage access rules for API services, however, by default, all users are allowed.

   39. Click Configure.