|
|
This section includes the following topics:
This document describes the procedures required to upgrade your application environment from BEA WebLogic® Integration 8.1.x and 8.5 x and 9.x to BEA WebLogic® Integration 10.2. An application environment includes applications, the WebLogic domains in which they are deployed, and any application data associated with the domain, and may include external resources, such as database servers, firewalls, load balancers, and LDAP servers.
The WLI environment consists of the:
BEA_HOME\user project\domain_name\. You can configure some attributes related to security, clustering, transaction, and logging.
Before you actually begin the upgrade it is useful to identify all the elements of the WLI environment that require updates. You also need to identify the tools, scripts, templates, and source code that is required to automate the tasks used to create the application environment.
The steps in the upgrade process are as follows:
You have to use Workspace Studio to upgrade 9.x applications to WLI 10.2 as there is no command line utility or Ant task available to update 9.x applications to WLI 10.2.
During the upgrade the following components are also updated:
.jpd, .jpf, .app, .jcs, .jcx, and .jws are changed to .java. All the JPD, DTF, JCX, and JCS Annotations are also updated to the JSR 175 based Annotation model.| Note: | Ensure that WebLogic Integration 8.1.x and 8.5 x application process instances are run to completion in the appropriate environment before they are used in WebLogic Integration 10.2 environment. |
In WLI 9.2, there were several architectural level changes, which were carried forward to WLI 10.2. These changes impact the upgrade process. Table 1-1 lists these changes. For a comprehensive list of new features in this release, see WebLogic Integration 10.2 Release Notes.
| Note: | Table 1-1 does not provide a complete list of new features. As a result of these enhancements, WebLogic Platform 8.1 applications will not be binary-compatible and will require automated or manual changes during an upgrade to WebLogic Integration 10.2. |
The Workspace Studio IDE is now based on Eclipse, 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.2.2 and Eclipse WTP 1.5.4, see
http://www.eclipse.org.
|
||
Workspace Studio 1.1 provides tools to make building applications with Apache Beehive 2.0 easier, including support for:
Apache Beehive is an open-source programming model designed to simplify J2EE programming tasks and is built on J2EE and Struts.
BEA developed Apache Beehive, which evolved from its BEA Workspace Studio product, to provide a simplified development model for all WebLogic applications. For more information about Apache Beehive, see
http://beehive.apache.org.
|
||
The programming model for Web Services, EJBs, Java controls, and Java Page Flows uses the new J2SE 5.0 metadata annotation language (specified by JSR-175). In this programming model, you create a Java file that uses annotations to specify the shape 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.
|
||
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 in WebLogic Web Services: Security.
|
||
WLI supports ALSB control that can invoke ALSB proxies and is deployed as a library on WLS using the
config.xml file.
In order to use the ALSB control you need to include a library reference in the
weblogic-application.xml file as follows:
|
||
WLI supports new standards for XMLBeans and XQuery APIs, as described in
XMLBeans and XQuery Implementations.
|
||
WebLogic Server offers the following enhancements to the structure of the WebLogic domain directory:
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.
|
We recommend that, before proceeding, you familiarize yourself with the following terminology:
.dtf and contain definitions of a data transformation that can be invoked from a JPD. From WLI 9.2, all .dtf files have a .java extension. For more information, see,
Building Your First Data Transformation..jcs. For more information, see,
http://download.oracle.com/docs/cd/E13226_01/workshop/docs81/doc/en/workshop/guide/controls/conGettingStartedWithJavaControls.html.
From WLI 9.2, all .jcs files have a .java extension.
.jcx. For more information, see
http://download.oracle.com/docs/cd/E13226_01/workshop/docs81/doc/en/workshop/guide/devenv/conJwiFiles.html.
From WLI 9.2, all .jcx files have a .java extension.
.jpd files have a .java extension..jsr files have a .java extension..xq. They contain only the XQuery. So, the term XQ could refer to the XQ file or the XQuery itself.
|