ml_add_property ( 
'comp_name', 
'prop_set_name', 
'prop_name', 
'prop_value'
)

The MobiLink server can be set to use different log verbosity for a targeted MobiLink user or remote ID. The MobiLink server checks the ml_property table every five minutes and looks for verbose settings for a MobiLink user or remote ID. If verbose settings exist, then it uses the new setting to log output messages for the given MobiLink user or remote ID. This enables you to see the details for a specific user or remote ID without the need for high verbosity settings that would negatively impact the server farm, and without requiring a restart of each server in the farm.

To set maximum verbosity for a targeted MobiLink user, for example ml_user1, log into the consolidated database and issue the following SQL command:

call ml_add_property( 'MLS', 'ml_user_log_verbosity', 'ml_user1', '-v+' )

To set maximum verbosity for a targeted remote ID, for example rid_1, log into the consolidated database and issue the following SQL command:

call ml_add_property( 'MLS', 'ml_remote_id_log_versity', 'rid_1', '-v+' )

Note that verbose_setting must be a valid MobiLink server -v option. For example, to log row data and undefined table scripts, the verbose_setting can be -vru or vru. The MobiLink server uses this verbose setting for ml_user1 or rid_1 after 5 minutes. See -v mlsrv12 option.

To disable log verbosity for a MobiLink user, log into the consolidated database and issue the following SQL command:

call ml_add_property( 'MLS', 'ml_user_log_verbosity', 'ml_user1', NULL )

To disable log verbosity for a MobiLink remote ID, log into the consolidated database and issue the following SQL command:

call ml_add_property( 'MLS', 'ml_remote_id_log_verbosity', 'rid_1', NULL )

The MobiLink server stops using the previous verbose setting for ml_user1 or rid_1 after five minutes.

If both the ml_user_log_verbosity and ml_remote_id_log_verbosity are set for a given MobiLink user and remote ID, and if the MobiLink user name and remote ID in a synchronization are identical to the given targeted MobiLink user and remote ID, the MobiLink server uses the ml_remote_id_log_verbosity setting to log output messages.

For server-initiated synchronization, the ml_add_property system procedure allows you to set properties for Notifiers, gateways, and carriers.

For example, to add the property server=mailserver1 for an SMTP gateway called x:

ml_add_property( 'SIS','SMTP(x)','server','mailserver1' );

The verbosity property applies to all Notifiers and gateways, and so you cannot specify a particular property set name. To change the verbosity setting, leave the property set name blank:

ml_add_property( 'SIS','','verbosity',2 );

For regular MobiLink synchronization, you can use this system procedure to associate properties with a script version. In this case, set the component_name to ScriptVersion. You can specify any properties, and use Java and .NET classes to access them.

For example, to associate an LDAP server with a script version called MyVersion:

ml_add_property( 'ScriptVersion','MyVersion','ldap-server','MyServer' )

• MobiLink server settings for server-initiated synchronization
• DBConnectionContext.getProperties method [MobiLink server Java]
• DBConnectionContext.getVersion method [MobiLink server Java]
• DBConnectionContext.GetProperties method [MobiLink server .NET] and DBConnectionContext.GetVersion method [MobiLink server .NET]
• ServerContext.getPropertiesByVersion method [MobiLink server Java]
• ServerContext.getProperties method [MobiLink server Java]
• ServerContext.getPropertySetNames method [MobiLink server Java]
• ServerContext.getPropertiesByVersion method [MobiLink server .NET], ServerContext.getProperties method [MobiLink server .NET], ServerContext.getPropertySetNames method [MobiLink server .NET]