|
Migrating from JRun 3.x
JRun provides a migration tool for migrating JRun 3.x servers and configuration settings to JRun 4. Although you can deploy JRun 3.x J2EE modules in JRun 4 without using the migration tool, the tool exports many of the settings on which modules depend.
Note: Before deploying a JRun 3.x web application in JRun 4, you must delete all compiled JSP classes from the web application WEB-INF/jsp directory. You must also delete the corresponding .java source files.
The migration tool does not migrate the following items:
 |
JRun 3.0 EJBs; you can migrate JRun 3.1 EJBs |
|
java:comp as the prefix for JNDI lookups; see JRun Administrator's Guide for JRun 4 JNDI naming conventions |
|
Launcher classpath settings |
|
Dependencies on JRun 3.x-specific classes |
|
The wildcard character (*) in the users.properties file |
|
Logging settings |
|
JavaMail settings |
|
JMS settings |
|
Advanced global.properties and local.properties overrides |
For more information, see the Property migration chart.
For more information about JRun 4 configuration, see JRun Administrator's Guide and JRun Assembly and Deployment Guide.
Before upgrading to JRun 4
Before running the migration tool, perform the following steps:
|
Ensure that your JRun 3.1 servers are valid before migrating them to JRun 4. |
|
Back up your JRun 3.1 project directories. |
|
In your JRun 3.1 applications, ensure that the WEB_INF/jsp directory is empty. |
Running the migration tool
The JRun 4 migration tool makes it easy for you to upgrade JRun 3.x servers and configuration settings to JRun 4. The tool migrates all servers and applications, and generates a summary report, migration.html, located in the root directory of your JRun 4 installation (jrun_root).
To use the migration tool:
| 1 |
At a command prompt, change to the jrun_root/bin directory of your JRun 4 installation. |
| 2 |
Enter the following command:
where jrun3.x_root is the root directory of a JRun 3.1 installation. |
| 3 |
After successfully running the migration tool, open the jrun_root/migration.html file in a web browser. |
|
The migration.html page is a migration activity report that indicates what the tool successfully migrated and what it could not migrate. |
 |
|
| 
