AppWave™ 5.1 Glossary

From AppWave
Jump to: navigation, search


This glossary includes terms from AppWave™ Enterprise Store, AppWave Public Store, AppWave Browser, AppWave Studio, and All-Access.


Index: A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

A

.aib
This file contains all registry keys and values and also the file structure for the app.
.app
This is the filename extension for an AppWave-enabled application file. So once you have managed a <Product> in AppWave Studio it is saved in the file <Product>.app. This file contains all files necessaries to run it: .tca, metadata.xml, .stc, .toc, .aib, and .pref. It also contains EULA files, icons, and screen shots.
.aw
An .aw file is a template that stores information about an application. This information includes: Product Name, Display Name, Version, Long Description, etc. The included files are: .tca, metadata.xml, templateversions.dat, EULA, icons, and screen shots.
Acceptance Criteria
In order for an app to be mastered it must meet required specifications. For example, no beta versions can be mastered, an original installer must be used, and Apps must be mastered using the prefetch option.
For more information see App Mastering Acceptance Criteria .
Administrators
This is the group of AppWave users that have access to the administrative functions in AppWave. They can access this functionality either through a web browser or through the Admin tab in the AppWave Browser. By default, the Administrators group is a member of the Authors group.
All-Access
Embarcadero All-Access licenses that are managed by AppWave provide you with industry-leading database tools, including DBArtisan®, Rapid SQL®, ER/Studio® family of products, and many more. They also provide powerful application development tools, including Delphi®, JBuilder®, C++Builder®, the InterBase® SMP database, and more.
All-Access Pass
This is a license key that unlocks all applications for a given All-Access level.
All Apps Folder
When installation is complete, the All Apps folder will not contain the All Users group. AppWave Browser users have access only to applications corresponding to the license level assigned on 1.x through the migration folder after an upgrade. Apps appear in Pending only when they are removed from All Apps folder; in this case the folder is not assigned to All Users group, but it contains all apps.
All Users
This is the group that contains all AppWave users. Members of this group have access to the Apps tab in the AppWave Browser. When a user connects to AppWave for the first time, they are automatically added to the All Users group.
App
Once an application is mastered, it is referred to as an App. Apps are the applications that are mastered into a single file that runs without installation. The application runs on the desktop, locally and under ‘full power’ but does not change OS or registry. Apps run within their own space, with no shared DLLs or other system-wide settings that could conflict with other applications. Application data, including settings and licenses are stored locally on the hard drive separate from the executable.
App Cache Size
This is the amount of memory set aside as cache for use with streamed applications.
App Channel
A channel is a landing page inside the AppWave Browser including an app description, reviews, and an app/version selector. Each product has a channel.
Application Repository
AppWave distributes Embarcadero products through a local or shared repository. When you specify the repository location, you then have to specify the access rights for that directory. The AppWave Browser gets the streamed apps through the streaming server and others (installers) have to be cached locally.
Application Service Provider (ASP)
A provider of streamable applications, which could be a user’s company IT group, a software vendor, or an online gaming company. An ASP packages software applications into a format that can be streamed to clients over the Internet or a company internet.
AppWave
AppWave is where you centrally provision, manage, and update your All-Access software and licenses inside your own firewall. You control what product versions are available to end users. With network licensing, you can use the server to centrally control the list of authorized users, and what licenses they have access to.
AppWave (formerly known as ‘host’)
The machine where AppWave is installed that the AppWave Browser connects to in order to browse and download applications.
AppWave App
This is an application that was mastered with AppWave. These apps have instant access to your products without installation. It is a ready-to-run app launched from the AppWave Store.
AppWave Browser
This is the client software that the AppWave user installs allowing a user to launch AppWave applications. It provides a primary entry point to the various products used with All-Access. You can launch, install, update, and select product versions, all from a single user interface. It can be configured to run standalone, to receive products from Embarcadero, or to run with AppWave on your own network.
AppWave Channel
A channel is a landing page inside the AppWave Browser including an app description, reviews, and an app/version selector. Each product has a channel.
AppWave for Custom Apps
The product name for the license to package internal applications of a costumer for use with AppWave.
AppWave Enterprise
The AppWave Enterprise describes the AppWave as an installed product catalog of apps within an organization typically used to broadcast commercial and custom apps relevant to that organization and accessed by employees of the same organization. AppWave Enterprise is typically behind the company firewall and in many cases without direct access to the internet.
AppWave for <Product>
The product name for a license to use <Product> when it has been mastered and is available on AppWave.
AppWave Name
The AppWave name is set by the Administrator in the System Management > System Properties page. You can set the name in General Properties in the AppWave name field. This is the name of the AppWave, not the name of the machine that holds the Host. This AppWave name appears as a folder in the Apps portion of the AppWave Browser.
AppWave Network Mode
When using AppWave to manage applications, it operates in network mode. Users connect to AppWave from a Web browser and download the AppWave Browser from the repository. Licensing is automatically handled by AppWave.
AppWave Public Store
The AppWave Public Store describes the AppWave accessible to the public containing free and commercial vendor apps for purchase. The AppWave Public Store can be accessed by anyone with access to the internet. This store is hosted and managed by Embarcadero.
AppWave Store
The AppWave that Embarcadero maintains for all of the Embarcadero-provided applications and templates and the e-commerce web site that allows customers to purchase applications they can use in AppWave. In the AppWave Store the user can purchase applications that they can use in AppWave. This includes Embarcadero-provided applications, templates, and e-commerce web sites.
AppWave Studio
The application (within the AppWave Browser) that a user can use to master applications for AppWave. You are walked through a series of steps where you master and then broadcast the App file for your selected application. This can then be run on the local machine and be launched from either the local hard drive or the network using AppWave Browser.
Authors
This is the group of AppWave users who are able to master applications for use in AppWave. Members of this group have access to the Studio tab in the AppWave Browser. Authoring permission is granted by the Administrator.
Autogrow
When streaming, if the cache cannot accommodate the size of the full app, the cache can automatically grow to accommodate the new size. The Autogrow default setting is On, and the command is available in the AppWave Browser under Menu > Options. If the Autogrow setting is not selected you will be asked, via the browser, to increase the size of the cache to meet the size requirements.
Auto Load
You have the option to always launch the AppWave Browser. This means that it automatically loads when the operating system is started. Then any previously run apps that have been downloaded are “auto loaded” as well as the catalog. Once an App is run, it automatically loads each time.

