|
|
This document provides information on upgrading from WebLogic Integration™ 8.1 to WebLogic Integration 9.2 or 9.2 MP1. Topics discussed include:
Before beginning the upgrade process, read Upgrading WebLogic Application Environments. This guide describes the procedures to upgrade your application environment to WebLogic 9.2. An application environment includes applications, the WebLogic domains in which they are deployed, any application data associated with the domain, and may include external resources, such as database servers, firewalls, load balancers, and LDAP servers.
WebLogic Integration 9.2 Upgrade Wizard allows you to upgrade domains created only in WebLogic Integration 8.1 SP4, 8.1 SP5, 8.1 SP6, 8.5, 8.5 SP5 and 8.5 SP6 (also referred to as 8.1.x and 8.5.x in this document).
At a high-level, the steps performed by the wizard during a domain upgrade are as follows:
file store, WseeFileStore, and the JMS server, WseeJmsServer, and its associated JMS module.JWSQueueTransport EJB, if it is present in the domain.P13n) applications. See also WebLogic Integration 9.2.1 library modules.SQLAuthenticator security provider to the domain. | Note: | Users portaladmin and weblogic are added to the SQLAuthenticator security provider. You can remove these users from the DefaultAuthenticator security provider after the domain is upgraded. |
pointbase.ini file is updated to set database.home, documentation.home and pbembedded.lic for PointBase v5.1. weblogic_eval and the associated datasource JDBC driver URLs accordingly fixed.
The PointBase related environment settings are carried over to the upgraded domain scripts, setDomainEnv.cmd and setDomainEnv.sh.
You may encounter an error in Linux while running the upgrade script. The steps to fix this error are as follows:
For more information on the domain upgrade process and things you need to keep in mind during upgrade, see Upgrading a WebLogic Domain available at the following URL: http://download.oracle.com/docs/cd/E13179_01/common/docs92/upgrade/upgrade_dom.html
WebLogic Integration 9.2 provides a set of utilities that allow you to upgrade your 8.1.x or 8.5.x includes applications to 9.2. This section describes how to upgrade applications built using WebLogic Integration.
Note that during upgrade, the logic and intent of the application is not altered. WebLogic Integration simply migrates the code to make it compatible with 9.2. This would involve changes such as making the applications compatible with the Eclipse framework and converting Javadoc annotations to JSR 175 compliant annotations, among others.
Application upgrade is a three-step process:
You can choose to upgrade your user applications using the Import Wizard or the Command Line utility—both provided by BEA Workshop for WebLogic Platform. Alternatively, you could use an Ant task. The subsequent sections describe these methods.
| Notes: |
weblogic-application.xml file.You can use the Import Wizard provided by BEA Workshop for WebLogic Platform to upgrade your applications to 9.2. The wizard does not alter the logic and intent of the existing 8.1 applications, nor extract the applications from any source repository. It migrates the 8.1 source artifacts into the 9.2 source and project model. However, it retains the 8.1 Javadoc annotations as they do not require any special processing in 9.2. These annotations are also retained to facilitate any manual processing that may be required after upgrading the application.
The following are some of the tasks executed by the import wizard:
src directory.| Note: | When you upgrade an 8.x application with an EJB or non-web or non-utility project that uses JPD or Process Proxy to make an RMI call to the JPD, do not add a process facet to all the non-web or non-utility projects. Instead, add the Library (Process Libraries) to the project's java build path as follows: |
BEA Workshop for WebLogic Platform also provides a command line utility that converts the entire application to work with WebLogic Integration 9.2.
The utility does not check out or delete files. It also does not check in the newly upgraded files automatically. It just copies the essential files over to the WebLogic Workshop 9.2 workspace for migration.
| Note: | When you run the command line utility, use JRE 1.5. Ensure that the classpath includes <%ECLIPSE_HOME%>/startup.jar. |
The command to upgrade your application is as follows:
java -cp %ECLIPSE_HOME%/startup.jar
-Dwlw.application=%WORK_FILE%
-Dweblogic.home=%WL_HOME%
org.eclipse.core.launcher.Main
-application com.bea.wlw.upgrade.upgradeStarter
-data %WORKSPACE%
-pluginCustomization %PREFS_FILE%
You can use the Ant task to upgrade to WebLogic Integration 9.2.
The command line upgrade contains an Ant task. You can locate the class of the Ant task in the wlw-upgrade.jar, deployed in the ./<WORKSHOP_HOME>/eclipse/plugins/com.bea.wlw.upgrade_9.2.0 folder.
| Note: | When you run the Ant task, ensure that the <%ECLIPSE_HOME%>/startup.jar is on the classpath of the task, as specified by the classpathref attribute in the following sample Ant task. |
A following sample shows how you can invoke an Ant task:
<target name="workshopUpgrade">
<echo message="${workshop.home}/eclipse"/>
<path id="eclipse.classpath"> <fileset dir="${workshop.home}/eclipse/plugins"
includes="com.bea.wlw.**/wlw-upgrade.jar"/> </path> <taskdef name="upgradeTask"
classname="com.bea.wlw.upgrade.cmdline.UpgradeTask"
classpathref="eclipse.classpath"/><upgradeTask data=%WORKSPACE%
eclipseHome=%ECLIPSE_HOME%
weblogicHome=%WL_HOME%
pluginCustomization=%PREFS_FILE%
wlwApplication=%WORK_FILE%/>
WebLogic Integration 9.2 generates a log of the upgrade changes, errors, and warnings, irrespective of the upgrade process you choose. If you use the wizard, this log is displayed in a dialog that you can review before the process is complete.
The log file is generated after the upgrade is completed and it is saved as:
<UPGRADE_WORKSPACE_HOME>\.metadata\upgrade.log
A log message in the file appears as follows:
!SUBENTRY 1 com.bea.wlw.upgrade severity_level date time
!MESSAGE Upgrade-related message.
The severity level contains two numbers with the same meaning. The date and time entries specify when the upgrade was attempted. The upgrade-related message describes the action, the warning logged, or the error that occurred. The following are two log entries:
!SUBENTRY 1 com.bea.wlw.upgrade 2 2 2006-02-27 17:17:53.687
!MESSAGE The 9.2 control context only supports a subset of the 8.1 control context APIs. Please see the Workshop for WebLogic upgrade documentation for more information.
!SUBENTRY 1 com.bea.wlw.upgrade 1 1 2006-02-27 17:17:53.687
!MESSAGE The import "com.bea.control.JwsContext" needs to be updated.
You might encounter certain outages while trying to deploy your upgraded application. For information on outages, see the Known Limitations section, in WebLogic Integration Release Notes.
When you are upgrading stateful JPD applications from WebLogic Integration 9.2.0.0 or 9.2.1.0 to 9.2.2.0 you could encounter the following error:
java.io.InvalidClassException: javax.xml.namespace.QName; local class
incompatible: stream classdesc serialVersionUID = 4418622981026545151, local class serialVersionUID = -9120448754896609940
This issue is due to a known bug in the JDK.
After upgrading the domain, before you restart the server, the suggested solution for systems running on:
Add the flag: -Dcom.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0 to the JAVA_OPTIONS variable in the startWeblogic.cmd file, located under the domain_home\bin directory to ensure a successful running process. Modify set JAVA_OPTIONS=%SAVE_JAVA_OPTIONS%
set JAVA_OPTIONS=%SAVE_JAVA_OPTIONS%
-Dcom.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0
-Dcom.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0"
After the upgrade is complete, you can optionally build and deploy the upgraded application to verify if the upgrade is successful. You can ensure that the required files have been moved or are available in the correct locations as follows:
|