PI Server for RtReports upgrade tasks

To ensure all data related to RtReports successfully migrates during an upgrade to the PI Server, and that reports you run after the upgrade will locate the correct PI Server, perform the following pre- and post-upgrade tasks listed here.

• Before the PI Server upgrade:

  • Choose the name of the new PI Server.

    • If you only run batch reports, or do not want to carry over comments and verifications from time reports, the new PI Server can have a different name than the old PI Server.

    • If you generate time-based reports and want to carry over the comments and verifications, name the new PI Server the same name as the old PI Server.

      This points RtReports to the correct PI Server using the unique identifier for report parameters, which is created using the PI Server name.

      If this is not possible, see Support multiple RtReports servers with a single PI Server instance for additional naming conventions.

• After the PI Server upgrade:

  1. Point the RtReports server to the new PI Server.

  2. Import RtReports security information to the new PI Server.

  3. Verify unique IDs of batches on the new PI Server.

  4. Replace PI Server names in templates.