Tuesday Feb 19, 2013

Tablet Layouts

There are some popular patterns for tablets that many developers are looking to implement.  First we'll describe a few of these and show you how to achieve them.

Flowing Layouts

Flowing layouts are the easiest to achieve.  You can simply add enough content so that i won't fit onto the page and the panelPage will automatically make the content scrollable so you can view it all.  Typically you would achieve this by using a tableLayout with many rowLayout components. 

Stretch Layouts

Sometimes it is desired to just separate your layout into multiple areas that are proportional to the width of the display and size dynamically based on orientation.  Many times you don't want these areas to flow but rather to resize to the size of the application size.  Let's take an example where you want to device the screen into two vertical areas, each 50% width but 100% of the height of the page.  You can achieve it like this:

<amx:tableLayout id="tl1" width="100%" shortDesc="Detail Table">
   <amx:rowLayout id="rl2">
      <amx:cellFormat id="cf2" height="#{deviceScope.hardware.screen.availableHeight-44}" 
               inlineStyle="background-color:yellow" valign="top" width="50%"  
               shortDesc="Column1 Cell">
         <amx:outputText value="Column 1 content goes here" id="ot6" 
               inline/>
      </amx:cellFormat>
      <amx:cellFormat id="cf3" inlineStyle="background-color:Aqua;" valign="top" 
               width="50%" shortDesc="Column2 Cell">
         <amx:outputText value="Column 2 content goes here" id="ot7" 
               inline/>
      </amx:cellFormat>
   </amx:rowLayout>
</amx:tableLayout> 

Note that the height attribute uses the availableHeight attribute of the deviceScope and the 44px is the height of the header (in a future release we may have some kind of constant so you don't need to hardcode this).  The availableHeight will change dynamically if the orientation changes.  The width of each cell can be set with percentages.  It is not possible to set the height using percentages with the tableLayout.  

Swim Lanes

This type of layout allows row of data to scroll horizontally independently of each other.  The lanes themselves can also be moved up and down so many different lanes can appear.  Below is an example.  You could replace the multiple hardcoded panelGroupLayout's with an iterator component to stamp out components based on a data collection. 

 <amx:tableLayout id="tl1" width="100%" shortDesc="Detail Table" cellPadding="0" 
      cellSpacing="0">
    <amx:rowLayout id="rlh1">
        <amx:cellFormat id="cfh1" valign="middle" height="30" 
                inlineStyle="background-color:blue" width="100%" 
                shortDesc="Content1 Header Cell" header="true">
            <amx:outputText value="Content1 Header" id="oth1"/>
        </amx:cellFormat>
    </amx:rowLayout>
    <amx:rowLayout id="rlc1">
        <amx:cellFormat id="cfc1" inlineStyle="background-color:yellow" width="100%" 
            shortDesc="Content1 Cell">
            <amx:panelGroupLayout id="panelGroupLayout5" inlineStyle="width:100%" 
                layout="horizontal">
                <amx:panelGroupLayout id="pgl11" styleClass="adfmf-panelGroupLayout-groupBox"
                                      inlineStyle="width:100px;height:100px">
                    <amx:outputText value="Lane1 Item1" id="otr11"/>
                </amx:panelGroupLayout>
                <amx:panelGroupLayout id="pgl12" styleClass="adfmf-panelGroupLayout-groupBox"
                                      inlineStyle="width:100px;height:100px">
                    <amx:outputText value="Lane1 Item2" id="otr12"/>
                </amx:panelGroupLayout>
                <amx:panelGroupLayout id="pgl13" styleClass="adfmf-panelGroupLayout-groupBox"
                                      inlineStyle="width:100px;height:100px">
                    <amx:outputText value="Lane1 Item3" id="otr13"/>
                </amx:panelGroupLayout>
                <amx:panelGroupLayout id="pgl14" styleClass="adfmf-panelGroupLayout-groupBox"
                                      inlineStyle="width:100px;height:100px">
                    <amx:outputText value="Lane1 Item4" id="otr14"/>
                </amx:panelGroupLayout>
                <amx:panelGroupLayout id="pgl15" styleClass="adfmf-panelGroupLayout-groupBox"
                                      inlineStyle="width:100px;height:100px">
                    <amx:outputText value="Lane1 Item5" id="otr15"/>
                </amx:panelGroupLayout>
                <amx:panelGroupLayout id="pgl16" styleClass="adfmf-panelGroupLayout-groupBox"
                                      inlineStyle="width:100px;height:100px">
                    <amx:outputText value="Lane1 Item6" id="otr16"/>
                </amx:panelGroupLayout>
                <amx:panelGroupLayout id="pgl17" styleClass="adfmf-panelGroupLayout-groupBox"
                                      inlineStyle="width:100px;height:100px">
                    <amx:outputText value="Lane1 Item7" id="otr17"/>
                </amx:panelGroupLayout>
                <amx:panelGroupLayout id="pgl18" styleClass="adfmf-panelGroupLayout-groupBox"
                                      inlineStyle="width:100px;height:100px">
                    <amx:outputText value="Lane1 Item8" id="otr18"/>
                </amx:panelGroupLayout>
                <amx:panelGroupLayout id="pgl19" styleClass="adfmf-panelGroupLayout-groupBox"
                                      inlineStyle="width:100px;height:100px">
                    <amx:outputText value="Lane1 Item9" id="otr19"/>
                </amx:panelGroupLayout>
                <amx:panelGroupLayout id="pgl110" styleClass="adfmf-panelGroupLayout-groupBox"
                                      inlineStyle="width:100px;height:100px">
                    <amx:outputText value="Lane1 Item10" id="otr110"/>
                </amx:panelGroupLayout>
            </amx:panelGroupLayout>
        </amx:cellFormat>
    </amx:rowLayout>
 </amx:tableLayout> 

Tiled Layouts

A popular layout is to have a horizontal layout of "tiled" objects that will move horizontally across the page until no more will fit and then wrap to the next line and continue until all are completed.  The entire page may scroll to enable the user to see all tiled objects.  Note that currently you need to apply the "display:inline-block" CSS attribute added to the child components that you want to wrap.  In a later release, this may be done automatically for you but until then you'll need to add this yourself.   This can be achieved by the following:

<amx:tableLayout id="tl1" width="100%" shortDesc="Detail Table">
    <amx:rowLayout id="rl1">
          <amx:cellFormat id="cfh2" valign="middle" height="30" inlineStyle="background-color:blue" 
                      width="100%" shortDesc="Content Header Cell" header="true">
              <amx:outputText value="Content Header" id="ot3" inline/>
        </amx:cellFormat>
    </amx:rowLayout>
    <amx:rowLayout id="rl2">
          <amx:cellFormat id="cf2" height="#{deviceScope.hardware.screen.availableHeight-44-30}"
                      inlineStyle="background-color:yellow" valign="top" width="50%" 
                      shortDesc="Column1 Cell">
              <amx:panelGroupLayout id="pgl1"
                      inlineStyle="height:100%">
                  <amx:panelGroupLayout id="pglw" layout="wrap">
                    <amx:panelGroupLayout id="pgl11" styleClass="adfmf-panelGroupLayout-groupBox"
                                            inlineStyle="width:100px;height:100px;display:inline-block">
                        <amx:outputText value="Lane1 Item1" id="otr11"/>
                      </amx:panelGroupLayout>
                    <amx:panelGroupLayout id="pgl12" styleClass="adfmf-panelGroupLayout-groupBox"
                                            inlineStyle="width:100px;height:100px;display:inline-block">
                        <amx:outputText value="Lane1 Item2" id="otr12"/>
                    </amx:panelGroupLayout>
                    <amx:panelGroupLayout id="pgl13" styleClass="adfmf-panelGroupLayout-groupBox"
                                            inlineStyle="width:100px;height:100px;display:inline-block">
                        <amx:outputText value="Lane1 Item3" id="otr13"/>
                    </amx:panelGroupLayout>
                    <amx:panelGroupLayout id="pgl14" styleClass="adfmf-panelGroupLayout-groupBox"
                                            inlineStyle="width:100px;height:100px;display:inline-block">
                        <amx:outputText value="Lane1 Item4" id="otr14"/>
                    </amx:panelGroupLayout>
                    <amx:panelGroupLayout id="pgl15" styleClass="adfmf-panelGroupLayout-groupBox"
                                            inlineStyle="width:100px;height:100px;display:inline-block">
                        <amx:outputText value="Lane1 Item5" id="otr15"/>
                    </amx:panelGroupLayout>
                    <amx:panelGroupLayout id="pgl16" styleClass="adfmf-panelGroupLayout-groupBox"
                                            inlineStyle="width:100px;height:100px;display:inline-block">
                        <amx:outputText value="Lane1 Item6" id="otr16"/>
                    </amx:panelGroupLayout>
                    <amx:panelGroupLayout id="pgl17" styleClass="adfmf-panelGroupLayout-groupBox"  
                                          inlineStyle="width:100px;height:100px;display:inline-block">
                        <amx:outputText value="Lane1 Item7" id="otr17"/>
                    </amx:panelGroupLayout>
                    <amx:panelGroupLayout id="pgl18" styleClass="adfmf-panelGroupLayout-groupBox" 
                                          inlineStyle="width:100px;height:100px;display:inline-block">
                        <amx:outputText value="Lane1 Item8" id="otr18"/> 
                    </amx:panelGroupLayout>
                    <amx:panelGroupLayout id="pgl19" styleClass="adfmf-panelGroupLayout-groupBox" 
                                          inlineStyle="width:100px;height:100px;display:inline-block">
                        <amx:outputText value="Lane1 Item9" id="otr19"/> 
                    </amx:panelGroupLayout>
                    <amx:panelGroupLayout id="pgl110" styleClass="adfmf-panelGroupLayout-groupBox" 
                                            inlineStyle="width:100px;height:100px;display:inline-block">
                      <amx:outputText value="Lane1 Item10" id="otr110"/> 
                    </amx:panelGroupLayout>
                    <amx:panelGroupLayout id="pgl111" styleClass="adfmf-panelGroupLayout-groupBox" 
                                            inlineStyle="width:100px;height:100px;display:inline-block">
                      <amx:outputText value="Lane1 Item11" id="otr111"/>
                    </amx:panelGroupLayout> 
                  </amx:panelGroupLayout>
            </amx:panelGroupLayout> 
          </amx:cellFormat>
    </amx:rowLayout> 
  </amx:tableLayout>

Using panelSplitter

The panelSplitter component is the most common method to achieve some simple layouts for tablets.  This provides a "navigation" facet that would typically contain a list or some kind of flowing component.  You can have multiple panelItems within the panelSplitter.  When the panelSplitter is displayed in portrait mode, the navigation facet is automatically collapsed into a popup to provide more space for the panelItems.  When in landscape mode, the navigator will appear normally.  The "position" attribute is used to define the size of the navigator facet, in either pixels or percentage.  Any of the above layout formats can be used within the panelItem so you can create a variety of master-detail layouts.  Here's an example using the stretch example above.

<amx:panelSplitter id="ps1">
    <amx:facet name="navigator">
        <amx:listView var="row" id="lv1">
            <amx:listItem id="li1" shortDesc="List Item 1">
                <amx:outputText value="Item 1" id="otli1"/>
                <amx:setPropertyListener from="Item1" to="#{pageFlowScope.item}"/>
            </amx:listItem>
            <amx:listItem id="li2" shortDesc="List Item 2">
                <amx:outputText value="Item 2" id="otli2"/>
                <amx:setPropertyListener from="Item2" to="#{pageFlowScope.item}"/>
            </amx:listItem>
            <amx:listItem id="li3" shortDesc="List Item 3">
                <amx:outputText value="Item 3" id="otli3"/>
                <amx:setPropertyListener from="Item3" to="#{pageFlowScope.item}"/>
            </amx:listItem>
            <amx:listItem id="li4" shortDesc="List Item 4">
                <amx:outputText value="Item 4" id="otli4"/>
                <amx:setPropertyListener from="Item4" to="#{pageFlowScope.item}"/>
            </amx:listItem>
            <amx:listItem id="li5" shortDesc="List Item 5">
                <amx:outputText value="Item 5" id="otli5"/>
                <amx:setPropertyListener from="Item5" to="#{pageFlowScope.item}"/>
            </amx:listItem>
            <amx:listItem id="li6" shortDesc="List Item 6">
                <amx:outputText value="Item 6" id="otli6"/>
                <amx:setPropertyListener from="Item6" to="#{pageFlowScope.item}"/>
            </amx:listItem>
            <amx:listItem id="li7" shortDesc="List Item 7">
                <amx:outputText value="Item 7" id="otli7"/>
                <amx:setPropertyListener from="Item7" to="#{pageFlowScope.item}"/>
            </amx:listItem>
            <amx:listItem id="li8" shortDesc="List Item 8">
                <amx:outputText value="Item 8" id="otli8"/>
                <amx:setPropertyListener from="Item8" to="#{pageFlowScope.item}"/>
            </amx:listItem>
            <amx:listItem id="li9" shortDesc="List Item 9">
                <amx:outputText value="Item 9" id="otli9"/>
                <amx:setPropertyListener from="Item9" to="#{pageFlowScope.item}"/>
            </amx:listItem>
            <amx:listItem id="li10" shortDesc="List Item 10">
                <amx:outputText value="Item 10" id="otli10"/>
                <amx:setPropertyListener from="Item10" to="#{pageFlowScope.item}"/>
            </amx:listItem>
        </amx:listView>
    </amx:facet>
    <amx:panelItem id="pi1">
        <amx:tableLayout id="tl1" width="100%" shortDesc="Detail Table">
            <amx:rowLayout id="rl1">
                <amx:cellFormat id="cfh2" valign="middle" height="30" inlineStyle="background-color:blue"
                                width="100%" columnSpan="2" shortDesc="Content Header Cell" header="true">
                    <amx:outputText value="Content Header" id="ot3" inlineStyle="color:White;"/>
                </amx:cellFormat>
            </amx:rowLayout>
            <amx:rowLayout id="rl2">
                <amx:cellFormat id="cf2" height="#{deviceScope.hardware.screen.availableHeight-44-30}"
                                inlineStyle="background-color:yellow" valign="top" width="50%"
                                shortDesc="Column1 Cell">
                    <amx:outputText value="Column 1 : #{pageFlowScope.item} content goes here" id="ot6"
                                    inlineStyle="color:Black;"/>
                </amx:cellFormat>
                <amx:cellFormat id="cf3" inlineStyle="background-color:Aqua;" valign="top" width="50%"
                                shortDesc="Column2 Cell">
                    <amx:outputText value="Column 2 : #{pageFlowScope.item} content goes here" id="ot7"
                                    inlineStyle="color:Black;"/>
                </amx:cellFormat>
            </amx:rowLayout>
        </amx:tableLayout>
    </amx:panelItem>
</amx:panelSplitter>


Friday Jan 11, 2013

Using Hi DPI Images in your Mobile App

Getting Started with ADF Mobile Sample Apps

Whether you are developing an ADF Mobile application or a classic ADF Server application, it is becoming more and more important to support hi-DPI screens (high resolution or "retina" displays). There is no easier way to make your application look out-dated than to use grainy, unprofessional image assets or use them improperly.

In HTML, the "px" unit corresponds to the same amount of space regardless of the DPI of your device (however, the number of device pixels may vary). The original iPhone models did not have hi-DPI displays. Each point of color on those screens corresponds to one HTML CSS "px" unit. Newer iPhone models introduced a hi-DPI (or "retina") display that has 4 device pixels in the same amount of space that 1 device pixel used to take up (2 device pixels wide by 2 device pixels tall); on these new devices, the width and height "px" values use twice the amount of device pixels.

Why is this a common problem? Since ADF Mobile uses HTML, displaying an image is not as simple as just specifying the source path and magically hoping the browser will know that you are using a high resolution image. You must specify dimensions to go along with the source path.

Let's work with an example. You have an image named "image-64.png". This image has a size of 64 by 64 individual dots of color (individual points of color information). If you coded your page like the following, the image will be shown with a width of 64px and a height of 64px (one color dot per "px"):

   <amx:image id="i1" source="images/image-64.png"/>

This would look just fine on a classic low-DPI display. However, on a hi-DPI display, it still takes up the same space but since there are more device pixels, the image will look very grainy.

In order to look crisp and professional, you need to set a size so that each dot of color corresponds to at least one device pixel. For a hi-DPI display, this means your image needs a width and a height specified such that you use 2 dots of image color information per HTML CSS "px" unit (e.g. a 64 by 64 sized image should be specified to use a width of 32px and a height of 32px. In code, your page should look like this:

   <amx:image id="i1" inlineStyle="width:32px;height:32px" source="images/image-64.png"/>

Even if you still want to support legacy devices for your application, this same image (with the same specified width and height) will look beautiful on low-DPI screens because of how images are processed modern browsers.

If for some reason you really needed or wanted to specify alternate images for each kind of device, you have the option to use a device properties EL variable to toggle the rendered state of alternate amx:image components or simply use that EL to alter the inlineStyle and the source path as desired.

Thursday Jan 10, 2013

ADF Mobile REST JSON/XML example

This article discusses and demonstrates the use of REST web services in your ADF Mobile applications.  

First you should download the RESTDemo example application and install it and run it and take a look.  The general usage of the app is that it takes a domain or IP address and returns you the geo-location of it.  The app provides this in a form and then you can view it on a map as well.  This demo uses a public web service provided by FreeGeoIP and it's author, Alexandre Fiori.  NOTE:  This service has a throttling mechanism of 1000 queries an hour so if you get a 403, you should wait until the next hour before you test again.

REST XML

There are two flavors of REST supported by ADF Mobile.  The first we'll talk about is REST XML.  The nice thing about REST XML is that it's structure is defined by an XSD and thus the design-time knows that the format should be and can provide you with a shape for the data when building your app.  You use the URL Data Control wizard from the new gallery to define a Data Control backed by a REST XML service.  You need to supply an XSD that defines what the structure will be.  Note: if you have a service that returns XML but you don't have an XSD, there are many free utilities that will generate the XSD for you.  When specifying the endpoint, you should typically keep this to the minimum needed for all methods of your web service.  You then specify the HTTP method for the method of your service you want to invoke.  Note that if you have a single service that supports multiple methods, you should be selecting the same endpoint and just keep adding methods to it, DO NOT generate separate Data Controls for each method.  Any extra info you need for specific methods, including parameters should be put into the Source field. 

Once your DC is created, it can be used just like any other Data Control.  You can optionally decide to invoke these Data Control methods from Java and follow the techniques outlines in the Web Service example #2 in this blog if you wish.

The REST XML Data Control for the Geo IP is used directly in the REST-XML feature and shows you how to declaratively use the DC without a bean.  

REST JSON

Because of the loosely structured nature of REST JSON services, there is no declarative model available for most because they do not provide a consistent way to describe the shape of the data model.  The way to use REST JSON services with ADF Mobile is to execute these services with our helper classes and then use the supplied JSON parsing classes to create beans from the data and bind your UI to those beans. 

In the second feature, REST-JSON, we have a managed bean created called RESTJSONBean.  This bean maintains the parameter that we send to the service method along with the JSON response that is returned. 

Steps to invoke and parse the REST JSON web service:

  1. The bean method loadData first declares an instance of the RestServiceAdapter class.  This is a helper class that lets you invoke REST web services and simply returns the results in string format. 
  2. The RestServiceAdapter lets you set the connection name (from connection.xml), the request type (GET/POST/etc), what the retry limits are and then you can specify anything else you want added to the URI. 
  3. The send method of the RestServiceAdapter is invoked and the service is called and the JSON string is returned.
  4. To easily parse the JSON string into a bean, we provide the JSONBeanSerializationHelper class.  This class has a fromJSON method where you can specify the destination class type and the string to parse and it will return an object of the class you specified.  In our case, we have defined a RESTJSONResponse class to hold our GeoIP information returned from the service.

Now that the service is invoked and the results are parsed into the bean, the UI is updated because it is already bound to the bean DC.  With the REST JSON version of this you don't need a Data Control for the service, but you do need a connection in your connection.xml to store the URL connection.   You can optionally bind the data directly to your bean or create a Data Control out of the Bean and bind that to the UI.  Normally it's easier to do the latter once you understand the binding framework.

What's next?

This pretty much completes this example.  I've added the map just as a nice UI representation of geo-coordinate supplied by this service.  In the future you will see some more structured REST JSON web services coming out of Oracle that have methods that provide schema information.  This will allow us to use them declaratively within ADF Mobile.

Good luck and happy coding!




Thursday Jan 03, 2013

ADF Mobile Configuration Service Usage

Overview 

ADF Mobile Configuration Service provides a mechanism for ADF Mobile Apps to update the end-points after they have been deployed to devices. This service allows any end-points configured in connections.xml to be updated on the server and have the deployed Apps uptake the changes without having to go through the normal App update process. All the end-points configured in the connections.xml like Web Service WSDL URI, REST Service URI, LoginServer URI, Remote URL etc can be updated using the Configuration Service.  

Scenarios 

1. Test to Production : When Apps are built they are configured to use dev/test end-points used by the developers for testing during development. Typically these end points are configured by administrators to point to production instances as part of application provisioning. Using Configuration Service allows mobile application administrators to configure the end-points a part of App provisioning.
2. Updating Configuration for Apps in production : In certain cases one may need to change the end points used by an App after deployment to a production environment due to maintenance or some other reason. Configuration Service  & checkForNewConfiguration() API can be used for the configuration changes to be propagated to the mobile apps in production.

Configuration Uptake Flow

First time App start up:

1. When Configuration Service is enabled in an ADF Mobile App, the user is prompted with a dialog to provide the credentials and URI for the Configuration Service. A default URL is populated for the Config Service URL field based on the seeded URL entry in adf-config.xml. User can change this to any end-point provided by the administrator

Config Service Login








































2. After the user enters the credentials and submits the FWK downloads connections.xml from the Configuration Service and restarts the App with the new configuration.

3. During the Application restart the FWK checks for the presence of the downloaded connections.xml and continues with the normal startup flow.

Configuration updates after deployment:  

Developers can use oracle.adfmf.framework.api.AdfmfContainerUtilities.checkForNewConfiguration() API to check if the connections.xml on Configuration Service has changed and if so, download a new version of the connections.xml file from the server. If a new version of the file is downloaded, the application is restarted with the new configuration. Developers can either invoke the API through some UI as shown in the attached sample app or do the check automatically as part of Application or Feature Lifecycle listeners at a certain event point in the App lifecycle.    






































Enabling Configuration Service

Configuration Service can be enabled using the  following configuration in adf-config.xml. This file is in <App root>/.adf/META-INF folder 

<adf:adf-properties-child xmlns="http://xmlns.oracle.com/adf/config/properties">
     <!-- Enable Configuration Service Check at Startup--> 
     <adf-property name="use-configuration-service-at-startup" value="true"/>
     <!-- Seeded Configuration Service URL -->
     <adf-property name="adfmf-configuration-service-seed-url" value="http://192.168.1.9:7101/ConfigService-ViewController-context-root/"/>
</adf:adf-properties-child>


Server Side Configuration Service Setup

Configuration Service can be implemented as a WebDav service or as a Service that accepts HTTP GET and returns connections.xml. The URL used by the Config Service Client is of the following format : <URL Configured in adf-config.xml>/<application bundle id>/connections.xml. The Config Service end-point can be secured using Basic-Auth or Basic-Auth over SSL.

Sample Details

The provided sample application has :
1. ADF MF App (ConfigServiceTest): This App has two features ; 1. remote URL feature pointing to google.com 2. Config feature with a page to check for config changes on the server. The App is configured to check for configuration during initial start-up. The URL used by the remote URL feature is configured in connections.xml. This URL can be changed in the Configuration Service App to point to say, for ex: http://m.bing.com and the mobile app can pick up this change using Config feature. 
2. J2EE app(ConfigService) that contains connections.xml at HTML root/<application bundle id> . This App does not have to be a J2EE App. In fact, it can be any endpoint that accepts HTTP GET and returns connections.xml using the specified URL format. 

Steps to try the sample:

1. Deploy the ADF Mobile App to a simulator or device.
2. Deploy the WAR file to a WLS instance(tested with integrated WLS shipped with JDev 11.1.2.3.0).

3. Start the mobile App. Enter the Config Service URL from step2 in the Config Service dialog displayed during the app startup as shown below. Make sure you change the host and port to point to the WLS instance used in step2.

Config Service Login








































4. The App will download the connections.xml from Config Service and restart.

5. When the App restarts Search feature will display google search page 

Config Service Login






































6. Change the remote URL in connections.xml in the Config Service App to http://m.bing.com. Make sure the changed end point is visible in the connections.xml by accessing the file from a browser
7. In the mobile app, access the Config feature and click on the "Check For Config Changes" button to detect the config change and download the new connections.xml.




































8. The App will restart after downloading the new configuration. This time the search feature will display the bing search page.  






































Config Service Login






































This approach can be used to change any end points used by the app like WSDL URI, REST Service URI, Login Server URI etc.

Wednesday Dec 12, 2012

Configuration Tips for better Performance with ADF Mobile Apps

Some tips to keep in mind to make sure ADF Mobile application's performance is optimal:

1. Select release mode in deployment profile. This is perhaps the most important thing to remember to ensure best performance for ADF Mobile Apps. Selecting this option causes the deployer to package optimized JVM and minified JS libs with the mobile app there by significantly improving the over all performance of the application.

deploy profile

2. For iOS you do not need to do anything else other than selecting  release mode in deploy profile. However, on Android you have to create a keystore and configure it in JDev --> Tools --> Preferences --> ADF Mobile --> Platforms : Android as shown in the snapshot below

android preferences

3. Steps for generating the Keystore for Android using keytool :

keytool





 4. Logging level setting in logging.properties: Make sure the log level is set to SEVERE for both framework logger as well as the application logger as follows

oracle.adfmf.framework.level=SEVERE
oracle.adfmf.application.level=SEVERE

5. When using SOAP WebServices with WebService Data Control make sure you select the option to copy the WSDL. This will cause the JDev to download the WSDL and all the XSDs referenced by the WSDL from the server at design time and package them with the application during deployment. This way the application does not incur the cost of downloading these resources at run time from the device.

wsdc creation



About

This blog is is dedicated to tips and tricks for developing, integrating, securing, and managing mobile applications using Oracle Mobile Platform. It is created and maintained by the Mobile Suite/Oracle ADF Mobile product development team.

Archive of past entries

Even More Mobile Development Blogs

Oracle A-Team Site - Mobile Related Entries

Code samples from the Community

Fusion Middleware Blogs

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today