I'm wondering what is the correct "Application Name" (procname) when setting up a trust for a PI Interface for Citect?
Actually, is there a table listing procnames for all the many PI interfaces?
Thank you all for your time and consideration!
According to this KB. it is PI CE.
KB00505 - How to recognize connecting application names in the PI Network Manager Statistics table and message logs
Thank you so much for your quick response to my enquiry. I have tried "PI CE" in the "Application Name" (procname) field in the trust definition. The connection from PI interface node ICU to PI server fails, however when I leave the "Application Name" field blank it *will* connect. For this reason I presumed I had the incorrect procname. Perhaps there is a different reason why I cannot cannot the interface node to the server with "PI CE" as the procname - I'll keep trying.
Thanks again for your assistance.
The application name should be logged, so you should be able to lookup which name is used when a connection attempt is made.
Can you please also verify which PI API version is installed on the interface node?
Potentially the issue you are experiencing is due to the PI API version not supporting PI Trusts. Please see AL00309 - Windows Integrated Security (WIS) replaces PI trusts and explicit logins in PI API 2016 for detailed information.
Generally you should be able to find detailed information in the PI Message Log on the PI Data Archive host as already suggested by Roger. For the usage of pigetmsg.exe please refer to the documentation.
It is possible in most PI Interfaces that you can manually configure your API connection name to be something other than the default. Please check this in your PI-ICU for the Citect Interface.
Windows Integrated Security is the way to go for the future, and in my opinion easier to manage and properly control than Trusts. In any new project during the last 2 years (when WIS in PI API was released), i don't use Trusts anymore.
Trusts are difficult to setup and maintain (whilst keeping them secure). WIS is setup once, then no looking back.
The biggest advantage, in my opinion, is the transport security when using WIS. It means that any communication between PI Server and PI Clients are encrypted using the windows credentials. More information can be found here: KB01092 - PI System and Data Encryption
Ha, i never knew that... Still learning!
Retrieving data ...