CMS Configuration Parameters

command-channels
Parameter Description
max-inactive Defines the amount of time that a command channel will be inactive before terminating the connection. The default value of 90 indicates that CMS will wait for up to 90 seconds before terminating the connection to the CMA. It will them attempt to re-establish the control connections to the control channel every 30 seconds (depending on the value of retry-interval).
retry-interval Defines how frequently CMS will attempt to establish a connection to the CMA when the connection to the CMA command channel is down.
timeout Define the timeout for TCP connection establishment to the control channel.
channel. Defines each CMA that the CMS connects to. You must define one channel for each CMA.
Parameter Description
address Defines the CMA IP address or IP name.
command-port Defines the IP port for command (that is, control) connections to the CMA. The CMA must be configured to listen on this port.
data-port Defines the IP port for data connections to the CMA. The CMA must be configured to listen on this port.
data channel
Parameter Description
connection-setup-timeout Defines the timeout for TCP connection establishment to the data channel.
socks
Parameter Description
connection-setup-timeout Defines the timeout for the TCP connection establishment to the destination (that is, target) server in the internal network.
command-channels
Parameter Description
valid-hosts Defines the Command Center hosts that can manage this CMS. IP addresses can be specified 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.
timeout Defines the timeout for the TCP connection establishment to the control channel.
allowed-dests.

Defines the destination IP address/IP names and IP ports that the CMS can connect to. This parameter can be defined in the following formats:

Parameter Format Description
10.1.2.3 Allows connections to all ports on IP address 10.1.2.3
10.1.2.0/24 Allows connections to all ports on Subnet 10.1.2.0
SQLServer1:1433 Allows connections to IP Name SQLServer1 on port 1433
FTPServer:40000-40100 Allows connections to IP Name FTPServer on ports 40000-40100

CMA (Connection Manager Agent) Configuration File

Note: You should update this file only when directed by Technical Support or when the Command Center is unable to manage the CMA.

Location: <CMA Install>/server/webapps/commgr/WEB-INF/reverseProxyDmz.xml 

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<proxy-config>
    <!-- internal proxy settings -->
    <internal-proxy>
        <!-- command channel settings -->
        <command-channels max-inactive="90">
            <!-- timeout and retry interval to setup command channel to DMZ proxy -->
            <connection-setup retry-interval="30" timeout="20"/>
            <!-- DMZ proxy hosts info to which to build command channel -->        
            <!--
            <channel>
                <address>specifyDMZServiceAddr2</address>
                <command-port>48000</command-port>
                <data-port>48001</data-port>
            </channel>
            -->
<channel>
<address>10.1.2.3.</address>
<command-port>48000</command-port>
<data-port>48001</data-port>
</channel>

        </command-channels>

        <!-- data channel settings -->
        <data-channel>
            <!-- timeout to set up data channel to DMZ proxy -->
            <connection-setup timeout="45"/>
        </data-channel>

        <!-- socks settings -->
        <socks>
          <!-- timeout to finish connecting to final destination -->
          <connection-setup timeout="45"/>
        </socks>
		
		<!-- which machines can manage this CMS -->
		<proxy-manage>
			<valid-hosts>10.0.0.0/8;192.168.0.0/16</valid-hosts>
			<password>xxxxxxxxxxxxxxxxxxxxxxxx </password>
		</proxy-manage>

		<!-- allowed final destinations. e.g. 10.97.196.100, 10.97.196.100/8, 10.97.196.100/8:21, 10.97.196.100/8:5000-5500. Empty means allow all -->
        <allowed-dest/>
    </internal-proxy>
</proxy-config>