Session state configuration scenarios

Last updated Wednesday, October 5, 2016 in Sitecore Experience Platform for Administrator, Developer

In the Sitecore Experience Database, you can use a session state server to track all your contact sessions across different browsers and devices. Configuring session state is particularly important if you have deployed a multiserver, fully scalable environment with clusters of content delivery or processing servers.

The following example scenarios provide guidance on how to configure session state on different types of Sitecore server configurations.

Single standalone server

On a single, standalone Sitecore instance, both session providers should use the in process (InProc) session state mode.

Single content delivery server and a separate content management server

On a content delivery server, you should configure both session providers to use the in process (InProc) session state mode.

Important

When configuring session state on content management servers, you should always configure session state providers to use the in process (InProc) mode. Sitecore xDB does not support sharing session state among a group of content management servers or between content management and content delivery servers.

Content delivery cluster with a sticky load balancer

On all content delivery instances, you should configure the ASP.NET session state provider to use the in process (InProc) mode. You should configure the shared session state provider to use one of the out of process modes connected to a database shared among all the content delivery instances.

Content delivery cluster with a non-sticky load balancer

On all content delivery instances, you should configure both session state providers to use one of the out of process modes connected to a database (or databases) shared among the content delivery instances.