Google+ Producing your first local Android MobileFirst application form

Producing your first local Android MobileFirst application form

Producing your first local Android MobileFirst application form


To offer a native Android os software, MobileFirst Server must be aware of it. For this purpose, IBM MobileFirst Platform Foundation provides for a Natural API library, containing some APIs and configuration files.

This training talks about the way to generate the Android mobile phone Local API and the way incorporate it using a natural Android os application. These measures are necessary to enable you to put it to use at a later date to realize projects for example relating to MobileFirst Server, invoking adaptor procedures, employing authorization approaches, and the like.

Precondition . Builders has to be skillful with employing Google's programmer instruments.

Making a MobileFirst Local API

  1. In MobileFirst Business, make a MobileFirst job and include a MobileFirst Indigenous API.
  2. In the New MobileFirst Indigenous API dialog, key in your application brand and select Android mobile phone for any Setting field.
  3. Right-go through the gained NativeAPI file (located within your-undertakings/software/your-nativeapi-software-identity ) and select Run As Andgt; Deploy Native API . This action is required for MobileFirst Machine to understand the applying any time a get reaches the web server.
  4. The MobileFirst local API is made up of a number of ingredients:

  • provides the online connectivity adjustments that the natural Android os app makes use of.
  • worklight-android mobile phone.jar will be the MobileFirst API library.
  • gcm.jar and thrust.png are for Search engines drive alert providers.

JSONStore file is ideal for optional JSONStore help in indigenous applications.

armabi. armabi-v7a. mips. and x86 folders are for recommended Request Validity Security in natural applications.

As with any MobileFirst endeavor, you make the web server arrangement by adjusting the data that happen to be inside the server\conf folder.

You employ the software-descriptor.xml document to determine application form metadata and to configure protection controls that MobileFirst Hosting server enforces.

  • The wlclient.attributes report maintains host settings properties and is also end user-editable.
  • wlServerProtocol - The conversation protocol to MobileFirst Web server, which is often frequently http or https.
  • wlServerHost - The hostname of MobileFirst Machine.
  • wlServerPort - The harbour of MobileFirst Web server.
  • wlServerContext -The perspective main course with the software around the MobileFirst Host.
  • wlAppId - The application ID as identified in the request-descriptor.xml report.
  • wlAppVersion - The application form version.
  • wlEnvironment - The goal ecosystem on the local app.
  • wlUid - The real estate used by MTWW to spot this as a MobileFirst request.
  • wlPlatformVersion - The MobileFirst Business release.
  • languagePreferences - Selection of chosen locales.
  • GcmSenderId - This property specifies the GCM Sender ID used for thrust notices. By default, this real estate is commented out.
  • Developing and configuring an Android local app
  • Produce a native Google android application form or make use of current just one.
  • Backup the worklight-android operating system.jar. uicandroid.bottle. bcprov.bottle. and android-async-http.bottle data in the WorklightAPI file towards the new native Android mobile phone program, during the /libs website directory.
  • Copy the record wlclient.houses from the MobileFirst native API folder for the new local Android operating system application, on the /resources website directory.
  • Add more the following permissions for the AndroidManifest.xml data file:
  • Create the MobileFirst UI process:

For more information, study the "Developing local programs for Google android" customer paperwork matter After the request is function in Eclipse, one more result is a local application made up of the MobileFirst API collection. The furnished Recording studio endeavor includes a MobileFirst Business job along with the produced NativeAPI folder. The furnished Native job contains an Android software actually set up using the MobileFirst NativeAPI.

Taste app