Integration Server 10.11 | Developing Data Synchronization Solutions with webMethods Mobile Support | Developing Solutions Using Mobile Support | Step 1: Write the Server-Side Business Logic | Writing the Adapter Services
 
Writing the Adapter Services
Adapter services allow you to connect to the adapter’s resource and initiate an operation on the resource from Integration Server. In a mobile data synchronization solution, adapter services specify the backend application fields that correspond to the fields specified in the business document type and the connection information that Mobile Support will use to connect to the backend application’s data store.
The adapter services that you create for a data synchronization solution depend on the type of adapter you are using and the type of flow service that will invoke the adapter services.
For this type of flow service...
Create the following...
Download flow service
*An adapter service that retrieves all of the backend data when the fetchAll parameter in the wm.mobile.datasync.specs:downloadSpec specification is set to Yes
*An adapter service that retrieves only a specific record when the fetchAll parameter in the specification is set to No
Upload flow service
*An adapter service that handles update requests received from a mobile device
*An adapter service that handles insert requests received from a mobile device
*An adapter service that handles delete requests received from a mobile device
For all adapter services written for mobile data synchronization, it is recommended to specify a result field to determine the success or failure of processing a particular record. This is particularly helpful for setting the rowStatus variable in the wm.mobile.datasync.specs:uploadSpec specification to 0 (to indicate success) or 1 (to indicate failure).
For more information about writing adapter services, see the documentation provided for the adapter you are using.