6 Managing Sessions

This chapter describes how to configure the behavior of and manage ongoing sessions in Oracle Communications Services Gatekeeper.

About Sessions

You can configure whether to use sessions between applications and Services Gatekeeper. Sessions can be used for establishing site affinity when using geo-redundant sites.

The setting of sessionRequired field specifies whether sessions are used. You can make sessions required, optional, or have sessions disabled.

When using sessions, the application must get a session from the Session Web Service before using the other application-facing interfaces. The application must also provide the session ID in all requests to the application-facing interfaces, except for requests to the Session Web Service.

A session has a unique ID. A session, once established, can have two states:

  • ACTIVE

  • INVALID

After a session has been established, it is always in the ACTIVE state.

Table 6-1 describes the possible states for a session, the state into which it can transition from the current state, and the condition under which such a transition occurs.

Table 6-1 Session States and Conditions for Successful Transition

Current Session State Valid Transition State Scenario in Which Transition Occurs

ACTIVE

INVALID

The age of the ACTIVE state of a session is older than a configurable time-interval. See the validityTime field of the ApplicationSessionMBean MBean in the ”All Classes” section of Services Gatekeeper OAM Java API Reference.

ACTIVE

Not applicable

This is not a state but rather that the session is not current or does not exist.

A management user performs one of the following ApplicationSessionMBean operations:

  • destroySession

  • destroyApplicationInstanceSession

  • destroyApplicationSessions

  • destroyServiceProviderSessions

INVALID

Not applicable

This is not a state but rather that the session is not current or does not exist.

The age of the INVALID state of a session is older than a configurable time-interval. See the expiryTime field in ApplicationSessionMBean in the ”All Classes” section of Services Gatekeeper OAM Java API Reference.

An ApplicationSessionMBean user performs one of the following management operations:

  • destroyApplicationInstanceSession

  • destroyApplicationSessions

  • destroySession

  • destroyServiceProviderSessions

For a description of the attributes and operations of the ApplicationSessionMBean MBean, see the ”All Classes” section of Services Gatekeeper OAM Java API Reference