B

B2B
Business to Business. B2B transactions are through purchase orders through our sales offices.
B2C
Business to Consumer. B2C transactions are processed with Cleverbridge as the payment processor.
Brand
This is one of the steps of mastering an application in the AppWave Studio. An application is identified or “branded”. The branding information includes product name, display name, version, publisher, web site, icons, product description, licensing information, etc. This information then appears in the Studio and/or AppWave Browser.
Broadcast
This is one of the steps of mastering an application in the AppWave Studio. Once you have broadcast a product to AppWave, that product is streamed or made available to users via AppWave.
Browser
See AppWave Browser

C

Cache Folder
This is where you will store your download. This is your Product Repository.
Caching
Caching occurs when you obtain your licensed installers and executables, and download them from Embarcadero to your AppWave.
Channel
Channels, or groupings, can be created for any purpose, by an administrator. For example, you could create the “New Hire Channel” to see all the applications needed to get started with your work. A channel is a landing page inside the AppWave Browser including an app description, reviews, and an app/version selector. Each product has a channel.
Client-Centered Environment
Also known as a client workstation mode, the AppWave Browser user downloaded products from Embarcadero which you then license using the Embarcadero Developer Network (EDN).
Client Network Mode
This is server-centered environment where app executables are provisioned and licensed by AppWave and then accessed using the AppWave Browser.
Common Gateway Interface
The CGI is a standard protocol that defines how web server software can delegate the generation of web pages to a console application. Such applications are known as CGI scripts; they can be written in any programming language, although scripting languages are often used.
Custom Scripts
The AppWave Studio Custom Script Support gives the user the ability to define a custom action called an AppEvent, at key points: (1) before or after an App is added to a machine; (2) before or after the App is launched; and (3) before or after the App is running.

D

Disposition Layers
The layers used to configure individual system resources, such as a file, folder, registry key, or registry value. The layer determines whether the system resource can be seen by the local system, and whether it is permanent or can be removed.
  • Layer 1: Installed-permanent - Copies assets (files, folder, registry keys, and registry values) permanently onto the local system, and can be seen by the entire local system.
  • Layer 2: Installed-temporary - Installs assets during the activation process, and uninstalls assets during the deactivation process. The original asset is backed up before the new asset is installed, and when the new asset is uninstalled the original asset is restored.
  • Layer 3: Virtual-integrated - (default setting) Assets that can be seen both by the streamed application and the local system, but are not physically installed on the local system.
  • Layer 4: Virtual-Isolated - Assets that can only be seen by the streamed application, and are not physically installed on the local system.
