Preparing the Application Server to Run Migrated Applications

You must make some changes to the configuration of the Application Server to enable it to run the migrated applications. These changes enable the Application Server to recognize the runtime compatibility libraries that are distributed with the Migration Tool. The following section discusses this modification.

Appending the Runtime Library to the CLASSPATH of the Application Server

Complete the following steps for Windows, Solaris, and Linux:

Open the <install_dir>/domains/domain1/config/domain.xml

Find the element "classpath-suffix" under the <java-config> tag.
Add <INSTALL_DIR>/asmt/lib/asmt-rt.jar and <INSTALL_DIR>/asmt/lib/classes12.zip, then save and exit the file.

You can download classes.zip from URL http://download.oracle.com/otn/utilities_drivers/jdbc/817/classes12.zip.

Reconfigure the server to keep manual changes:

asadmin reconfig --user admin --password password --host localhost --port 4848 --keepmanualchanges=true server

Restart the Application Server.

Installing a Session Bean to Provide WebLogic 5.1 Proprietary Scheduling Services

WebLogic 5.1 provides scheduling services to deployed applications. The Migration Tool provides equivalent services on the Application Server to support migrated applications that use this feature.

There are two EAR files in the <INSTALL_DIR>/asmt/util directory: Scheduler6.ear and Scheduler7.ear. Each EAR file contains two session beans that must be deployed on the Application Server before you can use the Migration Tool to migrate applications that use these services from Weblogic 5.1 and before you can deploy the migrated application(s).

Run the appropriate script, Scheduler7.cmd (Windows) or Scheduler7.sh (Solaris, Linux), to deploy the Scheduler7.ear archive to the Application Server:

Scheduler7 <password>

where password is the password for the admin user of the Application Server.

Start of Help