Show TOC Entering content frame

Background documentation J2EE Session Identifier Locate the document in its SAP Library structure

The general form of the J2EE session identifier is similar to the ABAP session identifier described in the previous section (ABAP Session Identifier). As opposed to the ABAP identifier, the destination server name is enclosed in parentheses (“()”) instead of colons.

This graphic is explained in the accompanying text

<sap-j2ee-sid> = URL-encode( “(“<sap-server-name> ”)”<internal-id>End )

ExampleExample

(ls3022_BIN_12)ID47500DB0.5138181876605873End

specifies a session on the SAP application server ls3022_BIN_12 (see also the example for the ABAP identifier in the previous section).

Session ID as Cookie

This graphic is explained in the accompanying text 

Cookie: JSESSIONID=<sap-j2ee-sid>

Session ID in URL

When specified in the URL instead of a cookie, the J2EE session ID is included as a standard semicolon-separated URI parameter (see RFC 2396: Section 3.3 “Path Component”). The name of the URI-parameter is “jsessionid”.

This graphic is explained in the accompanying text

<uri-path-segment> ;jsessionid=<sap-j2ee-sid> 

ExampleExample

/sap/j2ee;jsessionid=<sap-j2ee-sid> /foo/bar

 

Leaving content frame