With SOA Suite 11g on WLS SOAP optimization is automatically configured. In the scenario where you upgraded to 11g R1 and are using this optimization shortcut approach, you should specify the Server URL in the SOA Infrastructure Common Settings. Optimized calls are only active when the host name value (referred to as WSDL URL in the composite.xml) matches the Server URL.

To configure the SOA Infrastructure Common Settings choose from the SOA Infrastructure Menu > SOA Administration > Common Properties. As shown in the screenshot. Other access ways to this configuration screen are described here.

Enter the server URL in the Server URLs section. This URL is published as part of the SOAP address of a service in the concrete WSDL file. Either set both values to the host name (for example, myhost) or to the full domain name (for example, myhost.domain.com). If these values do not match, a regular SOAP call is performed instead of an optimized local call.

One of the scenarios that you have to set the Server URL in order to use the optimized local call is after a migration of AIA to AIA 11g R1.

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.

SOA Suite 11gR1 PS2 installation notes

Besides the reference in the documentation library to the Install Guide and the Quick Install Guide, there are several blogs describing the installation of 11.1.1.3. Which is actually a patch on 11.1.1.2:

• This post by Oracle ACE Eric Elzinga;
• The installation steps described by Theo van Arem;
• Installation of 11g PatchSet 2 on Windows by Niall Commiskey, members or Oracle PTS in EMEA;
• The one on Oracle blogs by James Taylor includes OSB 11.1.1.3

SOA Suite on Amazon EC2

This week it was announced that BPM 11g R1 is available as an Amazon Machine Image (AMI). This AMI includes SOA Suite 11gR1 Patchset 2 and JDeveloper with the SOA and BPM extension. In AWS filter on 64-bit and put soa-bpm in the search box. This should enable you to find oracle-soa-bpm-11gr1-ps2-4.1-pub. Some of the tips I posted on x SOA Suite in the cloud could be useful here as well.

Rob came up with two things:

• Use only one Domain in WLS. You’ll have to combine the admin en the SOA_domain. Running just one domain saves memory.
• Keep the database centralized. In the central database each developer has it’s own SOA schema that is especially created for him. To do this run the RCU for every developer and use the prefix to reflect for example the developers initials (example of using RCU on slideshare). Not running the database on your workstation saves memory and CPU.

In order to have new developers being able to use this quickly we copy the reference installation (with plug-ins, patches and the works) and alter the configuration:

• Alter the scripts in the C:\Devel\SOAMiddleware\user_projects\domains\soa_domain\bin directory to reflect your workstation name instead of that of the reference machine. You can do this easily by using an editor like Notepad++ and use Search > Find in files > Replace in files. Otherwise you’ll be stopping your teammates server…. (again sorry Rob)
• Change the configuration files in C:\Devel\SOAMiddleware\user_projects\domains\soa_domain\config\jdbc to reflect the prefix created especially for you while using the RCU. Again Notepad++ can help you here.

Now you can start the tools:

• WebLogic Server: C:\Devel\SOAMiddleware\user_projects\domains\soa_domain\bin\startWebLogic.cmd
• JDeveloper: C:\Devel\SOAMiddleware\jdeveloper\jdeveloper.exe

• SOA Suite 11g R1 PS2 new features.
• Download page
• The documentation index will probably be updated soon.

Existing PS1 users simply apply the patch to upgrade to 11.1.1.3.0.

Other releases

• Oracle Service Bus OSB 11g R1
• Business Process Management BPM 11g R1

• Full and complete support for BPEL 2.0 (designtime and runtime)
• Reintroduction of “BPEL domains” – that are called Partitions because there are already WebLogic Domains
• Enhancements to BPEL’s transactional behavior and audit-trail
• Full BPMN 2.0 support – part of BPM 11g which runs on top of 11g PS2 SOA core

Update: for the Java developer

In an additional post the features for the Java developer were announced. These include:

• Support for interface.java as a first class citizen next to interface.wsdl
• Full support for Spring as component implementation
• Support for EJB bindings (binding.ejb)
• Invocation of a composite service

http://www.flickr.com/photos/mraible/4378559350/

The presentation (that will be given at TSSJS Las Vegas 2010) this time-line originates from, can be found here. The overview was created by Matt Raible of Raible Designs.

1

java -jar jdevstudio11112install.jar

Running JDeveloper on 64-bit JVM

Running JDeveloper with the 64-bit JVM resulted in an error:

1
2
3

Unable TO launch the Java Virtual Machine  
located at path:  
C:\Java\jdk1.6.0_18\jre\bin\server\jvm.dll

A solution is to use the 32-bit JVM. To do this change the SetJavaHome in thejdev.conf that is located in the {JDEV_HOME}\jdev\bin\jdev.conf.

1

SetJavaHome C:\Java\jdk1.6.0_18_x86

Where the jdk1.6.0_18_x86 is a 32-bits JVM version.

Unable to create an instance on the Java Virtual Machine located on c:\jdeveloper11g\Middleware\jdk160_05\jre\bin\client\jvm.dll

Using Google and Oracle Support showed us that the virtual memory for the PC was not set to level that allowed the JVM to initialise.
The solution is to increase the virtual memory or swap area. To do this on Vista:

My Computer > Properties > Advanced System Settings > tab Advanced > Performance - Settings > tab Advanced > Virtual memory - Change