This tab only applies to MobiLink publications.
This tab 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.
TCP/IP Select this option to use the TCP/IP protocol for synchronization. For versions 8.0.x and 9.0.x, choosing TCP/IP and then Enable Certicom security is equivalent to choosing TLS.
TLS Select this option to use TLS (transport-layer security) for synchronization. TLS supports both elliptic-curve cryptography (ECC) and RSA encryption. This option is only available for version 10 and later.
HTTP Select this option to use the HTTP protocol for synchronization.
HTTPS Select this option to use the HTTPS protocol for synchronization. HTTPS supports both elliptic-curve cryptography (ECC) and RSA encryption.
HTTPS FIPS Select this option to use the HTTPS protocol for synchronization with FIPS-certified encryption algorithms. This option is only available for version 8.0.x and 9.0.x. For version 10 and later, this is equivalent to selecting the HTTPS protocol and then selecting the FIPS-certified option for Security.
ActiveSync Select this option to use Microsoft ActiveSync to exchange data with the MobiLink provider for Microsoft ActiveSync, which resides on the desktop computer. The Microsoft ActiveSync parameters describe the communications between the MobiLink provider for Microsoft ActiveSync and the MobiLink server. This option is only available for versions 8.0.x and 9.0.x. See Microsoft ActiveSync Provider Installation utility (mlasinst).
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 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.
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 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 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 Specify the network name so that 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 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 0 (closed).
Separately licensed component required.
ECC encryption and FIPS-certified encryption require a separate license. All strong encryption technologies are subject to export regulations.
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 server in the fields below for both the elliptic-curve and RSA algorithms.
Elliptic curves Uses the elliptic-curve algorithm to encrypt connections. You can use this algorithm 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 was formerly called Certicom encryption.
RSA Uses the RSA algorithm to encrypt communications. You can use this algorithm 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 algorithm is selected automatically with version 8 and 9 databases when you choose HTTPS.
FIPS-approved Uses the FIPS-certified RSA algorithm to encrypt communications. You can use this algorithm to encrypt TLS over TCP/IP and HTTPS connections with version 10 and later databases, and TCP/IP connections with version 9 databases. This algorithm is selected automatically with version 9 databases when you choose HTTPS FIPS. This algorithm is not supported for version 8 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.
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 specify the following in the Advanced field:
For a complete list of connection parameters you can specify in this field, see CREATE SYNCHRONIZATION USER statement [MobiLink].
You can set connection parameters for synchronization in several ways.
For information about how dbmlsync resolves conflicting options, see Priority order.
If a field is blank on the Connection tab of the MobiLink User Properties window, the MobiLink user may be inheriting the connection parameter setting from the synchronization subscription. You should only supply connection parameters on the Connection tab of the MobiLink User Properties window if you want to override the publication's settings.
Discuss this page in DocCommentXchange.
|Copyright © 2012, iAnywhere Solutions, Inc. - SQL Anywhere 12.0.1|