Please note : This help page is not for the latest version of Enterprise Architect. The latest help can be found here.

Prev Next

Manage Allocations

The 'Manage License Token Allocations' screen is displayed when the Manage Allocations... button on the 'Pro Cloud Server License Manager' screen is pressed.  This screen allows the user to control how tokens are consumed to enable Pro Feature functionality.

The Manage Allocations screen is broken up into 3 sections, a Summary of token usage, Explicit Allocations, and allocations of tokens which are shared for Web Access.

Token Summary

The token summary lists the following:

Total - The total number of tokens based on the active license/s.

Explicit - The number of explicit token allocations. These refer to tokens which have been allocated to enable specific features on the server.

Shared - The number of shared tokens which are available. Shared tokens are consumed when users access features such as WebEA. When logging out the token is returned to the shared token pool.

Click on the Usage button to display a more detailed break down of the token allocations, including how many tokens are currently in use.

Explicit Allocations

This section allows you to enable Integration Plugins for your Pro Cloud Server. Enabling integration with a specific product (e.g. Jira) consumes one token.

Shared for Web Access

WebEA, Prolaborate and OSLC users consume a single token with every logon. For most environments these allocations can be left with their default values (0 reserved and no maximum). In this case all users are accessing a single shared pool of tokens, regardless of what type of access (WebEA, Prolaborate or OSLC) they require. Alternatively, each user type can define a number of tokens that are reserved (ie. can only be used by that type of access) as well as a maximum number.

Note: a Max Allowed value of 0 implies that users are NOT allowed, ie if WebEA's Max Allowed value was set to 0, the Pro Cloud Server would deny all WebEA user requests to logon.

Note: a empty value for Max Allowed implies there is no limit on the number of users, although the total number of users is still limited to the number of available tokens.

Learn more