License Management FAQ

The number of users who can log on to Jedox is capped by the number of concurrent users. These numbers can be found in Jedox Web Administration under Licenses. The Free Concurrent column shows how many concurrent ports are available, i.e., how many more users can log on at the moment.

The screenshot above shows a Jedox Suite Full User License with 5 seats. Every seat has 3 concurrent access ports. Two seats are given to named users. Currently, one of these users is using one access port (see Active Sessions) and there are 14 free concurrent access ports for this license.

A user can log on via multiple clients at the same time. The license that is assigned to the user has to include the clients. For example, not every license includes the use of Jedox Excel Add-in.

When using multiple clients at the same time, each session consumes one concurrency port on the license to which the user is assigned. For example, if a user logs on to the Jedox Server from both Jedox Excel Add-in and Jedox Web, then two concurrency ports are being used at that moment. There is no limit to how many concurrency ports a single user can use, other than the overall limit of concurrent license ports for the license assigned to the user, minus the number of other, parallel user sessions.

By default, sessions on the Jedox OLAP Server time out after 5 minutes of inactivity. The server checks for expired sessions once per minute, so the session may remain active for up to 60 seconds after the timeout. The length of the timeout is configurable on the OLAP Server.

If a user is logged on to Jedox Excel Add-in and is not actively using the session (that is, using Excel reports that show OLAP data, or using Jedox Excel Add-in dialog), the configured session will time out after these 5 minutes. The user's concurrency port then is available to another user.

Once the user is active again in Excel (for example, when recalculating the report), Jedox Excel Add-in will silently try to create a new session, as long as there are concurrency ports available. If the user had not saved credentials in his OLAP connection, they would then be prompted to enter their credentials.

By contrast to Jedox Excel Add-in, Jedox Web actively keeps the running session active, even if there is no user activity. As long as the user is logged on, the concurrency port used for the web session will be in use and not free to be used by someone else.

In the Jedox Mobile app for iOS, the OLAP session will time out after a period of user inactivity, even if the user remains logged on (due to restrictions of the iOS platform). By contrast, in the Jedox Mobile app for Android, the session is kept alive even if the app is running in the background with no user activity.

Both the Supervision Server and Internal Suite sessions are used for internal purposes. Their sessions in the OLAP server are created automatically, but they do not count toward concurrency limits. The _internal_suite user exists in the Jedox OLAP user list, but it does not have to be assigned to a specific license, and thus will also not count against the Named User limit (listed as "Seats" in Jedox Web Administration - Licenses).

The information how often a license has been activated is not available in the Jedox User Interface. If the license activation limit has been reached, any further activation attempts will result in an error message. If you want to find out how often your purchased Jedox License has been activated, you can contact Jedox Support.

An activated Jedox License is bound to the hardware it was activated on. The license will not work on new hardware. In this scenario, the license has to be activated again.

If an Integrator job uses a connection to Jedox In-Memory DB Server, it will create a session in the Server (with the user as defined in the Integrator project). However, this session does not count against the Concurrency Limit of the license.