1. Migrate to Oracle Mobile Hub
  2. About Migrating to Oracle Mobile Hub

1 About Migrating to Oracle Mobile Hub

Learn about the benefits of migrating your existing instances from Oracle Mobile Cloud Service or Oracle Mobile Cloud, Enterprise to Oracle Mobile Hub, and understand the migration process and tools.

New features are being introduced into Mobile Hub and if you want to use those features you will need to migrate your mobile cloud configurations from Oracle Mobile Cloud Service (MCS) or Oracle Mobile Cloud Enterprise (OMCe) to Mobile Hub.

Migration is a big step to take so it's something that you should plan carefully. We provide guidance and tools to help you with this process.

  • While you are migrating your production instance, we advise that you run your current mobile instance and Mobile Hub in parallel for a while, probably a month.
  • The migration process should follow the following cycle, migrate > test > migrate, where you perform migration steps and test that the data that will be migrated is correct. If necessary, repeat this step a number of times. Finally you perform the migration by running the migration tool.
  • An external storage account is used for data transfer.

This guide uses the following terminology:

  • Source instance: Refers to the mobile cloud instance running in MCS or OMCe.
  • Target instance: Refers to the Mobile Hub.

This guide does not include detailed procedures on the migration of Oracle WebLogic Server users, groups, or policies from the source instance to the target instance. This includes users and groups that are defined in the default WebLogic Server authentication provider (embedded LDAP), as well as users and groups that exist in an external identity provider like an LDAP server. Refer to the migration (export/import) capabilities of your identity provider.

The processes of migrating from MCS to Mobile Hub and migrating from OMCe to Mobile Hub are slightly different so be sure to read the correct information for your source instance.

You can migrate to Mobile Hub from:

  • OMCe versions 18.2.1, 18.2.2, 18.2.3, or 18.2.5
  • MCS version 19.1.3

Learn About Oracle Mobile Hub

Mobile Hub is a cloud-based service that provides a unified hub for developing, deploying, maintaining, monitoring, and analyzing your mobile apps and the resources they rely on. As a service administrator, you can use this guide to provision, monitor, and maintain Mobile Hub instances.

Mobile Hub is a suite of public cloud services that consists of a set of integrated components that enables developers, managers, and mobile cloud administrators to develop, maintain, monitor, and export your mobile apps and the resources they rely on.

Find out more about how Mobile Hub provides a unified hub for developing, deploying, maintaining, monitoring, and analyzing your mobile apps and the resources that they rely on. See Developing Applications with Oracle Mobile Hub.

Plan your Migration Strategy

Follow these steps to migrate to Mobile Hub:

  • You need a new instance of Mobile Hub ready to use. See Getting Started.

  • You also need an object storage instance of 10Gb so that data can be migrated.

    The migration process uses Object Storage or Storage Classic for the data that is exported from MCS. Once the data has been imported to Mobile Hub, you can clean up the storage instance.

  • We provide a migration tool, which is a script which runs in a Docker environment. The migration tool for MCS is not the same as the migration tool for OMCe.

  • You should plan the migration process carefully and follow a cycle where you test the migration, possibly a number of times, to be sure that it produces the results you expect, and only then perform the actual migration.

  • (MCS only) You migrate your users from MCS, a traditional cloud account, to Mobile Hub, where users are stored in Identity Cloud Service.

This table describes the task flow for migrating to Mobile Hub.

Task Description How Do I Do This?

Get ready to migrate

Download the migration tool

The Migration Tool
(OMCe only) Patch the instance of OMCe If you are migrating from OMCe, you need to apply a patch to the service Patch OMCe

Configure the migration tool

Update the JSON file with the appropriate values for your source instance, the target instance, and the storage instance you’ll use for migration

MCS: Configure config.json for MCS

OMCe: Configure config.json for OMCe

Build the Docker image

Create a Docker image and create the container based on it

Build the Docker Container

Do a test runs of the migration tool

Check that the configuration file is correct by doing test runs that don’t update Mobile Hub

Test the Migration

Migrate to Mobile Hub

Once you are satisfied, run the migration tool for the final time

Perform the Migration

(MCS only) Migrate users to Mobile Hub

Export users from your traditional cloud accounts used by MCS, modify the resulting CSV file, and import users into IDCS used by Mobile Hub

Migrate Users

If the data to be migrated includes user-isolated storage collection objects, users must be migrated before data is migrated

Data Types

The migration tool exports the following types of data from the source instance (MCS or OMCe) to the storage instance, from where it is imported to the target instance, Mobile Hub:

  • Mobile Backends
  • Client Management
  • APIs
  • Connectors
  • Collections
  • Policies
  • Location data
  • Tables created by Database Access and Management APIs
  • Analytics data (MCS only)
  • Security certificates and credentials

Roles

You have to have the following roles to perform the migration:

  • Be administrator role on the MCS or OMCe instance, and on the Mobile Hub instance
  • For the storage instance, you need to:
    • Be administrator on the tenant that uses the object storage
    • Or, have the policy to use the object storage. For example:

      Allow user userOCID to manage objects in tenancy

      Allow group MigrationAdmins to manage objects in compartment OMHMigration