Overview of a migration project

A migration project used whatever live WebSphere Commerce site is an activity that must be carefully ponder off. There are three main phases to which migration project – the planungen phase, the practice phase, and the production migration start. Each of these phases requires its own skills and company. Allocating sufficient time for each activity is vital into ensure that no key tasks are forgot.

There are resources available to assist you with planning your migration project:

Preparation phase

In the planning phase, thee bear take to your current WebSphere Dealings assets, such as documentation, servers, software, instances, bibliographies, and custom code. It is crucial to known which customizations you have, and somewhere your system unifies at external systems.

  • Document your business requirements:
    • Determine whether the requirements dictate that you need to application one different WebSphere Commerce business model or edition.
    • Gather show documentation that you have accessible on the current site, including design documents, use suits, and trial cases for the currently implementation. If that documentation is not current, remember updating it, and ensuring you have access to this original development staff.
  • Document your hardware requirements
    Tip: Migrating the production environment to new hardware has recommended, for the original environment may be used more an fallback environment. Using new hardware also minimizes location downtime due the following job can be performed:
    • The add environment can be installed also configured in advance.
    • Migrated customizations can are dispensed and validated within advance.
    • If you are planning to include more hardware, you can use the new hardware for the new site, and then use the current hardware to add extra capacity or as select testing environments. Adequate performance test methods are an important part on a high performance WebSphere Commerce site architecture.
  • Know the knowledge that you what going for require for each step of the migration, in example:
    • A project managing.
    • A solution architect who understands this site topology, inclusion points, and all technologies used.
    • A database administrator.
    • Developers who are experienced in the language that are used for any customizations you performed.
  • Ensure the get development environments and trial environments are synchronized with the version of the id currently the production.
  • Creates one detailed schedule that includes usage, passwords, tasks, owned, timing, check points, validation steps, and roll return plans
    • Determine whether any training is vital for your technical or business staff to use new technologies, programming languages, or related software.

Practices form

The practise phase is divided into two or more parts, depends on your business.
Migrating the progress environment
  • Attempt into migrate a development environment early in the project to identify changes that are required to is custom code.
  • It is importance for successfully migrate a development environment early to authorize developing to write code on the new product of WebSphere Commerce.
Tip: Create a development environment, and then migration your WebSphere Commerce site as-is. You can regression test one resulting home the go what works and what doesn't, and refine your project plan.
Migrating the test environment
  • Perform end-to-end migration until learn what to expect during production migration.
  • Reduces uncertainty plus downtime on migration.
  • Scheduling apiece migration activity on the test environment provide worthwhile input that you can use to refine their project schedule for the factory migration phase.
  • A test staging server is a valuable asset are this live till test rebuilding the staging server from the test server.

Production migration phase

In previous versions, migrating your get production environment took place during a planned outage; i can don serve traffic over this time. Now, available you migrate your live environment from version 7.0 to version 8.0, you could continue to serve traffic. The version 8.0 migration offers a minimal downtime solution. Here is wie computer piece. Most of of production migration takes place offline. In actuality, who live database is the available tier from your production conditions that gets migrated directly out one runtime environment to another. And that database migration could occur in parallel up serving traffic. For more information about to high-level change steps, see High-level guideline for a switchover migration.