Building the first native Android os MobileFirst application form

Building the first native Android os MobileFirst application form


To serve a native Android operating system application form, MobileFirst Hosting server should be aware it. For this specific purpose, IBM MobileFirst Platform Groundwork delivers a Natural API catalogue, containing a pair of APIs and setup records.

This training talks about the best way to create the Android Native API and approaches to incorporate it by using a indigenous Android os request. These actions are needed so you can use it afterwards to realize tasks including joining to MobileFirst Web server, invoking adaptor processes, putting into action authentication strategies, and many others.

Prerequisite . Builders need to be skilled with making use of Google’s programmer resources.

Constructing a MobileFirst Indigenous API

  1. In MobileFirst Recording studio, develop a MobileFirst job and put a MobileFirst Indigenous API.
  2. Within the New MobileFirst Natural API dialogue, key in your application brand and select Android for any Surroundings field.
  3. Appropriate-go through the produced NativeAPI file (based in your-jobs/programs/your-nativeapi-app-label ) and select Run As Andgt; Deploy Indigenous API . This step is called for for MobileFirst Web server to realize the application each time a get actually gets to the server.
  4. The MobileFirst indigenous API has a number of factors:
  • wlclient.components has got the connection options a natural Android operating system application utilizes.
  • worklight-android.bottle would be the MobileFirst API library.
  • gcm.jar and drive.png are for Google and yahoo drive notice solutions.

JSONStore directory is made for suggested JSONStore assist in indigenous software programs.

armabi. armabi-v7a. mips. and x86 folders are for recommended Software Legitimateness Security in indigenous applications.

As with any MobileFirst project, you produce the machine arrangement by modifying the data files which are on the server\conf file.

You employ the software-descriptor.xml record to define program metadata as well as configure security environments that MobileFirst Host enforces.

  • wlclient.attributes
  • The submit holds machine arrangement qualities and it is end user-editable.
  • wlServerProtocol – The interaction protocol to MobileFirst Hosting server, which may be either http or https.
  • wlServerHost – The hostname of MobileFirst Web server.
  • wlServerPort – The port of MobileFirst Web server.
  • wlServerContext -The circumstance main pathway of the program for the MobileFirst Machine.
  • wlAppId – The application ID as identified on the software-descriptor.xml document.
  • wlAppVersion – The applying model.
  • wlEnvironment – Whatever target surroundings with the local program.
  • wlUid – The house applied by MTWW to find this being a MobileFirst request.
  • wlPlatformVersion – The MobileFirst Studio model.
  • languagePreferences – Selection of ideal locations.
  • GcmSenderId – This home describes the GCM Sender Identification used for thrust notifications. Automatically, this house is commented out.
  • Creating and configuring an Android operating system natural program
  • Produce a natural Android os app or work with an pre-existing one particular.
  • Copy the worklight-android mobile phone.bottle. uicandroid.jar. bcprov.jar. and google android-async-http.jar data out of the WorklightAPI directory to your new local Google android application, in the /libs directory.
  • Version the submit from your MobileFirst native API directory into the new natural Android request, in the /belongings listing.
  • Put the subsequent permissions towards the AndroidManifest.xml report:
  • Add more the MobileFirst UI action:

For more information, review the “Getting indigenous programs for Google android” individual documentation subject As soon as the application is work in Eclipse, the last end result is a native app consisting of the MobileFirst API library. The presented Business venture has a MobileFirst Studio venture together with the produced NativeAPI directory. The furnished Native undertaking features an Android app presently set up with the MobileFirst NativeAPI.

Sample application

Warning: Use of undefined constant php - assumed 'php' (this will throw an Error in a future version of PHP) in /home/kalamdb/public_html/wp-content/themes/bulletin/urdu-single.php on line 46