Introduction to Oracle E-Business Suite Mobile Apps Release 9.x and Earlier

Overview

Mobile access to enterprise applications is fast becoming a standard part of corporate life. Such applications increase organizational efficiency because mobile devices are more readily at hand than their desktop counterparts.

There are a number of scenarios where the standard functionality delivered by Oracle E-Business Suite may not be sufficient for the standard desktop worker. In recent years, the business requirements have expanded beyond connecting from a single location through a single device. Meeting this need effectively requires specific mobile capabilities.

This document provides recommendations and guidance for creating mobile apps that are designed to integrate and work optimally with Oracle E-Business Suite Releases 12.1.3 and 12.2. The objective is to describe the different types of application, outline the certified technologies that can be used, list the recommended interfaces, and outline the security options that are available.

From the integration perspective, the Oracle E-Business Suite web service infrastructure does not depend on a specific client type. This means that service implementation can work seamlessly, regardless of the platform being used for the client applications (native, hybrid or web applications).

Oracle E-Business Suite recommends using Oracle Mobile Application Framework (MAF) to build smartphone apps. Oracle MAF is a hybrid mobile architecture, one that uses HTML5 and CSS to render the user interface, Java for the application business logic, and Apache Cordova to access device features, such as e-mail, contacts, camera, geolocation, and so on. Because Oracle MAF uses these cross-platform technologies, you can build an app that runs on both Android and iOS devices without having to use any platform-specific tools. After deploying a MAF application to a device, the application behaves similarly to applications that are created using platform-specific tools, such as Objective C or Android SDK. Furthermore, Oracle MAF enables you to build the same application for smartphones or for tablets, thereby letting you reuse the business logic in the same application and target various types of devices, screen sizes, and capabilities. A MAF application installs on a user's device like any other application on the device.

Oracle E-Business Suite Mobile Apps Developed Using Oracle Mobile Application Framework

the picture is described in the document text

For more information on the benefits of using Oracle MAF, refer to the Oracle Mobile Application Framework page available at https://www.oracle.com/application-development/technologies/maf/oraclemaf.html.

Technology Infrastructure

Oracle E-Business Suite mobile apps architecture consists of three technology layers: presentation, business logic, and data.

Oracle E-Business Suite Mobile Apps Technology Layers

the picture is described in the document text

Presentation Layer

Oracle MAF lets you develop mobile apps using technologies such as HTML5, JavaScript, CSS, and Java, then deploy them to mobile device platforms, such as iOS and Android. Oracle MAF supports integration with native devices and also supports offline application interaction.

Business Logic Layer

Going by industry best practice, the core business logic that determines the functionality and behavior of an application should be reusable regardless of the presentation layer platform. Within Oracle E-Business Suite, the business logic resides in PL/SQL and Java-based Application Module Services.

Note: Application Module Implementation class is a Java class that provides access to business logic governing the OA Framework-based components and pages. Such Java classes are called Application Module Services and are categorized as a subtype of Java interface.

The Oracle MAF-based client apps can interact with server-side logic through REST services. Oracle E-Business Suite REST services provided through Oracle E-Business Suite Integrated SOA Gateway (ISG) are available for Oracle E-Business Suite mobile apps. Oracle E-Business Suite public interfaces written in PL/SQL or Java-based Application Module Services can be deployed as REST services.

Please note that REST services are deployed in Oracle E-Business Suite's application server, and this type of web services does not depend on Oracle Fusion Middleware components like Oracle SOA Suite.

REST services are available in Oracle E-Business Suite Release 12.1.3 and Release 12.2.

Data Layer

All Oracle E-Business Suite transaction data resides in the Oracle database on which Oracle E-Business Suite is installed. An application's business logic either runs on the application tier Java-based interfaces or PL/SQL code that reads from the database tables. Oracle E-Business Suite data is retrieved by the business logic layer, based on an application-specific security context.

For more information on the integration options for Oracle E-Business Suite, refer to Oracle E-Business Suite Release 12.1.3: Integration Products and Technologies Primer, My Oracle Support Knowledge Document 1494997.1.

Oracle Mobile Application Framework Runtime Architecture

Oracle MAF is based on a hybrid mobile architecture and an extension of Apache Cordova (see http://cordova.apache.org). It enables a combination of HTML5 and ADF-defined pages and task flows to be rendered in the same downloadable application.

Oracle MAF consists of the following parts:

Note: Oracle MAF's model-view-controller (MVC) stack resides on a mobile device and represents a reimplementation of ADF's model-view-controller layers. UI metadata is rendered to native components on the device, and bound to the model through the ADF model.

Oracle Mobile Application Framework Runtime Architecture

the picture is described in the document text

For more information about Oracle MAF, refer to Developing Mobile Applications with Oracle Mobile Application Framework.

User Experience

Mobile design patterns should be used when designing smartphone and other small format apps for platforms such as iPhone and Android. Design patterns are common flow or page designs that are intended for use across different product families. These patterns are built using industry best practices to meet common requirements, and extensively tested for usability. A complete set of mobile design patterns has been defined by user experience, and can be re-created with the mobile components and technology delivered by ADF and Oracle JDeveloper.

Mobile design patterns can be used across mobile platforms and fully support designs for apps running in a mobile browser. Platform-specific designs and style sheets are not yet available. The finalized Fusion Mobile look and feel is not represented in the current design patterns, and will be provided when available.

For more information on User Experience, consult the Mobile Patterns page at https://www.oracle.com/webfolder/ux/mobile/patterns.html.

Accessibility

Accessibility involves making your app usable for people with disabilities such as low vision/blindness, deafness, or other physical limitations. This means creating apps that can be used without a mouse (keyboard only), used with a screen reader, and generally used without reliance on sound, color, or animation and timing.

Hybrid and native mobile apps must meet the Web Content Accessibility Guidelines (WCAG) 2.0 (http://www.w3.org/TR/WCAG20/) and Section 508 (http://www.section508.gov/section-508-standards-guide) standards. Oracle MAF provides accessibility guidelines for components, page, and navigation structures. Although useful, these are not a substitute for familiarity with accessibility standards and performing accessibility testing with assistive technology. Apple and Android provide detailed information on their accessibility support, including information on testing and making your app accessible.

For more information, consult the following documents: