Introduce Command Throttling / Rate Limiting for User Commands in TWS

Business Requirement

We would like IBM to consider introducing a configurable command throttling or rate-limiting capability for user commands executed against the TWS Master Domain Manager.

Current Challenge

At present, users can submit a large number of commands in rapid succession without any built-in restriction or control. In environments with multiple users or during operational activities, this can result in a significant surge of command-processing requests on the Master Domain Manager.

Excessive user command execution can place considerable load on the TWS infrastructure, consuming CPU, memory, and command-processing resources. In extreme cases, this may lead to performance degradation, service instability, or unexpected termination of critical TWS processes, potentially impacting scheduling operations across the enterprise.

Requested Enhancement

Introduce a configurable mechanism that allows administrators to:

• Define the maximum number of user commands that can be executed within a specified time period.
• Apply limits based on individual users, groups, or roles.
• Queue, delay, or reject commands when configured thresholds are exceeded.
• Provide configurable alerting capabilities that automatically notify both the initiating user and designated administrators when command execution limits are breached, while also generating auditable events for monitoring and compliance purposes.
• Configure exemptions for privileged administrative accounts where required.

Business Benefits

• Protects the TWS Master Domain Manager from excessive command activity.
• Reduces the risk of service degradation or outages caused by command storms.
• Improves platform stability and resilience.
• Prevents accidental misuse while maintaining operational flexibility.
• Provides administrators with greater control and governance over command execution.

Expected Outcome

A configurable rate-limiting capability for user commands would help safeguard critical TWS scheduling components and ensure that excessive command activity from individual users cannot negatively affect the availability, stability, and performance of the TWS master environment.