Installing RtReports with PI Collective

When the RtReports server connection is initialized, it attempts to connect to the primary server of a collective. RtReports report templates are stored in the PI Module Database, and write access to the PI Module Database is only permitted on the primary of a server collective. The RtReports server will automatically detect failover events of a server collective and will take appropriate action. If the RtReports server is connected to a secondary server, all write operations are disabled, such as creating a new report template, generating new reports, or any versioning updates. While connected to a secondary server of a collective, adding new comments, verifications, and approvals will be disabled. The following error message will alert users when they are viewing a report, but the RtReports server is connected to the secondary PI Server: "Comments, verifications, and approvals for this report are disabled – the primary PI Server “PI Server Name” is not available, and the report contains PI Tag annotation data. Comments, verifications, and approvals are not available."

All functions that create, edit, or delete report templates are serviced by the RtReports server. When a user logs into the RtReports editor, if the RtReports server is connected to a primary server of a collective, all operations are enabled. If the user attempts a write operation against the RtReports server, and the RtReports server has failed over to a secondary server, the request is rejected, and a failure message is sent back to the RtReports editor. The RtReports editor will also automatically detect failover events of a server collective and take appropriate action. If the RtReports editor is connected to a secondary server of a collective, all write operations are disabled, such as creating, editing, and deleting report templates.

Note: RtReports does not support network load balancing and high availability.