Dynamic Cache
The dynamic cache is created with launching an application in the AppWave Studio. This cache is cleared when using the Remove Application option.
  • For Windows XP, the cache location is: C:\Documents and Settings\<your_user>\Local Settings\Application Data\Embarcadero\Product Repository\StreamingCore\Profiles\<your_user>\Sessions\<session_id>\Applications.
  • For Windows 7, Windows 8, and Vista the cache location is: C:\ProgramData\Embarcadero\Product Repository\StreamingCore\Profiles\<your_user>\Sessions\<session_id>\Applications; C:\Users\<your_user>\AppData\Roaming\Embarcadero\Product Repository\StreamingCore\<session_id>.

E

Embarcadero Development Network
The EDN provides support, updates, upgrades, new products, and access to premium content on the Embarcadero Developer Network and is a way to provide a cost-effective way to license products and tools. You can also create your own EDN accounts.
Embarcadero License Center
The ELC is integrated with AppWave and installs automatically when you install AppWave. If you are upgrading your Embarcadero License Center installation, you will set up licenses, users and groups. You do not have to cache products on AppWave if AppWave will only be managing your site licenses and you do not have an All-Access license.
exclusions.dat
This file contains information for autodetecting exclusions applications.

F

File Association
With file association, you have the ability to launch AppWave applications using the file format typically associated with that application. You can also access the functionality typically made available within the right-click menu of a file type. It also covers the proximity and visual presence of the AppWave Browser when launching an app directly via file association, license checking, etc.
Free AppWave Store Apps
This refers to free apps available from Vendors through the AppWave Store. End users will need to be connected to the internet in order to register and use free apps from the AppWave Store.
Fully Streamed
The streaming activity is initiated when a user selects to "Run" an app using the AppWave Browser. AppWave streams the app into the client cache and loads the app onto the screen of a user before it is fully streamed. The app is said to be "fully streamed" when 100% of the app has been streamed into client cache - which is also a pre-requisite for the offline use case. This improves performance and enables offline usage.

H

Harvesting
Harvesting refers to mastering an app from an application that is already installed on the app author’s PC. With this feature the app author does not have to master the app using the application’s installer.
Heartbeat Period
Number of minutes between “keep alive” pings to the streaming server. The heartbeat maintains streaming server connectivity and alerts AppWave when the streaming server does not respond.
Heartbeat Grace Period
The number of minutes to wait for the streaming server to respond to a heartbeat. If the streaming server does not respond within this period, the streaming server is considered to be offline and a notification is generated.
Hosted AppWave
An AppWave host that is located on the Amazon EC2 cloud or elsewhere outside of the customer's site and is managed by Embarcadero.

I

Integrated-Complex Apps
With AppWave you can master complex applications (for example, Microsoft Office, Visual Studio, Autodesk Design Suites, Adobe CS5, etc.). Suites, or larger product "bundles", require a deeper level of integration with the operating environment. Once mastered, common components are exposed within the Windows UI as a collection of executables, right-click menu extensions, and file associations.
ISV
An Independent Software Vendor would create, edit, and broadcast applications using the Studio’s Create an AppWave from Install function.
Item
Anything that has a SKU (Stock-keeping Unit) associated with it.

L

