Configuring proxy servers in TIBCO Mashery Local (ML)
Article ID: KB0073429
Updated On:
| Products | Versions |
|---|---|
| TIBCO Cloud API Management - Local Edition | 5.x and above |
Description
As documented proxy server configuration is done in tml_zones_properties.json using the below properties:
"mom_server_proxy_host": "",
"mom_server_proxy_port": 3128,
"mom_server_proxy_username": "",
"mom_server_proxy_password": "",
"target_server_proxy_host": "",
"target_server_proxy_port": 3128,
"no_proxy_pool": ""
This configuration is done per zone. As seen in the properties file, values have to be specified for each zone.
"mom_server_proxy_host": "",
"mom_server_proxy_port": 3128,
"mom_server_proxy_username": "",
"mom_server_proxy_password": "",
"target_server_proxy_host": "",
"target_server_proxy_port": 3128,
"no_proxy_pool": ""
This configuration is done per zone. As seen in the properties file, values have to be specified for each zone.
Issue/Introduction
This article provides inputs for configuring ML to use proxy server(s).
Environment
All Supported Platforms
Resolution
Here are additional inputs on these:
- If the cluster has only one zone, please provide values under zone0.
- The IP address(es) or hostname(s) for proxy_host properties should be enclosed in double-quotes.
#When the IP address was not in quotes:
- the attachment "ML_TM-containeragent_error_incorrect_proxy-in-zones-prop.txt" has sample errors in containeragent logs
- the proxy_error.log and proxy_debug.log were empty
- the javaproxy on the container did not even start, as the final properties file was empty
/opt/mashery/containeragent/resources/properties/tml_tm_properties_final.json & tml_tm_properties_internal.json
- If the cluster has only one zone, please provide values under zone0.
- The IP address(es) or hostname(s) for proxy_host properties should be enclosed in double-quotes.
#When the IP address was not in quotes:
- the attachment "ML_TM-containeragent_error_incorrect_proxy-in-zones-prop.txt" has sample errors in containeragent logs
- the proxy_error.log and proxy_debug.log were empty
- the javaproxy on the container did not even start, as the final properties file was empty
/opt/mashery/containeragent/resources/properties/tml_tm_properties_final.json & tml_tm_properties_internal.json
Attachments
Feedback
Yes
No
Powered by
