deltalounge

For the first time I had to make an integration to a service that had no WSDL deployed with it. Since the (SCA) Composite assumes a WSDL it takes some time to figure out how to realise this. Under default conditions a Reference in a (SCA) Composite in SOA Suite 11g looks something like:

<reference ui:wsdlLocation="SomeDataRef.wsdl"
                   name="SomeDataWebService">
  <interface.wsdl interface="http://ws.deltalounge.net/SomeDataService#wsdl.interface(SomeData)"
                  callbackInterface="http://ws.deltalounge.net/#wsdl.interface(SomeData)"/>
  <binding.ws port="http://ws.deltalounge.net/#wsdl.endpoint(SomeDataService/SomeData_pt)"
              location="http://ws.deltalounge.net/tstservices/SomeDataService?wsdl" />

The location of the binding.ws points to a WSDL. Which is no problem at compile time. However at runtime the WSDL can not be found and an error is raised.
This error can be prevented by pointing to the endpoint instead of to the WSDL. To accomplish this your Reference in a (SCA) Composite in SOA Suite 11g would look something like:

<reference ui:wsdlLocation="SomeDataRef.wsdl"
                   name="SomeDataWebService">
  <interface.wsdl interface="http://ws.deltalounge.net/SomeDataService#wsdl.interface(SomeData)"
                  callbackInterface="http://ws.deltalounge.net/#wsdl.interface(SomeData)"/>
  <binding.ws port="http://ws.deltalounge.net/#wsdl.endpoint(SomeDataService/SomeData_pt)"
              uri="http://ws.deltalounge.net/tst/services/SomeDataService"/>

Now there is an uri in the binding.ws refering to an endpoint.

While using the AIAMigrationUtility the following error occurs:

1
2
3
4
5
6
7
8
9

[exec]   [upgrade] Jul 26, 2010 3:02:04 PM oracle.viewgen.ViewGenerator main
[exec]   [upgrade] SEVERE: Upgrade failed. Check the logs for any exceptions. Ensure that the WSDL URLs specified in the project are reachable and a valid 10.1.3.x project is used for upgrade. Before re-attempting upgrade, restore the original project code source from the backup directory.
[exec]   [upgrade] oracle.j2ee.ws.wsdl.LocalizedWSDLException: WSDLException: faultCode=OTHER_ERROR: Failed to read WSDL from http://serverdomain:8001/orabpel/default/AIAAsyncErrorHandlingBPELProcess/1.0/AIAAsyncErrorHandlingBPELProcess?wsdl:WSDL not found
[exec]   [upgrade]         at oracle.viewgen.plugin.bpel.BPELPlugin.createComponentType(BPELPlugin.java:172)
[exec]   [upgrade]         at oracle.viewgen.ViewGenerator.main(ViewGenerator.java:223)
[exec]   [upgrade] Caused by: oracle.j2ee.ws.wsdl.LocalizedWSDLException: WSDLException: faultCode=OTHER_ERROR: Failed to read WSDL from http://serverdomain:8001/orabpel/default/AIAAsyncErrorHandlingBPELProcess/1.0/AIAAsyncErrorHandlingBPELProcess?wsdl:WSDL not found
[exec]   [upgrade]         at oracle.j2ee.ws.wsdl.xml.WSDLReaderImpl.openAsStreamConnection(WSDLReaderImpl.java:541)
[exec]   [upgrade]         at oracle.j2ee.ws.wsdl.xml.WSDLReaderImpl.readDocument(WSDLReaderImpl.java:427)
[exec]   [upgrade]         at oracle.j2ee.ws.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:366)

There is a regular expression in the replaceAIAAsyncURL target that doesn’t handle the versioned url. You can either replace it so it allows for version numbering:

1
2

<replaceregexp match="http://[\S&amp;&amp;[^/]]+(?::\d
+)??/orabpel/default/AIAAsyncErrorHandlingBPELProcess/.*AIAAsyncErrorHandlingBPELProcess\?wsdl"

