Migrate WebSphere Commerce Version 7 Feature Pack 8 to WebSphere Commerce Version 9.0.0.1+

The following section outlines the high-level steps that complete to migrate to WebSphere Commerce Version 9.0.0.1+. Start by migrating the development environment, which includes the development database, custom assets, storefront, and search application. With a successfully migrated development environment, you then deploy your migrated assets to the WebSphere Commerce Version 9.0.0.1+ runtime environments.


Before beginning

  1. Review Planning to migrate WebSphere Commerce.

  2. Upgrade the WebSphere Commerce Version 7 environments to Feature Pack 8.

  3. Update the development and runtime databases to one of the following versions.

  4. Update your Feature Pack 8 development and runtime environments to the to latest NIST SP 7.0-131A security standards.

  5. From your Feature Pack 8 environment, ensure that all tasks are approved and all workspaces are closed.

  6. From your Feature Pack 8 environment, use the following utilities to ensure that the staging database and production database are synchronized:

    1. stagingprop utility

    2. Propagating the search index

    Note: Once the staging and production databases are in sync, a content-freeze must be in effect until the live production database is migrated.

  7. Install the WebSphere Commerce Version 9 development environment, including the latest maintenance package.

  8. Plan and deploy the WebSphere Commerce Version 9 production environment, including the staging environment and the latest maintenance package.


About this task

The following steps outline the entire migration process. It is likely that your migration is completed in planned chunks, starting with migrating the development environments. If we are interested in only migrating the development environment now, complete steps 1 - 11. The remaining steps cover how to package and deploy your migrated assets for ythe production environment, and how to migrate our production database and switch your live traffic to your version 9.0 production environment.


Procedure

  1. Migrate the site security.
    Manually migrate your Feature Pack 8 security configurations to WebSphere Commerce Version 9.0.0.1+.

  2. Migrate your configuration files.
    Migrate the WebSphere Commerce configuration files by manually merging them with or copying them to the WebSphere Commerce Version 9.0.0.1+ development environment.

  3. Migrate the development database.
    To migrate the development database from Feature Pack 8 to WebSphere Commerce Version 9.0.0.1+, we must first prepare your Feature Pack 8 development database and the WebSphere Commerce Version 9.0.0.1+ development environment. Next, you run the migration utility to migrate your Feature Pack 8 development database to WebSphere Commerce Version 9, then run the updatedb utility to bring the database up to the WebSphere Commerce Version 9.0.0.1+ level.

  4. Migrate your Aurora store web project.
    To migrate your Feature Pack 8 store to WebSphere Commerce Version 9.0.0.1+, export your Stores project from your Feature Pack 8, then import the project into the WebSphere Commerce Version 9.0.0.1+ development environment. Next, configure your imported store project for WebSphere Commerce Version 9.0.0.1+.

  5. Migrate our custom struts applications
    WebSphere Commerce Version 9 uses Apache Struts 2 as the preferred platform for developing enterprise Java web applications. Struts 2 provides plugin support for REST and Spring, which are important components of the WebSphere Commerce platform. It is also designed for more streamlined development and is fully integrated with the WebSphere Commerce deployment pipeline.

  6. Migrate the WebSphere Commerce Search customizations.
    Whether you used BOD-based Search of REST-based Search in previous versions of WebSphere Commerce, we can migrate our custom Search assets to use REST-based Search in WebSphere Commerce version 9.0.0.3+.

  7. Migrate your EJB entity beans to Java Persistence API.
    Enterprise Java Entity Beans are no longer supported in WebSphere Commerce Version 9.0.0.1+. By using a combination of tools and manual steps, we can migrate your EJB 1.1 entity beans to JPA, and update your code to use WebSphere Commerce Version 9.0.0.1+ APIs.

  8. Migrate the Management Center.
    Run the Management Center Migration Utility to migrate our customized Feature Pack 8 Management Center to WebSphere Commerce Version 9.0.0.1+.

  9. Migrate our custom Physical Service Data Objects.
    Manually migrate our custom physical service data object from your Feature Pack 8 development environment to the WebSphere Commerce Version 9.0.0.1+ development environment.

  10. Migrate your command and data bean projects.
    Migrating command and data bean projects involves several steps. The WebSphereCommerceServerExtensionsLogic project must be exported from our old development environment, and imported into WebSphere Commerce Version 9.0.0.1+ development environment.

  11. Complete your post-migration tasks.
    After you migrate your Feature Pack 8 development database and application to WebSphere Commerce Version 9.0.0.1+, complete the following post-migration steps.

  12. Verify your migrated development assets on WebSphere Commerce Version 9.0.0.1+ Developer.
    Now in the migration, you have a fully migrated development environment. Verify that your migrated assets are working as designed in the development environment.

  13. Package our custom assets for deployment to the WebSphere Commerce Version 9 environment.
    The WebSphere Commerce Build tool is the tool that we use to build our customizations into input packages. These packages can be used to build new container images and deploy to the runtime environments. If a CI/CD pipeline implemented, you do not need to concern yourself with deployment.

  14. Build and deploy the WebSphere Commerce Version 9.0.0.1+ custom containers.
    Implement a continuous deployment pipeline for WebSphere Commerce Version 9.0.0.1+ by utilizing Docker containers.

  15. Migrate the staging database.
    Migrate the staging database by backing up the database, then restoring the backup to the WebSphere Commerce Version 9 environment. Once the database is restored, we can run the premigration check and migration commands.

  16. Migrate our production database.
    Migrating your Feature Pack 8 production database is completed in two parts: migrating a copy (or offline version) of our production database, and migrating the live version of the database. By migrating an offline version of our production database, we can test that database in the WebSphere Commerce Version 9.0.0.1+ production environment.