Converting the ESDMA Bundle into an Unwired Platform Package

Use the ESDMA Converter utility to convert an ESDMA bundle into an Unwired Platform package you can deploy to Unwired Server.

1. Create a META-INF directory under the <ESDMA_dir> where you downloaded and extracted the ESDMA bundle for your application.
2. In the META-INF directory, create a file named sup-db.xml.
3. Use a text editor to open sup-db.xml, and copy these lines into it:

   <package name="EXAMPLE" short-name="EXAMPLE" sup-name="EXAMPLE" version="1.0"
       java-package="com.sybase.example.db" /* For Android Application */
       cs-namespace="Sybase.Example.db" /* For Windows Mobile Application */
       oc-namespace="example_db_"> /* For iOS Application */
     <!-- Update with new host and port, listener.url must end with /doe/publish. -->
     <property name="listener.url" value="http://<Unwired_Server_host>:<listener_port>/doe/publish" />
     <database name="example-database" />
     <database-class name="ExampleDatabase" />
     <personalization-parameter name="language" type="string" owner="client" />
   
     <include file="afx-esdma.xml" />
   
   </package>
   

4. Replace the bolded values above as follows:
   • EXAMPLE – your Sybase Unwired Platform package name. This value appears three times.
   • com.sybase.example.db – the required Java namespace for BlackBerry application development.
   • Sybase.Example.db – the required C# namespace for Windows and Windows Mobile application development.
   • example_db_ – the required Objective C namespace for iOS application development.
   • http://<Unwired_Server_host>:<listener_port>/doe/publish – the Unwired Server host name and listener port.
     Note: The listener port must be followed by "/doe/publish", with no trailing "/".

     The default value for the listener port is 8000.

   • example-database – the name of the required database file.
   • ExampleDatabase – the name of the required database class.
5. (Optional) Add additional entity definitions not defined in the ESDMA.
   This is necessary to define client-side data entities that have no relationship with entities defined in the ESDMA bundle.
6. (Optional) In the <ESDMA_dir>\Resources directory, create a MetaMerge.xml file.
   This file is used by the Unwired Platform code generation and deployment tools to adapt the ESDMA bundle, if necessary to, for example:

   • Hide select data objects defined in the ESDMA.
   • Add supplementary indexes on data objects that can be used by the client.
7. Run the ESDMA converter utility to convert the ESDMA bundle resource metadata file to an Unwired Platform package.
   See esdma-converter Command in System Administration.
8. After running the ESDMA converter utility, verify that these files have been created in the META-INF directory:
   • afx-esdma.xml
   • ds-doe.xml