17 Using the AIA Migration Utility

This chapter provides an overview and describes how to use the Oracle Application Integration Architecture (AIA) Migration Utility.

The AIA Migration Utility seamlessly migrates AIA 2.4 and 2.5 BPEL and Enterprise Service Bus (ESB) services to AIA Foundation Pack 11g Release 1. The utility leverages the SOA upgrade utility to perform the bulk of the migration tasks and automates most of the pre- and post-migration tasks.

For more information about the SOA upgrade utility, see "Considerations When Upgrading All Oracle SOA Applications" in Oracle Fusion Middleware Upgrade Guide for Oracle SOA Suite, WebCenter, and ADF.

This chapter includes the following sections:

17.1 Overview of the AIA Migration Utility

The following operations are performed by the AIA Migration Utility:

  • Detects the type of service, and depending on whether it is a BPEL process or an ESB process, invokes the appropriate version of the SOA upgrade utility to perform the migration.

  • Updates AIAComponents references in WSDLs and XSDs to point to Oracle Metadata Services (MDS) repository.

  • Updates the AIAAsyncErrorHandlingProcess reference in bpel.xml to point to the AIA Foundation Pack 11g Release 1 error handling service.

  • Updates domain-value map (DVM) and cross-reference (XREF) signatures in XSL files to point to AIAComponents in MDS. This step takes care of updating references to template and function calls in the XSL files used by the process.

  • Inserts annotations in composite.xml.

    Annotations play a significant role in the AIA lifecycle and governance in AIA Foundation Pack 11g Release 1. The AIA Migration Utility injects annotations (empty placeholders) into the migrated composites.

    Depending on whether a process is a Requester Application Business Connector Service (ABCS), Enterprise Business Service (EBS), Provider ABCS, or Adapter service, appropriate annotations are inserted into the composites. The utility uses the process.type variable in AIAMigrationUtility.properties for this purpose.

    As a post-migration task, you must populate appropriate annotation values into the skeletal structure provided by the utility to be able to harvest AIA artifacts into Oracle Enterprise Repository.

For more information about annotation composites for harvesting, see "Annotating Composites" and "Harvesting Oracle AIA Content" in Oracle Fusion Middleware Developer's Guide for Oracle Application Integration Architecture Foundation Pack.

17.2 How to Use the AIA Migration Utility

The AIA Migration Utility is delivered as a part of AIA Foundation Pack 11g Release 1.

To use the AIA Migration Utility:

  1. The AIA Migration Utility is available in the AIA_HOME\utils folder. This is a standalone utility that can be used by unzipping it in any location, whether it is on a server or a developer's machine.

    Figure 17-1 shows the content of the AIA_HOME\utils folder.

    Figure 17-1 AIA HOME/util Folder Content

    This image is described in surrounding text

  2. Update AIAMigrationUtility\AIAMigrationUtility.properties using the values provided in Table 17-1.

    Ensure that your values use only forward slashes "/".

    Table 17-1 AIAMigrationUtility.properties Values

    Property Description

    jdev.home

    Value of JDeveloper home.

    Example for Windows:

    jdev.home= C:/oracle/Middleware/jdeveloper

    Example for Linux:

    jdev.home = /apps/oracle/Middleware/jdeveloper

    Example for ADE:

    jdev.home=/net/adc1006nap.example.com/vol/fade_
adc_txn/.fusionapps_ide/AIA/JDevs/JDEV_
5536/jdeveloper

    service.home

    Location value of the source project.

    Example:

    service.home=D:/Work/11g/workspace/source/Samples
AsyncCreateCustomerSiebelReqABCSImpl
service.home=/slot/ems1739/oracle/workspace/source/ 
sampleapp/SamplesAsyncCreateCustomerSiebelReqABCSImpl

    target.dir

    Location value of the target folder.

    Example:

    target.dir=D:/Work/11g/workspace/destination
service.home=/slot/ems1739/oracle/workspace/
destination

    service.name

    Project name value. If the project name and the service name (BPEL Process Name) are different, then you must provide the service name (BPEL Process Name) value.

    Example:

    service.name=SamplesAsyncCreateCustomerSiebelReq
ABCSImpl

    http.hostname

    Server location where Foundation Pack 11g Release 1 is installed.

    Example:

    http.hostname=ap6014rems.example.com

    http.port

    Server port value.

    Example:

    http.port=8001

    application.name

    Application name that the upgraded project should be a part of.

    Example:

    application.name=sampleapp

    process.type

    Indicates the type of AIA artifact that needs to be migrated. Basically, this property provides empty placeholder annotations within composite.xml. Input to this attribute can be one of the following values: Provider, Requestor, DBAdapter, JMSAdapter, OracleAppsAdapter, EBF, or EBS.Example:

    process.type=Provider

  3. Set the ANT and JDK paths by sourcing aiaenv.sh:

    source <AIA_HOME>/aia_instances/<AIA_INSTANCE>/bin/aiaenv.sh

  4. Invoke the AIAMigrationUtility as follows:

    ant -f AIAMigrationUtility.xml

  5. Open the migrated project in Oracle JDeveloper.

  6. Point to the JPR file created in the project folder to which the service has been migrated. Open the project.