iAnywhere.com - CREATE SYNCHRONIZATION USER statement [MobiLink]

CREATE SYNCHRONIZATION USER statement [MobiLink]

Description

Use this statement in an Adaptive Server Anywhere remote database to create a synchronization user.

Syntax

CREATE SYNCHRONIZATION USER ml_username
[ TYPE sync-type ]
[ ADDRESS network-parameters ]
[ OPTION option=value, ... ]

ml_username: identifier

sync-type: tcpip | http | https | ActiveSync

network-parameters: string

value: string | integer

Parameters

ml_username A name identifying a remote database. This name must be unique.

For more information about synchronization user names, see About MobiLink users.

TYPE clause This clause specifies the communication protocol to use for synchronization. The options are tcpip, http, https, and ActiveSync. The default protocol is tcpip.

ADDRESS clause This clause specifies network-parameters in the form keyword=value, separated by semi-colons. Which settings you supply depends on the communication protocol you are using (TCPIP, HTTP, HTTPS, or ActiveSync).

For a complete list of network parameters, see CommunicationAddress (adr) extended option.

OPTION clause The OPTION clause allows you to set options using option=value in a comma-separated list.

The values for each option cannot contain equal signs or semicolons. The database server accepts any option that you enter without checking for its validity. Therefore, if you misspell an option or enter an invalid value, no error message appears until you run the dbmlsync command to perform synchronization.

Options set for a synchronization user can be overridden in individual subscriptions or on the dbmlsync command line.

For information about extended options, see dbmlsync extended options.

Description

The sync-type, network-parameters, and options can be set in several places.

For information about how dbmlsync processes options that are specified in different locations, see Priority order for extended options and connection parameters.

Permissions

Must have DBA authority.

Side effects

Automatic commit.

Standards and compatibility

SQL/92 Vendor extension.
SQL/99 Vendor extension.
Sybase Supported by Open Client/Open Server.

Examples

The following example creates a user named SSinger, who synchronizes over TCP/IP with a server machine named mlserver.mycompany.com using the password Sam. The use of a password in the user definition is not secure.

CREATE SYNCHRONIZATION USER SSinger
TYPE http
ADDRESS 'host=mlserver.mycompany.com'
OPTION MobiLinkPwd='Sam'

The following creates a synchronization user called factory014 that will cause dbmlsync to hover and synchronize via Certicom-encrypted TCP/IP at a random time in every 8-hour interval. The randomness helps prevent performance degradation at the MobiLink server due to multiple simultaneous synchronizations:

CREATE SYNCHRONIZATION USER factory014
TYPE tcpip
ADDRESS 'host=mycompany.manufacturing.mobilink1;security=certicom_tls(certificate=mycompany_mobilink.crt;certificate_password=thepassword)'
OPTION Schedule='EVERY:08:00'

The following creates a synchronization user called sales5322 that will be used to synchronize with HTTP. In this example, the MobiLink synchronization server runs behind the corporate firewall, and synchronization requests are redirected to it using the Redirector (a reverse proxy to an NSAPI Web server).

CREATE SYNCHRONIZATION USER sales5322
TYPE https
ADDRESS 'host=www.mycompany.com;port=80;url_suffix=mlredirect/ml/'