The Session - Application is a table (meta_md_session_app) in the System Monitor module of iTopia. The Session-Application tracks iTopia applications that are currently active within a Web browser session.

• For example, when you log into iTopia the Session-Application view will create a record of your user id being active in the 'Portal' application. If your user id allows you access to the metadata portion of iTopia, then a second record containing your user id in the 'Meta' application is created.

• A session application clears from the Session–Application view when the browser tab is closed and the user logs out of the system. Note: If a user logs off of the iTopia session improperly, the record(s) still displays in this table. The record(s) is automatically cleared from the table after a period of time.

The following fields are available on the Session-Application view and are based on the order in which they appear in the grid on the search page:

• User Name - displays the user id of the user logged into iTopia.

• Full Name - displays the full name of the user.

• Session ID - displays the unique identifier for a session.

• Session Application ID - displays the unique identifier for the application.

• Application Name - displays the name of the application, which may be one of the following:
  • meta – displays when your user id has access to the meta based views.
  • portal – displays when your user id logs into PointForce iTopia.

• Starting Resource Name - displays the foreign key to the resource entity. It is the first resource executed, before any linking has occurred.

• Description - displays the actual name of the starting resource.

• Last Access Time - displays the date and time at which this session application was last accessed.

• Inactivity Timeout - every browser tab sends a 'keep application alive' signal (aka heartbeat). The information stored in this field represents the number of seconds the application may live without such a heartbeat. In other words, this field determines how long an application can be inactive before expiring. By default, this value is 1800 seconds (defined in the Tecsys.properties file). When an application goes undetected for the amount of time indicated here, the application is unregistered and the cleanup instructions are executed.

For information on the functionality of each button on the Session - Application Search Criteria Results/Grid page, click here.

Session - Application Details Page

The following list defines every field on the Details page:

• In the General section:
  • Application Name - displays the name of the application, which may be one of the following:
    • meta – displays when your user id has access to the meta based views.
    • portal – displays when your user id logs into the iTopia.

  • Starting Resource Name - displays the foreign key to the resource entity. It is the first resource executed within the tab, before any linking occurred.

• In the User and Date Stamps section:
  • Date Time Created - displays the date and time the application was started.

  • Last Access Time - displays the date and time at which this session application was last accessed.

  • Inactivity Timeout - every browser tab sends a keep application alive signal (aka heartbeat). The information stored in this field represents the number of seconds the application may live without such a heartbeat. In other words, determines how long an application can be inactive before expiring. By default, this value is 1800 seconds, and this is defined in the Tecsys.properties file. When an application goes undetected for the amount of time indicated here, the application is unregistered and the cleanup instructions are executed.

The Related views include:

• Session
• Application-Attribute
• Attribute
• Lock
• Application Server Instance

For information on the functionality of each button on the Session-Application Search Criteria Details page, click here.