Migrating from WebLogic Process Integrator 1.2/1.2.1

 

This section describes the processes required to fully migrate existing WebLogic Process Integrator 1.2/1.2.1 to WebLogic Integration 2.1. It contains information on the following subjects:

• Migration Process

• Before You Begin

• Migrating Your Database

 

---

Migration Process

Migrating WebLogic Process Integrator 1.2/1.2.1 to WebLogic Integration 2.1 is a two-step process:

1. Convert the database schema to WebLogic Integration 2.1 format. To do this, you need to:

   1. Convert the databases to 2.0 format, as described in Migrating the Database Schema.

   2. Convert the database schema from the 2.0 format to WebLogic Integration 2.1, as described in Migrating Using the WebLogic Integration Database Configuration Wizard in Graphical Mode in Migrating from WebLogic Integration 2.0 (SP 2, 3 and 4) to WebLogic Integration 2.1.

2. Migrate the security realm, as described in Migrating the Security Realm. Migrating the security realm is required because WebLogic Integration 2.1 runs on a later version of WebLogic Server than did WebLogic Process Integrator 1.2/1.2.1.

Note: The WebLogic Integration 2.1 installation includes everything you need to migrate your databases and security realm. You do not need to have WebLogic Integration 2.0 installed to perform any of these migration steps.

After you have completed database migration and security realm migration, you will also need to assign permissions to previously existing users and roles. See Assigning Permissions for more information.

Once the database is converted to the 2.1 level, tables that might not have existed in your WebLogic Process Integrator 1.2/1.2.1 database are added to WebLogic Integration. The result is that you now have the overall WebLogic Integration repository as opposed to just having the WebLogic Process Integrator tables.

 

---

Before You Begin

Before attempting to migrate to WebLogic Integration 2.1, it is highly recommended that you back up the entire database and export all of your workflows. If migration fails due to an environmental error, you can fix the environment as necessary and remigrate. You can run the migration script as many times as necessary without causing any adverse affects.

 

---

Migrating Your Database

This section includes information on the following subjects:

• Migrating the Database Schema

• Migrating the Security Realm

• Assigning Permissions

Migrating the Database Schema

To migrate your database schema, use this procedure:

1. Using your database administration tool, back up your existing WebLogic Integration component database, as recommended in Before You Begin.

2. With the WebLogic component database open, execute the appropriate .sql file listed in Table 2-1. These files are located in WLI_HOME/dbscripts/ DB_TYPE/migrate (where DB_TYPE is the subdirectory named for the type of database you are migrating; for example, Oracle or Sybase). Consult your database administrator for the procedure.

   Table 2-1 WebLogic Process Integrator Database Migration Scripts

   To migrate WebLogic component 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

3. Migrate the database schema from 2.0 format to WebLogic Integration 2.1 by running the migratedb script. See Migrating Using the WebLogic Integration Database Configuration Wizard in Graphical Mode in Migrating from WebLogic Integration 2.0 (SP 2, 3 and 4) to WebLogic Integration 2.1, for instructions on running this script.

Once you have completed steps 1 through 3, 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 any existing users of your system, you can add them to the WLPI_SUPER_USERS variable in the Migration.properties file, or assign permissions in the Studio client application after migration. For information on 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 upon the version of WebLogic Process Integrator you are migrating and the security realm you have deployed, choose one of these migration procedures:

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 security realm com.bea.wlpi.rdbmsrealm.RDBMSRealm	Use the procedure described in Migrate from RDBMS Realm (WebLogic Process Integrator 1.2 or 1.2.1).
WebLogic Process Integrator 1.2.1 and you deployed the security realm File Realm	Use the procedure described in Migrate from 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 Support for more information.

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

The following procedures assume knowledge of 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 the security realm com.bea.wlpi.rdbmsrealm.RDBMSRealm, use 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 and 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. In the right pane, select wlpiCachingRealm from the Caching Realm drop-down list.

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

12. Verify that the database URL in 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 like this:

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

16. Save the file.

17. Start theWebLogic 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 setting getGroupNewStatement from false to true (that is, getGroupNewStatement=true). For the other database types, this value can be left false.

21. Shut down the WebLogic Server.

22. In the server startup script file, 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 WLI_HOME/dbscripts/ directory and doing one of the following:

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

    • If you are using UNIX, run bpm20_tutorial_enabler.

Migrate from File Realm (WebLogic Process Integrator 1.2.1 Only)

The following procedures assume knowledge of 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, use this procedure:

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 and, 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 fileRealm.properties from the WebLogic Process Integrator 1.2.1 domain into the fileRealm.properties 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. 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.

Assigning Permissions

Once you have migrated your database and security realm, assign permissions to previously existing users and roles. Perform this task with the WebLogic Integration Studio. For information on default permission groups and their member users, and on assigning permissions to users and roles, see Administering Data in Using the WebLogic Integration Studio.