Danlaw uses a Token License Model to authorize the use of the capabilities of the MxSuite. Briefly this is how it works:
•The MxSuite has many separate components that we call MxComponents. The MxComponents are easily identifiable features or capabilities of the MxSuite. You may plan to use some of them on a regular basis, while using others only occasionally, or not at all.
•When you purchase a license to use the MxSuite you actually purchase a number of tokens. The tokens reside in a token pool on a computer we call a Token Host.
•Each MxComponent has an associated charge measured in Tokens. When you use that component a debit is made against a Token Pool. When you stop using the component, the Token Pool is credited by that same number of Tokens.
•If you attempt to use a component when there are insufficient Tokens remaining in the pool, the component will not start.
The MxSuite Price List itemizes and describes the available MxComponents and their associated token charge.
Tokens are served from a Token Pool. The computer that host the Token Pool is called the Token Host. The Token Pool can be stocked with Fixed or Floating tokens:
•Fixed Tokens - Fixed licenses (also known as node-locked licenses) are tied to a particular computer. That computer is a Token Host. It is only able to serve tokens to MxComponents running on that computer.
•Floating Tokens - Typically there is one Token Host computer in a department or organization. Any computer that has network access to the Token Host computer is able to borrow from its Token Pool.
Tokens may also have geographical restrictions:
•Site Floating - These tokens may be used within 3 kilometers of the Token Host only.
•Regional Floating - These tokens may be used only within the region defined in your license agreement.
•Global Floating - These tokens may be used anywhere.
Refer to your Danlaw Software License Agreement.
This is the simplest configuration. Fixed tokens are stored on the user's PC.
This is the basic floating token configuration. Multiple users access tokens from a shared pool on the Token Host.
You can configure token pools in many different ways using both fixed and floating tokens. In this example, PC 1 and PC 2 access tokens from a shared pool on the Token Host. PC 3 can access additional tokens from the Token Host after it has used the fixed tokens in its own token pool. See Using Multiple Token Pools. The fixed tokens on PC 3 can be used by the MxSuite application on PC 3 only. All instances of MxSuite can use the floating tokens on the Token Host.
Note: In the diagrams above, MxSuite is any MxSuite application.
MxServe™ is a Windows Service that runs on every Token Host computer. It is the guardian of the Token Pool. You interact with MxServe using the MxServe Manager™ and the MxV License Manager:
•MxServe Monitor is a stand alone application that enables you to add tokens, lend tokens, and report what tokens are in use and who has them checked out. It is used when installing floating licenses on a server. You should only run your primary instance of MxServe Monitor at any time.
•MxV License Manager is built into MxVDev, MxTransIt, and MxVDiff. Use it to install fixed (local) licenses.
These utilities have similar functions, which are organized into tabs.
Each client takes tokens from the first server in the list that has tokens available. Within each server, tokens are used in this order: