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

SQL Anywhere 11.0.1 » Context-Sensitive Help » SQL Anywhere plug-in help » Introduction to SQL Anywhere properties windows

 

Synchronization Profile Properties window: Connection

This tab has the following components:

  • Protocol   Choose the communication protocol to use for synchronization.

    • TCP/IP   Choose this option to use the TCP/IP protocol for synchronization. This is the default.

    • TLS   Choose this option to use TLS (transport-layer security) for synchronization. TLS supports both elliptic-curve cryptography (formerly Certicom) and RSA encryption. This option is only available for version 10 and later.

    • HTTP   Choose this option to use the HTTP protocol for synchronization.

    • HTTPS   Choose this option to use the HTTPS protocol for synchronization. HTTPS supports both elliptic-curve cryptography (formerly Certicom) and RSA encryption.

  • Host   Specify 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 Mobile, the default value is the value of ipaddr in the registry folder Comm\Tcpip\Hosts\ppp_peer. This allows a Windows Mobile device to connect to a MobiLink server executing on the desktop computer where the Windows Mobile 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   Specify the port number for the MobiLink server to communicate over. 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 server to listen on the port you specify.

  • Proxy host   Specify 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   Specify 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   Specify the suffix to add to the URL on the first line of each HTTP request. The default value is MobiLink. When synchronizing through a proxy server, the suffix may be necessary to find the MobiLink server. This option is only available for HTTP and HTTPS synchronization.

    • HTTP version   Specify the value 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 Windows or Windows Mobile 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.

  • Network name   Specify the network name so you can use the MobiLink auto-dial feature. This allows you to connect from Windows or Windows Mobile without dialing manually. The name should be the network name that you specified in the dropdown list Settings » Connections » Connections (Windows Mobile) or Network Connections (Windows).

  • 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 0 (closed).

Security
  • Cipher   When you choose TLS or HTTPS, the security options are enabled. These security options allow you to use a cipher suite to encrypt all communication through the connection.

    • Elliptic curves   Choose this option to use the elliptic-curve cipher to encrypt connections. You can use this cipher to encrypt TLS over TCP/IP and HTTPS connections with version 10 and later databases, and TCP/IP connections with version 8.0.x and 9.0.x databases. This was formerly called Certicom encryption.

      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.

    • RSA   Choose this option to use the RSA cipher to encrypt communications. You can use this cipher to encrypt TLS over TCP/IP and HTTPS connections with version 10 and later databases, and TCP/IP connections with version 8 and 9 databases. This cipher is selected automatically with version 8.0.x and 9.0.x databases when you choose HTTPS.

    • FIPS-approved   Choose this option to use the FIPS-approved RSA cipher to encrypt communications. You can use this cipher to encrypt TLS over TCP/IP and HTTPS connections with version 10 and later databases, and TCP/IP connections with version 9.0.x databases. This cipher is selected automatically with version 9 databases when you choose HTTPS FIPS. This cipher is not supported for version 8.0.x databases.

  • 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. See certificate_company.

  • certificate_unit   Type the certificate unit. This is also called the organizational unit. The server's and the client's values must match. See certificate_unit.

  • certificate_name   Type the certificate's common name. The server's and the client's values must match. See certificate_name.

  • trusted_certificates   Type the name of the certificate file the client uses to authenticate the server. See trusted_certificates.

  • Advanced   A semicolon delimited list of option=value pairs.