Purpose of Max Session Time field:
Max Session Time (hours)
Maximum time to keep server connections alive. The unit is based on the maxSessionTimeUnits user-defined parameter which can be 'minutes' or 'hours'. When maxSessionTimeUnits is not defined, the unit is defaulted to 'hours'.
What does this above definition means?
Basically this is the session time for the OAP/NAP connections made between Webgate & OAM Server.This is the TTL (Time to live) of these OAP/NAP connections.
Is this field defines the time in minutes or hours?
By default it is in 'hours'. But when you create a Webgate Agent Profile there is a user defined parameter defined as 'maxSessionTimeUnits' & it has value 'minutes'.Thus this makes the value configured in 'MAX SESSION TIME' in minutes.
- In this agent profile we have max session time configured as '2'. This is in minutes why?
- Because we have configured the user defined parameter 'maxSessionTimeUnits' & value of this parameter is 'minutes'.
But if you remove this parameter 'maxSessionTimeUnits' than MAX SESSION TIME will have 'hours' as its unit.
Note:
- User won't be challenged for credentials again because of the 'MAX Session time'. This time is not user session timeout. It is for the OAP/NAP connection timeout.
How will you test these connections?
bash$> netstat -anp | grep 5575 | grep httpd.worker
- Port 5575 is the listening port used by the OAM Server. While creating webgate agent profile server connection port is mentioned.
- 'httpd.worker' is the OHS server process.
- In this example 2 worker threads have made OAP/NAP connection with the OAM Server.
After 2 minutes these connections are re-established, here is the proof.
Hope it clears your doubts.....!!!!!!
Reference Doc:
http://docs.oracle.com/cd/E40329_01/admin.1112/e27239/register.htm#AIAAG631
Enjoy :-)
