IBM MobileFirst v7.1至v8.0用户迁移技术咨询

Got it, let's break this down step by step since you're migrating from MobileFirst v7.1 to v8.0 and need to preserve push subscription data without official migration scripts.

Since MobileFirst v8.0 changed some underlying push service mechanics compared to v7.1, you'll need to manually extract, transform, and load the subscription data. Here's how to do it:

• Step 1: Extract v7.1 push subscription data
  First, identify the tables in your v7.1 MobileFirst database that store push subscriptions. Typically, this is the PUSH_SUBSCRIPTIONS table (names might vary slightly depending on your setup). Use a SQL query to pull the critical data:

  SELECT USER_ID, DEVICE_TOKEN, SUBSCRIPTION_ID, DEVICE_PLATFORM, TIME_STAMP 
  FROM PUSH_SUBSCRIPTIONS;
  

  Export this data into a structured format like CSV or JSON for easy processing. Don't forget to back up your entire v7.1 database before doing any extraction—safety first!

• Step 2: Map data to v8.0's structure
  v8.0 uses a different schema for push subscriptions (e.g., tables might be prefixed with MF_ or include additional fields like TENANT_ID if you're using multi-tenancy). Connect to your v8.0 MobileFirst database and inspect the relevant tables (usually MF_PUSH_SUBSCRIPTIONS or similar) to note required fields and data types.
  For example, if v8.0 requires a DEVICE_ID instead of DEVICE_TOKEN, or adds a TENANT_ID field, you'll need to adjust your exported data to match these requirements (fill in default values for new fields if applicable).

• Step 3: Load data into v8.0
  You have two reliable options here:

  • Direct SQL insertion: If you're running a local on-premises MobileFirst v8.0 instance, you can write INSERT statements to push the transformed data into the v8.0 subscription tables. Make sure to respect any constraints (like foreign keys or unique indexes) to avoid errors.
  • REST API batch import: Use v8.0's Push Service REST API to create subscriptions programmatically. The endpoint is usually POST /imfpush/v1/apps/{your-app-id}/subscriptions—you can loop through your transformed data and send a request for each subscription record. This is safer if you're using a cloud-hosted MobileFirst instance.

• Step 4: Validate the migration
  After importing, test sending push notifications to a subset of migrated users to confirm they receive them. Also, check the v8.0 database to ensure subscription records are correctly stored and linked to user accounts.

Whether you need to run both v7.1 and v8.0 in parallel depends on your user rollout strategy:

• If users are upgrading gradually: Yes, parallel running is necessary. During the transition period, some users will still be on v7.1, and their push subscriptions are tied to the old system. You'll need to keep the v7.1 push service active to send notifications to these users until they upgrade.
• Key considerations for parallel operation:
  • When users upgrade to v8.0, their new app instance will register with the v8.0 push service. To avoid forcing users to re-subscribe manually, add logic in the v8.0 app's onboarding flow: check if the user had subscriptions in v7.1 (you can fetch this via a quick API call to the v7.1 system or from your user database), then auto-create those subscriptions in v8.0.
  • Once all users have upgraded to v8.0, you can safely decommission the v7.1 push service and database.
• If you can force an immediate full upgrade: No, parallel running isn't needed. But this is only feasible if you have full control over user updates (e.g., internal enterprise apps) and can ensure all users switch to v8.0 at the same time.

内容的提问来源于stack exchange，提问作者widj91942