USER MANUALS

Session Configuration (Data Marketplace, Design Studio, Diagnostic & Monitoring Tool, Scheduler and Solution Manager Administration Tool)

The content of this page applies to the installation of the Denodo Platform and Solution Manager.

In Data Marketplace, Design Studio, Diagnostic & Monitoring Tool, Scheduler and the Solution Manager Administration Tool, you can configure several types of timeouts. This page explains how to do it.

Idle Session Timeout

The idle session timeout is the period of inactivity after which the user is automatically logged out.

Default idle timeout: 30 minutes. This timeout is defined by the lowest value among the following two configuration properties:

  1. The value of the parameter <session-timeout> in the configuration file of the web container (i.e. <DENODO_HOME>/resources/apache-tomcat/conf/web.xml).

    The value of this parameter is in minutes.

  2. The value of the property server.servlet.session.timeout of the configuration file of the application. That is:

    • Data Marketplace: <DENODO_HOME>/conf/data-catalog/DataCatalogBackend.properties (Solution Manager does not include Data Marketplace).

    • Design Studio: <DENODO_HOME>/conf/design-studio/DesignStudioBackend.properties

    • Scheduler: <SOLUTION_MANAGER_HOME>/conf/scheduler-webadmintool/ConfigurationParameters.properties.

    • Solution Manager Administration Tool: <SOLUTION_MANAGER_HOME>/solution-manager-web-tool/SMAdminConfiguration.properties

    You need to do this in the installation of the Denodo Platform and/or Solution Manager; depending on the applications you use on each installation.

    The idle timeout of the Diagnostic & Monitoring Tool is the value of the <session-timeout> of the web.xml file.

    In this configuration file, you can specify the time unit in hours, minutes, seconds or milliseconds (milliseconds will be used by default). The following examples set 1-hour timeout using different time units:

    • server.servlet.session.timeout=3600000 (milliseconds will be used if the time unit is not specified).

    • server.servlet.session.timeout=3600s (seconds).

    • server.servlet.session.timeout=60m (minutes).

    • server.servlet.session.timeout=1h (hours).

After changing these values, restart the web container - not just the application - for the changes to take effect.

Configuration Example

To set a 2-hour timeout in Design Studio, do this:

  1. In <DENODO_HOME>/resources/apache-tomcat/conf/web.xml, change the value of <session-timeout>. I.e.

    <session-timeout>120</session-timeout>

  2. In <DENODO_HOME>/conf/design-studio/DesignStudioBackend.properties, change the value of server.servlet.session.timeout. I.e.

    server.servlet.session.timeout=2h

  3. Stop Virtual DataPort.

  4. Execute <DENODO_HOME>/bin/webcontainer_shutdown, to stop the web container; so the changes in the web.xml take effect.

  5. Start Virtual DataPort.

  6. Start Design Studio and the other web applications you use.

Maximum Session Timeout

The maximum session timeout is the maximum time a user can be logged in and after that, the session finishes.

Important

This is not an inactivity timeout; it will be applied even when the user is active.

This feature is disabled by default. To enable it, do this:

  1. In the configuration file of the application in which you want to enable this, change the value of session.maxTimeToLive to the required value. You can specify the time unit in hours, minutes or seconds (minutes will be used by default).

    Configuration file of each application (you need to do this in the installation of the Denodo Platform and/or Solution Manager; depending on the applications you use on each installation):

    • Data Marketplace: <DENODO_HOME>/conf/data-catalog/DataCatalogBackend.properties (Solution Manager does not include Data Marketplace).

    • Design Studio: <DENODO_HOME>/conf/design-studio/DesignStudioBackend.properties

    • Diagnostic & Monitoring Tool: <DENODO_HOME>/conf/diagnostic-monitoring-tool/DMTConfigurationParameters.properties

    • Scheduler: <SOLUTION_MANAGER_HOME>/conf/scheduler-webadmintool/ConfigurationParameters.properties.

    • Solution Manager Administration Tool: <SOLUTION_MANAGER_HOME>/solution-manager-web-tool/SMAdminConfiguration.properties

    The following examples set 1-hour timeout using different time units:

    • session.maxTimeToLive=3600s (seconds).

    • session.maxTimeToLive=60m (minutes).

    • session.maxTimeToLive=60 (minutes will be used if the time unit is not specified)

    • session.maxTimeToLive=1h (hours).

  2. After modifying the configuration file of the application, restart that application for the changes to take effect.

    You only need to restart the application; not the web container.

To disable this feature, set the value of this property to 0.

Single-User Concurrent Sessions Control

By default, a user can open multiple sessions in the web applications of Denodo. For example, a user can log in to Data Marketplace with the same credentials from two browsers (or two computers).

To enforce that a user is only logged in from one place at the time, do this:

  1. Add this property to the configuration file of the applications in which you want to enable this feature:

    concurrent-session-control.enabled=true

    Configuration file of each application (you need to do this in the installation of the Denodo Platform and/or Solution Manager; depending on the applications you use on each installation):

    • Data Marketplace: <DENODO_HOME>/conf/data-catalog/DataCatalogBackend.properties (Solution Manager does not include Data Marketplace).

    • Design Studio: <DENODO_HOME>/conf/design-studio/DesignStudioBackend.properties

    • Diagnostic & Monitoring Tool: <DENODO_HOME>/conf/diagnostic-monitoring-tool/DMTConfigurationParameters.properties

    • Scheduler: <SOLUTION_MANAGER_HOME>/conf/scheduler-webadmintool/ConfigurationParameters.properties.

    • Solution Manager Administration Tool: <SOLUTION_MANAGER_HOME>/solution-manager-web-tool/SMAdminConfiguration.properties

  2. After modifying the configuration file of the application, restart that application for the changes to take effect.

    You only need to restart the application; not the entire web container.

Consider this:

  • When this feature is enabled and a user logs in from one browser and then, from another browser, the user is allowed to log in the second time and the application closes the first session.

  • You do not need to enable this restriction in all the applications; you can do it only in some of them.

  • For Data Marketplace this feature is only available in non-cluster scenarios.

Add feedback