About this task
BTT server side uses HttpSession to manage session, so it can leverage
HTTPSessionListener to handle Session Expiration.
You can configure the
TimeoutHandler in BTT server application web deployment descriptor (web.xml).
com.ibm.btt.sm.TimeoutHandler implements
HTTPSessionListener:
<listener>
<listener-class>com.ibm.btt.sm.TimeoutHandler</listener-class>
</listener>
The session can expire in the following two ways:
- Session expiring explicitly:
eRCP application expires session explicitly
when the user logs off.
The following diagram illustrates the procedure
of how session expires explicitly:
- When the user logs off, the eRCP application invokes LogOff Operation
through MobileAdapter.
- MobileRequestServlet redirects the request to MobileRequestHandler.
- MobileRequestHandler invokes LogOffOperation to do the cleanup job related
to business logic.
- LogOffOpreration marks the session expired and returns.
- MobileRequestServlet cleans the session and invalidates the
HttpSession.
- MobileRequestHandler invokes MobilePresentationHandler to response.
- MobileAdapter gets the response.
- Session expiring when timeout
When the HTTP Session times out, the TimeoutHandler
will be invoked automatically to clean the session. The interval of session
timeout can be configured in WebSphere® Application Server admin console.