Upgrading Applications That Require Proxy Settings for Web Services

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.