Sessions (-> "Administration/Accounts")
All currently logged in users are displayed here. Logging off a user requires administrator rights. A user cannot terminate his own session.
Sessions overview
(1) Type: The type of the session.
(2) Login: The time when the user logged on.
(3) Locks: The number of entries locked by this user.
Context menu of a session line
|
Terminate session |
This allows you to terminate the selected session, provided that you have administrator rights and it is not your own session. |
|
Show/edit locked entries |
Display and edit the entries blocked by the user of the selected session. See the following section. |
Locked entries
Locked entries can either be an open entry (e.g. a profile that is being edited), or a blocked profile, or an erroneous job that has been locked.
(4) Type: The type of the locked entry.
(5) Name: The name of the entry.
Context menu of a locked entry
|
Unlock |
A locked entry will be unlocked. |
|
Go to menu item |
Jumps to/opens the entry. |
|
Unlock all but errors and blocked profiles |
All locked open entries are unlocked (e.g. an open profile that is edited), but not blocked profiles and not locked errors . Note: Locked open entries are automatically unlocked when you log in again with the same user. |
|
Reload |
Update the locked entry (a user might, in the meantime, have closed a profile or corrected or unlocked an error job). |
Allowed number of sessions
Once the maximum number has been reached, no further logins are possible.
Session timeout
If an Internet connection is available, then a session will last endlessly with the browser tab open.
Otherwise, the session will end after a timeout.
The timeout is specified in configuration file ./etc/webdefault.xml in minutes.
...<session-config> <session-timeout>30</session-timeout></session-config>...Note: In rare cases, this timeout mechanism may not work properly. This would lead to a collection of dead sessions and at some point the allowed number of sessions would be reached and users would no longer be able to log in. To prevent this, a secondary timeout mechanism can be used. To do this, use parameter timeoutIntervalHours (values are specified in hours) in configuration file ./etc/startup.xml. The secondary timeout should be set to a higher value than the primary timeout to avoid undermining the primary timeout. If the secondary timeout is exceeded and any user logs on to the system, the dead sessions are removed.
<?xml version="1.0" encoding="ISO-8859-1"?><!DOCTYPE Configure PUBLIC "-//EBD Integration//DTD Configure 1.0//EN" "http://www.ebd-integration.de/dtd/configure_1_1.dtd"><Configure class="com.ebd.hub.services.startup.StartupService">... <Call name="addApplication"> <Arg> <New class="com.ebd.hub.datawizard.app.DataWizardSetup"> <!-- if start of datawizard fails, stop the whole system --> <Set name="stopServer">true</Set> <Call name="setConfiguration"> <Arg> <New class="com.ebd.hub.datawizard.app.DataWizard"> <Set name="timeoutIntervalHours">2</Set>...