About
A Session is created after :
- the authentication of a user
- the first visit of a public user with the zero session feature
Articles Related
Id
Each session is assigned a unique identifier. The Application Express engine uses this identifier (or session ID) to store and retrieve an application's working set of data (or session state) before and after each page view.
Management
Get
The session ID can be seen:
- as the third parameter of the URL for a page request.
- in the page's HTML POST data and indirectly in the contents of a session cookie.
- with the GET_SESSION_ID Function
- with the GET_SESSION_ID_FROM_COOKIE Function
Variable
APP_SESSION
You can reference the session ID variable using the syntax:
- Short substitution string: &APP_SESSION.
- PL/SQL: V('APP_SESSION')
- Bind variable: :APP_SESSION
Example with the Apex url
f?p=6000:6003:&APP_SESSION.::NO:6003:MY_ITEM:1234
APP_SESSION_VISIBLE
APP_SESSION_VISIBLE enhance APP_SESSION by implementing also the zero session feature
View
Time out
Application Properties > Security > Session Timeout
Api
APEX_UTIL
See the APEX_UTIL package:
- GET_SESSION_LANG Function
- GET_SESSION_TERRITORY Function
- GET_SESSION_TIME_ZONE Function
APEX_CUSTOM_AUTH
You can use the APEX_CUSTOM_AUTH package to perform various operations related to session management.
Purge
The ORACLE_APEX_PURGE_SESSIONS job (DBMS_SCHEDULER) purges sessions older than 12 hours (the default). This job runs every hour.
Zero
The zero session ID function is in use in a public navigation context. See Zero Session Feature