Bookshelf v7.8: Enabling the Stand-Alone Synchronizer

A mobile user can control the synchronization start-up process by running the Siebel Remote client in a third-party scheduling program. Table 16 shows the command-line options for the Siebel Remote client.

NOTE: If a local connection to the client is open and the user uses the Siebel Remote icon to synchronize, synchronization works successfully. However, if a new database extract exists for that user, the synchronization fails, because it is trying to overwrite the sse_data.dbf file, which is already in use. Therefore, the stand-alone Siebel Remote client should only be used when the Mobile Web Client is not in use.

Table 16. Stand-Alone Synchronizer Command-Line Options
Option	Definition	Required/Optional	Default Value and Usage Notes
/?	Help	Optional	Provides online help for usage.
/a	Autostart mode	Optional	Available modes are Y or N.
/ApplyTxns	Apply transactions during this synchronization	Optional	Determines whether or not transactions will be applied to the local database during the current synchronization operation. Available modes are Y or N. Defaults to Y. A value of N directs transactions to be downloaded and uploaded, but not applied.
/c	Configuration file	Required	The default is siebel.cfg.
/comm	Communication parameters	Optional	Used for modem connections.
/d	Data source	Optional	The default is local.
/help	Help	Optional	Provides online help for usage.
/i	Iterations	Optional	Sets the number of iterations.
/l	Language	Optional	Language to use for the docking session.
/n	Client name	Required	Name of Mobile Web Client. The value must be entered using uppercase letters.
/p	User password	Required	Database connection password. The value must be entered using uppercase letters.
/p2	Confirmation password	Required	Required when initializing.
/ParallelApply	Apply transactions in parallel with data transfers	Optional	Determines whether transactions will be applied to local database while other transactions are still being transferred between client and server, or whether all transactions will be applied after data transfer is complete. Available modes are Y or N. Defaults to Y. This option is ignored if the ApplyTxns option is set to N.
/RecvAutoUpdFiles	Receive auto updates to files	Optional	Determines whether Mobile Web Client will download updates to requested files. Available modes are Y or N.
/RecvFiles	Receive files	Optional	Determines whether Mobile Web Client will download files from server. Available modes are Y or N.
/RecvPubFiles	Receive published files	Optional	Determines whether Mobile Web Client will download published files. Available modes are Y or N.
/RecvTxns	Receive transactions	Optional	Determines whether Mobile Web Client will download transactions from server. Available modes are Y or N.
/SendTxns	Send transactions	Optional	Determines whether Mobile Web Client will send transactions to server. Available modes are Y or N.
/sleep	Sleep time	Optional	Number of seconds to sleep between iterations.
/u	User name	Required	Database connection user name. The value must be entered using uppercase letters.
/v	Verbose mode	Optional	Available modes are Y or N.1

1You may want to run the Stand-Alone Synchronizer unattended by setting the verbose mode to N. After synchronization, the Stand-Alone Synchronizer returns 0 if the process succeeded, or a nonzero Siebel error code if it failed.

Using certain command line options, the process of uploading and downloading transactions can now be separated from the process of applying downloaded transactions to the local database. The purpose of this option is to let users choose the most convenient timing for these two portions of a synchronization, rather than requiring them to be performed together. The following procedures briefly describe how to transfer and apply transactions separately.