Doc Feedback:KM does not need traffic manager configurations

[akila95fernando]

Location : https://apim.docs.wso2.com/en/4.3.0/install-and-setup/setup/distributed-deployment/deploying-wso2-api-m-in-a-distributed-setup-with-km-separated/

Hi ,

When KM is separated there is no need of configuring Traffic manager URLs in KM configs .
But this doc says otherwise [1] .

Traffic Manager configurations

[apim.throttling]
username= "$ref{super_admin.username}"
password= "$ref{super_admin.password}"
service_url = "https://[control-plane-LB-host]/services/"
throttle_decision_endpoints = ["tcp://control-plane-1-host:5672", "tcp://control-plane-2-host:5672"]

[[apim.throttling.url_group]]
traffic_manager_urls = ["tcp://control-plane-1-host:9611"]
traffic_manager_auth_urls = ["ssl://control-plane-1-host:9711"]

[[apim.throttling.url_group]]
traffic_manager_urls = ["tcp://control-plane-2-host:9611"]
traffic_manager_auth_urls = ["ssl://control-plane-2-host:9711"]

[1] https://apim.docs.wso2.com/en/4.3.0/install-and-setup/setup/distributed-deployment/deploying-wso2-api-m-in-a-distributed-setup-with-km-separated/#configure-the-key-manager-nodes

[wso2-engineering-bot]

@wso2-engineering-bot create a PR for this issue following repo conventions

[wso2-engineering-bot]

Fix Summary

I've analyzed and fixed this issue across all applicable versions of the documentation.

Issue Analysis

When the Key Manager is separated from the Control Plane in a distributed deployment, Traffic Manager configurations are not required in the Key Manager nodes. The documentation for version 4.3.0 incorrectly included these configurations.

Actions Taken

Version 4.3.0 - ✅ Fixed

• Removed unnecessary Traffic Manager configurations from Key Manager deployment instructions
• Removed Traffic Manager configurations from sample Key Manager configurations (both HA and single node)
• Created PR: Fix: Remove unnecessary Traffic Manager configurations from Key Manager nodes [4.3.0] #10742

Versions 4.4.0, 4.5.0, 4.6.0, 4.7.0, and master branch - ✅ Already Correct

• These versions already have the correct configuration without Traffic Manager settings in the Key Manager section

Versions 4.0.0, 4.1.0, 4.2.0 - ℹ️ Not Applicable

• The documentation file for distributed deployment with separated Key Manager doesn't exist in these versions

Changes Made

The fix removes the following configuration blocks from the Key Manager sections in version 4.3.0:

• [apim.throttling] section with throttle_decision_endpoints
• [[apim.throttling.url_group]] sections with traffic_manager_urls and traffic_manager_auth_urls

These configurations are correctly placed in the Gateway and Control Plane sections where they belong.

Verification

• Documentation builds successfully with mkdocs build
• All changes follow Microsoft Style Guidelines for documentation