OpenEdge Development: Mobile Applications - Product ...

Chapter 1: OpenEdge Mobile Overview
Client access to the AppServer using Mobile services
Figure 2 provides an overview of how an OpenEdge JSDO accesses a Mobile
resource, which works the same for a given JSDO regardless of the type of Mobile App.
Figure 2: Accessing OpenEdge Mobile services and resources
Each JSDO created by a Mobile App can access a single Mobile resource, which can
be any of the Mobile resources provided by a particular Mobile service of the Mobile
Web application. A single Mobile Web application can support one or more Mobile
services, and an Apache Tomcat Web server can host multiple Mobile Web
applications.
In Figure 2, the Mobile Web application contains two Mobile services, Inventory and
OrderEntry. The OrderEntry service contains two Mobile resources, Orders and
Customers, which are implemented by the ABL class files Orders.cls and
Customer.cls, respectively, and are accessed, respectively, by the Orders and
Customers JSDOs on the client.
Note: The breakdown of resources in the OrderEntry service is for illustration only.
It implies that the two resources provide a single temp-table each, one with
Order records and one with Customer records. In practice, these temp-tables
might be related using a ProDataSet that is provided by a single Mobile
resource accessed by a single JSDO.
Note that an OpenEdge Mobile Web application installs and runs in an Apache Tomcat
Java container similar to an OpenEdge REST Web application, and can be managed
using the same OpenEdge-supported tools. Likewise, an OpenEdge Mobile service is
very similar to an OpenEdge REST Web service. The difference between them is in
how a Mobile service makes resources available to a Mobile App.
36 OpenEdge ® Development: Mobile Applications