Few days ago, Oracle released pre-configured Oracle SOA/BPM Suite 11g PS5 (126.96.36.199) VirtualBox image that is available for testing and evaluation purposes.
The VirtualBox image contains the following software:
- Oracle Enterprise Linux (64-bit) EL 5 Update 5
- Oracle XE Database 11.2.0
- Oracle SOA Suite 188.8.131.52.0 (includes Service Bus)
- Oracle BPM Suite 184.108.40.206.0
- Oracle Webcenter Content (Enterprise Content Management) 220.127.116.11.0
- Oracle Webcenter Suite 18.104.22.168.0
- Oracle JDeveloper 22.214.171.124.0
- JRockit R28.2.0-79-146777-1.6.0_29s
- Sun Java SDK 1.6.0_29-b11
It is available for download on this link.
A few weeks ago we faced an interesting challenge: how to propagate a transaction context between Oracle WebLogic 11g and IBM WebSphere 8. Propagating a transaction context between different Java EE servers can sometimes present a problem, especially if those servers support different Java EE versions. WebLogic 11g (10.3.5.0) supports Java EE 5 while WebSphere 8 supports Java EE 6. We successfully solved the problem using WS-Atomic Transaction (WS-AT).
In this post, I will present the main steps how we propagated a transaction from WebLogic (WLS) to WebSphere (WAS). The solution for the opposite direction will follow in a separate post.
A few days ago, Oracle released BPM Suite 126.96.36.199 Feature Pack, which includes many new features, bug fixes and performance improvements.
Some of the most important new features:
- Improved Business Process Composer (snapshot support, enhanced sharing and collaboration, improved ease of use)
- New Business Analyst features (report generation, BPMN 2.0 collaboration view)
- Advanced Service Integration (Support for BPMN Correlation and Conversation)
- Richer Human Workflow
- Improved Process Analytics (Round-trip simulations, Improved BI integration)
- Several improvements for developers (Draft-mode, Custom logging, Rule test framework, Enhanced rule audit trail, Workspace customization, BPM API javadoc available)
- And more…
For more info, please refer to: What’s new in BPM Suite 11g R1 PS 4Feature Pack
BPM Suite 188.8.131.52 feature pack is intended to use for BPM customers only!
Throughout July Packt Publishing (one of the leading publishers in Oracle books) will be celebrating the release of its 50th Oracle book.
To mark this milestone Packt is offering the following discounts:
- 20% off all Oracle print books
- 30% off all Oracle eBooks
Packt first started publishing Oracle books in 2006, and has since published best-sellers such as Getting Started With Oracle SOA Suite 11g R1 – A Hands-On Tutorial, Oracle Coherence 3.5 and Oracle Fusion Middleware Patterns. And with more than 20 exciting new Oracle titles scheduled for 2011 this current success is only set to increase.
Packt owes much of its success to its print-on-demand mantra which not only allows it to produce books on specialist areas, but enables a quick response to new developments in technology – which was recently demonstrated with Packt publishing the first ever book on GoldenGate, the Oracle GoldenGate 11g Implementer’s guide.
Packt’s entire range of Oracle books is also available via PacktLib, Packt’s Online Library, and as part of Packt’s celebrations it’s offering you the chance to win a year’s subscription to PacktLib worth $220 click here for details: http://www.packtpub.com/article/50th-oracle-book-offer.
I would also like to take the opportunity to promote the book WS-BPEL 2.0 for SOA Composite Applications with Oracle SOA Suite 11g which was written by two members of our team (Matjaz B. Juric and Marcel Krizevnik).
For further information on this, and other books published by Packt Publishing, please visit www.PacktPub.com.
When trying to improve Oracle WebLogic server performances, scalability and reliability, tuning JVM (Java Virtual Machine) is probably the most important step. However, this is usually far from being an easy task. JVM tuning includes selecting the right JVM, setting the appropriate heap size, selecting the most appropriate GC (garbage collector) strategy, etc. An in-depth discussion is beyond the scope of this post, we will just get familiar with the basic steps:
As an attempt to ease the application’s development in terms of packaging, versioning and deployment, Java 7 will introduce Java Module System (JMS). The Java Module System is being developed under the Java Community Process as JSR 277. The abbreviation itself does not seem very appropriate at first sight, as it can be easily confused with JMS (Java Message Service).
Java Module System’s architecture consists of three main components:
- Java module
- Versioning System
Java Module System is a new distribution standard which (similar as JAR file) contains a set of classes and other resources. However, JMS differs from JAR in that the modules can be versioned. A module can be defined as a logical unit of a set of files, resources and other dependencies that can be versioned, packaged and deployed in the module repository. The module repository is where java modules can be stored, discovered and used by other modules.
You can read more about JMS at the following link: http://www.javabeat.net/articles/101-introduction-to-java-module-system-in-java-70-1.html
OSB 11g (Oracle Service Bus 11g ) provides an interesting feature called service result caching through the use of Oracle Coherence in-memory data grid solution. In this way we can dramatically improve performances of business services if the response is relatively static.
To enable the use of service result caching globally using the OSB console, we have to open the Operations | Global Settings and set the Result Caching to true.
To enable service result caching on a particular business service, we open the Project Explorer and click on the business service. On the Configuration Details tab, we scroll down and edit the Message Handling Configuration. Then we expand the Advanced Settings. We select the Result Caching checkbox. Next, we have to specify the cache token, which uniquely identifies a particular cache result. This is usually an ID field. We can also set the cache expiration time.
Then we click Next and Save.
Now if the business service locates cache result through a cache key, it returns this result to the client instead of invoking an external service. If the result is not cached (or has expired), the business service invokes the external service, returns the result to the client, and stores the result in cache.
Service result caching works only when the business service is invoked from a proxy service!
Oracle SOA Suite PS3 brings many bug fixes and some important new features.
Let me mention some of the most important improvements:
Full BPEL 2.o support
The run time support for BPEL 2.0 has been already available for a while, what’s new is the design time support in JDeveloper 184.108.40.206.
When creating new BPEL process we can select which BPEL version we want to use: