Workshop version 10.x provides functionality through which you can use the import wizard to upgrade version 8.1 applications. This wizard makes nearly all of the changes that upgrade a working version 8.1 application to a working version 10.x application. Because the differences between version 8.1 and version 10.x are many, there can be a lot of changes to make. The list of changes made, of course, omits those that would involve rewriting your code or making non-obvious assumptions about what you intend your application to do.
Note: Your version 8.1 application must have been upgraded to SP4, SP5, or SP6 before using the wizard.
Keep in mind that using the import wizard is usually only one part of the upgrade process. Depending on the technologies your application uses, you might find that some preparatory work makes an upgrade process that incorporates the wizard more efficient. Likewise, some work after using the wizard is likely to be needed to get your upgraded application compiling and running. For more at a high level on the upgrade process, see Overview: Upgrading from WebLogic Workshop 8.1.
Note: Due to a known issue with the Sun JVM in which JAR files become locked, when upgrading applications on the Windows operating system there might be intermittent cases when files are left behind in the temp directory after upgrade. If this occurs you should be able to delete the files by first closing the IDE.
You can set defaults for some of the wizard's prompts. This is useful if you intend to upgrade multiple applications with the same settings. Use the following steps to set upgrade defaults:
Note that the settings themselves are described in the import and upgrade procedure below.
Before using the import wizard to upgrade very large applications, consider temporarily increasing the maximum amount of memory that the Java Virtual Machine allows to Workshop. The upgrade process requires a compilation step that potentially includes a large number of files. The recommended maximum memory is 1 gigabyte.
You can increase maximum memory in the following way:
-Xmxvalue with a sufficiently high memory maximum. By default, the launcher initialization file is located here:
For example, if the default setting is
then increase it to
set it to 1 gigabyte).
(When upgrading using the command line, add JVM memory arguments, for example: java -Xms512m -Xmx1024m.)
After you've finished using the upgrade tools, set the memory maximum back to a level that's appropriate for development.
While it is possible to deselect projects and so omit them from the upgrade, note that build and visibility dependencies between deselected projects and selected projects will be lost. You will need to manually reset these dependencies if you choose to upgrade the deselected projects at a later time.
Error handling options:
Message verbosity options:
For important information about upgrade and JSP tags, be sure to read about upgrading JSP tags in Upgrading Page Flows before upgrading JSP tags. Many of the NetUI custom JSP tags that were part of WebLogic Workshop 8.1 were donated to the Apache Beehive open source project. The latest versions of these tags are now in the Beehive project. Select this check box to have the version 8.1 tags in your upgraded projects replaced with the current tags.