Defining Business Object Model 

Purpose

In this process, the developer defines the structure of the replicated data, the properties of the mobile application, and the client view on the object model of the application. The MI server requires this metadata for the replication and software deployment.

Using the Process

This IT process is part of the following IT scenario:

IT Scenario	IT Scenario Variant
Developing, Configuring, and Adapting Applications	Developing Mobile Applications for Occasional Connection

Prerequisites

You have completed the process Defining Business Process.

Process Flow

The following process is incorporated in the DI usage type:

...

       1.      Create SyncBOs

The developer defines which fields of the business object are to be transported to the mobile device. He or she then defines further technical properties of the synchronizer business object (SyncBO), such as the default values, type checks for the fields, filter values and so on. SyncBOs are created in a special editor (SyncBO builder).

       2.      Create Mobile Component Descriptor

The Mobile Component Descriptor (MCD) describes the properties of the mobile application, such as the name, version, UI technology (JSP/AWT), the names of the SyncBOs used, and the names of the required authorization objects. The MCD is created in a special editor (MCD editor).

       3.      Generate client view on object model

The MI client requires a view on the object model. This is used to interpret the data stream and to validate types with newly created SyncBO instances. This view is provided to the application on the client-side in the form of an XML file. This is also generated in the SyncBO builder.

Result

You have defined the business object model. You now need to perform the process Developing at Client-Side.