Oracle Forms Fails if Started right after Oracle Discoverer in an EBS Environment
Last updated on MARCH 28, 2018
Applies to:Oracle Discoverer - Version 18.104.22.168.0 to 22.214.171.124.0 [Release 11g]
Information in this document applies to any platform.
***Checked for relevance on 28-Mar-2018***
Using E-Business Suite R12.1.3 integrated with Discoverer 11g, when calling Oracle Forms right after starting Applications session all works fine, however this fails when Forms is started after having called Discoverer session. Analysis shows that JSESSIONID cookie which is set by Discoverer, get picked up by Forms, causing an incorrect routing.
HTTP Header trace lines show
>>> This is HTTP request to Forms Servlet (/forms/...)
>>> Note this does not send the EBS JSESSIONID, but does pass the DISCOVERER JSESSIONID
>>> This JSESSIONID makes that Forms routing is failing and Forms session fails !!!!
Upgrade to Discoverer 11g
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms