An Application Configuration Profile (ACP) defines resources for Mobile Application
Framework (MAF) applications. An ACP is a collection of files and folders that are packaged
as a JAR file, which you can either upload to the SAP Mobile Platform Server or
package with an application.
The typical ACP task flow is:
- Create a new ACP or import one from an external JAR file.
- Edit the configuration in the ACP project using the Mobile Application Workbench
(MAW) editors and views. You can preview your changes using the viewer.
- Add resources to the configuration, such as images, demo data, and so on.
- Validate the project, and verify that it contains no errors.
- Export the ACP project to a JAR file. You can also export subsets of a
configuration.
- Package the exported JAR file with your application, or upload it to the
SAP Mobile Platform Server for provisioning. MAF applications can
consume the configuration and modify its behavior.
Exporting an ACP project creates an ACP JAR file that contains all the ACP project files,
packaged and zipped together.
The main elements of an ACP JAR file are:
- MAF Extensibility configuration (bindings, tile containers, tile layouts) –
composed of the configuration XML files that define the application screens and
their connections to an underlying data back end. These XML files must adhere to
the conventions of the official MAF Extensibility XML Schema Definition.
- MAF Reuse Skinning configuration – found in the styles.xml
file; it describes the appearance of the application, and governs the style of
each UI element.
- Localization – composed of a set of XML files that contain translated text for
various combinations of languages and countries. This text is usually
externalized; the configuration and the application code refer to text items
using their IDs.
- Application resources – generic files that applications use, such as images,
demo data, and so on. MAF makes these files available to the application at
runtime.