© 2011 AgilePoint, Inc. All rights reserved.
For newAgilePoint customers purchasing AgilePoint BPMS v5.0 or higher, the AgilePoint Floating User License is available. In a floating license model, only the active AgilePoint BPMS system users are counted against the number of purchased license seats. The number of active users is defined as the number of user sessions on the AgilePoint Server at a given time.
A user session lasts from initial login from any application to the time the session times out. (The timeout period is configurable.) If the user logs in before the current session times out, the session and the timeout period are renewed. Applications that can initiate a user session include AgilePoint Envision, AgilePoint Enterprise Manager, SharePoint, customized web applications, or web service calls from Microsoft Internet Explorer.
Use the following calculation to estimate the number of users you will require under the AgilePoint Floating User License. Note that this is a basic estimate to be used as a general guideline intended as a starting point. You can use your own estimating scheme if desired.
[total number of AgilePoint users] * [average number of hours per day each user will be actively using AgilePoint] / [number of hours per work day] = [number of required floating license seats]
Example: 200 total AgilePoint users * 2 hours average usage per user per day / 8 hours per work day = 50 floating user license seats
If your total number of concurrent users exceeds the maximum number of active users allowed by your License Agreement, the AgilePoint Server will generate an email warning to the system administrator. At this point, system performance may slow somewhat.
If you receive a warning regarding your maximum users, AgilePoint recommends that you 1) monitor your license usage, 2) try tuning your session timeout settings to accommodate your current user load, and 3) purchase additional license seats if required.
To monitor your actual number of users, query the AgilePoint database to analyze your maximum number of users in a day, and the frequency with which that maximum is reached. The AgilePoint system refreshes the user session count every 10 minutes. A record is generated each time the maximum number of license seats is reached.
To monitor your license usage, run the following query against the AgilePoint Database:
select DATE_OCCURRED, OBJECT_INFO, DESCRIPTION as WARNING from WF_AUDIT_TRAILS where CATEGORY=7 order by DATE_OCCURRED desc
The results look like the following. L=n represents the maximum number of floating license seats. A=n represents the number of active user sessions.
DATE_OCCURRED
OBJECT_INFO
WARNING
2010-05-10 17:34:40.027
L=2,A=3
The maximum number of concurrent users allowed by your AgilePoint License Agreement is 2, but your actual n ….
2010-05-10 17:29:04.400
L=2,A=2
NULL
In addition, you can run the query in Microsoft Excel to create graphs that will enable you to track your usage over time. For Excel, create the following view:
CREATE VIEW WFV_FLOATING_SESSIONS as select DATE_OCCURRED as [TIME],CONVERT(INT, RIGHT(OBJECT_INFO, LEN(OBJECT_INFO) - CHARINDEX('A=',OBJECT_INFO) - 1)) as ACTIVATED_SESSIONS, DESCRIPTION as WARNING from WF_AUDIT_TRAILS where CATEGORY=7
Then create the following query:
select * from WFV_FLOATING_SESSIONS
TIME
ACTIVATED_SESSIONS
WARNING
2010-05-10 17:34:40.027
3
The maximum number of concurrent users allowed by your AgilePoint License Agreement is 2, but your actual n ….
2010-05-10 17:29:04.400
2
NULL
If your number of concurrent, active user sessions are exceeding the number of seats in your Floating User License Agreement, you can change the session timeout interval to better accommodate your usage.
There is a tradeoff between greater numbers of available license seats and system performance. If you have shorter session timeouts, you tend to have a higher number of available license seats, but frequent user session renewals can negatively impact system performance. On the other hand, if you have a longer user session timeout period, performance is better because the system is not renewing user sessions as often. However, longer timeouts can yield fewer available license seats and active sessions for users who are not actively using the AgilePoint system.
To modify the session timeout, in the AgilePoint neflow.cfg file in the <server> node, modify the value of the UALExpirationPeriod attribute (<server UALExpirationPeriod="n" ...>). The unit for this value is minutes. The minimum value is 15.
To increase your floating license capacity, contact AgilePoint Sales.
© 2011 AgilePoint, Inc. All rights reserved.