There are several advantages when working in a project with Oracle SOA Suite to have a local installation of the SOA Suite on your workstation. While developing and trying bits of code you can’t break other peoples work as you can on a central server. Running FMW 11g on a workstation with say memory on the low end of the spectrum can be challenging. In this blog I’ll show you some additional (to this previous post) measure that my blogless colleague Rob Heikoop came up with.
Rob came up with two things:
Create an All in One AdminServer as described on the Oracle wiki. We skipped BAM in the installation 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.
One of the things on my To Do list was to move my local SOA Suite 11g R1 to The Cloud. It seemed a good idea to save my laptop some resources (to spare some for JDeveloper) with only a limited investment. Besides that it can be a good way to demo applications, and work together with my colleagues on these demos.
During the last months I noticed that there are several good blogpost on the subject. In this post I’ll show you the ones I used and provide some additions to them.
AMIs are per region: The Amazon Machine Instance (AMI) for SOA Suite (id = ami-acb557c5) is only available in the US East (Northern Virginia) Region.
Don’t bother to setup the Elastic Block Store (EBS) Volume. It is scripted in the latest version of the AMI, as described in step 5 of “SSH to your image and accept license”. The EBS Volume is seeded using a snapshot (id = snap-dd980db4) that is provided. This volume will be used to persist your data across sessions and AMI start/stop.
When launching the image (during the Configure Firewall step) set the SecurityGroup to accept HTTP traffic on port 7001 in case you want to use the SOA Suite from outside the Image.
According to the press release it is already fully integrated with Oracle Amberpoint:
Oracle SOA Goverance 11g is fully integrated with Oracle AmberPoint, a leader in Service-Oriented Architecture (SOA) Management. The new solution provides organizations more continuity of closed-loop governance processes across both Oracle and third party applications.
Besides that it is not clear to me what is new. The latest version of the Enterprise Repository was release a month ago. Any ideas? Please leave them in the comments.
The webcast of the SOA and Integration strategy was a few days later available as the overall strategy. You can find the entire webcast here.
The combined Oracle Sun solution focus boils down to the following bullets:
Oracle SOA Suite continues as the strategic product.
Sun JCAPS continues to be supported and maintained
GlassFish ESB continues as an open source project
A bridging technology is planned to support collaboration between JCAPS and Oracle SOA Suite.
Key functions from the Sun SOA products will be incorporated in the Oracle SOA products.
Oracle WebCenter stays the strategic portal offering. Support for both GlassFish Web Space Server and Sun Portal Server will be continued. An upgrade path to WebCenter is planned for both. The IP (Intellectual Property) for Sun’s Web Space Server will be released into the Liferay open source community.
From today there is a SOA Suite 10.1.3 familiy member available for WebLogic Server 10.3. Oracle SOA Suite 10.1.3.5.1 has been released. As describedearlier we were looking for a recent SOA Suite version that is certified for a recent WebLogic server version. And here it is: Oracle BPEL Manager, Oracle ESB, Oracle Rules, and OWSM (basically all versioned 10.1.3.5.1) are certified with WLS 10.3.1.
Metalink doc.id 745094.1 promises that 10.1.3.5 is the SOA Suite 10g release that wil be supported on WebLogic 10.3. Where older release were supported on 9.2 (although for 10.1.3.4 requiring the patch 490612 and patch 7337034).
So far the Metalink note has not been updated and is still stating a “planned” support. It could be that it is still a little premature to draw conclusions, since the released downloads and documentation pages haven’t yet been update with the information on this release.
Beside that no information on support on WebLogic 10.3 was found in the release documentation. The OTN downloaded page still features SOASuite10133OnWeblogic.
There should be no problem running Oracle Fusion Middleware 11g on a laptop. However if it’s memory is on the low end of the spectrum, it can be challenging. One of the changes you can make, is reducing the memory allocated to the Java process for the WLS domain running the SOA Suite. These memory settings can be altered in the following file: