Click here to view and discuss this page in DocCommentXchange. In the future, you will be sent there automatically.

SQL Anywhere 10.0.1 » SQL Anywhere 10 - Context-Sensitive Help » SQL Anywhere Plug-in Help » Introduction to SQL Anywhere property sheets

Synchronization Subscription property sheet: General tab Next Page

Synchronization Subscription property sheet: Connection tab


The Connection tab of the Synchronization Subscription property sheet has the following components:

Protocol    Choose 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 protocol, see:

Host    The IP number or host name of the computer on which the MobiLink server is running. The default value is localhost. You can use localhost if the MobiLink server is running on the same computer 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 server executing on the desktop computer 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.

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.

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 server.

Automatic connection    The following options allow MobiLink clients running on Windows or Windows CE 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.

See Scheduling synchronization.

Security    These options allow you to use a cipher suite to encrypt all communication through this connection. You can provide information about the certificate used to authenticate the server in the fields below for both the elliptic-curve and RSA ciphers.

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. This option is only available for versions 8.0.x and 9.0.x. Choosing this option with the TCP/IP protocol is equivalent to choosing the TLS protocol in version 10.

Separately licensed component required

ECC encryption and FIPS-certified encryption require a separate license. All strong encryption technologies are subject to export regulations.

See Separately licensed components.

For more information about security, see Transport-Layer Security.

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 CREATE SYNCHRONIZATION USER statement [MobiLink].

Note

You can set connection parameters for synchronization in several ways.

For information about how dbmlsync resolves conflicting options, see Priority order.

See also