Workspaces and projects created with version 10.0 must be migrated to version 10.x in order for you to use version 10.x to continue developing and testing projects in the workspace. After migration, migrated projects will no longer run in versions prior to 10.x.
During migration, the IDE updates project metadata, moves your facets to version 10.x.
Note: For information on upgrading from version 8.1 to version 10.x, see Upgrading WebLogic Workshop 8.1 Applications.
How to Migrate to Version 10.x
When you open a workspace created with Workshop for WebLogic version 10.0, the IDE will prompt you to migrate projects in the workspace. In addition, you will need to make any changes needed to support the version 10.x domain, such as updating the wl_home value in the domain start scripts.
To Do in Version 10.0 Before Opening in Version 10.x
To avoid errors in version 10.x, you should be sure to do the following with your workspace in version 10.0 before migrating the workspace:
- Close the version 10.0 Workshop perspective if it's open. For details, see Workbench Layout Error Due to Absence of Workshop Perspective.
- Ensure that all projects are open. It's possible to "close" a project in the IDE while leaving it in the workspace. Closed projects might create errors when you open the workspace in version 10.x.
If you want to migrate only certain projects, you can do so by removing the other projects (the ones you'd have closed) from the workspace before migrating (note that you can do so without deleting the removed projects from disk). You can later migrate the removed projects by importing them from the existing workspace.
- Check out all source artifacts from source control. For more information, see Check Out Source Artifacts from Source Control Before Migration.
- All applications must be undeployed before upgrading 10.0 domains in order for the migrated applications to be succesfully redeployed. You may use the WebLogic console to list and remove existing applications.
Changes Related to Migration
Check Out Source Artifacts from Source Control Before Migration
As a best practice, be sure to check out version 10.0 sources before migrating to version 10.x. While source control integration from the IDE will, in most cases, work to check out files that must be writable, in some cases this is not done.
Also make sure that you add new files created in the upgrade process to your source control system. For example, if you are using the Perforce plugin, note that the Perforce Pending Changelists view does not show all of the files created in the upgrade process. For example, the com.bea.workshop.wls.core.prefs which replaces the com.bea.wlw.libmodules.core.prefs file is not added to the view. Make sure to add any new files by selecting Team > Open for Add at the project level. The new .prefs file and any other new files added to the project will be added to the view.
Complete Workspace "Clean" Might Be Required
After migration, you might see errors in your version 10.x workspace. In some cases, you can remove these by performing a complete clean of all projects in the workspace. To do this, click Project > Clean, then in the Clean dialog, select the Clean all projects option and click OK.
Renamed or Moved Libraries are Not Supported for Migration
If you have renamed or moved Oracle-provided library JAR files in your version 10.0 workspace, migration of those libraries might fail. This includes libraries that were provided to support project facets.
How to update jars for projects created in 10.0 using the 'copy jars' option
If your 10.0 project was created using the 'copy jars' option (instead of
the J2EE library option), then no automatic update of the
jars to their 10.x counterparts will be performed.
You will need to manually copy the jars
from the current libraries into your applcation. The current Beehive and
WebLogic libraries are available at:
- BEA_HOME/modules/org.apache.beehive_1.0.2.2/apache-beehive-svn-snapshot/lib
- BEA_HOME/workshop_10.3/weblogic-beehive/lib
- BEA_HOME/wlserver_10.3/server/lib
Auto deployment of new J2EE libraries to a 10.0 domain could lead to a class not found during production deployment
In Workshop 10.1, when a user creates a new target runtime which points to a Workshop for WebLogic 10.0 installation, and develops an application against a domain from that installation, Workshop 10.1 will automatically publish newer versions of library jars for all facets in the application, if newer versions exist.
However when the user deploys the application to the 10.0 domain, the domain may not have access to the newer libraries.
Manually update the 10.0 domain to a 10.1 domain. To upgrade the domain follow the instructions below.
Upgrading Workshop for WebLogic 10.0 to 10.1: manual upgrade of domain may be required
In moving from a Workshop for WebLogic 10.0 or earlier domain to Workshop version 10.1, you should initiate domain upgrade by using the IDE. This will make the updates to the domain so that you will have the latest runtime binaries for Workshop version 10.1. If you are managing the domain of an environment that doesn't have the IDE available (for example a platform in which the IDE is not supported or a deployed server) manual upgrade may be required.
To add the 10.1 versions of the libraries to your domain.
- Manually change the setDomainEnv script to point to the 10.1 binaries.
- Start the server and deploy the following new libraries into the
domain.
beehive-controls-1.0.2.1.ear
beehive-controls-1.0.2.1.war
beehive-netui-1.0.2.1.war -- new
beehive-netui-resources-1.0.2.1.war
jsf-myfaces-1.1.3.war -- new
weblogic-controls-10.1.ear -- new
weblogic-controls-10.1.war -- new
The following topics will help you deploy the libraries using weblogic deployer and weblogic console.
To deploy the libraries using WebLogic Deployer, see Deploying Shared Java EE Libraries and Dependent Applications
To deploy the libraries using the WebLogic Server console, see Install applications and modules
Migrating Workspaces Created in Workshop 10.1
Runtime Behavior for Projects Created in Workshop 10.1
When you open and migrate a workspace created in Workshop version 10.1 in Workshop 10.2, the projects in the workspace continue to be targeted to their original WebLogic Server version 10.0 runtimes. Migration does not automatically re-target projects to a version 10.2 runtime.
By default, new servers created for the workspace will target the original 10.1 runtime. Note in the New Server dialog (File > New > Server) that two runtimes are available in the Server runtime dropdown: the runtime labeled "WebLogic Server v.10.0" refers to the version 10.1 runtime, while the runtime labeled "WebLogic Server v.10.0 (2)" refers to the version 10.2 runtime.
