Flawlessly upgrading to AIA Foundation Pack 11g

The latest release of the Oracle AIA Foundation Pack 11g is 11.1.1.4.

The AIA product development team has done a good job of ensuring that upgrading from AIA Foundation Pack 2.x to AIA Foundation Pack 11g is smooth. From an infrastructure perspective, this is not an in-place upgrade, so a completely new installation of AIA Foundation Pack 11g is required. Your SOA code will need to be modified accordingly to point to the new AIA Foundation Pack 11g environment and artifacts.

Based on a recent implementation, I can attest that modifying your code to take advantage of the upgraded AIA Foundation Pack 11g features and capabilities resulted in no broken code or rewrites needed.

CAVS Simulator

1. Simply modify the hostname and port from the 10g server to the 11g one. No other changes are needed.

10g:

http://soa10gserver:7777/AIAValidationSystemServlet/asyncrequestrecipient?wsdl

11g:

http://soa11gserver:8001/AIAValidationSystemServlet/asyncrequestrecipient?wsdl

CAVS Test Definitions

1. Log in to the AIA 2.x Console at http://soa10gserver:7777/AIA
2. Under 'Validation System', click "Go"
3. Export your CAVS test definitions
4. Navigate to the AIA 11g Console at http://soa11gserver:8001/AIA
5. Log in as the "weblogic" user (must have the 'AIAApplicationUser' group)
6. Under 'Composite Application Validation System', click on "Go"
7. Under the "Definitions" tab, select "Import", and choose the files to be imported

AIA System and AIA Error Notification

1. Log in to the AIA 2.x Console at http://soa10gserver:7777/AIA
2. Under 'Setup', click on "Go"
3. Click on "System"
4. Note all settings
5. Navigate to the AIA 11g Console at http://soa11gserver:8001/AIA
6. Log in as the "weblogic" user (must have the 'AIAApplicationUser' group)
7. Under 'Setup', click on "Go"
8. Click on "System", click on "Create", and use the values captured from the old environment
9. Click on "Error Notification", click on "Create", and use the values captured from the old environment

Async Error Handling BPEL Process

1. If any SOA code is using the the AIA Async Error Handling BPEL Process, modify the partner link urls as follows:

10g:

http://soa10gserver:7777/orabpel/default/AIAAsyncErrorHandlingBPELProcess/1.0/AIAAsyncErrorHandlingBPELProcess?wsdl

11g:

http://soa11gserver:8001/soa-infra/services/default/AIAAsyncErrorHandlingBPELProcess/client?WSDL

DVMs

1. If your code is using any of the DVMs, simply modify the lookup function and the DVM name as follows:

10g:

orcl:lookup-dvm ("CURRENCY_CODE", "Currency", "USD", "External", "Y")

11g:

dvm:lookupValue ("oramds:/apps/AIAMetaData/dvm/CURRENCY_CODE.dvm", "Currency", "USD", "External", "Y")

AIA Fault Policy

1. Simply add the AIA fault policy and bindings to the composite.xml immediately after the </service> closing element for each composite project you want it to apply to as follows:

<property name="oracle.composite.faultPolicyFile">

  oramds:/apps/AIAMetaData/faultPolicies/fault-policy.xml

</property>

<property name="oracle.composite.faultBindingFile">

  oramds:/apps/AIAMetaData/faultPolicies/fault-bindings.xml

</property>

AIAComponents (EBOs, EBMs, and WSDLs)

1. If you are importing EBOs, EBMs, or WSDLs in your code from AIA Foundation Pack 2.x, then update those references to import those objects from the MDS accordingly. For example:

10g:

<schema import="http://soa10gdev:77777/AIAComponents/EnterpriseObjectLibrary/Core/EBO/CustomerParty/V2/CustomerPartyEBM.xsd">

11g:

<schema import="oramds:/apps/AIAMetaData/AIAComponents/EnterpriseObjectLibrary/Core/EBO/CustomerParty/V2/CustomerPartyEBM.xsd">

XREF

1. Haven't done this, so can't speak to it.


Congratulations to the AIA product development team for making the upgrade flawless.