I'm aware that in order to deploy my application (that contains features requiring a Standard licence) I need to purchase a 25 Deployment Pack, authorize it, and embed the relevant license code snippet in my application code.
However, this raises 2 questions:
Is that all I need? Is there a licence file that needs to be deployed with the application (either manually or auto-created with the Deployment Builder tool)?
Does my application then 'call home' to Esri to validate that licence key? In other words, how do Esri ensure that having purchased 25 deployment licences I do not deploy 26 installations of my application?
The application may be installed in locations that do not contain an open connection to the internet - therefore if there's a licence check performed I'll need to deal with that somehow. The licencing and deployment documentation is very clear but doesn't expressly cover the above - especially point 2.
Good questions - sorry it wasn't clear in the doc. The summary is yes, it can work completely offline.
1. Is that all I need? Is there a licence file that needs to be deployed with the application (either manually or auto-created with the Deployment Builder tool)?
Correct - you just set the license string in code, in your application. There is no additional license file that needs to be deployed.
2. Does my application then 'call home' to Esri to validate that licence key? In other words, how do Esri ensure that having purchased 25 deployment licences I do not deploy 26 installations of my application?
There is no online validation in deployment, it's a trust-based licensing model. We wanted to make it as easy as possible for you to deploy apps in your scenario. However, that does mean it is your responsibility to ensure that you do not deploy the 26th app without purchasing additional licenses to cover those extra deployments. When you do purchase additional licenses, you do not need to make any changes to your app, you can just keep deploying up to the number you purchased.
Good questions - sorry it wasn't clear in the doc. The summary is yes, it can work completely offline.
1. Is that all I need? Is there a licence file that needs to be deployed with the application (either manually or auto-created with the Deployment Builder tool)?
Correct - you just set the license string in code, in your application. There is no additional license file that needs to be deployed.
2. Does my application then 'call home' to Esri to validate that licence key? In other words, how do Esri ensure that having purchased 25 deployment licences I do not deploy 26 installations of my application?
There is no online validation in deployment, it's a trust-based licensing model. We wanted to make it as easy as possible for you to deploy apps in your scenario. However, that does mean it is your responsibility to ensure that you do not deploy the 26th app without purchasing additional licenses to cover those extra deployments. When you do purchase additional licenses, you do not need to make any changes to your app, you can just keep deploying up to the number you purchased.
