Overview

This document describes the procedures required to upgrade your application environment to BEA WebLogic Integration 9.2 or 9.2 MP1 from:

An application environment includes applications, the WebLogic domains in which they are deployed, and any application data associated with the domains. It may also include external resources, such as database servers, firewalls, load balancers, and LDAP servers.

Terminology Used in This Document

We recommend that, before proceeding, you familiarize yourself with the following terminology:

Compatibility—The capability of an application built using one release or service pack to run in another release or service pack, with or without rebuilding the application.
DTF—Data Transformation File. DTF files have an extension of .dtf and contain definitions of a data transformation that can be invoked from a JPD. For more information on data transformation, see, http://download.oracle.com/docs/cd/E13226_01/workshop/docs81/doc/en/integration/dttutorial/tutWLIDataTransIntro.html
IDE—Integrated Development Environment. This refers to the BEA Workshop for WebLogic Platform development environment based on Eclipse, which is a development platform that blends open source and commercial software, and is standards-based.
Interoperability

The capability of an application deployed in one release or service pack to communicate with another application that is deployed in a different release or service pack.
The capability of BEA WebLogic Platform^™ components to communicate with third-party software over standard protocols.

JCS—Java Control Source file. JCS files have an extension of .jcs. For more information, see, http://download.oracle.com/docs/cd/E13226_01/workshop/docs81/doc/en/workshop/guide/controls/conGettingStartedWithJavaControls.html.
JCX—Java Control Extension file. JCX files have an extension of .jcx. For more information, see http://download.oracle.com/docs/cd/E13226_01/workshop/docs81/doc/en/workshop/guide/devenv/conJwiFiles.html.
JPD—A Java Process defined in a Process Definition for a Java file.
JSR—A Java Specification Request. For more information, see http://jcp.org/en/jsr/overview.
Migrate—To move an application or domain configuration from a third-party product to a BEA product.
Upgrade—To upgrade your JPD 8.1 source and related files to JPD 9.2 artifacts.
XQ—A short form for XQuery in some cases. XQuery files on Weblogic Platform have an extension of .xq. They contain only the XQuery. So, the term XQ could refer to the XQ file or the XQuery itself.

What's New that Impacts the Upgrade Process

Table 1-1 introduces a subset of enhancements being introduced in WebLogic Integration 9.2 and 9.2 MP1 that impact the upgrade process. For a complete list of new features in this release, see WebLogic Integration 9.2 Release Notes.

