Get access to a Mac that is running operating system 10.11.5 (El Capitan) or above.

Download and install XCode version 8.1.x, (included with this version of Xcode is iOS 10 and SDK. It is recommended that you remove any older versions of the Xcode and only have the 8.1.x version installed on your machine).

The Xcode and iOS SDK are available from Apple. Read more...

You can purchase/download Xcode and iOS SDK from the Apple App Store for Mac, or by participating in the iOS Developer Program. The download includes the Xcode IDE, Instruments, iOS Simulator, and the latest iOS SDK. You can compile and test the application with just Xcode and iOS SDK, but you must participate in the iOS Developer program if you want to deploy the application to an actual device. It is necessary when Xcode has just been installed for the first time to run it at least once, otherwise users will hit an error code 69.

Install the MAF extension by using the JDeveloper Update Center. Start JDeveloper Studio Edition (version 12.2.1.0), then select the menu item Help > Check for Updates.

Ensure the Search Update Center radio button is selected and click Next.

Click Available Updates select the check box by the Mobile Application Framework extension.

Then click Next.

Accept the license agreement by clicking I Agree.

Then, click Next and the download will start. Once the download completes, click Finish.

JDeveloper needs to restart. Click Yes to shut down and restart JDeveloper.
Might take a minute or two, be patient.

Once JDeveloper has started, you can confirm the extension was installed by examining the Extension tab in the About pane (Help > About menu options).

Next, you need to set preferences in JDeveloper to use the SDK provided by XCode 7.

Select the menu item JDeveloper > Preferences.

On the left side of the Preferences screen, click and expand the Mobile Application Framework node. If you are using the Mobile Application Framework extension for the first time, you may need to click the Load Extension button.

Next, expand the Mobile Application Framework node, and select iOS Platform.

In previous versions you needed to update the SDK and xcodebuild directory locations. This is no longer required. You only have the opportunity to update the iTunes location and should be populated by default.

This is also the place where you may specify any device signing certificates. The screen shot shows a selected profile.



Click OK to dismiss the Preferences pane.

In this part, you first create a “Hello World” MAF application, and then deploy this starter application to the iPhone simulator.

Preparing Mobile Application Framework applications for deployment is primarily comprised of creating platform-specific deployment profiles. Read more...

A deployment profile defines how an application is packaged into the archive that will be deployed to either an iOS device or emulator. The deployment profile:

- Specifies the format and contents of the archive.
- Lists the source files, deployment descriptors, and other auxiliary files that will be packaged into the archive file.
- Describes the type and name of the archive file to be created.
- Highlights dependency information, platform-specific instructions, and other information.

In the Applications Window click New Application to start the New Gallery dialog box.

In the New Gallery expand the General - Applications nodes and select Mobile Application Framework Application
Then click OK.

In the Name your application page, enter MyMobileApp in the Application Name field, and click Next.

Examine the Project Features for your first project, the ApplicationController.

Click Next twice and in the Name your project page, leave the default project name. Examine the Project Features for the ViewController project. Notice that the project uses Mobile Application Framework, HTML and CSS, Java, and JavaScript project features.

Click Next and Finish. You should see a new MAF application created in Applications window.

Right-click on the ViewController project and select New > From Gallery
In the New Gallery, select Web Tier - HTML and then the HTML Page item.
Then click OK.

Accept the default File Name and Directory, then click OK.

Using the Editor, in the body of the document, enter the following text "Deployment Successful".

Save all your work.

In the Structure Window, select the body component.
Then in the Properties Window, expand the Style node and set the Font Size to xx-large.

In this section, you configure a new feature so the user can access the newly defined AMX pages from the native application container. You will need to perform this task when ever you add pages or task flows to your application.

After you complete an Mobile Application Framework application project, JDeveloper adds both project and application level artifacts.Read more...

Among these artifacts is an MAF framework model project and the view-controller project (with the default name, ViewController) that has the MAF framework feature application resources. These resources include the configuration file for applications features, maf-feature.xml. The configuration file is a stub XML descriptor file that enables you to define feature applications that will be seen when the application runs. The maf-feature.xml defines details of each feature - for example, its icon, content type, starting point, etc.This file is configured with a default application, Hello, that you ran earlier.

The maf-application.xml file defines the details of the application itself, including reference to features. These feature applications, when packaged into a JAR file known as a Feature Archive file (FAR), provide the reusable content that can be consumed by other MAF applications. One reason for this distinction is to allow developers to create feature archives (which may contain one or more features referenced in the maf-feature.xml), and then create applications by simply pulling in feature archives.  Of course each app would only have one maf-application.xml.

