Wev Service Concurent Request Allotment

1

Copyright 2011, Oracle. All rights reserved. Oracle Confidential

Web Service Concurrent Request Allotment FAQs

Last Updated: November 18, 2011

Version: 1.1

2


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.

Frequently Asked Questions

Question Answer

Where is this value set and who sets it?

The Web Service Concurrent Request Allotment is configured by Oracle Global Product Support (Customer Care) via the Oracle CRM On Demand Internal Admin tool. This value cannot be updated by the customer; however the value can be viewed on the Service Allotment Administration page by a company administrator.

When are these stateless requests used?

Stateless requests are best suited to user interactive scenarios where requests are driven by user input. Stateless requests more efficiently utilize the resources of Oracle CRM On Demand, allowing a customer to serve a high number of users since a resource does not sit idle while waiting for additional work, resources are allocated as needed and are not dedicated to a specific user as is the

3


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.

Why is the concurrent request allotment important?

Each CRM On Demand POD has a limit for the total number of requests that can be processed at any time for all tenants on the POD. This value is established based on the resources allocated to the POD. It is therefore important that the POD limit is not reached.

How many sessions are provided for each CRM On Demand tenant?

Starting with CRM On Demand Release 19, each tenant is provided a number of sessions based on their CRM On Demand license type.

Multi-Tenant Enterprise customers will receive an allocation of 5 concurrent requests.

Single-Tenant Standard edition customers will receive an allocation of 10 concurrent requests.

Single-Tenant Enterprise edition customers will receive an allocation of 20 concurrent requests.

How many concurrent stateless requests do most customer use?

Most customers use very few concurrent stateless requests. Since the resources used to process a stateless request are released following completion of the request, they are only allocated to a user for a short period of time. In contrast, a stateful session is only released after 10 min of inactivity OR if the user explicitly logs off the session. The net result is that a greater number of concurrent users can be served via stateless requests than using stateful sessions since resources are not sitting idle waiting to be released or waiting for the next request to be received.

When should stateless requests be used?

In general, it is recommended that customers use stateless web services for several important reasons.

1. Stateless web services provide more efficient resource utilization for most business use cases.

2. Stateless Web services do not impact the Session Quota Limit.

3. Since customers are responsible for Web service development, stateless web services can

4


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.

Is the concurrent request allotment integration specific?

No. The allocation of concurrent requests is provided on a per tenant basis. All integrations which leverage stateless web services will share this pool of concurrent requests.

What happens when the maximum concurrent request allotment is reached?

Once the limit is reached, any attempt to process an additional request will result in an error being returned to the calling application.

What if more concurrent requests are required?

An option to purchase additional Concurrent Request capacity is not available.

PurposeOverviewFrequently Asked Questions

Documents

Wev Service Concurent Request Allotment