9-6 Oracle Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter, and ADF
9.3.1.2 Upgrading to the Oracle Fusion Middleware Infrastructure Management Java API for Oracle SOA Suite
Oracle SOA Suite 11g introduces a new infrastructure management API that replaces several other APIs previously available in Oracle SOA Suite 10g.
For more information about the new API, refer to the Oracle Fusion Middleware Release Notes, which are available as part of the Oracle Fusion Middleware 11g documentation
library.
9.3.2 Reviewing Your Projects for Dependent JAR Files
If you are upgrading an Oracle SOA Suite application that depends upon references to custom JAR file libraries. note that these references may not get upgraded
automatically when you open and upgrade your application in Oracle JDeveloper 11g.
As a result, you should review your projects for these types of dependencies and, after the upgrade, make sure that you add any missing references, by selecting the
Libraries and Classpath
link in the Oracle JDeveloper 11g Project Properties dialog.
9.3.3 Upgrading Applications That Require Proxy Settings for Web Services
If you are upgrading an application that uses Web services resources outside your company firewall, you must modify a configuration file that will enable the upgrade to
accesses proxy settings and adjust them accordingly during the upgrade of the application.
To configure Oracle JDeveloper 11g to use the proxies during the upgrade process:
1.
Locate the following file in the JDEV_HOMEbin directory: ant-sca-upgrade.xml
2.
Edit the file and modify the following settings to identify the proxy server and port required to resolve the Web services addresses for the applications you are
upgrading.
jvmarg value=-Dhttp.proxySet=true jvmarg value=-Dhttp.proxyHost=PROXY_SERVER
jvmarg value=-Dhttp.proxyPort=PROXY_PORT
Note that there are two locations in the file to modify these settings. One location is used to set the proxy when you are upgrading an ESB project to Oracle Mediator
11g; the other is used when you are upgrading Oracle BPEL Process Manager projects.
3.
Stop and start Oracle JDeveloper 11g so your changes can take effect and then open and upgrade your application in Oracle JDeveloper 11g.
9.3.4 Recreating build.xml and build.properties Files Not Upgraded by the Migration Wizard
When you open and upgrade an application in Oracle JDeveloper 11g, the build.xml and build.properties files associated with your application projects are not
upgraded.
Instead, you must recreate these files in Oracle JDeveloper 11g after the upgrade.
Considerations When Upgrading All Oracle SOA Applications 9-7
9.3.5 Upgrading Projects That Use UDDI-Registered Resources
The following information is important if any of your Oracle BPEL Process Manager or Oracle Enterprise Service Bus 10g projects use remote resources that are registered in a
UDDI Universal Description, Discover and Integration registry, such as Oracle Service Registry OSR.
Refer to the following for more information:
■
Verifying that serviceKey Endpoints Are Available Before Upgrade
■
Changing to the orauddi Protocol
9.3.5.1 Verifying that serviceKey Endpoints Are Available Before Upgrade
If you have a 10g Release 3 10.1.3 project that references an endpoint URL that uses a serviceKey from OSR, then you must be sure that the endpoint URL is up and
available when you upgrade the application. Otherwise, the upgrade of the application will fail. To prevent such a failure, verify that the endpoint URLs are
available, and if necessary, modify the endpoint URLs in bpel.xml or the routing service to point to new URL which is accessible.
9.3.5.2 Changing to the orauddi Protocol
In Oracle Application Server 10g Release 3 10.1.3, Oracle BPEL Process Manager and Oracle Enterprise Service Bus projects used the uddi protocol to obtain resource
references from OSR. In Oracle Fusion Middleware 11g, Oracle BPEL Process Manager and Oracle Mediator projects use the orauddi protocol.
As a result, prior to upgrading your Oracle BPEL Process Manager or Oracle Enterprise Service Bus projects, you must do the following:
1.
Use the service registry to modify the registered service so it uses the new bindings supported by Oracle Fusion Middleware 11g.
For example, in OSR, do the following:
a.
Log in to your Oracle Service Registry.
b. On the Search tab, click Businesses.
c. Click Add Name to search for a business by name.
d.
From the search results, click the name of the business you want to modify.
e.
In the left pane of the View Business page, right-click the service you want to modify and select Add Binding from the context menu.
f. From the Type drop-down menu on the Add Binding page, select
wsdlDeployment
.
g. In the Access Point field, enter the URL.
For example: http:machine:portProj_ep?WSDL
h. Click Add Binding.
i. Click Save Changes.
2.
Open and upgrade the application in Oracle JDeveloper 11g.
3.
In Oracle JDeveloper, edit the composite.xml file for the upgraded project and configure the endpoint URL using the UDDI Registry option on the Resource
Palette.
9-8 Oracle Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter, and ADF
For more information about the UDDI registry, visit the following URL: http:www.oracle.comtechnologytechsoauddiindex.html
9.3.6 Understanding File Naming Conventions in Oracle SOA Suite 11g
Note that before you upgrade a SOA composite application, verify that the name of the the application or project does not start with a number.
For example, if you attempt to upgrade a 10g sample application called 110.JMStoJMSHeaders, Oracle JDeveloper displays a grammar validation error
when you attempt to open the composite.xml.
To work around this problem, simply rename the application and remove the number before you upgrade the application.
9.3.7 Using the Oracle SOA Suite Command-Line Upgrade Tool
The following sections describe how to use the Oracle SOA Suite command-line upgrade tool:
■
Benefits of Using the Oracle SOA Suite Command-Line Upgrade Tool
■
Using the Oracle SOA Suite Command-Line Upgrade Tool with Oracle JDeveloper 11g
■
Limitations When Upgrading Human Workflow Applications with the Oracle SOA Suite Command-Line Upgrade Tool
■
Upgrading BPEL or ESB Projects with the Oracle SOA Suite Command-Line Upgrade Tool
■
Combining Multiple BPEL Projects Into a Single Composite with the Oracle SOA Suite Command-Line Upgrade Tool
■
Upgrading Oracle Enterprise Service Bus ESB Projects with the Oracle SOA Suite Command-Line Upgrade Tool
■
Upgrading Domain Value Maps DVMs and Cross References XREFs in the ESB Repository
9.3.7.1 Benefits of Using the Oracle SOA Suite Command-Line Upgrade Tool
The Oracle SOA Suite Command-Line Upgrade Tool has the following benefits:
■
You can use the command-line tool to automate your application upgrade work, using scripts or other command-line automation tools.
■
The command-line tool upgrades both Oracle BPEL Process Manager projects, and upgrades Oracle Enterprise Service Bus 10g projects to Oracle Mediator 11g.
■
With the command-line tool, you can merge BPEL projects together and create a single composite out of multiple BPEL projects. This is not possible when you use
the Oracle JDeveloper Migration Wizard.
■
The functionality is exactly the same as the JDeveloper mode when it comes to dealing with SOA project contents because the same codebase is used.
9.3.7.2 Using the Oracle SOA Suite Command-Line Upgrade Tool with Oracle JDeveloper 11g
The Oracle SOA Suite Command-Line Upgrade Tool is compatible with restrictions with the Oracle JDeveloper Migration Wizard. In other words, you can choose to
Considerations When Upgrading All Oracle SOA Applications 9-9
remain in command-line mode all the way through the upgrade process upgrade, compile, package, and deploy, or you can choose to move to Oracle JDeveloper, or
you use both tools, with no functionality loss.
However, it is important to note that the command-line tool upgrades SOA project artifacts only. Other Oracle JDeveloper artifacts for example, the .jpr and .jws files
are ignored.
To work around this restriction, note the following:
■
The Oracle SOA Suite Command-Line Upgrade Tool copies files from the BPEL suitcase directory the BPEL subdirectory or the directory hosting the BPEL files
to the specified target directory, specified on the command line.
■
The above copying action does not copy the .jpr or .jws files. After the upgrade, the target directory contains only the upgraded SOA project contents.
■
To remedy this problem in Oracle JDeveloper, you can create a new application or new project, and then define the project directory to be the newly upgraded
composite directory.
9.3.7.3 Limitations When Upgrading Human Workflow Applications with the Oracle SOA Suite Command-Line Upgrade Tool
If you attempt to use the Oracle SOA Suite Command-Line Upgrade Tool to upgrade an application that contains Oracle Human Workflow projects, note that the tool will
create a separate project for each upgraded task form.
This resulting project is an Oracle ADF project and Oracle ADF does not support command line deployment. As a result, after using the Oracle SOA Suite
Command-Line Upgrade Tool, you must open the upgraded projects in Oracle JDeveloper 11g deploy it from JDeveloper.
For information about how to open the upgraded project in Oracle JDeveloper, see Chapter 9.3.7.2, Using the Oracle SOA Suite Command-Line Upgrade Tool with
Oracle JDeveloper 11g .
9.3.7.4 Upgrading BPEL or ESB Projects with the Oracle SOA Suite Command-Line Upgrade Tool
The files required to run the Oracle SOA Suite Command-Line Upgrade Tool are installed automatically when you install Oracle JDeveloper 11g and when you install
Oracle SOA Suite 11g:
■
When you install the Oracle SOA Suite 11g, the required XML files are installed in the bin directory of the Oracle SOA Suite Oracle home.
■
When you install Oracle JDeveloper 11g, the required XML files are installed in the bin directory of the Oracle JDeveloper home.
You can use this files in this directory, together with Apache Ant, to migrate your 10g Release 3 10.1.3 SOA projects to 11g.
Note: For the purposes of this procedure, it is assumed you are
running the Oracle SOA Suite Command-Line Upgrade Tool from the Oracle home of an Oracle SOA Suite installation.
If you are running it from a Oracle JDeveloper home, replace ORACLE_HOME with JDEV_HOME in the following procedures.
