Migrating

Follow this tutorial for a full-fledged migration from IBM MobileFirst Platform Version 8.0 to the Persistent Mobile Foundation Version 9.0.x.

Migrating to the Persistent Mobile Foundation Version 9.0.x. has following advantages:

  • Reduce efforts, skills and time required to build apps

    • Build apps faster, simpler, and smarter with standard package managers (npm, CocoaPods, Gradle, NuGet) and Maven for Java Adapter build automation.
    • Simpler, modular, and easier PMF SDKs plugins.
    • Improved user experience including anticipating users’ next best action and providing guided help throughout for registering, configuring, and deploying apps.
  • Enhanced Automation, Dev and IT Self-Service

    • Live update to externalize and dynamically change app configurable information (Push Notifications, Authentication, Adapters, App behavior, and workflow).
    • User-friendly console for registering, deploying, and managing apps.
    • Simple architecture that eliminates the need for Dev and IT interdependence.
    • Features like crash analytics, configurable alerts, and root cause analysis.
    • Push Notifications services enable targeted, subscription-based notifications sent from web console.
  • Multi-channel API creation and management

    • Step-up API Connect multichannel security with mobile specific security extensions (For example, Step-up, Multi-factor) for maximum protection, then enforce in the Demilitarized Zone (DMZ) with IBM® DataPower.
    • Create and define IBM® API Connect-compatible Swagger REST APIs in the IBM® Mobile First Platform Version 8, and then manage and secure them in the API Connect.

Migrating existing applications to PMF SDKs

You can add support to your existing applications Persistent Mobile Foundation Version 9.0.x features existing applications by adding the PMF SDK plug-ins to your app, for more information refer the following links.

Migrating adapters and security

Basically, Adapters are Maven projects. The PMF security framework is based on OAuth, security scopes, and security checks. Security scopes define the security requirements to access a resource. Security checks define how a security requirement is verified. Security checks are written as Java adapters.

For more information, see the Creating Java and JavaScript Adapters and Authorization concepts tutorials.

PMF operates only in session-independent mode and adapters should not store a state locally to a Java virtual machine (JVM). You can externalize adapter properties to configure adapters for the context where they run, for example a test server or a production server. You can define them from the PMF Operations Console, or by using a command-line tool or the server REST API.

Migrating push notifications support

Push notifications can also be migrated from earlier releases to PMF 9.0.x easily. The push certificates are stored on the server. You can set them from the PMF Operations Console or you can automate certificate uploads by using a command-line tool or the push service REST API. You can also send push notifications from the PMF Operations Console. The push service is protected by the OAuth security model. You must configure server-side components that use the push service REST API must be configured as confidential clients of PMF.


Migrating from the IBM Mobile First Platform

Describes the detailed migration process.

Last modified on