SOTI
Deploying BlueFletch Enterprise via SOTI
System Requirements
Windows machine for SOTI Package Studio (Windows VM for Mac users)
SOTI MobiControl account/environment
SOTI Package Studio
BlueFletch Files/Applications
Android devices enrolled to SOTI
Getting Started
Log into SOTI MobiControl
Select hamburger in top left, click on Packages
Download Package Studio
Save to your desired destination on your machine
Launch Package Studio-9
Building Packages using SOTI Package Studio
New Package Project
Click on File
Project Name
This will be the identifier for your package
Each component (e.g. APKs, Files, scripts, etc) should have it’s own package
Best Practice: Naming convention should leverage “BlueFletch ”
Examples:
BlueFletch - Enterprise Launcher v3_0_12 052020
BlueFletch - Authentication
BlueFletch - Support Agent
Platform
Select Android
Set OS Version Range
Minimum for BlueFletch Enterprise is 5.0
Comments
This field is optional
Vendor
Enter BlueFletch
New Package Wizard - Add Scripts
Notes:
Only the BlueFletch - Enterprise Launcher app package should require a script
The checkboxes are only recursors to the scripts being added to the package. You will add the scripts themselves in step 10
New Package Wizard - Add Files or Folders
Reference the Grouping SOTI Packages section below to determine which files or applications are needed and ensure the correct destination on device is set
Adding a Files
Adding an APK
Once all necessary files or APKs have been added to the package, click Next and you'll be taken to teh Size Settings screen
New Package Wizard - Size Settings
Do not alter default settings
If a script is NOT required, then select "Build Package Now"
If a script IS required, select "close" and move to step 10.
Finalizing Custom Scripting
Save changes to the script using ctrl +s or from the File dropdown.
Build Package
On Menu, select Project (drop down)
Make note of the destination path in Output Window for the “Package Saved at:” location
Repeat steps 1-11 for each of the Packages in the Grouping Packages section below
Uploading Package Builds to SOTI MobiControl
After all packages have been created, navigate browser to SOTI MobiControl
Click ‘New Package’ in the top, right area of the screen
Repeat steps 1-7 for all Packages built in MobiControl Studio based on the Groupings below
Grouping Packages - In Order of Installation
BEST PRACTICE TIPS : Limit packages to no more than one application at a time so that the packages can be easily updated without having to re-create multi-app packages.
BlueFletch - Launcher Config Package
Click Add Files
Select customized Launcher.json file from local machine and set destination on device to
%sdcard%\Download\ems\
Make sure the Launcher config is titled
launcher.json
when being added to the Package
Installing a logo: Select desired Icon and wallpaper png images from local machine and set destination on device to
%sdcard%\Download\ems\
BlueFletch - Sitelist Package
Click Add Files
Select the Sitelist.csv from appropriate storage location and set destination on device to
%sdcard%\Download\ems\
BlueFletch - Device ID Package
Add Files > Add Android APK
Select the Device ID APK from appropriate storage location
Deselect Automatically Run Activity after Install
Scripts The following scripts will initialize Device ID after they have been installed.
Post Install
sendintent -a "intent:#Intent;action=com.bluefletch.ems.deviceid.ACTION_INIT;component=com.bluefletch.ems.deviceid/com.bluefletch.ems.deviceid.MainActivity;end;"
BlueFletch - Messaging Package
Add Files > Add Android APK
Select the Messaging APK from appropriate storage location
Deselect Automatically Run Activity after Install
BlueFletch - Device Finder Package
Add Files > Add Android APK
Select the Device Finder APK from appropriate storage location
Deselect Automatically Run Activity after Install
BlueFletch - Support Analytics Package
Add Files > Add Android APK
Select the Support Agent APK from appropriate storage location
Deselect Automatically Run Activity after Install
BlueFletch - Auth App Package
Add Files > Add Android APK
Select the Auth APK from appropriate storage location
Deselect Automatically Run Activity after Install
BlueFletch - Launcher App Package
Add Files > Add Android APK
Select the Launcher APK from appropriate storage location
Deselect Automatically Run Activity after Install
Scripts The following scripts will initialize Support Agent and Enterprise Launcher after they have been installed.
Post Install
sendintent -a "intent:#Intent;action=android.intent.action.MAIN;component=com.bluefletch.ems.emm.support/com.bluefletch.ems.emm.support.features.ui.hidden.SilentInitActivity;end;"
sendintent -a "intent:#Intent;action=android.intent.action.MAIN;component=com.bluefletch.ems.emm.launcher/com.bluefletch.ems.emm.launcher.Launcher;end;"
Create Profile to Deploy Packages
Once all Packages have been created per the groupings above, a Profile needs to be created for deploying the all of the packages to enrolled devices.
Navigate back to SOTI MobiControl Cloud
General Tab
Profile Name
Apply a profile name that correlates to the packages being added
e.g. "BlueFletch Enterprise Suite"
Description
Best Practice - This is good opportunity to utilize information such as “Pilot”, “POC”, or specify test groups, etc. Gives the admin the ability to recognize the purpose of the specific profile
Configurations Tab
If not already set via a separate profile, ensure Restrictions > Feature Control configuration “Disable Verify Apps” is checked.
Packages Tab
Select Add
Click the check box next to all Packages uploaded in section “Uploading Packages to SOTI MobiControl” above.
Select OK.
Click ‘Save and Assign’
Select to the Device Group containing device(s) for testing BlueFletch Enterprise.
Wait for device(s) to receive assignments from SOTI.
Remotely Wiping a Device (Enterprise Reset)
BlueFletch Enterprise Launcher disables the ability to Enterprise Reset Zebra devices unless in Local Admin mode. To remotely wipe a device you must first enable the InvokeEnterpriseReset parameter on device. Then you can follow these steps to execute a remote wipe of the device(s).
Create a .xml file and title it
AllowEnterpriseReset.xml
Enter the follow into the file:
<wap-provisioningdoc> <characteristic version="8.1" type="SettingsMgr"> <parm name="InvokeEnterpriseReset" value="1" /> </characteristic>
Save the file
Create a new SOTI Package
Check Post-Install Script box to add to project
Add Files:
Select
AllowEnterpriseReset.xml
and set destination to/sdcard/Download
Add a script to the Post-Install Script file:
mxconfig /sdcard/Download/AllowEnterpriseReset.xml
Build package and add to the appropriate Profile
Deploy Profile
Last updated