Several system procedures are available to manually set up device tracking for 9.0.0 Listeners or Listeners for Palm devices. These procedures update the ml_device, ml_device_address, and ml_listening MobiLink system tables on the consolidated database.

With manual device tracking, you can address recipients by MobiLink user name without providing network address information. However, the information cannot be automatically updated by MobiLink if it changes; you must change it manually. This method is especially useful for SMTP gateways because email addresses seldom change.

For UDP gateways, you can not rely on static entries if your IP address changes every time you reconnect. You can resolve this problem by addressing the host name instead of IP address. However, this solution slows updates to DNS server tables, and can misdirect push notifications. You can also set up system procedures to update the system tables programmatically.

To manually set up device tracking for 9.0.0 Listeners or Palm Listeners

1. For each device, add a device record to the ml_device system table. For example:

   CALL ml_set_device( 'myFirstTreo180', 'MobiLink Listeners for Treo 180 - 9.0.1 Palm Listener', '1', 'not used', 'y', 'manually entered by administrator' );

   The first parameter, myFirstTreo180, is a unique user-defined device name. The second parameter contains optional remarks about the Listener version. The third parameter specifies a Listener version; use 0 for SQL Anywhere 9.0.0 Listeners, 1 for post-9.0.0 Listeners for Palm devices, and 2 for post-9.0.0 Listeners for Windows. The fourth parameter specifies optional device information. The fifth parameter specifies whether device tracking should be ignored. The final parameter contains optional remarks for this entry.

   See ml_set_device system procedure.

2. For each device, add an address record to the ml_device_address system table. For example:

   CALL ml_set_device_address( 'myFirstTreo180', 'ROGERS AT&T', '55511234567', 'y', 'y', 'manually entered by administrator' );

   The first parameter, myFirstTreo180, is a user-defined unique device name. The second parameter is a network provider ID, which must match the network_provider_id carrier property. The third parameter is an IP address for UDP. The fourth parameter determines whether to activate this entry for sending push notifications. The fifth parameter specifies whether device tracking should be ignored. The final parameter contains optional remarks for this entry.

3. For each remote database, add a recipient record to the ml_listening system table for each device you added. This maps the device to the MobiLink user name. For example:

   CALL ml_set_listening( 'myULDB', 'myFirstTreo180', 'y', 'y', 'manually entered by administrator' );

   The first parameter is a MobiLink user name. The second parameter is a user-defined unique device name. The third parameter determines whether to activate this entry for device tracking addressing. The fourth parameter specifies whether device tracking should be ignored. The final parameter contains optional remarks for this entry.

   See also

   • ml_set_listening system procedure
   • ml_set_device_address system procedure
   • Device tracking gateways
   • Carrier properties