Generate a license for a collective deployment

For a collective deployment, you only need to generate a license file for the primary Data Archive member of the collective. When each secondary member is added into the collective, that member will utilize the license from primary member.

On each host machine for a secondary Data Archive member, use the temporarylicense.dat file from the primary member install to finish the installation.

1. Generate the machine signature file (MSF) on the primary member by launching the PI Server install kit on the primary member host machine.

   The MSF is automatically generated by the setup kit. Copy the location of the MSF for the next step.

2. Verify your license manifest for the MSF supports the number of secondary members for your collective.

   1. Locate and expand on the Data Archive server for your site under the list of Products.

   2. Click on Generate License.

   The Generate License Activation File for PI Server page appears displaying the PI License Activation System.

   1. Ensure that the Additional HA Servers field specifies the correct number of additional Data Archive servers allowed for your collective deployment. This number must be greater than or equal to the number of secondary members planned for your PI collective.

   The license file allows the specified number of secondary servers that will be able to connect to the primary server. This number must be greater than or equal to the number of servers in the collective in addition to the primary server.

   1. If you see a problem in the license manifest, click the MLA Problem Report Form link and submit that form to report the problem.

   My License Activations (MLA) is an online self-service tool that you will use to create a site-specific Data Archive license file. You should get a response within 24 hours. If you cannot delay the installation, contact the Customer Portal to request a 2-week temporary license. For more on temporary license files, see View license activation history.

3. Select the MSF to upload it on the PI License Activation System and click Generate License Activation File.

4. Finish the setup for the primary Data Archive member.

   The resulting pilicense.zip file contains your license file (pilicense.dat), as well as the temporarylicense.dat file to use for setting up all secondary members of the collective.

5. Copy the temporarylicense.dat onto the machine you intend to host a secondary Data Archive member of the collective.

   The temporarylicense.dat file is a temporary license file that allows you to test Data Archive installation before adding the secondary Data Archive server to the collective. When you add the secondary Data Archive server, the Collective Manager automatically replaces this temporary license file with the license file on the primary Data Archive server.

6. Rename the temporarylicense.dat to pilicense.dat on the secondary host machine.

7. Launch the PI Server install kit to install the secondary member.

8. Specify the renamed license file to complete the installation of the secondary member.

9. Create a collective on the primary Data Archive member using Collective Manager. See the High Availability topic Create a collective.

10. Add this secondary Data Archive member to the collective by using Collective Manager. See the High Availability topic Add a secondary server to a PI Data Archive collective.

11. Copy the pilicense.dat file on the primary Data Archive member and paste the file onto each secondary member of the collective, replacing the existing pilicense.dat file on the secondary member.