Using cookies for session management

Use the Configuration Manager to enable cookies for session management.

Procedure

  1. Open the Configuration Manager
  2. Select WebSphere Commerce > node_name > Commerce > Instance List > instance_name > Instance Properties > Session Management.
  3. Select the appropriate session values.
    OptionDescription
    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, see Session management support.
    • A WebSphere Commerce session cookie is internal to WebSphere Commerce and does not persist to the database.
  4. Optional: Click the Advanced Tab. Select the appropriate session values.
    OptionDescription
    Cookie domain Specifies a domain restriction pattern. A domain restriction pattern specifies the servers that can view a cookie. By default, cookies are only sent back to the WebSphere Commerce Server that issued them. For example, if you make a request to a WebSphere Commerce Server at subdomain.domain.com, then cookies that are created by that server are only visible to the server at that subdomain when the user returns to it. Specifying a domain name pattern overrides this behavior. 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.
  5. Click Apply.
  6. Close the Configuration Manager.
  7. Restart your WebSphere Commerce instance.