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

SAP Sybase SQL Anywhere 16.0 » Context-Sensitive Help » SQL Anywhere plug-in help » SQL Anywhere properties windows

 

Synchronization Subscription Properties window: Connection tab

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.

This tab has the following components:

  • Protocol   Choose the communication protocol to use for synchronization. TCP/IP is used by default.

    • TCP/IP   Select this option to use the TCP/IP protocol for synchronization.

    • TLS   Select this option to use TLS (transport-layer security) for synchronization.

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

    • HTTPS   Select this option to use the HTTPS protocol for synchronization.

  • 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 Mobile, the default value is the value of ipaddr in the registry folder Comm\Tcpip\Hosts\ppp_peer. Specifying ipaddr 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.

    • Port   The MobiLink 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 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 to find the MobiLink server.

    • HTTP Version   Select 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 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 Synchronization schedules.

    • Network name   Specifies the network name so that you can use the MobiLink auto-dial feature. This allows you to connect without dialing manually. The name should be the network name that you specified in the dropdown list in 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 closed.

    • 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 Windows Mobile. (On Windows, you can control this feature by configuring the connection profile.) The default is 120 seconds.

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

    Note

    Separately licensed component required.

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

    See Separately licensed components.

    • Cipher  

      • Elliptic curves   This option is only available for version 12 and earlier databases. Uses the elliptic-curve algorithm to encrypt connections. You can use this algorithm to encrypt TLS over TCP/IP and HTTPS connections.

      • RSA   Uses the RSA algorithm to encrypt communications. You can use this algorithm to encrypt TLS over TCP/IP and HTTPS connections.

      • FIPS-certified   Uses the FIPS-certified RSA algorithm to encrypt communications. You can use this algorithm to encrypt TLS over TCP/IP and HTTPS connections. FIPS-certified encryption requires a separate license.

    • Trusted certificate  

      • Select File, and type the name of the certificate file the client uses to authenticate the database server.

      • Select Name, and choose a certificate from the dropdown list of certificates stored in the remote database

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

  • 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 specify the following in the Advanced field:
    buffer_size=58000;persistent=TRUE

    For a complete list of connection parameters you can specify 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