Session state support

In order to achieve the best performance, Safewhere Identify recommendation for session state mode is as follow:

• Single server setup: since this type of setup uses only one web server to host Identify instances, InProc session state mode is the best choice. You can also opt to use SQL Server mode.
• Redundant setup: redundant setup has more than one web server to host Identify instances. We recommend the following two solutions for session state:
  • Use InProc session state mode with a load balancer that supports sticky session based on client IPs to ensure that a client is always routed to the same host within a session.
  • If such a load balancer is unavailable, you can opt to use SQL Server mode or State Server mode. You can learn more about it: https://msdn.microsoft.com/en-us/library/ms178586.aspx

You can also find more detail information about system requirements for Safewhere Identify by clicking the following link.