Table mappings indicate which tables should be synchronized, how tables should be synchronized, and how the synchronized data should be mapped between the consolidated and remote databases.
Upload-only, download-only, and non-synchronized tables or columnsBy default, MobiLink does a complete, bi-directional synchronization. You can change each table to be upload-only or download-only. You can also choose to not synchronize a table, which removes its table mapping.
In a synchronization model, you can only specify tables as download-only; you cannot create download-only publications.
To change the table mapping directionIn the left pane of Sybase Central, expand MobiLink 12, your MobiLink project name, Synchronization Models, and then select your synchronization model name.
Open the Mappings tab in the right pane.
In the Table Mappings pane, select a consolidated table.
In the Mapping Direction dropdown list, select one of the following:
Not synchronized. Choosing this option is the same as deleting the table mapping.
Bi-directional
Download to Remote Only
Upload to Consolidated Only
To remove a table mappingIn the left pane of Sybase Central, expand MobiLink 12, your MobiLink project name, Synchronization Models, and then select your synchronization model name.
Open the Mappings tab in the right pane.
In the Table Mappings pane, select a table mapping.
In the Mapping Direction dropdown list, choose Not Synchronized.
Changing table and column mappingsIf your model is based on an existing remote database, the table and column mappings represent a best guess. You should check them and customize them as required.
To change table mappingsIn the left pane of Sybase Central, expand MobiLink 12, your MobiLink project name, Synchronization Models, and then select your synchronization model name.
Open the Mappings tab in the right pane.
In the Table Mappings pane, select a table mapping.
To change the remote table that is mapped, from the Remote Table context menu, select a different table from the list of unsynchronized remote tables.
You can only choose remote tables that are not already mapped to consolidated tables.
If you want to add tables to your remote schema, see Updating schemas.
To add a table mapping for an unmapped consolidated table, use File » New » Table Mappings to open the Create New Table Mappings dialog where you choose the tables. Take care to not choose any shadow tables that were created from previously deploying synchronization models (for example, with the default suffixes of "_del" or "_mod").
If you are creating a new remote schema from the consolidated schema, enable the option to also add the tables to the remote schema.
You can map a column in a synchronized consolidated table to a remote table column, a value determined when synchronizing, or exclude the column from synchronization. When mapping to a value, you can use the MobiLink user name, the remote database ID, or a SQL expression (which can include MobiLink named parameters). When you map a primary key column to a value and the table mapping is bi-directional, you need to prevent duplicate primary keys when downloading to remote databases.
To change a column mapping for a table mappingIn the Table Mappings pane, select the table mapping.
In the lower pane, open the Column Mappings tab.
Right-click the column mapping you want to change, and select one of the following from the context menu:
To synchronize the consolidated column with a remote column, select the unmapped remote column from the bottom group of the menu. Only unmapped remote columns are listed.
To exclude the consolidated column from synchronization, choose None. The Direction icon shows that the consolidated column will not be synchronized.
To map the consolidated column to a value, you can choose the MobiLink User Name, the Remote ID, or use Custom to enter a SQL expression that is evaluated when the remote table's upload_insert, upload_update and upload_delete synchronization scripts are executed during the synchronization. The Direction icon shows that the value will only be uploaded; the consolidated column will not be downloaded to the remote database.
 |
Discuss this page in DocCommentXchange.
|
Copyright © 2010, iAnywhere Solutions, Inc. - SQL Anywhere 12.0.0 |