License Types (Magic xpa 3.x)
The Magic xpa License File, when initially created, contains a default demo license. This demo license has no time limit but is limited in its functionality and cannot be used for the development and deployment of mission-critical applications. No PAK information is required for demo licenses.
MGDEMO, Development and Deployment Demo License
The MGDEMO license limitations are:
-
Application and data file capacity is 500 records
-
Maximum number of programs allowed is 150
-
Maximum number of data sources is 20
-
Maximum number of components allowed is 3
Permanent licenses have no time limit. Before you run a permanently licensed product, please follow the instructions supplied with the license.
When you start Magic xpa without specifying a license name, the Single User Edition will run.
Magic xpa's Single User Edition provides almost the complete range of features found in the commercial edition of Magic xpa, excluding multi-user related features and capabilities. See the Magic xpa Editions Comparison table to obtain a more detailed analysis of the differences between Magic Software’s Magic xpa editions. The single-user limitation is relevant for both the development of the application, as well as its deployment. The Single User Edition only works with the broker and not the space.
When working with the Space middleware, if you updated the license, you need to restart the space in order to use the updated license.
|
|
|
|
|
MGDEMO
|
Magic xpa Demo. Used for checking Magic xpa. Can be used for both the Studio and Runtime.
|
Yes
|
Concurrent users
|
No
|
MGCSTK
|
Magic xpa Studio. Used for developing applications (C/S and Web).
|
Yes
|
Concurrent users
|
No
|
MCSRT
|
Magic xpa Runtime Client Server. Used for deployment of Client-Server applications (Online).
|
Yes
|
Concurrent users
|
No
|
MGENTx**
|
Magic xpa Enterprise Server. Used for deployment of server and web based applications.
|
Yes
|
Concurrent requests
|
Yes
|
MGINTx**
|
Magic xpa Server used for Internet only.
|
Yes
|
Concurrent requests
|
Yes
|
MGPARTx**
|
Magic xpa Server used for Partitioning only.
|
Yes
|
Concurrent requests
|
Yes
|
MGRIA
|
Used for deployment of Rich Internet applications (Rich Client) for both mobile devices and desktop applications.
|
Yes
|
Concurrent users*
|
Yes
|
MGXTK
|
Express Studio. Same as the Studio license but limited to Pervasive DB only.
|
No
|
Concurrent users
|
No
|
MGXRT
|
Express Runtime Client Server. Same as the Client-Server license but limited to Pervasive DB only.
|
No
|
Concurrent users
|
No
|
MGXSRV
|
Express Server. Same as the Enterprise license but limited to Pervasive DB only.
|
No
|
Concurrent requests
|
Yes
|
* Multiple RIA clients running the same application on the same machine will be counted as 1 user.
** x can be either 1 or 2, depending on the server platform: 1 is for Intel-based servers (Windows, Linux) and 2 is for non-Intel based servers (AIX over PowerPC, Solaris over Sparc, IBM i over PowerPC).
*** Host locking – These licenses are bound to a specific host and can start only from that host.
License requirement example:
To develop a RIA application and deploy it later on, on mobile devices and on some desktops, you need to acquire an MGCSTK license for development, and an MGRIA license for deployment.
To develop an HTML merge application and deploy it later on, on desktops, you need to acquire an MGCSTK license for development and an MGENT1/2 license for deployment.