SOA Suite 12.2.1 is released. Below is the summary of New Features

SOA Suite 12.2.1 was released and below is the summary of new features.

·         Patch running instances of the composites.

This features enables us to patch the running instances of a composite and recover faulted instances after patching the runtime. However we can only include those fixes in the patch that are compatible with Composite Instance Patching.

To create the patch we need to use the SOA Patch Developer role in Oracle JDeveloper

This will help us to deliver urgent composite fixes that can be picked up by long running instances. This enables us to make changes without aborting in-flight instances. If a patched running instance comes across a business process that has been fixed by the patch, say a BPEL transformation, then it picks up the fixes applied to the business process. Read more here 

·         Support for in Memory SOA: Oracle has been pushing hard on coherence and this is one more example where coherence cache can be used. Using this feature the non-transactional business process as read and write operations are performed out of the cache as opposed to database in previous releases. The database performance and management also improves, as the costs associated with continuous disk reads and writes are significantly reduced. Read more here 

·         Debugging Improvements in XSLT mapper: Now we can debug our XSLT maps using the SOA Debugger. We can add breakpoints just like java at strategic locations in the XSLT map. During debugging, the debugger halts execution at the breakpoints, enabling us to verify the data and output.

Read more here 

·         Support for End-to-End JSON and JavaScript.  Now our SOA composites can use JSON from end to end. This means that now the REST service can receive the REST request and route it to the BPEL engine without translating it to XML. The BPEL component can use the JavaScript action, and also use JavaScript in conditional and iterative constructs, to work on JSON objects directly. The REST reference can receive the REST message from the BPEL engine and route it to an external REST endpoint without translation. Following are some of the features:-

1. Enable End-to-End JSON
2. Enable End-to-End JSON
3. Enable REST support in new or existing services.
4. Integrate with external REST APIs.
5. Orchestrate a set of RESTful state transitions (RPC/Hypermedia as the Engine of Application State (HATEOAS) approach).
6. Support for XML, JavaScript Object Notation (JSON) (with automatic translation to and from XML), text, opaque (binary), and URL-encoded payload data.
7. Generation of sample URI for REST service operations.
8. Support for WADL services. The WADL can be provided by a deployed Oracle SOA Suite or Oracle Service Bus service or a non-Oracle SOA Suite or Oracle Service Bus service such as a Jersey REST service.  Read more here 

Reference :- Oracle Docs