or manually alter the bpel.xml files replacing the

1

http://serverdomain:8001/orabpel/default/AIAAsyncErrorHandlingBPELProcess/1.0/AIAAsyncErrorHandlingBPELProcess?wsdl

with

1

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

or the versioned wsdl of the Async error handling.

It is possible you noticed that after the installation of Oracle AIA 11g R1 starting the Managed Server of WLS takes more time than before the installation. This is not only due to the new Composites. There are also some settings you could change to reduce the time the Managed server to which you deployed AIA needs to start up.

Change JDBC settings

JDBC Settings

Change the settings of the following JDBC Data Sources that were created during the install of AIA of the AIA Demo:

• AIACentralDS
• AIADataSource
• FODDataSource
• FODDS
• LifeCycleDataSource
• mds-soa
• XrefDataSource

Data Source Settings

Login Delay

In this blogpost I’ll share some steps you can take to get your AIA 11g R1 installation back on track. If you do not perform the Pre-Installation Configurations as described in the Foundation Pack 11g Release 1 (11.1.1.2.0) Installation Guide (available as partnumber E17949-01 via eDelivery), it is possible that your AIA installation fails. After checking the pre-installation configuration it is possible to start the installation again if you follow these steps:

1. Navigate to /user_projects/domains/ and delete the edit.lok file.
2. Delete any file located in /user_projects/domains//pending
3. Log into the weblogic console and activate all the changes.
4. Restart SOA Suite and Weblogic domain.
5. Press retry button on the installation screen

If the installation screens are no longer available because you closed them, use the log files to figure out what targets haven’t been performed yet and run these targets (in the sample case below it were Deployments and PostInstallScript):

Move to the /aia30/aia_instances/aia30poc/bin and source ./aiaenv.sh.

ant -f /aia30/Infrastructure/Install/AID/AIAInstallDriver.xml -DDeploymentPlan=/aia30/config/FPInstallDP.xml -DPropertiesFile=/aia30/config/AIAInstallProperties.xml Deployments

ant -f /aia30/Infrastructure/Install/AID/AIAInstallDriver.xml -DDeploymentPlan=/aia30/config/FPInstallDP.xml -DPropertiesFile=/aia30/config/AIAInstallProperties.xml PostInstallScript

Oracle Application Integration Architecture, or AIA in short, recently became available for SOA Suite 11g R1. We did an installation of this AIA 11g R1 release. To prepare for this we used Foundation Pack 11g Release 1 (11.1.1.2.0) Installation Guide. Which is available as part number E17949-01 via edelivery. In the software requirements in the document it is stated that:

Download the AIA-Foundation Pack 11.1.1.2.0 patch 9717829 and follow the instructions in the document “Installing a fresh instance of AIA FP 11gR1 PS2 on Oracle SOA Suite 11g PS2” before you install AIA Foundation Pack 11g Release 1 (11.1.1.2.0). Apply AIA-Foundation Pack 11.1.1.2.0 patch 9717829 after you install AIA Foundation Pack 11g Release 1 (11.1.1.2.0).

Please be careful: patch 9717829 is only required if you are using SOA Suite 11g R1 PS2 (11.1.1.3). This can become clear when reading the document “Installing a fresh instance of AIA FP 11gR1 PS2 on Oracle SOA Suite 11g PS2” and the readme.txt that comes with the patch.

If you’re installing AIA-Foundation Pack 11.1.1.2.0 on SOA Suite 11g R1 PS1 (11.1.1.2) this patch is not needed.

AIA Foundation Pack 11g Certification Matrix

The certification matrix for AIA FP 11g R1 can be found here. It states:

AIA Foundation Pack 11gR1 (11.1.1.2) is certified against Oracle SOA Suite 11gR1 (11.1.1.2) or Oracle SOA Suite 11gR1 (11.1.1.3) through patch 9717829.