MI Web Console
| Application
Deployment | Deployment
during development | Mobile Component
Descriptor | Add-Ons
Software Logistics
Introduction
Mobile applications span over several systems: a Java part on the mobile device,
customizing or code on the WebAS and business logic in the application backend.
This situation makes software logistics of mobile applications be a great challenge.
For more information on the software logistics strategy of MI, please refer
to the following chapters:
This chapter will be considerably enhanced in upcoming editions of the MDK.
Miscellaneous
- The client-side of a mobile application is built in Java. To manage the
various files that make a mobile application (Java sources, property files,
images, XML files, JSP, HTML, style sheets, etc.) a source code management
system like CVS or Perforce should be used. Such systems manage versions of
files and hence allow for a complete change history and prevent data loss.
- To create a runnable client-side application from its source files, a build
step needs to be performed. Most commonly, ANT
is used for building of Java applications.
If MDK's plugins are used, the building of the project can be done locally
from within Eclipse. The MDK Plug-Ins ensure that the folder structure of
the project conforms to certain standards recommended by MI. If the folder
structure is adhered to, the ANT scripts contained in the plug-ins build the
project and automatically create the war file. If another folder structure
is used, the plug-ins cannot be used and you need to create your own ANT scripts.
- Transport landscape
- Upgrade strategy: The client is upgraded by de installing the old and installing
the new application. The application data is not (IS it?? ) deleted. The
application receives an event (which one?) from the framework prior to de installation.
- Delivery: a complete MI application consists of the client software, customizing
data on the Web AS (entries in tables BWAFMAPP, MEMAPPDEST, SyncBO definitions,
..) and the backend application logic (Gen.Sync: Wrapper functions + application
function modules; Smart sync: Bapi wrappers +application function modules
(possibly customizing?)