CMA Configuration File

The CMA configuration file is located in the <CMA_Install>/server/webapps/commgr/WEB-INF/reverseProxyDmz.xml directory.

Note: It is good practice to update this file only when directed to by TIBCO Technical Support or when you cannot use TIBCO MFT Command Center to manage CMA.

A sample CMA configuration file is as follows: 

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<proxy-config>

    <!-- DMZ proxy settings -->
    <dmz-proxy>

        <!-- command channel settings -->
        <command-channel>
            <!-- address and port to accept command channel request from internal RP proxy -->
            <listener handshake-timeout="20" keep-alive="45" keep-alive-timeout="30">
                <address>0.0.0.0</address>          <!-- empty means 0.0.0.0 -->
                <port>48000</port>
            </listener>
            <!-- valid hosts from which to accept command channel -->
            <valid-internal-hosts>10.0.0.0/8;192.168.0.0/16</valid-internal-hosts>
        </command-channel>

        <!-- data channel settings -->
        <data-channel>
            <!-- address and port to accept data channel request from internal RP proxy -->
            <listener>
                <address>0.0.0.0</address>           <!-- empty means 0.0.0.0 -->
                <port>48001</port>
            </listener>
            <data-pipe connect-timeout="45" idle-timeout="1800"/>
        </data-channel>

        <!-- SOCKS channel settings -->
        <socks-channel>
            <!-- address and port to accept sock5 request -->
            <listener>
                <address>0.0.0.0</address>           <!-- empty means 0.0.0.0 -->
                <port>41080</port>
            </listener>
            <!-- valid hosts from which to accept sock5 requests, can use ; to separate multiple hosts -->
            <valid-sock5-hosts>127.0.0.1;::1</valid-sock5-hosts>
        </socks-channel>
		
		<proxy-selector state="cma"> <!-- state: on|off|cma, on|off are used by MFT's sock selector, cma means this config is for cma, not for mft -->
			<internaladdress>10.0.0.0/8;192.168.0.0/16</internaladdress>
			
            <!-- CMA's sock server end point. use: host:port[;host:port] format -->
			<socks-servers loadBalance="no">127.0.0.1:41080</socks-servers>
		</proxy-selector>

		<!-- which machines can manage this CMA -->
		<proxy-manage>
			<valid-hosts>10.0.0.0/8;192.168.0.0/16</valid-hosts>
			<password>xxxxxxxxxxxxxxxxxxxxxxxx </password>
		</proxy-manage>
			
    </dmz-proxy>
	
</proxy-config>