Skip to content

Deploying to Mobile Services

This topic describes the steps to deploy the generated bundle.js and bundle.js.map to mobile service on NEO and Cloud Foundry.

Prerequisites

The identity provider configured for mobile services admin APIs must support basic authentication.

Context

Use these steps to deploy the generated bundle.js and bundle.js.map to mobile service on NEO and Cloud Foundry.

Procedure

  1. Set the mobile service admin API and app ID in the settings.json file, using the user setting mdk.mobileservice.

    {
      "mdk.mobileservice": {
        "adminAPI": "",
        "appId": ""
      }
    }
    

    Note

    • For deploying on Cloud Foundry, mdk.mobileservice settings should be set.
    • For deploying on NEO, mdk.mobileservice settings takes the priority. If mdk.mobileservice isn’t set, then the appRoot specified in launch.json and user setting is used.
  2. To trigger the deploy command, perform one of the following sub steps. Select MDK:Deploy menu item to trigger the deploy command.

    • In file explorer panel, right click on node Application.app and select the menu item MDK:Deploy.
    • In command palette, select MDK:Deploy.
  3. Provide the username and password for mobile service admin API to complete the deployment.

    User name and password for mobile service admin API is not required during each time of deployment. In other words, after providing the user name and password for the first instance, a session is established between Mobile Development Kit extension and mobile service. During the lifecycle of the session, the provided user name and password remains active.

    If successful, the deployment revision number is displayed, else an error message is displayed.


Last update: August 12, 2020