Oracle Mobile Application Framework Foundation

Oracle Mobile Application Framework Foundation ("MAF Foundation") is included as a restricted use component. The following tables describe the applicable MAF Foundation usage rights and restrictions. Table 1 below lists the MAF Foundation capabilities that may be used and what, if any, restrictions apply. Table 2 lists the MAF Foundation capabilities that may be not used. Any use of the capabilities described in Table 2 requires an appropriate quantity of full use licenses for (a) Oracle Mobile Application Framework, or (b) Oracle Mobile Suite and Oracle Mobile Suite Client Runtime.

MAF Foundation is the version of Oracle Mobile Application Framework that is restricted for use as described in this document. When MAF Foundation is included as a component within another Oracle product (the "Primary Product") then, depending on the particular Primary Product, MAF Foundation may be included in the Primary Product, may be separately downloaded from Oracle Software Delivery Cloud, or may be downloaded as an extension to Oracle JDeveloper. JDeveloper is a prerequisite to using MAF Foundation and must be downloaded from Oracle Technology Network ("OTN"); see http://www.oracle.com/technetwork/developer-tools/jdev/downloads/index.html. Notwithstanding any other terms, use of JDeveloper is subject to the OTN license agreement associated with JDeveloper; view the license agreement at http://www.oracle.com/technetwork/licenses/jdev-license-152012.html.

Definitions

"Application Archive" refers to the MAF Foundation mobile application archive, which is an Oracle proprietary mobile application deployment format that can only be used with Oracle supported development tools. It is not related to or based on any non-Oracle application archive format, including iOS application archives.

"Application Executable" refers to a mobile application executable installation file, such as an apk or ipa file.

"Application Workspace" refers to a series of files making up the source code of a mobile application developed using MAF Foundation.

"Data Control" refers to MAF Foundation mobile application artifacts that provides standard metadata interfaces to business services (such as web services) accessed by the mobile application.

"Feature" refers to specific MAF Foundation mobile application artifacts that are the building blocks of a mobile application, where each Feature integrated into the mobile application performs a specific set of tasks.

Table 1

Capabilities that may be used when MAF Foundation is included as a component within another Oracle product.

Capability	Description
Sign and deploy Application Archive or Application Workspace into an Application Executable	Sign the mobile application with the appropriate certificates, and deploy the Application Archive or Workspace into an Application Executable.
Make modifications to an Application Archive as specified, except as listed in Table 2 below	The following modifications to Application Archives are allowed. For details of how to work with MAF Foundation Application Archives, consult the Oracle® Mobile Application Framework Developing Mobile Applications with Oracle Mobile Application Framework Guide. Deploy a browser-based Oracle mobile application into MAF Foundation to run as Remote URL Feature(s) Access device-native services such as the notification framework or camera Change branding details such as mobile application/navigation bar icons and skins Modify business logic components and the user interface of the mobile application to align with your implemented business processes and customizations in the associated Oracle non-mobile application(s)
Distribute Application Executable generated from Application Archive or Application Workspace	Distribute the Application Executable generated from an Application Archive to the extent permitted by, and in full compliance with, (a) the Oracle license terms associated with the Primary Product, and (b) any applicable third-party distribution terms and conditions required either by the mobile operating system provider or the application distribution platform provider (such as Apple Inc., Google, Inc.).
Manage the mobile application using mobile application management (MAM) solutions	Use MAM solutions with mobile applications generated from an Application Archive; for example, wrapping the mobile application binaries with the containers provided by the MAM solution.

Table 2

Capabilities that may not be used when MAF Foundation is included as a component within another Oracle product.

Capability	Description
Add a new Mobile Application Framework Feature	Add a new MAF Feature such as AMX or Local HTML-based Features, except when embedding a web-based Oracle Application as a Remote URL Feature (as addressed in Table 1 above).
Add a Remote URL Feature to Applications outside of App License Agreement	Add a Remote URL Feature pointing to any application or features that are not part of the Primary Product. For example, for an Application Archive shipped as part of the Oracle PeopleSoft application, add a Remote URL Feature pointing to Oracle Siebel CRM application or to third party applications.
Add a new MAF Data Control	Add a new Data Control to the MAF-based mobile Application Archive or Application Workspace. For example, a Web Service Data Control that exposes backend data services or a Bean Data Control that exposes custom Java code to the application's user interface.