Launch at Startup
You have the option to always launch the AppWave Browser. This means that it automatically loads when the operating system is started. Then any previously run apps are “auto loaded” as well as the catalog. Once an App is run it automatically loads each time.
License, AppWave Browser User
This license is required for each AppWave Browser user. This license entitles the user to connect to AppWave and run Embarcadero applications as permitted by the administrator.
License, AppWave for Premium Product
This license is required in order for an AppWave Studio user to master and deploy a premium application to AppWave. This license is purchased separately for each application and gives the AppWave Studio author access to an Embarcadero-created template that guides the Studio user easily through the mastering process of premium applications.
License, AppWave for Products License
These licenses are purchased by organizations from Embarcadero so they can master and run complicated commercial applications and run them in their own AppWave environment.
License, AppWave for Custom Apps
This license is required in order to use AppWave Studio to master and deploy applications, such as in-house applications, for which Embarcadero is not currently providing premium support.
License, Concurrent
Floating license. Can be assigned to a group or an individual user. A concurrent license can be borrowed from the license pool and when the user quits the application, the license is returned to the shared pool and made available for another user to use.
License, MyApps
This license is required for the AppWave Browser user who will be connecting to AppWave in order to launch and run custom or premium Apps mastered in your company.
License, Network Named
A network named license is a license assigned to a specified user for their use anywhere on the network, from any IP address.
Licenses, Premium or Custom App Product
Through License Automation, AppWave can manage the licenses of custom 3rd party Apps you have mastered. This provides the license key and displays information on how to use the license when the AppWave Browser user launches a 3rd party App. Depending on the App, in the AppWave License Automation pages, you need to provide the license as either a serial key or as a .csv file containing multiple serial keys.
License Automation
The License Automation feature enables AppWave to automatically provision licensing information for 3rd party Apps. An AppWave admin must set up licenses for license automated supported Apps in the Admin console. The number and types of licenses can be customized by the admin. AppWave will then allocate licenses through license automation and ensure the number of simultaneous users of that app does not exceed the specified settings.
Lightweight Directory Access Protocol
LDAP is an application protocol for querying and modifying directory services running over TCP/IP.

M

MD5
Message-Digest algorithm 5 (MD5) is used to check the integrity of files. The .aw and the .app files must come together with the associated md5 message digest file. Each time one of the two files needs to be changed, the .md5 file must be changed too.
Managed Apps
Contains shortcuts to apps that you have downloaded. Helps you easily find your apps. You can change the title of this menu item to something like Denny’s Apps, in the AppWave options dialog accessed on the Tools and Options (Tools.gif) menu.
Master
When you package or wrap an application so it can be used in AppWave.
Mastering Template
This is a plug-in that allows the user to master a given application with default settings.
Metadata.xml
This is the information used by Appwave host to add the new app or template to the server catalog.
MSI Installer
MSI files are database files, used by Windows Installer. They contain information about an application which is divided into features and components, and every component may hold files, registry data, shortcuts etc. The MSI file also contains the UI that is to be used for installing, and various other data such as any prerequisites to look for, custom actions to execute, the order of the installation procedure, whether to support Administrative installations, etc. MSI files are the current recommended way of doing installations on Windows. The .msi files provided must have the ability to run in Unattended mode.
Membership
Provides support, updates, upgrades, new products, and access to premium content on the Embarcadero Developer Network (EDN), plus Embarcadero® AppWave for one-step access to your tools without installation.
Multiple Entry Points
There are products which include several applications. So when the applications are being mastered, the installer installs several applications which could be launched with different command lines. It could be a different executable or the same executable but with different command line parameters. With Multiple Entry Points, you do not have to produce several Apps with different command line arguments. This eliminates the need for extra disk space on the server (in the repository and in the streaming cache folder and client local cache). In addition you do not have to master additional Apps.
My AppWave Name
Managed Apps is the Default setting in the AppWave Browser. However, you can change the title of this menu item to something like Denny’s Apps, in the My AppWave Name field in the AppWave options dialog accessed on the Tools and Options Gear.png menu.
My Documents
The My Documents folder is your own personal folder in which you can store your documents, graphics, and other personal files. When there is more than one person using the computer, Windows creates a My Documents folder for each user on the computer. By default, the target or actual location of the My Documents folder is C:\Documents and Settings\user name\My Documents , where C is the drive in which Windows is installed, and user name is the currently logged-on user. However, companies can change this folder to a network location instead of their local machines
My Tools License (Enterprise Client)
A concurrent license that is consumed by the AppWave Browser, that governs whether a user can run Apps that were mastered by a customer. Only one license is required per user and machine. All Apps requiring a MyApp license share the same MyApps license. This is to simulate "machine" license.

N

Notifications
These messages come from AppWave. The AppWave administrator configures what types of messages are sent out as notifications. Notification messages can include new product or version availability, downloads complete, and download errors. You can also subscribe to an RSS news feed of notifications from the AppWave Home page of the AppWave console application.

O

