Skip to main content

By clicking Submit, you agree to the developerWorks terms of use.

The first time you sign into developerWorks, a profile is created for you. Select information in your profile (name, country/region, and company) is displayed to the public and will accompany any content you post. You may update your IBM account at any time.

All information submitted is secure.

  • Close [x]

The first time you sign in to developerWorks, a profile is created for you, so you need to choose a display name. Your display name accompanies the content you post on developerworks.

Please choose a display name between 3-31 characters. Your display name must be unique in the developerWorks community and should not be your email address for privacy reasons.

By clicking Submit, you agree to the developerWorks terms of use.

All information submitted is secure.

  • Close [x]

developerWorks Community:

  • Close [x]

Migrating to WebSphere Process Server Version 7

Migrating from WebSphere Process Server V6.2.0.x to V7.0.0.x

Phani Madgula (mabalaji@in.ibm.com), Software Engineer, IBM
author image
Phani Madgula is currently working for WebSphere Process Server Support at the India Software Labs (ISL). He has 7 years of experience at IBM. He worked in various product teams, including WebSphere Application Server Community Edition, WebSphere Business Integration Adapters, and DB2. He has experience in developing JEE applications, product support, and database administration. He is an Oracle9i certified professional.
(An IBM developerWorks Contributing Author)
Rajiv Madassery (rajiv.madassery@in.ibm.com), Principal Software Engineer, IBM
Author photo of Rajiv Madassery
Rajiv Madassery works as a Principal Software Engineer for the WebSphere Process Server Level 2 Support Team at the India Software Lab (ISL). Rajiv joined IBM in 2003 and has worked with the WebSphere Business Integration Adapters Functional Verification Test and WebSphere Application Server Level 2 Support teams.
(An IBM developerWorks Contributing Author)

Summary:  This tutorial provides instructions on migrating from WebSphere® Process Server V6.2.0.2 to V7.0.0.1. It highlights steps where administrators need to be cautious to prevent losing valuable business data.

Date:  03 Mar 2010
Level:  Intermediate PDF:  A4 and Letter (3871 KB | 62 pages)Get Adobe® Reader®

Activity:  27441 views
Comments:  

Introduction

This tutorial is presented in similar lines as Migrating to WebSphere Process Server V6.2. However, WebSphere Process Server V7.0 (hereafter called Process Server) brings forth an improved set of tools and commands that help in performing the migration. It also presents a new set of terminology that helps customers understand the whole migration process clearly, thereby reducing the chances for any mistakes being committed while performing the migration. Different migration methods are recommended according to requirements or constraints that customers may have on their running deployment environments. The migration types distinguish migration of a standalone profile from migration of a clustered environment. In summary, the migration process takes a unique procedure, depending on the requirements or constraints and the source type environment. Based on experience over the years, the Process Server development team has accumulated significant improvements in the V7.0 migration process.

With the release of the latest versions of Process Server and older versions going out of support, there is always an urge to move the running environments to the latest supported versions. The latest releases of the product will bring new functional capabilities along with fixes for known defects. They are generally more reliable than earlier versions. However, the current running environments and applications might have been well configured, fine tuned, and robustly tested for the custom requirements of the business. This is a challenge for customers if there is no automatic way of performing migration on the configuration and application data from the current version to the latest version. Manually creating the same environment in the latest version is laborious and error-prone. To help customers move to the latest versions automatically, a set of procedures along with the tools and commands are available in the latest versions. When customers decide to move to a latest major version of Process Server from the current version, it is termed as a “version-to-version migration”. Here, the latest version of Process Server is installed along side the current version. A set of migration tasks are performed to copy and transform configuration data, relevant application data, and database schema from the current version to the latest.

This is different from a Process Server upgrade task where out-of-date files or data of an existing installation are replaced with the most current information. Applying refresh packs, fix packs, and interim fixes are examples of an upgrade.

The migration process is a complex task, which needs to be carefully planned to successfully move the previous versions of Process Server environment to the latest versions. The applications running in a Process Server environment make use of various components, such as Service Integration Bus (SIB), Business Process Choreographer (BPC), Business Space, and so on. Each of these components uses databases to store runtime data. Therefore, the risks involved in the migration process need to be properly understood and proper backup and restore plans have to be in place before performing the migration. This avoids losing valuable business data in case of a migration failure. In addition to the above aspects, administrators must also follow specific recommendations and procedures if their current Process Server environment has profiles created with different capabilities, augmentation levels, and clusters. If users require minimum downtime, there are specific procedures that need to be followed to perform the migration. For more information, see the WebSphere Process Information Center topic, Migration overview.

In this tutorial

This tutorial provides a step-by-step procedure to migrate from Process Server V6.2.0.2 to V7.0.0.1. It illustrates the procedure as follows:

  • An example deployment environment, configured for gold topology on Process Server V6.2.0.2 is chosen as the source environment. The source environment is migrated to Process Server V7.0.0.1. The migrated deployment environment in Process Server V7.0.0.1 is referred to as a target environment.
  • A sample BPEL application containing a human task is deployed onto the source environment. Before starting the migration, some BPEL instances will be started and left in running state. After performing the migration, these BPEL instances will be worked on in the target environment. This illustrates the BPC database schema or runtime data migration.
  • Similarly, a sample application that generates failed events is deployed on to the source environment. A sample set of failed events are generated before migration. After performing the migration, the failed events will be retrieved in the target environment. This illustrates the application compatibility with the new version.
  • The migration wizard tool is used to perform the migration. The application data and configuration data are migrated using this tool.
  • The database schema and runtime data are migrated using database scripts.

Note on WebSphere Process Server fix packs

In this tutorial, we are using Process Server V6.2.0.2 for the source environment and Process Server V7.0.0.1 for the target environment. The procedure is the same when migrating from Process V6.2.0.x (from any fix pack) to Process Server V7.0.0.x (to any fix pack). On the target side, we recommend applying the latest fix packs before starting the migration process.

The tutorial is divided into the following sections:


Prerequisites

  • You need a good understanding of J2EE concepts and database concepts.
  • You need to be skilled in configuring Process Server deployment environments (gold, silver, and bronze topologies) and performing administrative activities on the deployment environments.
  • You have good hands-on experience in creating and managing DB2® databases. You know how to run administrative scripts on the DB2 databases.

System requirements

For the migration exercise illustrated in the tutorial, the following environment is required:

  • Two Microsoft® Windows 2003 servers, or Windows XP Service Pack 2 desktops with at least 2 GB of RAM
  • IBM® DB2 Fix Pack 9.5.0.1
  • IBM WebSphere Process Server V6.2.0 Fix Pack 2
  • IBM WebSphere Process V7.0.0.0 Fix Pack 1

Duration

  • Configuring the source (WebSphere Process Server V6.2.0.2) environment: 8 hours
  • Performing the migration: 6 hours

1 of 10 | Next

Comments



static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=Business process management, WebSphere
ArticleID=470684
TutorialTitle=Migrating to WebSphere Process Server Version 7
publish-date=03032010
author1-email=mabalaji@in.ibm.com
author1-email-cc=dwu@us.ibm.com
author2-email=rajiv.madassery@in.ibm.com
author2-email-cc=dwu@us.ibm.com