mv.NET is licensed in 2 parts; Client Interface Developer (CID) and Database Access Licenses (DALS). Firstly, if you have purchased developer licenses (CIDs), each developer's workstation needs activating using the mv.Net License Registration Utility. Secondly, each server will need a relevant number of database access licenses (DALS), these are sometimes referred to as run time sessions/licenses.
These links will help with requesting and installing mv.Net Licenses.
Client Interface Developer (CID) - Developer Product Licensing
The Client Interface Developer (CID) is required for the following mv.Net components:
Core Objects class library binaries
mv.NET services
Initial Configuration Database structure and content
Server components download files
Data Manager application
Session Manager components
Visual Studio.NET integration assemblies
The CID provides the programming interface into the Core Objects technology, along with plug-in extensions to Visual Sudio.NET to allow management of many aspects of a MultiValue database system from within the VS.NET native IDE. The primary feature of the Client Interface Developer is a class library holding the series of classes that allow a developer to connect to and work with a MultiValue database.
A single CID License allows you connect to and manage multiple multivalue databases.
The CID License activates the full use of the mv.Net Data Manager which provides for the configuration and profiles database, the account, file and dictionary maintenance and the terminal emulation and data transfer.
Database Access Licenses (DALS)
The basic concept of database access licensing within mv.NET is that an access license (DAL) for a set number of concurrent connections to a specific database installation on a specific database server (licensed machine) needs to be purchased and installed.
The DAL can be on a remote machine to the system running the mv.Net Data Manager as long as it can connect with the mv.Net license Manager for that database.
For the mv.NET Session Manager to establish a connection (session) to a database, it must also be able to contact to the mv.Net License Manager that has the appropriate access license (DAL) installed.
The License Manager checks the number of active sessions vs. the number of licensed sessions to decide whether the Session Manager is to be allowed to establish a new connection.
So, DALs control the number of database connections that can be opened at any one time and thus create the "throttle" for database access via .NET.