CRM WebUI and Maximum HTTP Sessions

How many concurrent WebUI sessions can you run on CRM 7.0

After launching WebUI with successful login, an agent can just use CTRL+N key combination to launch another window. If you use the option File->New->Window or CTRL+N in IE, it is another window in an existing browser process to a maximum of 6 (default). This can be configured up to a maximum of 16 as long as you are on SAP Basis 640 Patch Level 231; 700 Patch Level 152. As of SAP Basis version 701 parameter icm/HTTP/esid_max_ctx is available in all patch levels. 

 To find out which patch your system is on (not SP because that is what you will see when accessing System -> Status -> Magnifying Glass) use transaction SM51 and click on Release Notes.

 A click on the desktop icon or in the start menu creates a new browser process. You can start the windows task manager and check this under the processes tab. You will see a new process with name iexplore.exe each time you double click on the IE icon on the desktop or in the start menu. As long as you use individual browser processes you can start a WebUI Framework session in each of those processes. As nothing is shared between those browser processes each will require authentication unless you use certain forms of single sign on (SSO), e.g. X.509 certificates. SAP Logon Ticket based SSO will not work across browser processes as it is stored in the memory of a browser process. Please keep in mind that it is not recommended to open more than one session if you are using IC_AGENT role or any other roles with telephony integration.

 Another way to access parameters is by executing transaction SE38. In the Program box type RSPARAM and click on execute. Check “Display also unsubstituted?” and execute. Here you can see the System Default Value and User-Defined Value for each parameter. Not all parameters have user defined values. You can than double-click on any parameter and see what  the current value is.

 However IE8 throws IE7 session handling out the window. By default IE8 uses a shared browser session no matter how you start it. Whether you start it via the icon on the desktop or via start menu, IE 8 will use a new process, but cookies, etc are shared via a shared browser session. This can be gotten around by using the “-nomerge” parameter when you start the application i.e.  "iexplore.exe -nomerge". IE8 also has the option to create a completely new session (File -> New Session). This way the cookies are managed independently for each session.

A similar behavior as -nomerge can be achieved by help of profiles in Microsoft Edge. For further information see  https://docs.microsoft.com/en-us/deployedge/edge-ie-mode-faq and  Sign in and create multiple profiles in Microsoft Edge