Max Purchase -- The
maximum number of times a single customer is allowed to purchase a
given Offer. This is typically used to restrict access to free
Offers.
Seats -- The number of systems
(e.g., Enterprise Edition Request Broker hosts, Express or Lite
Edition Driver hosts, Virtuoso Server hosts) on which the product
(license) may be deployed.
ADO.NET
Provider -- A Software Application that provides a data
access channel between an ADO.NET compliant applications and a
backend database management system, using the native protocols of
the target DBMS or Driver vendor.
Agent -- A Software Application.
May be a Bridge Agent or a Database Agent.
Bridge Agent -- A
Software Application. Provides connections to a DBMS-agnostic Data
Access Mechanism (e.g., ODBC, JDBC). Enterprise Edition only.
Broker Operating System -- The
Operating System on which the Enterprise Edition Request Broker,
Database Agents, and/or Bridge Agents will run; where the
Enterprise Edition product (license) will be deployed.
Broker Operating System Type
-- The Types (Workstation or Server) of Operating System on which
the Enterpris Edition product (license) may be deployed.
Data Access Protocol Scope --
Specific data access protocol(s) (ODBC, JDBC, ADO.NET, OLEDB,
and/or XMLA) supported by data access driver (Express or Lite
Edition) and/or license (Enterprise Edition).
Database Agent
-- A Software Application. Provides connections to a specific DBMS
(e.g., Oracle 11g, Microsoft SQL Server, MySQL 5.x). Enterprise
Edition only.
Database Engine -- Specific
version(s) of a Database Management System (DBMS) supported by an
ODBC driver, JDBC driver, ADO.NET provider, OLEDB provider,
XMLA provider, or License File.
DBMS Family -- Database Management
System (DBMS) Family.
Generic Client
-- A Software Application. An ADO.NET Provider, JDBC Driver, or
ODBC Driver which connects a client application using such Data
Access Mechanism to a Request Broker and associated Agents.
Enterprise Edition only.
JDBC Driver -- A
Software Application. A Software Application that provides a data
access channel between a JDBC compliant applications and a backend
database management system, using the native protocols of the
target DBMS or Driver vendor.
Maximum Concurrent Client
Machines — The maximum number of client hosts (physical or
virtual, metered by IP address) which may simultaneously open ODBC,
JDBC, ADO.NET, OLEDB, and/or XMLA database sessions through a
Request Broker and/or Database or Bridge Agent under the given
license. Only applicable to Enterprise Edition.
Maximum Database Sessions --
Maximum concurrent database sessions which may be opened under the
given license. Opening a new session increments the count; closing
an active session decrements the count. For Express or Lite Edition
Drivers, this is per licensed host. For Enterprise Edition, this
pool is shared by all client connections going through a given
Request Broker.
Maximum Logical Processors --
The maximum number of Logical Processors which the operating system
reports as present in the machine (physical or virtual) on which
the product (license) is deployed, i.e., the Express Edition Driver
Host, Lite Edition Driver Host, or Enterprise Edition Request
Broker Host.
ODBC Driver -- A
Software Application. A Software Application that provides a data
access channel between an ODBC compliant applications and a backend
database management system, using the native protocols of the
target DBMS or Driver vendor.
OLEDB
Provider -- A Software Application. A Software Application
that provides a data access channel between an OLEDB
compliant applications and a backend database management system,
using the native protocols of the target DBMS or Driver
vendor.
Request Broker
or simply Broker -- A Software Application. Receives
connection requests from Generic Clients, and apportions these to
Agents according to Rules defined by its administrator. Enterprise
Edition only.
XMLA Provider --
A Software Application. A Software Application that provides a data
access channel between an XMLA compliant applications and a backend
database management system, using the HTTP protocol.
Client Application
Restrictions -- Client application restriction which
specifies the criteria of how a license allows an application to
connect to a server.
Client Connection
Restrictions -- Client connection restriction which
specifies the criteria of how a license allows a client to connect
to a server.
Connections --
Client interface portals, formerly known as
Database Server Threads . A configurable number are
dedicated to handling HTTP-based client requests; the remainder are
available for any other data access mechanism (ODBC, JDBC,
OLEDB, ADO.NET, XMLA, etc.).
CPU Affinity -- A
programming mechanism by which an Application binds to one or more
CPU Cores (Logical and/or Physical), irrespective of total
available.
CPUs -- The
maximum number of Logical Processors which the Software Application
will utilize. On Windows and Linux (and soon on Solaris, AIX, and
HP-UX), this is managed by CPU Affinity, so the license may be used
on machines which report any number of processors, but the software
will only utilize the number specified by the license.
Note: Mac OS X does not support CPU Affinity, so your
license must enable utilization of at least as many Logical
Processors as are reported present in your Mac.
This document is empty and basically useless. It is generated by a web service that can make some statements in HTML+Microdata format.
This time the service made zero such statements, sorry.