Table 1-1 What's New that Impacts the Upgrade Process
Enhancement	Description
Library Modules 9.2.1	The version of library modules in 9.2 GA was 9.2.0 and references to it in `config.xml` need to be updated. After upgrading to 9.2 MP1, you must run the domain upgrade tool as described in Upgrading Domains to Version 9.2 MP1, at http://download.oracle.com/docs/cd/E13218_01/wlp/docs92/upgrade/upgrade_domain_mp1.html to update the reference to library modules in `config.xml` to point to version 9.2.1.
Eclipse-based IDE	The BEA Workshop for WebLogic Platform 9.2 IDE is now based on Eclipse 3.1.2, delivering a software development platform that blends open source and commercial software, and is standards-based. The IDE provides access to core Eclipse features, such as source editing, jUnit test integration, and refactoring. It also includes a robust tool set available from the Eclipse Web Tools Platform (WTP) 1.0 project, including server plug-ins for multiple runtimes. For more information about Eclipse 3.1.2 and Eclipse WTP 1.0, see http://www.eclipse.org. In WebLogic Integration 9.2, the IDE delivers design views for developing JPDs. Additional design views to support Web Service and Java control development will be provided in later releases of WLI 9.2. Note: In February 2005, BEA joined the Eclipse Foundation as a Strategic Developer and Board Member to further its commitment to open source and standards organizations.
Apache Beehive 2.0	BEA Workshop for WebLogic Platform 9.2 provides tools to make building applications with Apache Beehive 2.0 easier, including support for: Java controls—based on Plain Old Java Objects (POJO) architecture. NetUI—based on Struts, and including Page Flows and JSP tags. Apache Beehive is an open-source programming model designed to simplify J2EE programming tasks and is built on J2EE and Struts. BEA enhanced Beehive, which evolved from its BEA Workshop for WebLogic Platform product, to provide a simplified development model for all WebLogic applications. For more information about Apache Beehive, see http://beehive.apache.org.
Metadata Annotations	The programming model for Web Services, EJBs, Java controls, and Java Page Flows uses the new J2SE 5.0 metadata annotation language (specified in JSR-175). In this programming model, you create a Java file that uses annotations to specify the structure and characteristics of the component. From these annotations, the compiler takes care of generating the required supporting artifacts, including Java source code, deployment descriptors, and so on. The annotations that you can specify include: Web Service annotations defined Web Services Metadata for the Java Platform specification (JSR-181). For more information, see http://www.jcp.org/en/jsr/detail?id=181. EJB annotations as defined in EJBGen Reference in Programming WebLogic Enterprise JavaBeans. Java control and NetUI (Page Flow) annotations as defined in Apache Beehive 2.0. For more information, see http://beehive.apache.org. WebLogic-specific annotations to support security policy configuration, asynchronous failure and response, and conversational Web Service support. For more information, see Programming the JWS File in Programming Web Services for WebLogic Server.
Web Service Policy Framework	Security and authentication configuration has been enhanced to use the standards-based Web Services Policy Framework (WS-Policy), as described in Configuring Message-Level Security for Web Services.
XMLBean and XQuery API Standards	WebLogic 9.2 supports new standards for XMLBeans and XQuery APIs, as described in XMLBeans and XQuery Implementations.
Changes in Directory Structure	WebLogic Server 9.2 offers the following enhancements to the structure of the WebLogic domain directory: To improve configuration management and promote XML file validation, WebLogic Server supports the specification of domain configuration data in multiple files, including `config.xml` in the new <`domain_name>/config` directory. (Here, `domain_name` specifies the domain directory.) In previous releases, the `config.xml` file was the repository for all configuration information. In WebLogic Integration 9.2, new subdirectories of the `config` directory maintain configuration modules for diagnostic, JDBC, JMS, Node Manager, and security subsystems. Each configuration file adheres to an XML Schema definition. Startup and shutdown scripts are maintained in the `domain_name/bin` directory. In previous releases, they were stored in the root directory of the domain. In addition to the structural enhancements to the domain directory, WebLogic Server supports new utilities for managing changes to server configuration. These new tools enable you to implement a secure, predictable means for distributing configuration changes in a domain. For more information, see Understanding Domain Configuration.

The Upgrade Process

WebLogic Integration allows you to upgrade using any one of the following methods:

At a high-level, the steps involved in upgrading from WebLogic Integration 8.x to WebLogic Integration 9.2 or 9.2 MP1 are:

Use the Upgrade Wizard, or the upgradeStarter command or the upgrade Ant task to upgrade WebLogic Integration 8.x.
Use the WebLogic Upgrade Wizard to upgrade the domain. The Wizard updates the directory structure, and the following to WebLogic Integration 9.2 or 9.2 MP1:

WebLogic Domain
Domain Database Tables
Custom Security Providers
Node Managers
For 9.2 MP1, run the upgrade tool to modify config.xml to point to 9.2.1 libraries.

Upgrade External resources such as Firewalls, Load Balancers, Databases, and LDAP servers. For example, Apache 1.3 should be upgraded to 2.0 and Oracle 8.1.7 should be upgraded to Oracle 9i to function with WebLogic Integration 9.2.
Check and compare the supported configurations for WebLogic Integration 9.x and 8.x and ensure that the configurations are upgraded to match version 9.x specifications.
Use the Application Upgrade tool to upgrade the Application Source. You can run the tool from the Eclipse IDE or the command line. The Eclipse plug-in is an extension to the BEA Workshop for WebLogic Platform framework. It updates the:

Project model
Application source code
WebLogic Integration 8.x artifacts such as JPD, DTF/XQuery, JCX Controls and JCS files to WebLogic Integration 9.2 standards. It changes all file extensions such as .jpd, .jpf, .app, .jcs, .jcx, and .jws to .java. It also updates all JPD, DTF, JCX, and JCS Annotations to the JSR 175 based Annotation model.
Optionally, upgrade XQuery 2002 files to XQuery 2004. You may require to update these files manually.

If required, you need to manually upgrade application components.

Note:

Ensure that WebLogic Integration 8.x application process instances are run to completion in the appropriate environment before they are used in WebLogic Integration 9.2 environment.

You need to recompile and redeploy the applications once the upgrade is complete.

Upgrade Guide

Overview

Scope of this Document

Terminology Used in This Document

What's New that Impacts the Upgrade Process

The Upgrade Process