The Connection tab of the Synchronization Subscription property sheet has the following components:
Protocol Specify the communication protocol to use for synchronization. TCP/IP is used by default.
The settings you can specify on the Connection tab depend on the communication protocol you are using. Any additional parameters, such as buffer_size, can be set in the Advanced field.
For a complete list of parameters supported by each of the protocols, see or .
TCP/IP Select this option to use the TCP/IP protocol for synchronization. TCP/IP supports both elliptic-curve (formerly Certicom) and RSA encryption.
HTTP Select this option to use the HTTP protocol for synchronization. HTTP supports both elliptic-curve (formerly Certicom) and RSA encryption.
HTTPS Select this option to use the HTTPS protocol for synchronization. You can only use RSA encryption with the HTTPS protocol.
HTTPS FIPS Select this option to use the HTTPS_FIPS protocol for synchronization.
ActiveSync Select this option to use ActiveSync to exchange data with the MobiLink provider for ActiveSync, which resides on the desktop machine. The ActiveSync parameters describe the communications between the MobiLink provider for ActiveSync and the MobiLink synchronization server.
For more information, see .
Host The IP number or host name of the machine on which the MobiLink synchronization server is running. The default value is localhost. You can use localhost if the synchronization server is running on the same machine as the client.
For Windows CE, the default value is the value of ipaddr in the registry folder Comm\Tcpip\Hosts\ppp_peer. This allows a Windows CE device to connect to a MobiLink synchronization server executing on the desktop machine where the Windows CE device's cradle is connected.
For the Palm Computing Platform, the default value of localhost refers to the device. It is recommended that you specify an explicit host name or IP address.
Port The MobiLink synchronization server communicates over a specific port. The default port number is 2439 for TCP/IP, 80 for HTTP, and 443 for HTTPS. If you choose a different value, you must configure your MobiLink synchronization server to listen on the port you specify.
Proxy host Type the host name or IP address of the proxy server. The default value is localhost. This option is only available for HTTP and HTTPS synchronization.
Proxy port Type the port number of the proxy server. The default value is 80 for HTTP and 443 for HTTPS. This option is only available for HTTP and HTTPS synchronization.
URL suffix Type the suffix to add to the URL on the first line of each HTTP request. The default value is MobiLink. This option is only available for HTTP and HTTPS synchronization.
When synchronizing through a proxy server, the suffix may be necessary in order to find the MobiLink synchronization server.
HTTP Version Type the value specifying the version of HTTP to use for synchronization. You have a choice of 1.0 or 1.1. The default value is 1.1.
Automatic connection The following options allow MobiLink clients running on Pocket PC 2002 or Windows desktop computers to connect through dial-up network connections.
When used with scheduling, your remote device can synchronize unattended. When used without scheduling, you can run dbmlsync without manually dialing a connection.
For more information about scheduling, see .
Network name Specify the network name so that you can use MobiLink's auto-dial feature. This allows you to connect from a Pocket PC 2002 or Windows desktop computer without manually dialing. The name should be the network name that you have specified in the dropdown list in Settings > Connections > Connections (Pocket PC) or Network & Dialup Connections (Windows).
Network connect timeout When you specify a network name, you can optionally specify a timeout after which the dial-up fails. This feature applies only to Pocket PC 2002. (On Windows, you can control this feature by configuring the connection profile.) The default is 120 seconds.
Leave open When you supply a network name, you can optionally specify whether the connection should be left open (1) or closed (0) after synchronization finishes. By default, the connection is closed.
Enable Certicom security Select this option to encrypt all communication through this connection. You can use the elliptic-curve or RSA cipher. By default, elliptic curves are used.
Separately licensable option requiredTransport-layer security requires that you obtain the separately-licensable SQL Anywhere Studio security option and is subject to export regulations.To order this component, see . |
For more information about security, see .
Elliptic curves Uses the elliptic-curve cipher to encrypt connections. You can use this cipher to encrypt TCP/IP and HTTP connections. This was formerly called Certicom encryption.
RSA Uses the RSA cipher to encrypt all connections. You can use this cipher to encrypt TCP/IP, HTTP, and HTTPS connections.
RSA FIPS Uses the RSA FIPS cipher to encrypt all connection. You can use this cipher to encrypt communications over the TCP/IP and HTTPS FIPS protocols.
Certificate company Type the name of the certificate authority or organization that issued the certificate. The server's and the client's values must match.
Certificate unit Type the certificate unit. This is also called the organizational unit. The server's and the client's values must match.
Certificate name Type the certificate's common name. The server's and the client's values must match.
Trusted certificates Type the name of the certificate file the client uses to authenticate the server.
Advanced Type any additional connection parameters in this field, entering them in the form parameter=value, with multiple parameters separated by semicolons. For example, to set the maximum body size for a fixed content length message, and to instruct the client to attempt to use the same TCP/IP connection for all HTTP requests in a synchronization, you would enter the following in the Advanced field:
buffer_size=58000;persistent=TRUE
For a complete list of connection parameters you can enter in this field, see .
You can set connection parameters for synchronization in several ways.
For information about how dbmlsync resolves conflicting options, see .