B Cookie Structures

This appendix provides an overview of the cookie technologies that RUEI supports.

In order to accurately monitor your Web environment, RUEI needs to know and understand the cookie technology you Web site is using. The procedure for specifying the cookie technology is fully described in Section 7.1, "Specifying Cookie Technology".

The structures for supported cookie technologies are shown in Table B-1:

Table B-1 Cookie Structures

Technology	StructureFoot 1
ADFFoot 2	JSESSIONID=%
Apache	Apache=%
ASP	ASPSESSIONID*=% ASP.NET_SessionId*=%
ColdFusion	CFTOKEN=%
Google	__utma=%
JD EdwardsFootref 2,Foot 3	JSESSIONID=%
OracleFoot 4	OraTrack=% MfTrack=% mf_sess=%
PeopleSoftFootref 2,Footref 3	ps_token=%
PHP	PHPSESSID=%
SiebelFootref 2,Footref 3	_sn=%
WebLogic Portal (WLP)Footref 2	JSESSIONID=%
WebSphere	JSESSIONID=%
(custom)	CUSTOMNAMEFoot 5 =%
(URL argument)	URLARGUMENTFoot 6 =%

^Footnote 1 * is zero (or more) characters of any kind. % is the matching part of the string.

^Footnote 2 These are implemented as preconfigured custom cookies.

^Footnote 3 These cookies are only available if the relevant accelerator package has been installed.

^Footnote 4 Contains the deprecated Moniforce cookie. Note this does not automatically work for all Oracle products.

^Footnote 5 CUSTOMNAME is the cookie name.

^Footnote 6 URLARGUMENT is the name of the argument in the URL. This is explained in more detail in the following section.

Session Tracking Using URL Arguments

When you specify that a URL argument should be used to track user sessions, the object's URL is first checked for the specified argument. If it is not found, the parent page's URL is searched for the specified argument.

For both the object's and the parent page's URL, the following example URL structure is assumed:

www.domainname.com/sitename/shop;;URLARGUMENT=blabla?......

If the specified URL argument is not successfully located, the following URL structure is assumed:

www.domainname.com/sitename/shop?URLARGUMENT=blabla&......