Oracle released some more Cloud offerings and in this article we introduce the Integration Cloud Service. This cloud service lets your organization create integrations between cloud applications, but also between cloud and on premise applications. Create connections to well-known and less known SaaS applications using a bunch of cloud adapters, publish or subscribe to the Messaging Cloud Service, or use industry standards like SOAP & REST. The available set of cloud adapters will certainly grow in the future when the marketplace is fully up-and-running.
Why should organizations consider the Cloud?
Let's get started with the key benefits and features before diving into them more detailed. Why should organizations consider the Cloud?
Oracle is accelerating the delivery of all of its Software as a Service (SaaS) solutions and Platform as a Service (PaaS) solutions to gain market share in the cloud space. The Oracle Process Cloud Services (PCS), a Paas Solution, is one of the new services that is delivered now in controlled availability to a selected set of customers, and will be general available in the near future. With this service we are entering a new era for development and management of processes with Oracle technology. The cloud based delivery and management model of the processes is aimed at simplification and improvement of time-to-market.
PCS builds on top of the already existing Oracle BPM technology. The delivery of functionality towards the cloud will be gradually extended in the coming releases. We see this product as a potential game-changer in the market, because of the simplicity and possible mash-up scenarios with other Oracle PaaS offerings and on-premise applications.
In this article we will have a quick glance at what the Process Cloud offers, look at typical use cases and see the look-and-feel of development.
With the help of my A-Team colleagues (Sushil Shukla, Siming Mu, John Featherly, Pete Farkas), and based on collective experiences visiting numerous BPM customers worldwide, I have put together my “Top 10″ list of things everyone should know when embarking on a BPM project.
You might agree, you might disagree, most of all, feel free to comment.
A frequently discussed topic these days is the Micorservices architectural paradigm. Discussions on various internet blogs and forums are showing the trend that proponents of this approach are not tired of emphasizing why Microservices are different to a holistic SOA approach, when dealing with breaking up or avoiding monolithic software architectures.
For this reason it’s time for the Cattle Crew team, to take a closer look on this arising architectural style and the corresponding discussions from a different perspective.
Amongst others Martin Fowler published a blog about what is characteristic for Microservices and applications build on the foundation of this architectural style . According to this and other blog posts (see also , ), the goal of a Microservices approach is to avoid software systems to become monolithic, inflexible and hardly manageable, by splitting a system into modular, lightweight and maximum cohesive services. Applications build on this architecture should ensure the agility regarding changes caused by changed business requirements, because affected services of an application can simply be adapted and be redeployed independently from other components.
Effectively a Microservice is a in itself cohesive, atomic application, which fulfills a dedicated purpose. Therefore it encapsulates all needed elements, e.g. UIs, logic components, may also have its own separated persistent store and may run in a separate JVM, to ensure as less impairment to other services as possible. Furthermore the implementation technologies for a specific service may vary. For each service the best-fitting technology should be used; there should be no restrictions regarding the used technologies.
Oracle released SOA Suite 12c (12.1.3) bringing a further integration between components and a bunch of new features. Most of them are quite spectacular, but at the same time all are useful. A release to persuade potential buyers and a lot more to please users of the product.
This blog will go through the most important new features in summary and will reference the blogs that will go through the new features per technology. This blog will list the most game changing feature(s) per technology/tooling; Jdeveloper, SOA Suite (SCA Composites), Service Bus (SB), Enterprise Manager, OEP, Managed File Transfer (MFT), etc.
Disclamer: Screenshots are made in Beta version of SOA Suite 12c, so may differ in final version!
Developer Productivity & Integration
Developer installer with integrated server
To kick-start developing with 12c, ’30 minutes to Hello World’, Oracle created a single download for JDeveloper and Database, Weblogic and SOA Suite. It’s one single package which include JDeveloper, a integrated Weblogic service with SOA Suite (including Service Bus), JavaDB (for it’s Database) and the Enterprise Manager.
by Rajesh Raheja
This the season of giving, so for this last post of the year, I am pleased to make available some of our most requested cheat sheets used internally and by various implementation partners world wide. These cheat sheets were created as part of the Oracle SOA Black Belt training sessions - advanced hands-on workshops that are available only to experienced Oracle SOA practitioners to gain deeper insight into the workings of the engine, enabling them to architect scalable solutions. If you have gone through this workshop, or have been working with the BPEL engine, I hope you will find this as a handy resource.
In case you are curious about this "black belt" workshop, here is a day-by-day blog written by one of our attendees.