CMA Configuration Parameters

command-channels
Parameter Description
listener handshake-timeout Defines how long CMA will wait for the handshake to complete.
keep-alive Defines how frequently CMA will issue heartbeat requests to the CMS. The default value of 45 indicates that CMA sends heartbeats to CMS every 45 seconds during periods of inactivity
keep-alive-timeout Defines the number of seconds that CMA will wait for heartbeat response from CMS before closing the connection.
address Defines the adapter IP address that CMA binds to prior to listening for incoming control channel requests. The default of 0.0.0.0 will use all adapter IP addresses.
port Defines the IP port that CMA listens on for incoming control channel connections.
valid-internal-hosts Defines IP addresses of internal CMS servers. IP addresses can be specifies as a full IP address or an IP address with the number of subnet bits. Multiple IP addresses can be defined by separating them with a semi-colon.
data-channel
Parameter Description
address Defines the adapter IP address that CMA binds to prior to listening for incoming data channel requests. The default of 0.0.0.0 uses all adapter IP addresses.
port Defines the IP Port that CMA will listen on for incoming data channel connections.
connect-timeout Defines how long CMA waits for a CMS connection, requested by CMA over the command (that is, control) channel.
idle-timeout This parameter is for future use and should be ignored.
socks-channel
Parameter Description
address Defines the adapter IP address that CMA binds to prior to listening for incoming requests from the Internet Server. The default of 0.0.0.0 uses all adapter IP Addresses.
port Defines the IP port that CMA listens on for incoming connections from the Internet Server.
valid-sock5-hosts Defines the Internet Server hosts that CMS accepts connection requests from. The default value of 127.0.0.1 accepts requests from the local host. Multiple IP addresses can be defined by separating them with a semi-colon.
proxy-manage
Parameter Format Description
valid-hosts Defines the Command Center hosts that can manage this CMS. IP addresses can be specifies as a full IP address or an IP address with the number of subnet bits. Multiple IP addresses can be defined by separating them with a semi-colon.
password Defines the encrypted Command Center Management password.

Internet Server Connection Manager Configuration File

Note: You should update this file only when directed to by Technical Support or when the Command Center is unable to manage the Connection Manager component of Internet Server.

Location: <MFTIS Install>/server/webapps/cfcc/reverseProxyDmz.xml 

<?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="on"> <!-- 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;1.2.3.4/32</internaladdress>
			
            <!-- CMA's sock server end point. use: host:port[;host:port] format -->
			<socks-servers loadBalance="no">10.1.2.3: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>