Licensing Terminology
OpenLink Virtuoso Universal Server requires a license based on a number of standard pricing units and deployment models. This page introduces those pricing units and models and clarifies terminology used to express them.
OpenLink Client Hosts
In a Workstations Model environment, the OpenLink client hosts are the Workstation machines. In an Application Server Model environment, the OpenLink client hosts are the Application Server hosts.
Concurrent Connections
Concurrent connections are the maximum number of distinct HTTP and SQL threads opened by applications and other technologies that interface with Virtuoso. Concurrent connections may also be referred to as database sessions.
Database Sessions
This term is synonymous with concurrent connections. See above.
HTTP Threads
Virtuoso HTTP threads are initiated when connections are established to the Virtuoso HTTP ServerPort. The HTTP ServerPort is a Virtuoso configurable in the main .ini file. An associated parameter allows administrators to set aside a pool of threads that are reserved for HTTP connectivity. (These threads consume license points on Virtuoso server startup.) Threads associated with HTTP ServerPort are consumed by Web Services, RDF, SOA, BPEL, and other HTTP-based protocols and applications.
SQL Threads
Virtuoso SQL threads initiated when connections are established to the SQL ServerPort. The SQL ServerPort is a Virtuoso configurable in the main .ini file. An associated parameter allows administrators to set aside a pool of threads that are reserved for SQL connectivity. (These threads consume license points on Virtuoso server startup.) Threads associated with this port are consumed by ODBC, JDBC, OLE DB, .NET, isql, and any other APIs and applications that seek direct access to data in Virtuoso's native SQL92 or virtual database schema.
Client Types
Client types are the individual APIs, sometimes called Data Access Mechanisms, that client applications use to connect to Virtuoso. Some applications use the ODBC API; others use the JDBC, OLE DB, ADO.NET, or XMLA APIs or some combination of these.
Licensees must take account of all applications in the environment that use OpenLink products for data access purposes. Then, users need to tally the data access mechanisms used by these applications. Sales will adjust the license price upward by a set percentage, if two or more "client types" or data access mechanisms are required.
Processor Cores
OpenLink licenses take into account the number of physical processor cores found in the machine(s) on which they are deployed.
A dual-core processor has 2 processor cores; a quad-core processor has 4 cores. A machine with two dual-core processors has 4 cores.
Virtual processors such as Solaris containers or AIX micropartitions should not be tallied by OpenLink's licensing technology.
Processors are one factor in OpenLink's licensing cost calculation. However, OpenLink does not employ a simplistic, per-core pricing model. Our license technology makes allowances for Workstation machines that have high physical processor core counts. Multi-core machines hosting Workstation operating systems like "Home", "Personal", or "Desktop" variants of Linux, Mac, and Windows are covered by licenses with a lower price entry point. A core count threshold is also applied to server class machines in recognition of the fact that different servers possess larger or smaller number of physical cores by default.
Operating System Types
OpenLink's license model clearly distinguishes between Client / Desktop / Workstation and Server operating system editions. For instance the Home and Professional Editions of Windows are Client/Desktop/Workstation variants of Windows, while Web, Server, and Advanced Server are regarded as Server variants. The same applies to Mac OS X and Mac OS X Server, and Linux variants. OpenLink's commercial license terms prohibit the use of Client/Desktop/Workstation editions of operating systems for Application Server license model installations. Thus, the License Manager will test for such violations and treat the Client / Desktop / Workstation platforms as Server edition operating systems.
Operating System Type also dictates licensing costs associated with physical processor cores in host computers. However, OpenLink does not employ a simplistic, per-core pricing model. Our license technology makes allowances for Workstation machines that have high physical processor core counts. Multi-core machines hosting Workstation operating systems like "Home", "Personal", or "Desktop" variants of Linux, Mac, and Windows are covered by licenses with a lower price entry point. A core count threshold is also applied to server class machines in recognition of the fact that different servers possess larger or smaller number of physical cores by default.
Workstation
Workstation is another term for a Client Host when that Client Host is a part of a Workstation configuration. See above.
Product Formats
From a licensing perspective, Virtuoso licensing is partitioned as follows: Personal, Workgroup, and Enterprise.
- Personal: Desktop Edition Operating Systems only
- Workgroup: Desktop or Server Operating System without Cluster Edition Option
- Enterprise: Server Operating System only with Cluster Edition Option.
Note: Prior to release 6.x, only Virtuoso Personal and Workgroup Editions are available.