Académique Documents
Professionnel Documents
Culture Documents
Allotment FAQs
1
Copyright 2011, Oracle. All rights reserved. Oracle Confidential
Purpose
This document is a quick reference for Oracle CRM On Demands Web Service Concurrent
Request Allotment.
Overview
The Web Service Concurrent Request Allotment sets the number of concurrent stateless Web
service requests that can be processed at the same time for a specific Oracle CRM On Demand
tenant.
Note that a customer may have one or more Production tenants, e.g. customer contracts for 500
Multi-Tenant licenses but due to various business reasons, they elect to provision 100 users in
tenant A (the users may be North America sales) and 400 users in tenant B (this tenant
represents both sales and call center worldwide). Therefore, in this example, the customer has
two (2) Production tenants. The Web Service Concurrent Request Allotment is set at the tenant
level and each tenant receives an allotment of 5 concurrent stateless requests.
An active stateless request represents a stateless web service operation that is being executed
for a user that is logged into the Oracle CRM On Demand application for a specific tenant. When
processing work, the request consumes both CPU and memory.
Oracle sets the Web Service Concurrent Request allotment to manage resources for Oracle CRM
On Demand services. By setting allotments, Oracle can monitor workload and resource
requirements resulting in improved performance for each customer and improved performance for
the service as a whole.
Answer
2
Copyright 2011, Oracle. All rights reserved. Oracle Confidential
Question
Answer
case with stateful web services.
We refer to this use case as a stateless Web services
because the state of the connection is not maintained.
3
Copyright 2011, Oracle. All rights reserved. Oracle Confidential
Question
Answer
dramatically reduce complexity and cost of
developing new integrations since resource
management is performed by Oracle. For stateful
Web services, this is the customers responsibility.
For example, customers do not need to logoff
following a stateless request/response thus
allowing a higher level of concurrency that stateful
web services.
4. Additional error handling logic is also the
customers responsibility and must be implemented
correctly with stateful Web services.
Especially in the case of high concurrency for interactive
web service use cases, customers should update their
applications to use stateless web services.
4
Copyright 2011, Oracle. All rights reserved. Oracle Confidential