CMS session tracking

The CMS implements a simple tracking algorithm. When a user logs on, he or she is granted a CMS session, which the CMS preserves until the user logs off, or until the WCS session variable is released.

The WCS session is designed to notify the CMS on a recurring basis that it is still active, so the CMS session is retained so long as the WCS session exists. If the WCS session fails to communicate with the CMS for a ten-minute time period, the CMS destroys the CMS session. This handles scenarios where client-side components shut down irregularly.

Note:    If you are familiar with the SDK, you should note that a CMS session is an instance of an EnterpriseSession object.