Active Connections

File -> Active Connections


This screen allows you to view current user connections connected to the database.  A slightly different screen layout will be presented in an HTTPS environment Vs a TCP/IP environment.


Licensing Behaviour in Continuum

Active User Connections

Typically, a user launches the Ostendo.exe application, which consumes one local user Licence per connected user. This is the core application used for normal system operation.

An alternate application, Datascreens.exe, is also available. This application restricts the user to running only:

  • Custom Datascreens (e.g. Full Time Capture)
  • Timesheets
  • Reports
  • Views
  • Analysis Grids


Multiple Datascreens.exe sessions can be run simultaneously; however, they will only consume a single local user Licence in total, regardless of how many Datascreens sessions are active.

Licence Consumption Rules

Local user Licences are consumed as follows:

  • Each user connected to the database using Ostendo.exe consumes one local user Licence per user.
  • All users connected via Datascreens.exe collectively consume only one local userLicence , regardless of the number of sessions.
  • If Ostendo API Security Records are defined, they will consume one additional local userLicence .

Example

In the example shown:

  • CATHY, BEN, and BRIAN are connected using Ostendo.exe, consuming three local user Licences.
  • FACTORY and PAINTING are logged in separately but are using Datascreens.exe, collectively consuming one localLicence .
  • An indicator (3) shows that one or more Ostendo API Security records are defined, which consumes one additional Licence.


Therefore, the example below shows five active user connections consuming local Licences.

Active Connections Screen (HTTPS Environment)


  1. When this screen is initially launched you should press the Get Connections button to return all current database connections. This will populate the body of the screen with each connection record
  2. In this example, there are currently 5 connections to this database that are consuming local Licences.
  3. The wording (API Licence Active) indicates that one or more Ostendo API Security records are defined, therefore it is assumed the API is currently running.
  4. UserName: Indicates the user that logged on to initiate that session
  5. Logged in at: Indicates when that user logged into Ostendo
  6. Process: Indicates the actual process running either Ostendo or Datascreens
  7. ClientIP: Shows the IP address of the session (This is only visible for Remote Databases)
  8. Last Accessed (Remote Client Only): Shows the last activity date/time (This is only visible for Remote Databases)
  9. Session Type: Remote Client for Remote databases or Ostendo User for TCP/IP environments.
  10. Load Licence: This button only needs to be pressed if an initial Licence requires loading into the database, from that point on, all renewal Licences are applied automatically.





Special Note - Timed-Out Sessions in an HTTPS Environment Only:

Unlike previous versions of Ostendo, in an HTTPS environment, sessions that remain inactive for approximately 10 minutes will automatically time out and disconnect from the database, freeing the associated user Licence.

When the user returns and resumes activity, Ostendo automatically reconnects the user and their session, provided that sufficient user Licences are available at that time.

In previous versions of Ostendo, administrators had the ability to forcibly disconnect users to free up Licences. However, this could be undesirable if the user was in the middle of a critical process or transaction.

This enhancement ensures that users who leave their sessions open do not continue consuming a Licence while inactive. Licence usage is therefore self-managed, removing the need for administrators to manually disconnect inactive users.


If a user launches Ostendo and does not proceed to Log In and simply leaves the Log In screen active, this screen will be automatically closed down by Ostendo after 5 minutes of inactivity.

Active Connections Screen (TCP/IP Environment)


  1. When this screen is initially launched you should press the Get Connections button to return all current database connections. This will populate the body of the screen with each connection record
  2. In this example, there are currently 3 connections to this database that are consuming local Licences.
  3. The wording (API Licence Active) indicates that one or more Ostendo API Security records are defined, therefore it is assumed the API is currently running.
  4. UserName: Indicates the user that logged on to initiate that session
  5. Logged in at: Indicates when that user logged into Ostendo
  6. Process: Indicates the actual process running either Ostendo or Datascreens
  7. Session Type: Always displayed as Ostendo User
  8. Load Licence: This button only needs to be pressed if an initial Licence requires loading into the database, from that point on, all renewal Licences are applied automatically.




Special Note - Timed-Out Sessions

If a user launches Ostendo and does not proceed to Log In and simply leaves the Log In screen active, this screen will be automatically closed down by Ostendo after 5 minutes of inactivity.