Registers MobiLink users at the consolidated database. For SQL Anywhere remotes, the users must have previously been created at the remote databases with the CREATE SYNCHRONIZATION USER statement.
mluser [ options ] -c "connection-string" { -f file | -u user [ -p password ] }
Option | Description |
---|---|
@data |
Use this to read in options from the specified environment variable or configuration file. If both exist with the same name, the environment variable is used. See Configuration files. To protect passwords or other information in the configuration file, you can use the File Hiding utility to obfuscate the contents of the configuration file. See File Hiding utility (dbfhide). |
-c "keyword=value;..." |
Use this to supply database connection parameters. The connection string must provide the utility sufficient privileges to connect to the consolidated database using an ODBC data source. This parameter is required. |
-d | Deletes the user name(s) specified by -f or -u. This option cannot be used with mluser -r option. |
-f filename | Reads the user names and passwords from the specified file. The file should be a text file containing one user name and password pair on each line, separated by white space. You must specify either -f or -u. |
-fips | When set, mluser fails if support for FIPS-certified encryption is not installed. |
-n user authentication policy name |
Registers a MobiLink user with LDAP user authentication. |
-o filename | Logs output messages to the specified file. |
-ot filename | Truncate the log file and then append output messages to it. The default is to send output to the screen. |
-pc collation-id |
Supplies a database collation ID for character set conversion of the user name and password. This should be one of the SQL Anywhere collation labels such as those listed in Alternate collations. This option is required when user names and passwords are read from a file that is encoded in a different character set than the default character set determined by locale. |
-p password | Password to associate with the user. This option can only be used with -u. |
-r remote-id |
Use this option with -u username and mluser resets the synchronization state for the given remote ID and username. The last_upload_time and last_download_time columns in the ml_subscription table are reset to their default values for the given username and remote ID. The default values for the progress, last_upload_time, and last_download_time columns are 0, '1900/01/01 00:00:00', and '1900/01/01 00:00:00', respectively. This option cannot be used with the mluser -d option. CautionThis option resets the synchronization state information for the given username and remote ID and this action cannot be undone. After the synchronization status is reset, the MobiLink server always accepts the first synchronization request from the client without checking the last synchronization status. |
-u username | Specify the user name to add (or delete, if used with -d). Only one user can be specified on a single command line. This option is used with -p if passwords are being used. You must specify either -f or -u. |
-v | Specifies verbose logging. |
Given a user/password pair, the mluser utility first attempts to add the user. If the user has already been added to the consolidated database, it attempts to update the password for that user.
There are alternative ways to register user names in the consolidated database:
Use Sybase Central.
Specify the -zu+ command line option with mlsrv16. In this case, any existing MobiLink users that have not been added to the consolidated database are added when they first synchronize.
The MobiLink user must already exist in a remote database. To add users at the remote, you have the following options:
For SQL Anywhere remotes, set the name with CREATE SYNCHRONIZATION USER and synchronize with that user name.
For UltraLite remotes, you can either use the user_name field of the ul_sync_info structure; or in Java, use the SetUserName() method of the ULSynchInfo class before synchronizing.
![]() |
Discuter à propos de cette page dans DocCommentXchange.
|
Copyright © 2013, SAP AG ou société affiliée SAP - SAP Sybase SQL Anywhere 16.0 |