The License Manager manages Studio licenses. Licenses are leased to a server for a one-week period. After one week, the licenses are reclaimed and the License Manager can re-assign them. This system of leasing licenses offers two advantages. First, you can easily move licenses from one server to another as usage demands. Second, if you used a distributed configuration for Studio, your users can continue to access applications even if a connection to a central server is unavailable.
You can allocate licenses from your license pool to a specific Application Server. When you allocate these licenses, you determine the number of startup licenses (licenses available to the server on startup) and the number of incremental licenses (the number of licenses allocated to the server each time it reaches its limit of available licenses). For example, you can configure an Application Server to have 20 licenses on startup and get an additional 10 licenses each time the number of licenses available to that server is exceeded. The startup and incremental licenses are set from the Servers View. For instructions on modifying the number of startup and incremental licenses, see Editing Server Properties.
Under normal operating circumstances, a server requests new licenses from the License Manager well before its current licenses are reclaimed, ensuring that your users always have access to the applications they need.
There are two types of licenses available for Studio: base licenses and maintenance licenses. A base license provides authorization for the version of Studio that you purchased. Base licenses do not expire, but they do not allow you to upgrade to a newer version of Studio. A maintenance license allows you to use a base license with a newer version of Studio. For example, a maintenance license allows you to upgrade from Studio 4.x to Studio 5.x. Maintenance licenses are valid only through a specific date.
Was this article useful?
The topic was:
Inaccurate
Incomplete
Not what I expected
Other