Organize license components into topologies

AVEVA Enterprise Licensing is scalable and flexible. You can set up single-node or multiple-node systems. The information, guidelines and topology models in this section are provided to assist in designing and then implementing a topology that matches your working environment.

You can create a topology of two general types:

• Single node topology

• Distributed topology

A third type is actually a subset of these - the disconnected topology. This is any topology where an internet connection is not available. Each of these general types of topologies is described in the following topics. The topology models topics then go into greater detail of the different topologies you can use to deploy your system. See Licensing topology models.

The License Server and License Manager are delivered with the AVEVA Enterprise software products as independent components to allow you to deploy them to the nodes where they fit your requirements.

In this sample topology, a single node system, the product machine has both the License Server and License Manager components.

The components of the product interact with the License Server. The product component acquires and releases activated licenses in the License Server to enable product functionality and client connectivity.

Guidelines for designing and implementing your licensing system

1. When centralizing licenses in a License Server:

   1. If you have multiple licenses for the same product with the same functionality hosted in the same License Server, reservations are not needed.

   2. If one or more licenses for the same product have unique functionality, then reservations are needed to ensure that those unique licenses are acquired by the proper node(s).

      For example, if you host five InTouch 5K Run-Time licenses in a License Server and you have five InTouch nodes, no reservations are required. Any node can acquire any license.

      If you host four InTouch 5K Run-Time licenses and one InTouch 60K Run-Time license and you have five InTouch nodes, then you must reserve the 60K Run-Time license for the node that must acquire it to ensure only that node can use it.

2. The System Platform installation allows you to install the License Server, the License Manager, or both. These can be installed in separate machines or all in a single node.

   Consider the best location to install them based on your topology and system needs.

3. If you chose to centralize your licenses in one License Server, always leverage the License Server Redundancy capability. License Server redundancy capability is available at no additional cost.

4. When working with virtualized environments, be sure to deactivate all licenses in a License Server before cloning a VM. If this is not done, the cloned License Server will go into Grace Period mode of 15 days, after which it will cease serving licenses.