Is there any concern to setting the ServiceManagerInactivityTimeoutMinutes higher, like to 8 hours?

Alan_Foster

Is there any concern to setting the ServiceManagerInactivityTimeoutMinutes higher, like to 8 hours? Will we run into performance issues? 

Billy_Wilson

I would imagine that would depend on what kind of load you normally have on your Portal server (# of active connections) and how much memory is available on that server since those sessions are held in memory. Here is the info on that setting from our KB - 

Whenever a user logs into the Cireson Portal via either forms authentication or Windows integrated authentication an object is created in memory that stores a cache of data from SCSM and a connection.  This object is called an EnterpriseManagementGroup object for those that are familiar with the inner workings of SCSM.  This object is stored in memory for quick access and reuse.  Whenever the connection object is needed, the Cireson Portal web site checks to see if an existing connection object exists in memory for that user.  If there is a connection object in memory for that user, it will use that connection.  If there is no active connection object in memory, a new connection object will be created.  This can take a few seconds because the SCSM SDK library is caching some information into the connection object from the SCSM server.  This connection object has a limited lifespan so that the memory it is utilizing can be freed up when it is not being used.

Hope this helps.

Billy_Wilson

I would imagine that would depend on what kind of load you normally have on your Portal server (# of active connections) and how much memory is available on that server since those sessions are held in memory. Here is the info on that setting from our KB - 

Whenever a user logs into the Cireson Portal via either forms authentication or Windows integrated authentication an object is created in memory that stores a cache of data from SCSM and a connection.  This object is called an EnterpriseManagementGroup object for those that are familiar with the inner workings of SCSM.  This object is stored in memory for quick access and reuse.  Whenever the connection object is needed, the Cireson Portal web site checks to see if an existing connection object exists in memory for that user.  If there is a connection object in memory for that user, it will use that connection.  If there is no active connection object in memory, a new connection object will be created.  This can take a few seconds because the SCSM SDK library is caching some information into the connection object from the SCSM server.  This connection object has a limited lifespan so that the memory it is utilizing can be freed up when it is not being used.

Hope this helps.

Kristoffer_Stormark

We have done that, and don´t see any problems, have the session timeout and UserTokenExpirationMinutes in that area aswell. 

20 min timeout was not acceptable for my users