Doorgaan naar hoofdcontent

How to explain Cordys BPM?

Today I got a question from Anita one of my Twitter followers:

"Most people just dont get the whole application, BPM, layered language, how do you explain Cordys to people?"

So to get a discussion going i post this question to my Blog so that we can discuss here !

A few questions come to me:
  • What do people don't get? The layering? The BPM language? Or the step towards Cordys?

The whole thing about BPM is that you get a flexible business architecture that is abstracting the business processes from the technical implementation.
This way you get technical flexibility as well as business flexibility. BPM brings business and IT together !

Cordys BOP4 is a platform that supports this notion of layering and processes with a service oriented architecture.
It follows the principles as set by Thomas Erl's SOA Principles.
Within the SOA patterns there is also the layering pattern:



This is about layering your Services into three abstraction layers. Thomas talks about
  • Task Services - A business service with a functional boundary directly associated with a specific parent business task or process.
  • Entity Services - A service centric service that bases its functional context and boundary one a related business entity.
  • Utility Services - Services that provide cross-cutting functionality, also known as application services or technology services.

When we talk about SOA layering you also see the 5-layering architecture. In those layering the presentation layer and application/data layer is added.
Example:

Within the Cordys BOP4 platform this is mapped to:
  • Visual Layer - XForms, WebBased GUI
  • Business Process Layer - BPM processes modelled with BPMN and exposed as WebServices
  • Business Service Layer - Entity Services modelled with BPMN and exposed as WebServices
  • Technical Service Layer - Application Connectors, like FTP, File and Database connectors, exposed as WebServices.
  • External Systems - These are the external systems that are used within the SOA/BPM architecture.

The WebServices is the Standardized Service Contract SOA Principle used within Cordys.

Can't wait to here your comments !


Labels:

Reacties

  1. Dinesh Bang28 juli 2010 om 16:59

    Thanks Roger,

    I am new to Cordys stuff and had been wandering since a few days to understand about Cordys architecture.

    Your explanation is a short and effective one.
    If you have any more references or links on how to start developing application in cordys let me know.
    Thanks again.

    BeantwoordenVerwijderen
  2. Roger van de Kimmenade28 juli 2010 om 20:35

    Hello Dinesh,
    Glad that you liked the architecture recap.
    There are some nice documents on the Cordys Community site: http://community.cordys.com

    For example: https://wiki.cordys.com/display/PI/2009/12/03/Insight+into+Cordys+BOP-4+Architecture

    Think you can get a member for free there.

    Regards, Roger

    BeantwoordenVerwijderen
  3. Roger van de Kimmenade28 juli 2010 om 20:49

    Deze reactie is verwijderd door de auteur.

    BeantwoordenVerwijderen
  4. Roger van de Kimmenade28 juli 2010 om 20:52

    You can also find this article here:
    http://tiny.cc/ydn9x

    BeantwoordenVerwijderen
  5. Scottaltham20 maart 2012 om 07:30

    Dag Roger, nice post. Although I already knew how the Cordys stack maps to these layers, with being a visual learner myself, I really like, basic, visual, to the point posts like this rather than those that are dripping in business/technical/SOA jargon that dilute the point being made. Dit is een zeer goede post! (Yeah, my dutch is rubbish!)

    BeantwoordenVerwijderen
  6. Unknown11 februari 2013 om 12:58

    Hi Roger What is BPM Testing and what we test in Cordys automation?

    I need help.

    BeantwoordenVerwijderen
  7. Roger van de Kimmenade17 februari 2013 om 19:00

    Hello Sriram,
    Please fill in the wordd "test" in the search box at the right corner of my blog.
    You will find some blog items about testing.
    Please let me know when you need more info and about what aspect.

    Regards
    Roger

    BeantwoordenVerwijderen

Een reactie posten

Populaire posts van deze blog

OSB 10gR3 and SWA and MTOM

This blog is about using soap with attachments and the use of MTOM within the OSB (10gR3). A service is created that accepts a soap with attachment (DocumentService) and translates it to a service that accepts a binary element. MTOM is used for performance reasons for the second. Some notes: * For the use of attachments you need RPC-style document instead of the usual document-style. This due to the fact that the document-style limits a message to a single . * A service can not have both SWA and MTOM within OSB. First a WSDL is setup for the DocumentService: The $attachments variable holds the attachments and the body holds the attachment data. Also other data is stored within the attachment element (see h...
12 reacties
Meer lezen

Microservices mindmap

"The tree" - See also   my photo page When you are fairly new within the Microservices land, there are a lot of terms fired at you. So also for my own understanding i have made a mindmap. I think it has a good status now, so that i can share it with you. As always feedback is very welcome ! You can download the mindmap here .
48 reacties
Meer lezen

Book review: Data Management at Scale (Piethein Strengholt)

 This blog is a review of the book "Data Management at Scale (See also at bol.com ) Data Management is a hot topic nowadays and this book does a fantastic job at adding value to this topic. It is a must read and one of the few technical books I finished reading in a weekend. The book gives a fantastic overview on how to implement a Data Mesh data architecture. The Data Mesh concept is explained by Martin Fowler here . The book is a good mix between conceptual and implementation architecture level. It gives a lot of examples of how this architecture at scale can work, for both small and big companies. It is practical and I used it to implement it at one of my customers. The book describes an architecture in which the focus is on the DIAL (Data- and Integration Access Layer).  On a high level the book covers the following topics: The key principles for data management at scale - Domain-Driven Design  - Domain Data Stores - Meta data management Ready Data Store The concept ...
5 reacties
Meer lezen