Multiple Database connections for one user
- Thread starter WagnerJ
- Start date
tamhas
ProgressTalk.com Sponsor
Actually, since the dawn of PSC time, "concurrent user" has always been defined as one person sitting at one device and so even though they have multiple sessions started and appear as separate users from the point of view of -N, from a license perspective they are one user. If the sessions are on separate devices, however, then they count as multiple users.
In OE10 there are more options (including continuing to use concurrent user if that is what you have now). The Registered Client model licenses the device, regardless of the number of people who use it. This model is good for things like a shop floor where a large number of people might use a single station. Like Concurrent User, there can be multiple sessions on the same device and it counts as one user from a license perspective.
The Named User model licenses the person, regardless of the device. So, one person could actually have sessions active on multiple devices simultaneously and would still be one user from a license perspective.
Access Agent licensing can only be used for Occasional or Unknown users. Occasional is defined as an identifiable person who uses the application less than 2 hours a week and who is allowed into the application via restricted access, i.e., you have the potential for measuring the 2 hours. Unknown users are ones who cannot be identified and who access via a public website. For these user classes, you license the number of AppServer agents required to support the users.
It is clear that one can combine Access Agent licensing with either Named User or Registered Client. It appears to be within PSC policy to accept using all three, but you may encounter resistance on this from individual reps. Some reps are known to be accommodating about allowing one to purchase OE10 Concurrent Users without going through the fiction of buying them as V9 and upgrading, but this is certainly not universal nor official policy. Similarly, expect pressure to convert Concurrent User to either Named User or Registered Client if you want to use Access Agent. Policy is murky here too.
In OE10 there are more options (including continuing to use concurrent user if that is what you have now). The Registered Client model licenses the device, regardless of the number of people who use it. This model is good for things like a shop floor where a large number of people might use a single station. Like Concurrent User, there can be multiple sessions on the same device and it counts as one user from a license perspective.
The Named User model licenses the person, regardless of the device. So, one person could actually have sessions active on multiple devices simultaneously and would still be one user from a license perspective.
Access Agent licensing can only be used for Occasional or Unknown users. Occasional is defined as an identifiable person who uses the application less than 2 hours a week and who is allowed into the application via restricted access, i.e., you have the potential for measuring the 2 hours. Unknown users are ones who cannot be identified and who access via a public website. For these user classes, you license the number of AppServer agents required to support the users.
It is clear that one can combine Access Agent licensing with either Named User or Registered Client. It appears to be within PSC policy to accept using all three, but you may encounter resistance on this from individual reps. Some reps are known to be accommodating about allowing one to purchase OE10 Concurrent Users without going through the fiction of buying them as V9 and upgrading, but this is certainly not universal nor official policy. Similarly, expect pressure to convert Concurrent User to either Named User or Registered Client if you want to use Access Agent. Policy is murky here too.
