Web Services Session Limit Quota

FAQ

Last Updated: November 18, 2011

Version: 1.0

1
Copyright 2011, Oracle. All rights reserved. Oracle Confidential

Purpose
This document provides answers to frequently asked questions about the Oracle CRM On
Demands Web Services Session Limit Quota.

Overview
The Session Limit Quota sets the number of concurrent Web service sessions that can be active
at the same time for a specific Oracle CRM On Demand tenant. A session is established when a
user logs into the Oracle CRM On Demand application using stateful Web services. A session
may be actively processing work, or it may be waiting to process work. When processing work,
the session consumes CPU and memory. A session that is waiting to process work consumes
memory only.
Oracle sets the Session Quota Limit to manage Oracle CRM On Demand resources. By setting
limits, Oracle can monitor tenant workload and allocate resources accordingly, resulting in
performance and availability benefits.

Frequently Asked Questions

Question

Answer

Who sets this value?

The Session Limit Quota is configured by Oracle Global

Product Support (Customer Care).

When are sessions used?

Customers use sessions when they establish a stateful

Web service connection to Oracle CRM On Demand. This
is more efficient for bulk data processing because it avoids
making a connection for each Web service request.
Instead, it reuses an existing session, attempting to send
requests in sequence, as fast as possible. Note that in
such a scenario, CPUs are still waiting most of the time
because CPUs are significantly faster than memory, I/O,
and network operations.
This use is referred to as stateful because the state of the
Web service connection to Oracle CRM On Demand is
maintained and reused for several Web service requests.
The Session Limit Quota applies only to stateful Web
service requests.

How does use of stateless Web

services impact the Session
Limit Quota?
How many sessions are provided
for each CRM On Demand
tenant?

Stateless Web services do not maintain session state and

therefore are not counted against the Session Limit Quota.
Starting with Oracle CRM On Demand Release 17, each
new tenant is provided with a quota of 10 sessions.

2
Copyright 2011, Oracle. All rights reserved. Oracle Confidential

Question

Answer

How many sessions do most

customers use?
When should stateful sessions
be used?

The vast majority of customers use less than 10 sessions.

Why are stateless Web services

generally recommended?

In general, it is recommended that customers use stateless

Web services for several important reasons:

Stateful Web services are generally used when querying a

large number of records or performing bulk data
operations, for example, uploading large volumes of data.

1. Stateless Web services provide more efficient

resource utilization for most uses.
2. Stateless Web services do not impact the Session
Quota Limit.
3. As customers are responsible for Web service
development, stateless Web services can
dramatically reduce the complexity and cost of
developing new integrations because resource
management is performed by Oracle CRM On
Demand. For stateful Web services, resource
management is the customers responsibility.
4. Stateless Web service requests achieve a higher
level of concurrency because Oracle CRM On
Demand code manages sessions.
5. Additional error handling logic is also the
customers responsibility and must be
implemented correctly with stateful Web services.
Customers should ensure stateless Web services are used
for short, interactive requests where high concurrency is
required.
Is the session limit integration
specific?

No. The limit is per tenant. Partner and customer

integrations share the same limit. Customers should
encourage their partners to use stateless Web services
whenever possible to improve performance, availability,
and concurrency.

What happens when the

maximum Session Limit Quota is
reached?

Once the limit is reached, an attempt to establish an

additional session will result in an error being returned to
the calling application:
The concurrent web services Session Limit Quota has
been reached. Please ensure that all unused web services
sessions have been logged off and retry your request.

3
Copyright 2011, Oracle. All rights reserved. Oracle Confidential

Question

Answer
For high concurrency uses, customers should consider
updating their applications to use stateless Web services.
An alternative approach consists of implementing a
clientside session pooling algorithm to share stateful
sessions. However, using stateless Web services is
generally a more cost effective approach.
To make the most effective use of allocated sessions, log
off unused sessions if no further requests need to be
processed.

4
Copyright 2011, Oracle. All rights reserved. Oracle Confidential