4 Installing and Setting up the Application - JET Mobile
Prerequisites
You must have a separate IDCS application provisioned.
Format: RGBU_SIOCS_< EnvType><EnvIndex >_SOCS_MOBILE
Example: : RGBU_SIOCS_DEV1_SOCS_MOBILE
Configuring Application Settings
This section describes the configuration that is required (and some that is optional) prior to building and deploying the Oracle SOCS application.
Definitions of JET Mobile
Configuring the application includes Configuring Service End Points mainly for allowing the application to authenticate users, and connect to web services.
The client application configuration can be input manually using the UI that will appear after the EULA is displayed if the configuration is empty or incomplete.
Alternatively, the application configuration can be setup via an Android compatible MDM.
In both cases there are 3 configuration settings that are required.
When entering these settings using an MDM it is important to use the correct key and type for each value.
In Android, these MDM settings are referred to as Managed Configurations.
Base Service URI:
For example the full SIOCS service URI would be:
Note:
The <Region Name> and <Customer Subnamespace> part of the URL should be replaced with the one specific to your environment. This will be the same as your cloud service Application URL provided in the Welcome email.The base URI does not need to include the suffix “siocs-client-services/internal” but it will be removed if it is included.
MDM managed configuration properties:
Key: idcsBaseUri
Type: String
IDCS Base URI:
This is the base URI for the IDCS tenant.
MDM managed configuration properties:
Key: idcsBaseUri
Type: String
OAuth Client ID:
This is the IDCS public client app that was provisioned in IDCS for this mobile client application.
Format: RGBU_SIOCS_< EnvType><EnvIndex >_SOCS_MOBILE_APPID
Example: RGBU_SIOCS_DEV1_SOCS_MOBILE_APPID
MDM managed configuration properties:
Key: oauthClientId
Type: String
Configuring DataWedge Profile for Scanning
Note:
This is applicable to Zebra /Symbol / Motorola Android devices only.-
Click on the Menu Bar at the top right corner. Select New Profile.
-
Enter the profile name.
-
Select the newly created profile.
-
-
Make sure only these are checked:
-
Profile enabled - enable/disable this profile
-
Barcode Input - enable/disable scanner input
-
Intent Output - enable/disable output via intent
-
-
Under the APPLICATIONS group select Associated Apps:
-
Select the oracle.retail.sim.mobile.client identifier.
-
-
Under the INTENT OUTPUT set:
-
Intent action to oracle.retail.sim.mobile.SCAN
-
Intent category to android.intent.category.DEFAULT
-
Intent delivery to Send via Broadcast Intent
-
-
Save the settings and you would be able use the hardware buttons to provide scan inputs to the JET mobile application.
Details on Item Images
If configured, the JET mobile application will display images for items that have been entered into the system. Different sizes of images are supported in the application for optimal performance.
Image Sizing
There are two different image sizes used in the SOCS mobile application. These sizes exist to improve performance where different sizes of images are displayed by not using excess bandwidth (for example high resolution images being loaded and scaled down to a small space).
Thumbnail Images
Thumbnail images are the main images utilized in the application. These images are intended for areas in the application where smaller images are displayed (for example lists of items). The suggested resolution of these images is about 128x128px to 256x256px depending on the resolution and DPI of the mobile device's screen running the application. Any higher resolution images are scaled down, and the increased bandwidth to load the images is merely wasted and can cause decreases in performance. Thumbnail images are loaded asynchronously after the screen is populated, and there is a configurable amount of background threads to increase the rate multiple images are loaded into the application.
High Resolution Images
High resolution images, denoted by the size code 'H' in the system, are loaded on demand by a user. These images are meant to be large up to full screen images of an item. Thus, the suggested resolution of these images is up to the screen resolution of the device. These images can be 600x600 pixels to 800x800 pixels or even greater.
Network Considerations
Images are sent as a URL from the server to the JET mobile application. The JET mobile application webview then will load and display the image that corresponds to the URL the server provided. Therefore the end user devices need network access to any image URL endpoints for the images to be loaded and rendered.