Migrating from WebLogic Process Integrator 1.2 or 1.2.1

 

This section provides procedures for migrating an existing installation of WebLogic Process Integrator 1.2 or 1.2.1 to WebLogic Integration 2.1 Service Pack 1 (SP1). Specifically, it provides information about the following subjects:

• Before You Begin

• Migration Process Overview

• Migrating the Database

 

---

Before You Begin

The WebLogic Integration 2.1 Service Pack 1 (SP1) installation includes all the tools and files you need to migrate your databases and security realm. You do not need to have WebLogic Integration 2.0 installed to perform any migration procedure.

Before you attempt to migrate to WebLogic Integration 2.1 SP1, we strongly recommend that you back up your entire database and export all your workflows. With this preparation, you will be able to fix your environment and start the migration again if your migration attempt fails. You can run the migration script as many times as necessary without causing any adverse results.

 

---

Migration Process Overview

To migrate WebLogic Process Integrator 1.2 or 1.2.1 to WebLogic Integration 2.1 Service Pack 1 (SP1):

1. Migrate the database schema to the WebLogic Integration 2.1 SP1 format as described in Migrating the Database Schema.

2. Migrate the security realm, as described in Migrating the Security Realm. Migration of the security realm is required because WebLogic Integration 2.1 runs on a version of WebLogic Server other than that on which WebLogic Process Integrator 1.2 or 1.2.1 runs.

After completing your database migration and security realm migration, you must also assign permissions to existing users and roles. For more information, see Assigning Permissions.

Once the database is converted to the 2.1 level, tables that might not have existed in your WebLogic Process Integrator 1.2 or 1.2.1 database are added to WebLogic Integration. The resulting database contains the overall WebLogic Integration repository, instead of only the WebLogic Process Integrator tables.

 

---

Migrating the Database

This section provides instructions for the following tasks:

• Migrating the Database Schema

• Migrating the Security Realm

• Assigning Permissions

Migrating the Database Schema

This section provides a procedure for converting the WebLogic Process Integrator 1.2 or 1.2.1 database schema to the WebLogic Integration 2.1 Service Pack 1 format, as represented in the following figure.

Figure 2-1 Migration from WebLogic Process Integrator 1.2 or 1.2.1 to WebLogic Integration 2.1 Service Pack 1

 

To migrate your database schema:

1. Using your database administration tool, back up your existing WebLogic Integration component database, as recommended in Migrating the Database.

2. With the WebLogic Integration component database open, execute the appropriate BPM_12x-20.sql file listed in Table 2-1.

   Table 2-1 WebLogic Process Integrator Database Migration Scripts

   To migrate WebLogic Process Integrator tables for this database . . .	Use this dbscript file . . .
   Oracle 8.1.6	WLI_HOME/dbscripts/oracle/migrate/BPM_12x-20.sql
   Microsoft SQL Server 7.0 with Service Pack 3 or Microsoft SQL Server 2000	WLI_HOME/dbscripts/mssql/migrate/BPM_12x-20.sql
   Sybase System 11.9.2	WLI_HOME/dbscripts/sybase/migrate/BPM_12x-20.sql

   All files are located in WLI_HOME/dbscripts/DB_TYPE/migrate, where DB_TYPE is the subdirectory named for the type of database being migrated, such as Oracle. For directions on how to run the sql script for your database, see your database administrator.

3. Migrate the database schema from WebLogic Integration 2.0 format to WebLogic Integration 2.1 SP1 format by completing the steps in Migrating from WebLogic Integration 2.0 with Service Pack 2, 3, or 4 to WebLogic Integration 2.1 Service Pack 1.

Now proceed to Migrating the Security Realm.

Migrating the Security Realm

WebLogic Integration 2.1 uses a new security model which you need to adopt in order to access Studio and Worklist functions. (For more information, see About Security Realms in Using the WebLogic Integration Studio.)

The WLI_HOME/dbscripts directory of your WebLogic Integration 2.1 installation includes a utility you can use to upgrade your security realm, along with an additional utility that allows you to run the tutorial example without any additional setup. (For more information, see Learning to Use BPM with WebLogic Integration.)

Note: If you need to assign all permissions to existing users of your system, you can add the users to the list in the WLPI_SUPER_USERS variable, which is defined in the Migration.properties file. Otherwise you can assign permissions in the Studio client application after your migration is complete. For information about the default users and passwords provided in a new WebLogic Integration 2.1 installation, see About Security Realms in Using the WebLogic Integration Studio.

Select a Migration Procedure

Based on the release of WebLogic Process Integrator you are migrating and the security realm you have deployed, choose one of the migration procedures listed in the following table.

Table 2-2 Migration Procedures

If you are migrating from . . .	Do this . . .
WebLogic Process Integrator 1.2 or 1.2.1 and you deployed the com.bea.wlpi.rdbmsrealm.RDBMSRealm security realm	Use the procedure described in Migrate from the RDBMS Realm (WebLogic Process Integrator 1.2 or 1.2.1).
WebLogic Process Integrator 1.2.1 and you deployed the File Realm security realm	Use the procedure described in Migrate from the File Realm (WebLogic Process Integrator 1.2.1 Only).
WebLogic Process Integrator 1.2 and you deployed the Weblogic.Properties security realm	There is no automatic migration path. Please contact BEA Customer Support for more information.

Migrate from the RDBMS Realm (WebLogic Process Integrator 1.2 or 1.2.1)

