A Data Management Service destination is the endpoint that you send data to and receive data from when you use the Data Management Service to provide data distribution and synchronization in your applications. You configure Data Management Service destinations in the data service section of the services-config.xml file or a file which that file includes by reference. By default, the services-config.xml file is located in the WEB_INF/flex directory of the web application that contains Adobe LiveCycle Data Services ES. In the services-config.xml files that ship with LiveCycle Data Services ES, Adobe references individual configuration files for the Data Management Service, Message Service, Remoting Service, and Proxy Service. You can also dynamically configure services by using the run-time configuration feature; for more information, see Run-time configuration.

The following example shows a basic Data Management Service configuration. It contains one destination that uses the Java adapter to interact with a data resource.

<destination id="inventory">
     <adapter ref="java-dao" />
    <properties>
        <source>flex.samples.product.ProductAssembler</source>
        <scope>application</scope>
        <metadata>
            <identity property="productId"/>
        </metadata>

        <network>
            <paging enabled="false" pageSize="10" />
        </network>
    </properties>
</destination>

A Data Management Service destination references one or more channels that transport messages, and contains network- and server-related properties. It can also reference a data adapter, which is server-side code that lets the destination work with data through a particular type of interface, such as a Java object. You can also configure a specific data adapter as the default data adapter, in which case you do not have to reference it inside the destination. A destination can also reference or define security constraints for a destination.

To use the Java adapter, you write an assembler class or use the HibernateAssembler or SQLAssembler class. An assembler class is a Java class that interacts indirectly or directly with a data resource. When you use either the HibernateAssembler class or the SQLAssembler class, you typically start with the existing Assembler class, and only have to write Java code if you extend the functionality they provide. A common design pattern is for the assembler to call a data access object (DAO) that calls a data resource.