User manual

set mgmtnetwork
144 Chapter 2 Command Descriptions
connectionmethod={auto|none|mt|mdh|proxy}
The Connectware Device Protocol firewall traversal method.
auto
Automatically detect the connection method.
none
No firewall; connect using TCP.
mt
Connect using TCP.
mdh
Connect using HTTP.
proxy
Connect using HTTP over proxy.
proxyaddress=string
The proxy host address when the connection method is “proxy.”
proxyport=port
The proxy host port when the connection method is “proxy.”
proxylogin=string
The login string when the connection method is “proxy.”
proxypassword=string
The proxy password when the connection method is “proxy.”
proxypersistentconnection={on|off}
Whether the device server should attempt to use HTTP persistent
connections when the connection method is “proxy.” Not all HTTP
proxies correctly handle HTTP persistent connections. The use of
persistent connections can improve performance of the exchange of
messages between the device server and Connectware Manager, when
that connection is HTTP/proxy. The reason for this is that the same HTTP
connection can be reused for multiple consecutive HTTP requests and
replies, eliminating the overhead of establishing a new TCP connection
for each individual HTTP request/reply, then closing that connection
when the request is complete.
on
The device server should attempt to use HTTP persistent connections.
off
The device server should not attempt to use HTTP persistent
connections.
mtrxkeepalive=time
The transmit keep alive time when connection method is “mt,” where time
is the number of seconds to wait between sending keep-alive messages.
mttxkeepalive=time
The receive keep alive time when connection method is “mt,” where time
is the number of seconds to wait for a keep-alive message from the
Connectware Manager server before assuming the connection is lost.