To use cookies in WebSphere Commerce:
- Open Configuration Manager
- Select the Instance, then open the Session Management folder.
- Select the appropriate session values.
- Cookie acceptance test
Select this check box to check if the customer's browser accepts cookies for a site that only supports cookies.
- Cookie session manager
Select whether you want WebSphere Commerce or WebSphere Application Server to manage your cookies. The default is WebSphere Commerce.
- A WebSphere Application Server session cookie is based on the servlet HTTP session standard. WebSphere Application Server cookies persist to memory or to the database in a multinode deployment. For more information, search for "session management" in the WebSphere Application Server Information Center (http://www.ibm.com/software/webservers/appserv/infocenter.html.
- A WebSphere Commerce session cookie is internal to WebSphere Commerce and does not persist to the database.
- Cookie acceptance test
- Click the Advanced Tab. Select the appropriate session values.
- Cookie path
Specifies the path for the cookie, which is the subset of URLs to which a cookie should be sent. Usually, this field should not be altered.
For details on cookie paths, see Netscape's Cookie Specification and RFC 2109.
- Cookie domain
Specifies a domain restriction pattern. Usually, this field should not be altered.
A domain specifies the servers that should see a cookie. By default, the cookies are only sent back to the WebSphere Commerce Server that issued them. By default, cookies are returned only to the host that saved them. Specifying a domain name pattern overrides this. The pattern must begin with a dot and must contain at least two dots. A pattern matches only one entry beyond the initial dot. For example, ".ibm.com" is valid and matches "a.ibm.com" and "b.ibm.com" but not "www.a.ibm.com". For details on domain patterns, see Netscape's Cookie Specification and RFC 2109.
- Cookie path
- Click Apply.
- Close Configuration Manager.
- From the WebSphere Application Server Administration Console, stop then restart the WebSphere Commerce Server instance.