On-Demand
Tools can be delivered on demand to users as they need them from the AppWave Browser. Applications they have licenses for automatically show up in their Browser. You can see what previous versions are available and can run versions side-by-side without conflicts and without uninstalling and reinstalling versions.
One-click Mastering
The AppWave Studio has third party commercial and OSS applications that have already been mastered previously by Embarcadero and have auto-fix capabilities. If you master one of those apps, then a plug-in has been created to help you fix all potential problems.
Open Mode
In unrestricted or open mode, broadcast Apps are published to the All Apps folder which is assigned to the All Users group. The administrator can fine-tune the members of the All Users groups and the Apps available in the All Apps folder to restrict application usage. In open mode, all users can access all reviews on AppWave as soon as they are submitted.

P

PADE
The purpose of a Packaging Analyst & Design Engine (PADE) is to help correct problems frequently encountered when preparing an application for an APP. PADE allows for plug-ins to analyze the content of the application and recommend changes and potentially make changes.
A single plug-in can support multiple resolutions.
Parsing
Parsing takes a TCA profile and maps the file location to where they are going to appear when you are either running or have the app mounted on your machine. It mounts the app as part of your profile.
.pref
This file contains information to improve the timing of when an application is launched, and is recorded in the Test page of the AppWave Studio after mastering the app.
Prefetch
Prefetching is the process of streaming application blocks prior to their being explicitly requested by AppWave Browser, in anticipation of being needed by the application. Be advised that only some key blocks of application data from AppWave are necessary for the application to launch and perform basic functions.
Premium Application
A premium application is an application for which Embarcadero provides a mastering template. This template contains licensing information which allows for License Automation. Once a premium application has been mastered the licenses for the application can be managed by AppWave.
Premium or Custom App Product Licenses
Through License Automation, AppWave can manage the licenses of custom 3rd party Apps you have mastered. This provides the license key and displays information on how to use the license when the AppWave Browser user launches a 3rd party App. Depending on the App, in the AppWave License Automation pages, you need to provide the license as either a serial key or as a .csv file containing multiple serial keys.
Private Server
A Private Server means those operated by AppWave Enterprise licensed owners, in their own network. Private servers can be configured to authenticate via several means (local, LDAP, etc). When a user starts AppWave Browser or connects to AppWave, the application-populated folder appears in the Private AppWave. The apps are broadcast from AppWave to AppWave Browser user.
Product Channel
A channel is a landing page inside the AppWave Browser including a description, reviews, and an app/version selector. Each product has a channel.
Product Name
When creating an app for an Embarcadero product, choose the Product Name from the drop-down list of available names. This is done during the Branding step of the creation process. You must select the correct name or the concurrent licensing will not be managed by AppWave.
Public Server
Public servers are operated by Embarcadero.

R

Repository Cache
This is the directory where the applications that will be streamed are saved on the AppWave Browser user’s local machine. The primary purpose for the cache is to allow partial downloading of an application before showing the application to the user. This is especially important when working with large applications because caching the application allows the user to begin using the application sooner, before the entire application has been cached.
Restricted Mode
You can operate AppWave in either Restricted Mode or Open Mode. In restricted mode, the admin must approve any new reviews or broadcast Apps before they are made available to AppWave Browser users. In unrestricted or open mode, broadcast Apps are published to the All Apps folder which is assigned to the All Users group. The administrator can fine-tune the members of the All Users groups and the Apps available in the All Apps folder to restrict application usage.
Runtime
This refers to execution runtimes that some products need like the .NET framework which RADStudio needs. Runtimes are provided for authors to include when creating their apps. They can pick and choose what to include.

S