A FAR is essentially a self-contained collection of everything that a feature requires, such as icon images, resource bundles, HTML, JavaScript, or other implementation-specific files. The FAR includes a single maf-feature.xml file, which identifies each of the packaged feature applications by a unique ID. You can edit this file to update feature properties. For example, you can specify the content implementation (local or remote HTML files, AMX pages, or a native application written in platform-specific language). You can also control the display of content based on such factors as user roles and privileges, or device properties. A mobile application can reference one FAR, several of them, or none at all.

In the Application Navigator, expand the ViewController project. Locate and expand the Application Sources folder. Then expand the META-INF folder. You will see the maf-feature.xml file as shown.

Double click on the maf-feature.xml file to open the Feature editor.

Add a new feature by clicking the green plus sign on the Features table near top of the editor. If you cannot see the plus sign, scroll the Feature editor to the right (the plus sign is on the far right side of the Feature editor).

In the Create MAF Feature dialog, modify the following values:

- Feature Name: Success
- Feature ID: oracle.success
- Confirm the Add a corresponding feature reference to maf-application.xml check box is selected, and then click OK.

In the Features table, select the newly created feature oracle.success. Under the Features table, click the Content tab, and locate the Content table. Notice that the content item oracle.success.1 is created by default.

Confirm the Id field of the content item is set to oracle.success.1.

In the Content area, ensure the Type property is set to Local HTML .

In the Content section, find the URL text box.

On the right side of the URL text box, click the magnifying glass icon.

In the Open window, select the html page you created earlier. In this case, untitled1.html. Then click Open.

The resulting definition should look like the image below.

Save all your work.

In the Application menu, select Deploy - New Deployment Profile to start the Create Deployment Profile dialog box.

There are three other predefined deployment profiles you can use. One for an default iOS deployment, another for a default Android deployment. The third type is used to create a mobile application archive. This archive includes everything, files, icons, reference links but not any signing certificates. It would be used if you wanted to transport an application and install and deploy it using different credentials.

For our purposes, lets examine what we get when we go through the whole process.

In the Profile Type drop-down list, ensure MAF for iOS is selected and then click OK. Leave the Profile Name at the default value.

In the MAF for iOS Deployment Profile Properties dialog box, examine the deployment options.

Select the iOS Options node and confirm the Simulator Target Version is set to 7.0.

Then, select the target simulator you wish to use. This must be done in all deployment profiles to determine which simulator to run when the application is deployed. At runtime, you can still switch to view the application in a different device simulator.

This tutorial uses the iPhone 5 simulator, but feel free to select any simulator you like.



Click OK, and then save all your work.

Before deploying the application, confirm the iOS Simulator is working correctly.

Run the Simulator by launching Xcode and selecting Xcode > Open Developer Tool > iOS Simulator.
Once it has started, you can leave it alone.




If at anytime you need to return to the simulator's home page, select Hardware > Home.

In the Application menu, select Deploy > iOS2 deployment profile.



In the subsequent dialog box, select Deploy application to simulator, and click Finish.

There are two approaches to testing an MAF application: Read more...

1. Testing on a mobile device: This method always provides the most accurate behavior, and is also necessary to gauge the performance of your application. However, you may not have access to all the devices on which you wish to test, making device testing impractical.

2. Testing on a mobile device emulator or simulator: This method usually offers better performance and faster deployment, as well as convenience. However, even though a device emulator or simulator closely approximates the corresponding physical device, there might be differences in behavior and limitations on the capabilities that can be emulated.

Typically, a combination of both approaches yields the best results.

In the Deployment Log the Cordova plugman will be installed to support the Cordova plugins. If the Log window is not viewable, select Window > Log from the JDeveloper menu.

Watch the Deployment Log window for any errors. If the compilation and deployment process completes as expected, you should see the Deployment Log window as shown below.

The next step in the process is to start the iOS Simulator.

After the simulator is started, you'll be taken right into the application .A popup notification will appear asking if you would like send notifications. Click OK.

The MyMobileApp application currently contains your HTML page running inside the MAF application. Because there is only one feature in the application currently, you'll only see one option at the bottom of the page.
.

To clear out the application from the simulator, select iOS Simulator - Reset Content and Settings... from the menu. Then click Reset to confirm.



To clear the settings, click OK in this pane.

Shut down the iPhone simulator by clicking the iOS Simulator menu item (on the top of the Mac desktop), and selecting Quit iOS Simulator.