Using page content for session identification

Runtime components : Channels components : HTML Channel : Tasks : Using page content for session identification

To maintain HTML client session identity when linking to a JSP, it is necessary to use URL rewriting by embedding the session ID into the URL link. (The technique described here should not be confused with WebSphere Application Server URL rewriting.) When the specified JSP is rendered into the HTML page requested by the client, the session ID provided by the client is returned as part of that HTML page.

Following is a JSP sample of a hidden input field:

Following is a JSP sample of URL rewriting:

<a href="accountinquiry.jsp?dse_sessionId=<%= sessionId %>">Account Summary>
</a>

Note that this mechanism would directly invoke a JSP on the server and would therefore skip the toolkit multichannel access architecture. In order to behave according to the correct model, an operation should be requested to display a JSP as follows:

<dse:a action="/DSE_HtmlSampleAppl/Request" opName="displayPageOp"
nextEventName="dseSkipRender" errorPage="menu.jsp"
extraParams="pageName=accountinquiry.jsp"><dse:label
text="Account_Summary"/></dse:a>

This example comes from menu.jsp in the HTML Sample Application. See Maintaining session identity using page content in the HTML Channel documentation for more information.