Comparing a brand new Oracle Process Cloud Service (PCS) with traditional on-premise Oracle BPM Suite by Lukasz Romaszewski
By Juergenkress-Oracle on Apr 27, 2016
As you may have heard, Oracle is quickly extending its middleware stack to the public cloud platform, by implementing there, one by one, every possible piece of technology from its portfolio. One of the most successful and powerful component of the traditional Fusion Middleware stack is Oracle BPM, which has been widely adopted in many organizations and companies to drive down the costs and increase agility and business control over all of the business processes in place. No surprise that BPM is one of the first technology to become available in the cloud, in the form of Process Cloud Services. In this blog post I would like to take you in the quick tour over PCS, how it looks like, and most important thing - what are the differences between the traditional on-premise version and the new cloudify BPM.
Just to make things clear - I have based all my comparisons on some early beta version of PCS, which may look and behave differently from the final GA version.
Similar to all other PaaS components, PCS is totally web based and there is no such thing as IDE/JDeveloper tool to install and run on the local environment. Which of course clearly puts this product into the business toolbox, rather than developer/IT one. The very first thing which you notice once you open your instance of PCS is the new Alta look&feel, consistent with every other cloud product made by Oracle:
you log in, you will end up at the cloud version of old, good BPM
Composer's starting page, with some more or less visible changes in the
layout and names of particular modules: Read the complete part 1 here and part 2 here.
For regular information on Oracle SOA Suite become a member in the SOA & BPM Partner Community for registration please visit www.oracle.com/goto/emea/soa (OPN account required) If you need support with your account please contact the Oracle Partner Business Center.