Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

Install the Marvis Client

SUMMARY Complete the pre-install tasks, and then choose the method that you want to use to install the Marvis Client on your device.

Before You Begin

Configure your network firewall settings to allow the Marvis client to connect to your Mist organization.

  • If your Mist organization resides in Amazon Web Services (AWS) cloud (default), use the following settings:

    • wss://client-terminator.mistsys.net:443/ws or protocol WSS (websocket) port 443 for domain/path

    • https://api.mist.com

      or HTTPS protocol port 443 for domain

  • If your Mist organization resides in Google Cloud Platform (GCP) cloud, use the following settings:

    • wss://client-terminator.gc1.mist.com/ws or protocol WSS (websocket) port 443 for domain/path

    • https://api.gc1.mist.com/

      or HTTPS protocol port 443 for domain
    Note:

    If your Mist organization resides in a cloud other than AWS or GCP, contact the support team for the appropriate URLs to configure the firewall settings.

Get the QR Code (Secret Token)

  1. Select Organization > Admin > Mobile SDK from the left menu.
  2. Click Token at the top of the Mobile SDK page.
  3. Create a new token, or use an existing token:

    • For a new token—Click Create Invitation. Enter a name for this invitation, and then click Create. When the token appears on the page, click View to see the QR code.

    • For an existing token—Refer to the token names to find the one that you want to use. Click the View link on the right side of the page to see the QR code.

Deploy the Marvis Client Using the SOTI MDM

To deploy the Marvis client using a mobile device management (MDM) solution, you must customize the Android package kit (APK) package deployment. You customize the APK deployment with the Intent action to set the secret software development kit (SDK) token upon installation. When you launch the customized application package, the client will be fully preconfigured and onboarded for operation.

You can onboard the Marvis client using the SOTI MDM.

Note:

We do not present the overall generic Android application deployment process with SOTI. We present only the information necessary to customize the Android application to complete the client deployment.

Before you begin:

  1. Ensure that you have a Windows device or a virtual machine (VM). You will run Package Studio, which runs only on Windows devices.

  2. Download SOTI’s MobiControl Package Studio (McStudio.exe).

To deploy the Marvis client using MDM:

  1. On your Windows device or VM, launch Package Studio and create a package project with the following settings:

    • Processor—All (unless targeting specific CPU or device types)

    • Platform—Android

    • OS Version—5 to 13 (unless you want to use a specific version)

    • Version String—Set to the same versioning as the APK version

    • Vendor—Mist Systems, Inc.

    • Optional space requirement specifications

  2. Add the Marvis client APK.
  3. Add the following Script file:

    • Script Engine—Legacy

    • Script Type—Post-Install

  4. Import the script file. The script file must have the following content:

    If you have configured a specific port on a Zebra device for voice calls, then the script file must have the following content:

  5. Build the package.

When you deploy the customized package with SOTI, the Marvis client is preconfigured and onboarded.

Deploy the Marvis Client Using AirWatch or VMWare Workspace ONE

We do not cover the overall generic Android app deployment process with AirWatch. We only cover the specific steps needed to complete the agent deployment.

Use the following intent command to deploy the agent:

If you have configured a specific port on a Zebra device for voice calls, then use the following content:

You can use the following references to deploy the intent command:

Deploy Marvis Client Using Other MDMs

If you are using any other MDM, verify that the MDM supports intent execution. If the MDM does not support intent deployment, then you can use the sideloading procedure described in Install Through Sideloading. Here is another example for ADB based (developer/debug) deployment that you can use to adapt to an MDM of your choice:

If the MDM solution does not support execution of Android intents, you might need to onboard each deployed client device manually.

Install Through Sideloading

Note:

Follow this procedure for internal use, development, testing, or debugging. This process is not for official customer deployments. However, you can use this procedure in cases where the MDM solution does not support executing Android Intents to automatically configure the secret token on installation.

This procedure requires manual intervention for each device being onboarded.
  1. Install the APK on the device. You can use Android Debug Bridge (ADB), MDM, or file manager (local device storage or an SD card containing the APK).
  2. Open the Marvis client application on the device.
  3. Tap the Marvis icon 7 times to open a special debug menu.

    For Zebra devices, the debug menu shows the port that is configured for voice calls.

  4. Onboard the client using the secret code or scan code:

    To use the QR code:

    1. Tap the Scan Organization button to open the camera and scan the invitation QR code. Provide the necessary permissions.

    2. When the QR code is scanned, the matching secret token value is inserted into the Secret field.

      The secret value is applied to the Marvis client automatically. A message appears indicating that the value is applied.

    To use the secret code:

    1. Type or paste the secret token value in the Secret field. The default value of Secret is empty.

    2. Tap the gray Start Marvis button to apply the changes.

      A message appears indicating that the value is applied.

You have successfully onboarded the Marvis client.

Verify the Installation

After you install and onboard the Marvis client, verify that those processes have run correctly.

To verify the installation:

  • Confirm that the secret token value is added correctly. Close the Marvis client process and then launch it again. Open the debug menu by tapping the Marvis icon 7 times, and verify that the secret token value is still stored in the field.

    If the secret token field is empty and the data does not persist, enter the secret token value manually, as described in Install Through Sideloading. You might also need to configure the application deployment to retain the application data.

  • About 15 minutes after you onboard the Marvis client, confirm that the Marvis client data is available on the Mist dashboard. You need to wait for a minimum of 10 minutes after onboarding the Marvis client for the data to propagate to the Mist cloud.

    If the data is not available in the Mist dashboard, a problem occurred in the client workflow of collecting data and sending it to the Mist cloud. Contact the support team. If you are able to use tools such as logcat or Android Debug Bridge (ADB), then you can use them to collect the Marvis client logs and share the logs with the support team.

    For Zebra devices, use the RxLogger tool to collect logs.

    When you contact the support team, you must share the Marvis client UUID. You can find the UUID on the Marvis client debug mode screen. The UUID is used to track the data flow from the Marvis client to the Mist cloud.