How many concurrent access licenses do you need for Esko WebCenter?


Type in how many users of each type there will be and you'll see how many licenses you need. You get two proposals:

  • Minimal number of licenses: When having this number of licenses, some people will still sometimes get locked out but this will be seldom. You get an estimation of how many times per year you'll exceed the maximum of users.
  • Safe number of licenses: When having this number of licenses it is very unlikely that anybody will get locked out.

 Concurrent access calculation

This WebCenter will be used as ArtiosCAD Enterprise Server
Number of frequent users (>1 hour per day) or guaranteed users:    users
Number of normal users (>1 hour per week):    users
Number of occasional users (<1 hour per week):    users
Number of Automation Engine Channels connecting to WebCenter:    channels
Licenses Lock-outs per year
Minimum number of concurrent licenses:   licenses  lock-outs
Safe number of concurrent licenses:   licenses  lock-outs
Other number of concurrent licenses:   licenses  lock-outs

Questions and answers

Question: What are the biggest benefits of concurrent licenses?


  • Invite new people to WebCenter at low additional cost. Adding a user to the WebCenter database has no extra licensing cost. Only when this person starts using WebCenter frequently, he'll consume log-in licenses. At that moment, the benefit is clear.
  • Lower user management effort. It is not needed to remove people from the user database when they are not actively using WebCenter for a longer time. Since they don't use it, they don't cost money. When they log on anyway, they cannot see anything more than what they are supposed to see.
  • Low cost and high availability for frequent or very important users. The WebCenter administrator can give certain people guaranteed access. These people can always log on, no matter how many other people are logged on already. The cost of this is only 1/3 of a concurrent access license.

Question: If I login from multiple browsers, maybe even from different computers, is this counted as separate logins?


No. The number of concurrent licenses counts the number of different users logging in at the same time. There is however a restriction on the number of times the same user can log in at the same time. (maximum 5)

Question: Can a user login be shared between multiple people?


This can only be done for people really acting as one person (for example a "duo-job") and there are a number of restrictions to be taken into account:

  • The number of sessions per user is restricted to 5. Each time you login, you get a session, and it stays open until you log out or until the session expires (typically after 30 minutes of no activity). Multple sessions are allowed to allow using multiple browser windows at the same time, which is sometimes really practical, for example to use one as a dashboard and another one for navigating. When however multiple users use the same login account "user guest", the maximum of 5 is rapidly reached and this becomes unworkable. People sharing the same login should really be time-sharing, for example the 2 operators of the same station in a 2-shift operation. Also remark that regulated environments don't allow sharing passwords between employees.
  • Each WebCenter user has one single e-mail address. WebCenter makes heavily use of e-mail notifications so you lose a lot of the value if not each person gets his e-mails personally.

Question: How do I create a guest user?


Guest users are created for 2 reasons:

  • Allow a large number of people to enter WebCenter and retrieve information without any shape of security. This works like a "public" website. We advise to give these people each a login anyway and add them to a group called "guest users". Give this group access to all "public" projects.
  • Demonstrate WebCenter by allowing people to play with it. Also here it is better to give people a real login so they get a better idea of the possibilities once they have a real account.

For limited use, it is clearly still possible to have a user with name guest. If too many people are using this account, they'll have to wait until a slot gets free.

Question: Explain the Automation Engine Channel Connections


When Automation Engine connects to WebCenter, it needs a session and therefore a username and password. WebCenter does not make a difference (and does not see the difference) between a machine connecting and a human-operated browser. By default, this means that Automation Engine can only make 5 connections per user (see above for the maximum number of connections). When more than 5 concurrent operations run between Automation Engine and WebCenter, some requests will fail and the Automation Engine task will fail. From WebCenter 14.1 onwards, there is a solution for this: a user can be given the right to connect more than 5 times (so change the session limit). Since this is added value for large systems and since this would allow to circumvent the WebCenter licensing system, we have decided to count these sessions as guaranteed access sessions. This means that for each 3 Automation Engine connections, 1 concurrent license is blocked. Remark that the old option (live with the 5 session limit) is still available and even the default.