Typical deployment licensing scenario described
A typical deployment scenario might be a developer who wants to deploy 50 applications that use the Network Analyst extension capability. The 50 applications are the same runnable .jar file.
In this case, he would purchase two deployment packs (at time of publication, deployment packs come in packs of 25). When he purchases the packs, he indicates that he wants the packs to include 50 Standard product licenses and 50 Network Analyst extension licences (because any extension license requires a Standard product license). Esri emails him one software authorization number (or authorization file) that represents both deployment packs (50 deployments). The software authorization number is set to unlock the Standard product and Network Analyst extension for those deployments.
To license his application before deploying it to devices, he would:
- Point to the software authorization number in the Software Authorization Wizard. How do I do this? This task generates license strings for the products and extensions purchased. In this case, it generates a Standard product license string and a Network Analyst license string.
- Use the License Viewer to obtain the license strings so that he can add them to his project. How do I do this?
- Compile the project.
- Deploy the application by copying, to each device, the runnable .jar file, client libraries, runtime components, and associated files, such as data to be used local to the device, to each device. He can copy the files to 50 different devices. How do I do this?