| Oracle® BPEL Process Manager Installation Guide 10g Release 3 (10.1.3.1.0) for UNIX and Microsoft Windows Part Number B28980-03 |
|
|
View PDF |
| Oracle® BPEL Process Manager Installation Guide 10g Release 3 (10.1.3.1.0) for UNIX and Microsoft Windows Part Number B28980-03 |
|
|
View PDF |
This chapter describes how to migrate from an Oracle BPEL Process Manager release 10.1.2.0.2 installation to release 10.1.3.1.0.
This chapter contains the following sections:
Understanding What is Meant By Oracle BPEL Process Manager Migration
Migration Information for Oracle BPEL Process Manager for OracleAS Middle Tier
An Oracle BPEL Process Manager migration potentially includes the following main tasks:
Migrating BPEL data from the previous release to the current release (for example, from release 10.1.2.0.2 to 10.1.3.1.0) in the same dehydration store database
Migrating BPEL processes and completed process instances
Installing new releases of Oracle Application Server middle tier and Oracle BPEL Process Manager on the same host as was used in the previous release
Loading project files from a previous Oracle JDeveloper release
10g Release 3 (10.1.3.1.0) supports only project migration. No data or process migration is supported.
As of 10g Release 3 (10.1.3.1.0), Oracle JDeveloper is no longer bundled with Oracle BPEL Process Manager. You must install Oracle JDeveloper separately for use with Oracle BPEL Process Manager projects.
Use the companion CD to install Oracle JDeveloper 10.1.3.1 Studio.
You cannot migrate Oracle BPEL Process Manager for OracleAS Middle Tier release 10.1.2.0.2 to 10.1.3.1.0.
Instead, install Oracle BPEL Process Manager for Middle Tier release 10.1.3.1.0 and also install Oracle JDeveloper 10.1.3.1.0. You can then open Oracle JDeveloper 10.1.3.1.0 and point it to the source files of your 10.1.2.0.2 projects. You can redeploy your projects with Oracle JDeveloper or ant and proceed.
Oracle JDeveloper 10.1.2.0.2 projects can be deployed in Oracle JDeveloper 10.1.3.1.0.
Note:
Only 10.1.2.0.2 projects can be migrated.Follow these procedures to use Oracle JDeveloper 10.1.2.0.2 projects in 10.1.3.1.0:
Install Oracle BPEL Process Manager for Developers 10.1.3.1.0 into a new Oracle home directory on the same host as Oracle BPEL Process Manager for Developers 10.1.2.0.2.
Start Oracle BPEL Server 10.1.3.1.0 if it is not currently running.
Start Oracle JDeveloper 10.1.3.1.0 for the first time.
A message appears asking if you want to migrate from a previous release of Oracle JDeveloper.
Click Yes.
The Migrate User Settings window appears.
Click Browse.
Select the Oracle_Home\integration\jdev\jdev\system10.1.2.0.2.nn directory of Oracle BPEL Process Manager for Developers 10.1.2.0.2.
Click Select.
Applicable settings on the Migrate User Settings window are automatically selected.
Click OK.
A message appears that describes details about migrating user settings.
Click OK.
Your 10.1.2.0.2 project files (for example, WSDL, BPEL, bpel.xml, and so on) are loaded into the Applications Navigator of Oracle JDeveloper 10.1.3.1.0.
Note:
If you do not select to migrate your projects from a previous Oracle JDeveloper release, you can still load them into 10.1.3.1.0 by following these procedures:Create a new workspace in Oracle JDeveloper 10.1.3.1.0.
Select Open from the File main menu.
Navigate to the process_name.jpr file of the process you want to open.
Double-click the process_name.jpr file.
Your 10.1.2.0.2 project files are loaded into the Applications Navigator of Oracle JDeveloper 10.1.3.1.0.
This section provides additional information about migrating projects. It contains these topics:
You can continue to use your existing release 10.1.2.0.2 projects that use services (workflow, notification, and sensors) in release 10.1.3.1.0 without modifications to the process. However, you will need to redesign the human workflow portion of the process if you wish to use new 10.1.3.1.0 functionality.
There are two options for deploying 10.1.2.0.2 projects in release 10.1.3.1.0:
Open the project in Oracle JDeveloper 10.1.3.1.0 and redeploy.
See Also:
"Opening Oracle JDeveloper 10.1.2.0.2 Projects in 10.1.3.1.0"
Oracle BPEL Process Manager Developer's Guide for additional detailsabout migrating workflow definitions from 10.1.2 to 10.1.3.1
Manually change the build.xml file in the project to conform to the new 10.1.3.1.0 format, and redeploy.
The JCA adapter WSDLs can be reused in 10.1.3 without any changes. Although there are a number of enhancements in this area, they do not factor into project migration.
However, you will need to pay attention to JCA connection factories, particularly the Database adapter and the AQ adapter, which have significant changes in this release. Both adapters refer exclusively to data source definitions instead of inline connection strings.
In order to migrate, say, a database connection factory, you will need to create a new data source, reflecting the 10.1.2 connection settings, and then create a new connection factory entry referring to this data source.
Similar considerations apply to the AQ adapter.
This section describes miscellaneous migration-related issues. It contains these topics:
To avoid issues that may arise when migrating older projects, adopt the following best practices when migrating 10.1.2.0.2 projects to 10.1.3.1.0:
Create a new project with the same name as the BPEL process.
Copy the project files from the old project and replace them in the right target directories.
Change the port references in WSDL files and bpel.xml (that is, references to WSDL locations) as needed.
Open ear files also in Oracle JDeveloper and redeploy them post-compilation.
If a BPEL process (defined in a file with the .bpel extension) contains the "bpel:exec" extension element containing a language="Java" attribute (note the capitalized "J" in Java), you need to manually change this to lowercase so that it reads language="java".