The following procedures are based on the assumption that you are familiar with WebLogic Server 6.1 and the WebLogic Server Administration Console. For more information, see the WebLogic Server documentation at the following URL:

http://download.oracle.com/docs/cd/E13222_01/wls/docs61/index.html

If you are migrating from WebLogic Process Integrator 1.2 or 1.2.1 and you have deployed the security realm com.bea.wlpi.rdbmsrealm.RDBMSRealm, complete the following procedure:

1. Start the WebLogic Server from the WebLogic Integration 2.1 BPM domain, as described in Starting, Stopping, and Customizing BEA WebLogic Integration.

2. Start the WebLogic Server Administration Console.

3. Choose Security—>Realms—>wlpiRDBMSRealm. In the right pane, select the Configuration and Schema tabs.

4. Back up the Schema Properties by copying the text to a temporary file.

5. In the migrate directory of your WebLogic Process Integrator installation, open the file rdbmsrealm_migration_schema.txt in a text editor.

6. Copy the text from the rdbmsrealm_migration_schema.txt file and paste it into the Schema Properties window in the WebLogic Server Administration Console, overwriting the original text. Click Apply.

7. In the right pane, select the Database tab.

8. Verify that the database URL in the JDBC connection pool specifies your WebLogic Process Integrator 1.2 or 1.2.1 database, and modify any settings that are incorrect for this database. If you make any modifications, restart the WebLogic Server.

9. Select Security in the left pane and select the Filerealm tab in the right pane.

10. From the right pane, select wlpiCachingRealm from the Caching Realm drop-down list.

11. In the left pane, choose Services—>JDBC—>Connection Pools—>wliPool. In the right pane, select the Configuration and General tabs.

12. Verify that the database URL in the JDBC connection pool specifies your WebLogic Process Integrator 1.2 or 1.2.1 database, and modify any settings that are incorrect for this database.

13. Shut down the WebLogic Server.

14. From the WLI_HOME/config/bpmdomain/ subdirectory of your WebLogic Integration 2.1 installation, open the startup script file, startWeblogic.cmd (on Windows) or startWeblogic (on UNIX), in a text editor.

15. To the CLASSPATH setting, immediately following -classpath, add the following:

    %WLI_HOME%\lib\oldrdbmsrealm.jar;

    The line should look as follows:

    -classpath %WLI_HOME%\lib\oldrdbmsrealm.jar;%WLISERVERCP%

16. Save the file.

17. Start the WebLogic Server. Ignore any error messages you may receive.

18. Run the realm migration utility by going to the WLI_HOME/dbscripts/ directory and doing one of the following:

    • If you are using Windows NT, run the bpm20_realm_migrator.cmd script.

    • If you are using UNIX, run bpm20_realm_migrator.

19. Start the WebLogic Server Administration Console.

20. Copy the text from the temporary file you created in step 4 and paste it into the schema properties in the WebLogic Server Administration Console, overwriting the original text. Click Apply.

    Note: If you are using MSSQL7, you also need to change the schema properties by changing the setting of getGroupNewStatement from false to true (that is, getGroupNewStatement=true). For the other database types, the value false is correct.

21. Shut down the WebLogic Server.

22. From the server startup script, remove the text you added to the CLASSPATH setting in step 15, and save the file.

23. Start the WebLogic Server.

24. Optionally, run the tutorial enabler utility by going to the WLI_HOME/dbscripts/ directory and doing one of the following:

    • If you are using Windows NT, run bpm20_tutorial_enabler.cmd.

    • If you are using UNIX, run bpm20_tutorial_enabler.

Migrate from the File Realm (WebLogic Process Integrator 1.2.1 Only)

The following procedures are based on the assumption that you are knowledgeable about WebLogic Server 6.1 and the WebLogic Server Administration Console. For more information, see the WebLogic Server documentation set at the following URL:

http://download.oracle.com/docs/cd/E13222_01/wls/docs61/index.html

If you are migrating from WebLogic Process Integrator 1.2 or 1.2.1 and you deployed a file realm, complete the following steps:

1. Start the WebLogic Server from the BPM domain, as described in Starting, Stopping, and Customizing BEA WebLogic Integration.

2. Start the WebLogic Server Administration Console.

3. Choose Services—>JDBC—>Connection Pools—>wliPool. In the right pane, select the Configuration and General tabs.

4. Verify that the database URL in the JDBC connection pool specifies your WebLogic Process Integrator 1.2.1 database and modify any settings that are incorrect for this database.

5. Shut down the WebLogic Server.

6. Merge the fileRealm.properties files from the WebLogic Process Integrator 1.2.1 domain into the fileRealm.properties file in the WLI_HOME/config/bpmdomain directory of your WebLogic Integration 2.1 installation.

7. Start the WebLogic Server. Ignore any messages you may receive.

8. Run the realm migration utility by going to the WLI_HOME/dbscripts/ directory and doing one of the following:

   • If you are using Windows NT, run bpm20_realm_migrator.cmd.

   • If you are using UNIX, run bpm20_realm_migrator.

9. If you like, run the tutorial enabler utility by going to the WLI_HOME/dbscripts/ directory and doing one of the following:

   • If you are using Windows NT, run bpm20_tutorial_enabler.cmd.

   • If you are using UNIX, run bpm20_tutorial_enabler.

Assigning Permissions

Once you have migrated your database and security realm, you must assign permissions to existing users and roles. You can do so with the WebLogic Integration Studio. For information about default permission groups and their member users, and about assigning permissions to users and roles, see Administering Data in Using the WebLogic Integration Studio.