About Sessions in Agile Platform

In Agile Platform a Session is created after the first request the end-user establishes to the Platform Server and allows to keep context during the end-user navigation. The session consists in the set of session variables defined in the eSpaces the end-user accesses during its interaction. The session variables can be used when you are implementing the business logic of your eSpace, for example, in user-actions, screen preparations, and screen actions.

The session is created on the server and can be shared by several eSpaces if you are using the Single Sign-On feature that enables an unified view of users and sessions by a set of eSpaces. See more about Single Sign-On.

Session Lifetime

The session begins on the first request of the end-user and ends explicitly when that end-user logs-out or automatically due to a session timeout. There are, however, some details specific to the channel used for the end-user interaction. Learn more about Agile Platform Session Lifetime.

When the session is created, either in a Web or SMS interaction, the action handling the OnSessionStart system event is executed. See more about the OnSessionStart Event.

Session Time-out

The session time-out specifies the period of time that a session can remain idle, without any end-user interaction, before the Platform Server ends the session automatically.

The default value for the session time-out depends on the application server:

.NET: 20 minutes and this value can be configured in machine.config file, on the .NET server.
J2EE: 30 minutes and this value can be configured in web.xml file, on the JBoss server.

In Platform Server it is not possible to trap the session time-out event.

Sessions in Consumer and Producer Scenario

When a public action from a producer eSpace is invoked in a Consumer eSpace, a producer session is created (with all the producer session variables) inside the Consumer eSpace to keep its values between invocations. See Consumer and Producer eSpaces.