OpenEdge Development: Mobile Applications - Product ...

Getting started with OpenEdge Mobile development
3. When the Define AppServer content module page appears, the available
AppServers are displayed in a Supported servers list. Select a state-free
AppServer in the list. The installed default state-free AppServer is restbroker1.
If you want Mobile services to be updated on the Web server immediately after
changes are saved, select Publish changes immediately.
4. When the Create a Mobile service page appears, select Create a Mobile
service only if you want a default Mobile service created for the project. You still
must go back and add Mobile resources to it after you build them. Otherwise, you
can use the New Mobile Service wizard to both create the service and add Mobile
resources to it after you have built the resources. For information on building
Mobile resources, see the “Creating Mobile resources” section on page 77. For
information on using the New Mobile Service wizard, see the “Creating Mobile
services” section on page 79. If you choose to create the default service, note that
the service relative URI is the immediate parent URI for the URIs of all Mobile
resources that you add to the service. In the OE Web Servers list, select all
instances of OE Web Servers where you want the service to be published for
testing. The installed default is restmgr1.
5. When the Create a Mobile App page appears, select Create a Mobile App only
if you want a default Mobile App created with the new Mobile project. The process
for doing this is similar to creating a Mobile App using the New Mobile App dialog
after the Mobile project has been created. For more information, see the sections
on creating a Mobile App in Developer Studio in Chapter 4, “Creating Mobile Apps
using JSDOs.”
6. When the Define PROPATH page appears, you can configure the PROPATH
similar to setting the PROPATH as part of the project properties.
7. When the Select database connections page appears, you can configure and
select existing database connections or add and select new database connections
against which the Mobile project allows you to compile ABL source code and from
which the project allows you to choose to define given AppServer run
configurations.
8. When the Static Web Project page appears, the Context root allows you to
specify the default name of the Mobile Web application root, which is also the
name for the relative URI of the Web application and the parent URI of all Mobile
services that you create in the Web application; and it is also the name of the
top-level folder where the Mobile Web application is deployed on the Web server.
The Web content folder name allows you to specify the folder for OpenEdge
JavaScript files that are deployed with the Web application for a Mobile Web App.
9. At this point, choosing Finish creates the folders and all supporting files for the
specified Mobile project. If you chose to create a Mobile App and are using the
Mobile App Builder (see Step 5), the Mobile App is also created as a project in
Mobile App Builder, which automatically displays the project page in the external
browser.
OpenEdge ® Development: Mobile Applications 67