There are two connection specifications, one for an Initiator and one for an Acceptor. Between the two, there is a large overlap of properties. We'll introduce the common properties in a table and then show each of the distinct set of properties in their own respective tables.

Connection properties common to the Initiator and Acceptor

parameter	current value	description
instanceName	myAcceptor_9797	a unique string to name the enigne.
isAcceptor	true	Is this connection an acceptor [ true , false ]
hostname	127.0.0.1	IP address: when Initiator, the IP address to connectect TO; when Acceptor, the IP address to open for connecitons.
port	9797	The port to use with the hostname.
channelOptions	[macro to expand to a complete set of values]	see Include File's ChannelOptions.xml
socketOptions	[macro to expand to a complete set of values]	see Include File's SocketOptions.xml. Note there are two macros that are available. One for a Gracefull close and one for an Immediate close.

Initiator Connection properties

                    <Channel_initiater_8282>
                        <instanceName>Channel_Initiator_8282_${cmdLine_appNameSuffix}</instanceName>

                        <isAcceptor>false</isAcceptor>

                        <hostname>${Acceptor_9797_hostname}</hostname>
                        <port>${Acceptor_9797_port}</port>

                        <channelOptions>${ChannelOptions}</channelOptions>
                        <socketOptions>${SocketOptions_ImmediateClose}</socketOptions>

   	       <!--  Initiator unique tags below  -->
                        <!--  to allow testing acceptor host, set host,port that initiator will connect from -->
                        <inititators_localHost_optional>${Test_8282_hostname}</inititators_localHost_optional>
                        <inititators_localPort_optional>${Test_8282_port}</inititators_localPort_optional>

                        <fixSpec>
                            ${Test_8282_initiator_tags}
                        </fixSpec>

                    </Channel_initiater_8282>
    		    
  

parameter	current value	description
inititators_localHost_optional	127.0.00.1	to allow testing acceptor's ability to restrict messages from hosts. Force initiator to login from a host
inititators_localPort_optional	8282	works with inititators_localHost_optional
fixSpec	[macro to expand to a complete set of values]	see Include File's TestFixConnections.html

Acceptor Connection properties

                    <Channel_myAcceptor_9797>
                        <instanceName>myAcceptor_9797</instanceName>

                        <isAcceptor>true</isAcceptor>

                        <hostname>${Acceptor_9797_hostname}</hostname>
                        <port>${Acceptor_9797_port}</port>

                        <channelOptions>${ChannelOptions}</channelOptions>
                        <socketOptions>${SocketOptions_GracefullClose}</socketOptions>

	       <!--  Acceptor unique tags below  -->
		    
                        <hostConnectionCountOfOne_IsRequired>true</hostConnectionCountOfOne_IsRequired>
                        <hostConnectionCountOverride>
                            <host ip="127.0.0.1" limit="2"/>
                            <host ip="127.0.0.1" limit="2"/>
                        </hostConnectionCountOverride>

                        <fixSpecList>
                            <acceptorSpec>
                                <fixSpec>${Test_8383_initiator_tags}</fixSpec>
                                <remoteHostname>${Test_8383_hostname}</remoteHostname>
                            </acceptorSpec>

                            <acceptorSpec>
                                <fixSpec>${Test_8282_initiator_tags}</fixSpec>
                                <remoteHostname>${Test_8282_hostname}</remoteHostname>
                            </acceptorSpec>

                        </fixSpecList>
                    </Channel_myAcceptor_9797>

  

parameter	current value	description
hostConnectionCountOfOne_IsRequired	true	When true, requires each IP that connects to be listed; connection attempts from unlisted IPs will be silently disconnected. When false, an unlisted IP address is allowed to connect one time. Second attempts are disconnected unless overridden by the hostConnectionCountOverride property.
hostConnectionCountOverride	[multi value list of the 'host' element with attribues 'host' and 'limit'. See example for syntax.]	Each host entry specifies the maximum number of connections permitted from a host IP. (Note: the fix layer has logic to ensure each business client has only one live connection at a time.)
fixSpecList	[has many acceptorSpec definitions]	This is a list of FixSpecs and Remote Host IPs that are permitted to connect to the Acceptor. Where the initiator had only the FixSpec, the Acceptor as many FixSpec-RemoteHostName pairs. Note how the FixSpec property in the Acceptor is identical to the one in the Initiator. For the fixSpec definition, see Include File's TestFixConnections.html