OpenEdge Development: Mobile Applications - Product ...

est
URIs for accessing Mobile Web applications, services, and resources
This is a literal relative URI that identifies the root for all OpenEdge REST
resources provided by a Mobile Web application.
Note: Unlike the /static relative URI that identifies the physical location of most
static Web resources, such as Web pages, this URI does not represent a
physical folder on the Web server, but simply identifies a dynamic point in
a URI where the relative URI to a given REST resource begins.
/service-name
The relative URI for the Mobile service, where service-name defaults to the name
you assign the service when you define it in Developer Studio. You can also
assign a different name for the URI at the time the Mobile service is defined. For
more information, see the “Creating Mobile services” section on page 79.
/resource-name
The relative URI for the Mobile resource, where resource-name defaults to the
name you assign the resource when you define it in Developer Studio. You can
also assign a different name for the URI at the time the Mobile resource is defined.
For more information, see the “Creating Mobile resources” section on page 77.
op-element
A relative URI or a URI query parameter that is specified to identify only certain
Mobile operations, as follows:
• ?filter=filter-string — For the read operation, identifies the INPUT
filter parameter value passed to the implementing ABL routine, where
filter-string is the string value you type, quoted if necessary.
• /routine-name — For an invoke operation, where routine-name is the
case-sensitive name of the ABL routine that implements the specified invoke
operation
Note that all other INPUT (and the input side of INPUT-OUTPUT) parameters passed
to the implementing ABL routines for Mobile operations are passed in the body of
the HTTP request. For more information, see the following section on using Mobile
URIs in a REST client.
OpenEdge ® Development: Mobile Applications 85