Where do PI SDK and/or PI AF SDK obtain alias lists from?

We're having problems referencing a secondary archive collective member programmatically using the PI AF SDK because of a persistent alias pointing from the secondary archive to the primary archive. We've deleted the alias in AboutPI-SDK and from the AFSDK.Config file, but the alias reappears in AboutPI-SDK shortly after deleting it.

 

Are there any other locations where the alias might be stored that is causing it to repopulate?

Parents
  • Hello ​ ,

     

    there is no need to modify the Known Servers Table (KST) for PI Data Archive Collectives and you will not be successful in doing so. When a client, no matter if PI SDK or AF SDK, connects to a Collective or a member, the KST is adjusted according to the information found server side. Usually you do not need access to individual members of a PI Collective but maybe to read configuration information. Access to individual servers is than done through the Members property of the Collective. Please refer PICollective Class.

    When writing time series data to PI Point(s) of a PI Collective, please use PI Buffer Subsystem to Buffer and Fan the data. Please do not attempt to write against Secondary members.

Reply
  • Hello ​ ,

     

    there is no need to modify the Known Servers Table (KST) for PI Data Archive Collectives and you will not be successful in doing so. When a client, no matter if PI SDK or AF SDK, connects to a Collective or a member, the KST is adjusted according to the information found server side. Usually you do not need access to individual members of a PI Collective but maybe to read configuration information. Access to individual servers is than done through the Members property of the Collective. Please refer PICollective Class.

    When writing time series data to PI Point(s) of a PI Collective, please use PI Buffer Subsystem to Buffer and Fan the data. Please do not attempt to write against Secondary members.

Children
No Data