Again I want to talk from my area of expertise of Fusion Applications and talk about their design fundamentals. If you look at the table below and start at the bottom Oracle have defined all of the business objects e.g. accounts, people, customers, invoices etc. used by Fusion Applications; each of these objects contain all of the information required and can be expanded if necessary.
That Oracle have created for each of these business objects every action that is needed for the applications e.g. all the actions to create a new customer, checking to see if it exists, credit checking with D&B (Dun & Bradstreet < http://www.dnb.co.uk/> ) , creating the record, notifying those required etc. Each of these actions is a stand-alone web service. Again you can create a new actions or subscribe to an external provided web service e.g. the D&B check.
Then the Intelligent Business Process is the order in which you run these actions, this is Service Orientated Architecture, SOA. Not only is SOA used to orchestrate actions within Fusion Applications it is also used in the integration of Fusion Applications with the rest of the Oracle stable of applications such as EBS, PeopleSoft, JDE and Siebel. The other applications are written with propriety development tools so how do they work with SOA? It’s a very simple answer, with the introduction of the Oracle SOA platform each process within these applications was made available to be called as a web service. I won’t go into technically how that is done but what’s known as a wrapper to allow each of them to act in this way was added.
Cloud Computing Hype Introduction
Why is everyone talking about cloud computing? Drawn-out, expensive IT projects that are planned and implemented with few benefits for the business stakeholders are commonplace. In contrast, cloud computing offers business users the chance to immediately implement services with usage-based billing that are tailored to their requirements, often without the need to consult with the IT department.
However, aspects including security, architecture, availability, and standards are often not evaluated. Cloud consumers find themselves at the mercy of the cloud provider. Scenarios that require changing cloud providers after a cloud provider goes bankrupt, and the associated moving of data and/or applications, have not yet been sufficiently tested. Business continuity should play a key role from the start of a cloud evaluation process.
One of the greatest challenges here is the integration of existing data and systems into the cloud solution. Without integration spanning clouds and on premise systems, processes can only be executed in isolation, leading to cloud-specific silos of isolated solutions. Important information for users is not available across processes and systems. Problems that would have occurred in the company's internal IT are now shifted to the cloud provider. To prevent "legacy clouds" or solutions that are hard to maintain, it is important to manage the entire architecture proactively and, in particular, the integration into the cloud. Even if cloud providers want us to believe otherwise, not every aspect of IT can be outsourced to cloud solutions!
A new version of Oracle BPM Suite 220.127.116.11 with Adaptive Case Management (ACM) is now available, so what will that mean for requirements gathering? BPM project requirements can be documented using Business Process Model and Notation (BPMN 2.0). For ACM, there is a new notation in the works. It is called Case Management Model and Notation (CMMN). For now, this notation isn’t included as a modeling tool in the new version of Oracle BPM Suite 18.104.22.168 with ACM, but it is possible that a modeling tool could be included in a future release.
What is CMMN?
CMMN is a standard intended to capture the common elements that Case Management Products use, the same way that BPMN is a standard for BPM products (such as Oracle BPM). CMMN is created by the Object Management Group (OMG) and is still in the beta version. In April 2014, OMG released the second beta version the CMMN 1.0, and the most recent version is available here.
CMMN captures some of the elements that are commonly used when talking about ACM such as Cases, Milestones, and Tasks. It also introduces some elements that you may not automatically hear when talking about ACM such as Stages, Events, and Decorators. Here is a quick summary at a few (but not all) of the elements of CMMN taken from the CMMN spec.
Industrial SOA is a 14-part article series focused on service orientation, written collaboratively by a group of recognized experts and community leaders in service oriented architecture.
"SOA and service-orientation have laid the foundation for a variety of emergent service technology innovations such as cloud computing and big data, while the original building blocks of SOA and service-orientation continue to evolve by embracing fundamental service technologies, concepts and practices."
An in-depth look at the interaction of people, processes, and technologies in the transition to a service-oriented architecture. Author's Note: This article presents a profile of a fictitious organization, NOPERU. The story of NOPERU as told in this article is actually a collage of the events at some dozen organizations that I have been involved with over the past few years. None of these organizations sport all the characteristics of NOPERU - but all of them have gone through or are going through a similar transition as described here and all aspects of this article were taken from real life at one or usually many of these organizations.
Thanks to Dan Atwood and the AVIO team for the excellent BPMN2.0 poster for BPM Suite!
Immediately increase your value on Oracle BPM projects by downloading our BPMN for Oracle 11g poster that explains the meaning of each BPMN shape - visit the AVIO website to get the poster here.
Further increase your value by attending one of the AVIO Academy Oracle BPM training courses for developers and business people.
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.
Em Julho de 2013, o best-seller Thomas Earl em conjunto com o professor Doutor Ricardo Puttini lançaram o livro "Cloud Computing: Concepts, Technology & Architecture" (3CTA). O título é resultado de um intenso trabalho de pesquisa e, ainda, fruto da vivencia profissional de ambos os autores, tornando-se uma excelente fonte de informação para profissionais de TI e gerentes que querem aprender e entender cloud computing. O livro fundamenta os conceitos, modelos de implantação, tecnologias e mecanismos para cloud, levando em consideração a independência de plataformas tecnológicas, o que permite que o mesmo seja utilizado como referência por longo tempo.
Knowledge-driven processes are typically unpredictable in their execution. Experts working on them decide what’s the next best action to take. This is in contrast to traditional BPM, in which all possible paths of a process are predetermined and modeled into the process. Case management is a way to control and implement these unstructured processes. With the poster below we'd like to bring some of the key aspects of Adaptive Case Management (ACM) on one page. Feel free to download the PDF-version if you are interested in:
- What is ACM?
- Why should I use ACM?
- How can ACM user interfaces look like?
- What are the main building blocks of an ACM solution?
- How to visualize ACM cases with CMMN 1.0?