When a browser is sending requests to an application, a session is created between the browser and the application. When doing Cross-Context Flows in which the second context requires a display, the browser must be redirected to the application running under the second context. This redirection causes a new session to be created between the browser and the second application.
Since there are two separate sessions created by the application server(s), the second application does not have direct access to the session information of the first application.
To complete the transfer, the session information from the first application must be transferred to the second application. The session information is transferred using a URLConnection and stored in a Java Message Service (JMS) while the browser is redirected to the second application. When the browser and the second application initiate a session, the session information is reloaded from the JMS.
For this technique to work, the JMS must be configured on each Application Server that will participate in Cross-Context Flows. In addition, the JMS connection factory name and queue name must be configured during assembly in the Build Tool.
Note: The Assemble process only supports JMS configuration for WebLogic and WebSphere Application Servers. If Cross-Context Flows are to be used with other Application Servers, then Application Server specific customizations will have to be made to the EAR file after the Assemble process has completed. These customizations will be in addition to the usual JMS configuration steps that are required on the Application Server itself.
|
Copyright © 2013 CA.
All rights reserved.
|
|