How to Store JSESSIONID as a Cookie and Disable URL Rewriting (Doc ID 2043892.1)

Last updated on OCTOBER 31, 2024

Applies to:

Goal

Oracle Forms is a stateful technology.  In other words, in order to maintain the health of a Forms application session, client activity during the session must be retained and synchronized with its corresponding server side companion.  In order to properly match this client and server relationship, a JSESSIONID is generated and retained throughout the life of the running application. In the absence of such a session identifier, the server would not be able to distinguish between communications arriving from its related client and other clients sending requests.  Because Oracle Forms does require statefulness, JSESSIONID is also used for loadbalancing.  The JSESSIONID is used to ensure that loadbalancers properly route communications to and from the correct client/server partners.

By default, Oracle Forms requests a JSESSIONID be generated and maintained in the URL of each exchange between the client and server.  The JSESSIONID is generated by the WebLogic Server (WLS) managed server hosting the Forms Servlet. WLS adds the JSESSIONID to the URL using a method called URL Rewriting.  For some environments, including the JSESSIONID in each URL exchange may not be desirable.

This document will describe how the session's JSESSIONID can be stored as a cookie rather than data in the URL.

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.