Oracle Siebel · Rate Limits
Oracle Siebel Rate Limits
Oracle Siebel CRM is a customer-deployed application; its REST, SOAP, EAI, and Object Interface APIs do not enforce a centrally-published per-second or per-minute rate-limit table. Throughput is bound by the customer-deployed Siebel Application Object Manager (AOM), Application Server, Web Server, and Database tier capacity. Rate limiting, when enforced, is implemented at the surrounding application server (Oracle WebLogic / IIS / Apache) or via a customer-fronted API gateway.
3 Limits
CRMEnterprise SoftwareOracle CloudRate Limiting
Limits
REST API Throughput deployment
bound by Siebel AOM / Application Server capacity
Throughput is governed by the deployed Siebel Application Object Manager and Application Server sizing rather than a public per-tenancy rate.
SOAP Web Services Throughput deployment
bound by Siebel AOM / Application Server capacity
As with REST, SOAP web service throughput is bound by the deployed Siebel server tier.
EAI Inbound / Outbound Throughput deployment
bound by deployed EAI configuration
EAI throughput depends on the configured business-service component pools and underlying transport (HTTP, JMS, MQ).
Policies
Capacity-Bound Throttling
Throughput limits are determined by the deployed Siebel Application Object Manager, Application Server, Web Server, and Database tier sizing rather than a published per-tenancy rate-limit table.
Backoff Strategy
Clients should implement exponential backoff with jitter on 5xx responses; honor any Retry-After header when present.
AOM Tuning
Siebel administrators should tune AOM component thread pools, MaxTasks, and MaxMTServers settings to match observed load rather than relying on a centrally-imposed rate.
API Gateway Pattern
Customers exposing Siebel APIs to third parties should front them with an API gateway (Oracle API Platform, Apigee, etc.) and apply rate limits there.