License Service and Architectures (version 24)

License Service

Licenses are applied at the server level where the License service is installed, never on a client's machine. The location of the License service is determined when installing the Canary product, whether it be local or remote.

If the Remote option is selected the user will be prompted in the next screen to specify where the License service is located.

License Architectures

At least one License service per network is required, but multiple services can be used if there are multiple Historians in the same network. Consider the following architecture where 3 Canary systems (Prod, DR, and Dev) reside on the same network.

Each system contains its own License service and is independent of one another. If one server goes down, the others are not affected in terms of licensing. All three servers must be licensed separately, similar to how licenses were applied prior to version 24.

Now consider the next architecture where only one server (PROD) contains the License service.

The License service is only installed on PROD, but it contains the licenses for ALL three servers. DR and DEV connect remotely to lease a license for their installed products. The benefit of having one License service per network is that licenses are managed in one location. The downside, however, is that if the server goes down or becomes unavailable, all remote servers requiring a license will also become unavailable. For this reason, it is recommended that each system use its own License service.

If the Canary system is installed on different levels throughout the network, each level should contain its own License service assuming one level cannot reach the other.

If two Historians on the same network have differing tag counts, two License services are required. One License service CANNOT contain two Historian licenses of different tag counts.