Skip Headers

# Overview

Previous

Next

Before using the TopLink migration tool, review this section to understand how the TopLink migration tool works and to determine what BEA WebLogic persistence manager metadata is, and is not, migrated.

Input and Output

The TopLink migration tool takes the following files as input:

- `weblogic-ejb-jar.xml`

- `weblogic-cmp-rdbms-jar.xml`

It migrates as much BEA WebLogic-specific persistence configuration as possible to a new `toplink-ejb-jar.xml` file and creates the following new files in a target directory you specify:

- `orion-ejb-jar.xml`

- `toplink-ejb-jar.xml`

- TopLink Workbench project file `TLCmpProject.mwp`

The input BEA WebLogic files may be in an EAR, JAR, or just standalone XML files. If you migrate from standalone XML files (rather than an EAR or JAR file), ensure that the domain classes are accessible and included in your classpath.

The TopLink migration tool creates a new `orion-ejb-jar.xml` and `toplink-ejb-jar.xml` file to the target directory you specify in the same format as it reads the original files. For example, if you specify an EAR file as input, then the TopLink migration tool stages and creates a new EAR file that contains both the new `orion-ejb-jar.xml` and the new `toplink-ejb-jar.xml` file, but is otherwise identical to the original.

The TopLink Workbench project file is always created as a separate file.

Note: Oracle recommends that you make a backup copy of your `weblogic-ejb-jar.xml`, `weblogic-cmp-rdbms-jar.xml`, and `toplink-ejb-jar.xml` files before using the TopLink migration tool.

For information on configuring the weblogic-ejb-jar.xml file, see "Configuring the weblogic-ejb-jar.xml File for BEA WebLogic Server".

Migration

As it operates, the TopLink migration tool logs all errors and diagnostic output to a log file named `wls_migration.log` in the output directory. If you use the TopLink migration tool from TopLink Workbench, see also TopLink Workbench log file `oracle.toplink.workbench.log` located in your user home directory (for example, `C:\Documents and Settings\<``user-name``>`).

The TopLink migration tool processes descriptor, mapping, and query information from the input files. It performs the following:

- It builds a TopLink descriptor object for each entity bean and migrates native persistence metadata like mapped tables, primary keys, and mappings for CMP and CMR fields.

- It builds a TopLink mapping object for every CMP and CMR field of an entity bean and migrates native persistence metadata like foreign key references.

- It builds a TopLink query object for each `finder` or `ejbSelect` of an entity bean and migrates persistence metadata like customized query statements.

Table: BEA WebLogic and TopLink Feature Comparison lists BEA WebLogic features and their TopLink equivalents configured by the TopLink migration tool.

BEA WebLogic and TopLink Feature Comparison

Feature | weblogic-cmp-rdbms-jar.xml | toplink-ejb-jar.xml
--- | --- | ---
Direct mapping | Field mapping Table mapping | Direct-to-field
Relational mapping | WebLogic-RDBMS relation | One-to-one One-to-many Many-to-many
Multiple tables | Table mapping | Supported
Read-only | Read-only: concurrency strategy | Supported
Pessimistic locking | Enforce pessimistic concurrency on a per-bean basis | Supported

Large Objects (LOB) support

Map the current field to one of the following:

1. `CLOB` or `BLOB` in an Oracle database

2. `LongString` or `SybaseBinary` in a Sybase database

Supported for Oracle BLOB only

Optimistic locking | Optimistic: concurrency strategy Verify columns: optimistic concurrency strategy | Version Timestamp
Cascade delete | Database cascade delete | Privately owned
Sorting database dependency | Order database operations | unit of work
Lazy loading (fetch group) | Field group | Not supported. Alternatively, you can manually configure the TopLink equivalent, if appropriate (see "Fetch Groups").