Grass Valley iControl V.6.02 - Manual (Page 96)

License Management
[Workflow]: Requesting and Activating a License for a Single Application Server
86
[Workflow]: Requesting and Activating a License for a Single Application Server
If you would like to activate one or more licenses on a single Application Server, perform this
workflow.
Flowchart depicting licensing workflow (single Application Server)
IMPORTANT: Considerations in choosing a licensing strategy
Licensing several Application Servers at once carries with it the advantage of not
having to perform a licensing workflow on each of potentially many servers. In
such a networked licensing topology, one server requests and activates licenses
for itself, and these newly unlocked features will subsequently become unlocked
on the remaining Application Servers (on the same site).
There is, however, a reduction in robustness in the networked model: If the
Application Server originally used to request and activate licenses goes offline,
the network-licensed features on the remaining servers may become locked
again should these servers, in their own right, need to reboot or have their
iControl Services restart. If resilience and robustness in feature licensing is critical
to your network of Application Servers, you may want to consider individually
licensing each Application Server.
IMPORTANT: System behavior
If you would like to activate licenses on a single Application Server (to the
exclusion of all others) but have a Redundancy Group configured for this server,
you will not be able to remove the other servers that belong to this Redundancy
Group from the license activation list.