Migrate > Plan to migrate WCS


High level steps for a switchover migration

Overview

Switchover migrations are performed on new hardware, enabling the existing production system to be left in place until the moment that the new WCS is ready to handle traffic.

The traffic is then redirected to the new site, and the old hardware can be used to add capacity or serve as performance test systems.


Steps for a switchover migration

  1. Schedule training.
  2. Create a regression test plan for the site.
  3. Update custom scripts, including build, deployment and data load scripts.
  4. Backup the existing assets, across all tiers.
  5. Migrate the development environment:
    1. Upgrade the software levels to the levels required by WCS v7.0 - for example, the operating system level.
    2. Migrate a test database
    3. Migrate the custom code
    4. Execute post migration steps that are applicable to the development environment, including:
      • Migrating the promotions from WCS Accelerator to the Management Center
      • Migrate the marketing campaigns and activities from WCS Accelerator to the Management Center
    5. Upgrade and migrate any additional software, including
      • Virtual Member Manager
      • MQ
      • Likeminds
      • WebSphere Portal Server
    6. Test the migrated site
  6. Migrate the testing or QA environment:
    1. On the source test system execute pre-migration steps.
    2. Back up the source test system
    3. On the new test system install the WCS software
    4. Migrate a copy of the source test WCS database
    5. Migrate the WCS application
    6. Complete the post instance and database migration steps.
    7. Upgrade and migrate any additional software, including...
      • Virtual Member Manager
      • MQ
      • Likeminds
      • WebSphere Portal Server
    8. Migrate the Payment Manager instance and database
    9. Deploy the custom code and perform a full regression test with the migrated database
    10. Use the test results to modify the sizings, project plan, and project schedule.
  7. Migrate the production environment:
    1. On source production system execute required pre-migration steps
    2. On source production system backup instance
    3. On new production system install the WCS software
    4. Migrate a copy of the source production WCS database
    5. Migrate the source WCS production application
    6. Complete the post instance and database migration steps
    7. Upgrade and migrate any additional software, including...
      • Virtual Member Manager
      • MQ
      • Likeminds
      • WebSphere Portal Server
    8. Migrate the Payment Manager instance and database
    9. Deploy the custom code and test with the migrated database
    10. Production cutover (to new production machines)
    11. Backup the source production system
    12. Bring the source WCS production site fully offline
    13. Migrate the source WCS database
    14. Complete any post instance and database migration steps as required
    15. Migrate the Payment Manager database.
    16. Execute a full regression test on the migrated WCS site
  8. Go live with the migrated system
  9. Recreate the staging server.


+

Search Tips   |   Advanced Search