.stc
The .stp file is an appset file. It is encrypted and stores the files, folders, and registry settings needed to reproduce the application being mastered on the end users machine. This file is the result of mastering a project in Test page. It's a zip file containing necessary files (.stc, .toc, and .aib) for running an application. It can also contain EULA information files, icons, and screen shots.
SDK
Software Development Kit is typically a set of development tools that allows for the creation of applications for certain software, software framework, hardware platform, computer system.
Search
The search function in both the AppWave Browser and AppWave Store searches all fields with the exception of product reviews written by the user.
Staff
In the AppWave Store, the Staff is all the personnel who have access to the Vendor’s account. The information for each staff person is displayed on the Staff tab and includes ID number, name, e-mail address, and status.
Stage
In the AppWave Store, once you create and manage your application you submit it to Embarcadero for staging. This is where your submission is reviewed. You can then review the feedback on the review.
Start
In the AppWave Studio, this is the first step in creating your App. You select a source and begin to build your App. This step currently allows you to select the launch command (the application's executable), view and edit files, view and edit registry entries, and manage environment variables.
Static Cache
You can view the size of the Static Cache (also referred to as the App Cache) in the AppWave Browser Options. Click Options and then click Clear.
  • For Windows XP, the cache location is: Repository\StreamingCore\Profiles\<your_user>\Sessions\<session_id>\Cache.
  • For Windows 7, Windows 8, and Vista the cache location is: C:\ProgramData\Embarcadero\Product Repository\StreamingCore\Profiles\<your_user>\Sessions\<session_id>\Cache.
Streaming
An application is constantly received by and presented to an end-user while being delivered by a streaming provider.
Subject Channel
Channels can be created for any purpose, for example a “DBA Channel”. Channels can include both Product and Subject Channels. So a subject channel would contain apps pertaining to a specific type.
Subscribing
You can also ensure you always have the latest version of your applications by subscribing to AppWave notifications and by checking the Notifications folder in AppWave Browser, so you will always know when a new version is available.
Suite Product
Suite Products are complex applications such as Microsoft Office, Visual Studio, Adobe CS5, etc., that have multiple entry points. The Suite contains multiple applications. For example Microsoft Office includes Excel, Word, PowerPoint, etc.

T

.tca file
The .tca file contains the registry and folder and files structure captured during a software installation along with resources, launch points, and registry settings required to run a product. It also contains information about the product such as the version, name, and editions. Every time a user needs to master an App, a .tca file is created.
templateversions.dat
This file contains information about harvesting. Some templates will contain several versions of an application, and this file indicates which tca file will be used for which version.
Test
In this step you master all the elements needed to build the app and then test the results.
Threshold
Default or user-defined values that mark performance boundaries. Thresholds are the point that must be exceeded to begin producing a user-defined effect or result or to elicit a response.
Ticket
When a customer encounters a problem and reports it in the AppWave Store, a ticket is generated and submitted to the vendor for correction, additional information, etc. The Ticketing site is where you manage all aspects of your tickets.
.toc
This is the token file, containing the information used by the player to run the app. It includes the launch command, environment variables, all the custom settings, and app events for the app.
Turbo Option
This is a performance option that allows the AppWave Browser to run in a more resource-efficient and feature-rich fashion. This is the default option. If the user does not have administrator rights at the time of install, the AppWave Browser installs without the turbo option. The executing code has complete and unrestricted access to the underlying hardware. It can execute any CPU instruction and reference any memory address. The Turbo mode is generally reserved for the lowest-level, most trusted functions of the operating system.

U

User Mode Streaming
In User mode, the executing code has no ability to directly access hardware or reference memory. Code running in user mode must delegate to system APIs to access hardware or memory. Due to the protection afforded by this sort of isolation, crashes in user mode are always recoverable. Most of the code running on your computer will execute in user mode.

W

Web Caching
Web Caching configures a transparent proxy set up between AppWave and AppWave Browser. If this proxy is configured, AppWave would add special headers to streaming data sent to the AppWave Browser. This allows the streamed data to be cached on the proxy server so that the next time an AppWave Browser user asks for the relevant application, the streamed data is sent directly to the AppWave Browser from the proxy. This ability may be useful when the communication channel between AppWave and AppWave Browser is poor.
Windows Authentication
Automatically authenticates connections between Microsoft Internet Information Services, Internet Explorer, and other Active Directory aware applications.
Windows Services Registration
AppWave is automatically registered as a Windows service, therefore it starts when your machine starts. By default, the service is named Embarcadero AppWave. If you do not want AppWave to start as a Windows service, you can reset or otherwise change the service by selecting Start > Embarcadero AppWave X.X > Configure AppWave. In the Embarcadero AppWave Properties dialog, select the General tab and change the service parameters.
Working Folder
The user can pick a directory in the working file directory. However, you can’t enter your own path, the folder has to exist already. When the launch command manages it, it is converted to what is needed.
Workstation License
A workstation license is a license assigned to a specific workstation for its use by specified users associated with that workstation. Permissions allow you to define who can and cannot use the workstation license and under what circumstances, offline or online only.
Retrieved from "https://docwiki.embarcadero.com/AppWave/5.1/e/index.php?title=Glossary&oldid=1128"