OpenEdge Development: Mobile Applications - Product ...

Chapter 3: Creating Mobile Services
Mobile URIs for testing access from REST clients
After first developing and publishing Mobile services, you might want to test the Mobile
resources they provide before you create a Mobile App to access them using JSDOs.
You can do this using various REST clients, such as the Postman REST Client, that
allow you to access Mobile operations directly as REST resources. (Remember that a
single Mobile resource encapsulates several REST resources as Mobile operations.)
In this case, you need to know the exact absolute REST URI for the Mobile resource
that represents each Mobile operation.
As described in previous sections of this chapter, when you create Mobile resources
and the Mobile services to contain them, you assign a relative URI (or use the default)
for each Mobile service and resource that you define. In addition, each operation that
you define for a Mobile resource is assigned a prescribed relative URI as part of the
resource annotations added to the ABL.
The absolute URI to access a given operation is a concatenation of all these relative
URIs with the absolute root URI of the deployed Mobile Web application, as specified
using the following syntax:
Syntax
scheme://host[:port]/web-app/rest/service-name/resource-name[op-element]
scheme//host[:port]
The beginning of every absolute URI, as described previously (see the “Mobile
URIs for Mobile App access” section on page 81).
/web-app
The relative URI for the Mobile Web application, where web-app is the name of
the Mobile Web application that contains your Mobile service or services, and
serves as the root URI for all Mobile resources provided by the Mobile Web
application. By default, this is the filename of the WAR file that you use to publish
or deploy the Mobile services to your OE Web Server, and it is also the name of
the Web server folder in which all of the Web application’s Mobile services and
Web resources are deployed. As noted during development (see the “Publishing
Mobile services for testing” section on page 80), Developer Studio publishes each
Mobile service defined for a project in its own WAR file with the filename set to
name of the Mobile service. For production deployment, you can export multiple
Mobile and REST services in a single WAR file, which by default has the name of
the Mobile project. Note that during production deployment, a Web administrator
can change the filename of the WAR file and the name of the Web application to
a different value.
Note: During development, you cannot change the name of the WAR file that
Developer Studio publishes for each Mobile service in a project.
84 OpenEdge ® Development: Mobile Applications