Dedicated Communication Channels and Port Separation for TWS Components

Business Requirement

We would like IBM to consider enhancing TWS communication architecture by providing dedicated communication channels and configurable ports for different access methods, such as APIs, OCLI, and Dynamic Workload Console (DWC).

Current Challenge

Currently, API, OCLI, and DWC traffic are all processed through the same communication port (31116). As a result, the TWS Master Domain Manager cannot easily distinguish the origin or type of incoming requests. This makes it difficult for administrators to identify, monitor, control, or selectively restrict traffic generated through a specific interface.

In addition, when all communication types share the same port and processing path, excessive activity from one access method can impact the overall load on the master, potentially affecting performance and responsiveness for all users and integrations.

Requested Enhancement

Introduce the capability to:

• Configure separate communication ports for APIs, OCLI, and DWC connections.
• Clearly identify and classify the source of incoming requests based on the connection type.
• Apply independent security controls, firewall rules, and access restrictions for each communication channel.
• Enable administrators to selectively block or rate-limit traffic from a specific interface without affecting other access methods.
• Provide monitoring and reporting that distinguishes API, OCLI, and DWC activity.

Business Benefits

• Improved visibility into the source and nature of TWS traffic.
• Greater administrative control over access methods and security policies.
• Ability to isolate problematic traffic sources during incidents or performance issues.
• Enhanced resilience by preventing one interface from adversely affecting others.
• Reduced load contention and improved overall Master Domain Manager performance.
• Simplified troubleshooting, auditing, and capacity planning.

Expected Outcome

The TWS Master Domain Manager should be capable of differentiating between API, OCLI, and DWC traffic and, ideally, support dedicated configurable ports for each communication method. This would provide improved traffic management, stronger security controls, greater operational flexibility, and better performance protection for critical scheduling infrastructure.