IBM WebSphere · Rate Limits

Websphere Rate Limits

IBM WebSphere runs inside the customer's data center / hybrid-cloud footprint; its admin REST, JMX, and hosted-application surfaces are not subject to a centrally published rate-limit policy. Concurrency, thread-pool sizing, and connection limits are configured by the operator via the WebSphere admin console / server.xml.

Websphere Rate Limits is the machine-readable rate-limit profile for IBM WebSphere on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 1 rate-limit definition, measuring varies.

The profile also includes 1 backoff/retry policy defined.

Tagged areas include Application Server, Cloud Native, Enterprise Java, J2EE, and Rate Limiting.

1 Limits
Application ServerCloud NativeEnterprise JavaJ2EERate LimitingContact Sales

Limits

Deployment-Tuned Throughput deployment
varies
configured per WebSphere cell / server / thread-pool

Policies

Self-Tuned Limits
WebSphere exposes thread-pool, connection-pool, and JCA / EJB pool tuning that the operator configures. There is no public per-call quota imposed by IBM on customer deployments.

Sources