Migrating from WebLogic Integration 2.0 to WebLogic Integration 2.1 Service Pack 1

 

This section provides two procedures for migrating from BEA WebLogic Integration 2.0 to BEA WebLogic Integration 2.1 Service Pack 1 (SP1). This section includes the following topics:

• Migrating from WebLogic Integration 2.0 with No Service Pack or Service Pack 1 to WebLogic Integration 2.1 Service Pack 1

• Migrating from WebLogic Integration 2.0 with Service Pack 2, 3, or 4 to WebLogic Integration 2.1 Service Pack 1

 

---

Migrating from WebLogic Integration 2.0 with No Service Pack or Service Pack 1 to WebLogic Integration 2.1 Service Pack 1

To migrate WebLogic Integration 2.0 with no service pack or with Service Pack 1 (SP1) to WebLogic Integration 2.1 SP1, complete the following procedure:

1. Migrate from WebLogic Integration 2.0 with no service pack or with SP1 to WebLogic Integration 2.0 Service Pack 4 (SP4) by following the directions in "Migration Issues" in the Release 2.0 SP4 edition of the BEA WebLogic Integration Release Notes. This document is available at the following URL:

   http://websupport.bea.com/custsupp/docs/wlintegration/v2_0sp4/relnotes/appa.htm

   Access to this URL requires a BEA WebSUPPORT login and password. BEA WebSUPPORT is one of the many benefits provided to contract customers of BEA Customer Support. For more information about BEA WebSUPPORT, go to the following URL:

   http://support.bea.com/welcome.jsp

2. Migrate from WebLogic Integration 2.0 SP4 to WebLogic Integration 2.1 SP1 by following the directions in Migrating from WebLogic Integration 2.0 with Service Pack 2, 3, or 4 to WebLogic Integration 2.1 Service Pack 1.

 

---

Migrating from WebLogic Integration 2.0 with Service Pack 2, 3, or 4 to WebLogic Integration 2.1 Service Pack 1

This section provides a procedure for migrating from BEA WebLogic Integration 2.0 with Service Pack 2, 3, or 4 to BEA WebLogic Integration 2.1 Service Pack 1. It contains information about the following subjects:

• Migration Process Overview

• Before You Begin

• Database Migration

Migration Process Overview

In addition to providing a direct migration procedure from WebLogic Integration 2.0 Service Pack 2, 3, or 4 to WebLogic Integration 2.0 Service Pack 1, the procedures provided in Database Migration can also be used to complete the overall migration processes described in the following chapters and sections:

• Migrating from WebLogic Process Integrator 1.2 or 1.2.1.

• Migrating from WebLogic Collaborate 1.0 or 1.0.1.

• Migrating from WebLogic Integration 2.0 with No Service Pack or Service Pack 1 to WebLogic Integration 2.1 Service Pack 1.

For example, when migrating from WebLogic Integration 2.0 with no service pack or with Service Pack 1, you must first migrate to WebLogic Integration 2.0 Service Pack 4 and then migrate to WebLogic Integration 2.1 Service Pack 1.

Before You Begin

Before following the procedures provided in Migrating with the Database Configuration Wizard or Migrating with the Command-Line Migration Script, you must consider the following:

• Domain Migration

• Remote Database Server

• Security File Realms

Domain Migration

The procedures provided in Migration Utilities, run only migration utilities that migrate the WebLogic Integration repository information stored in database tables. These utilities do not migrate WebLogic Server domain information for your application.

To migrate the WebLogic Server domain information for your application, complete the following procedure:

1. Migrate the WebLogic Integration 2.0 repository information to one of the preconfigured WebLogic Integration 2.1 domains, as described in Database Migration. For more information about domains, see "WebLogic Server Domains" in Getting Started in Starting, Stopping, and Customizing BEA WebLogic Integration.

2. Copy any application-specific entries from the config.xml file for your existing WebLogic Integration 2.0 domain to the config.xml file for your existing WebLogic Integration 2.1 domain.

   WebLogic Integration 2.1 is delivered with four preconfigured domains: bpmdomain, eaidomain, samples, and wlidomain. The config.xml files for these domains are located in the WLI_HOME/config/DOMAIN_NAME directory, where DOMAIN_NAME is bpmdomain, eaidomain, samples, or wlidomain. For example, the config.xml file for the wlidomain is located in the WLI_HOME/config/wlidomain directory.

Remote Database Server

If the machine on which WebLogic Integration 2.1 Service Pack 1 is installed and on which you plan to run the migration utility is different from the machine that hosts the database server with the WebLogic Integration repository, you must meet the following prerequisites before running the migration utility:

• A client installation of the database product must be installed on the WebLogic Integration machine.

• The database directory that contains the command-line executables for the database must be included in the PATH environment variable. For example, for the Oracle database on a UNIX platform, $ORACLE_HOME/bin must be included in the PATH.

Security File Realms

If you are using the file realm for Security, you must complete one more task before starting a migration procedure (either Migrating with the Database Configuration Wizard or Migrating with the Command-Line Migration Script). Before beginning either procedure, you need to merge the WebLogic Integration 2.0 filerealm.properties file with the filerealm.properties file for WebLogic Integration 2.1 in WLI_HOME/config/DOMAIN_NAME.

Database Migration

The migration utilities provided with WebLogic Integration 2.0 Service Pack 1 provide a direct migration path from WebLogic Integration Service Pack 2, 3, or 4 to WebLogic Integration 2.0 Service Pack 1. This direct migration path is represented by the gray arrow labeled Migrate database in the following figure.

Figure 4-1 Direct Migration Path from WebLogic Integration 2.0 Service Pack 2, 3, or 4 to WebLogic Integration 2.1 Service Pack 1

 

If you are currently running WebLogic Integration 2.0 with Service Pack 2, 3, or 4, you can migrate to WebLogic Integration 2.1 by following the procedure in either Migrating with the Database Configuration Wizard or Migrating with the Command-Line Migration Script.