Use AVEVA Recipe Management Client API (aka RestAPI) from ArchestrA Graphic Symbol Scripting

If you are writing ArchestrA Symbol Scripting and using the AVEVA Recipe Management Client API (aka RestAPI), you may have trouble connecting to the AVEVA Identity Manager (AIM) to register the node as a valid AVEVA Recipe Management client. You will typically see Unauthorized or Access Denied exceptions in the logger if this happens. You can use any of the following three approaches to resolve this:

• Option 1: Install and configure Client Connection Configuration feature. This will fetch the SSL Certificates from AIM and AVEVA Recipe Management server nodes and add them to Trusted store. It will also register all the AVEVA Recipe Management clients with AIM.

• Option 2: Deploy an AppObject using the AVEVA Recipe Management RestAPI in some scripting to each AVEVA InTouch application platform. This will force a client registration of those platforms with the AIM. You only need to do this one time per platform. The AppObjects does not need to stay deployed. For client registration to succeed with AIM, the ArchestrA Network account user on the AVEVA InTouch application platform should have Administrator privileges, and AIM Registrar credentials need to be supplied to RestAPI constructor used in the scripting.

• Option 3: Log on to the desktop of the AVEVA InTouch application using the ArchestrA Network account user. Start the AVEVA InTouch application with the RestAPI scripting. It should work correctly, causing the AVEVA InTouch client to be registered with the AIM. Now you can log on to the desktop as any user and it should work as expected. Again for this option too, the ArchestrA Network account user should have Administrator privileges, and AIM Registrar credentials need to be supplied to RestAPI constructor used in the scripting. This will ensure client registration is successful with AIM.