Doorgaan naar hoofdcontent

Oracle BPM Suite 11g in Pictures

Overview




Licencing



Modeling tools and Users

Business/Enterprise Architect
  • Business Strategy
  • Implement Business Architecture
  • Process Analysis/documentation
Business User
  • Understands the business
  • High level business processes
Process Analyst
  • BPMN 2.0 expert (business view)
  • Understands the details of the business
  • Make implementation decisions
Process Developer
  • BPMN 2.0 expert (technical view)
  • WebServices, XML
  • Enterprise Apps
  • Implement processes and UIs

Collaborative Design



BPM Studio

Process Analytics

Social BPM

SOA Platform

End-to-End instance and Flow checking due to integrated platform.

BPMN 2.0 support


Change with BPMN 1.1 :
  • Model execution
  • Models are interchangeable
  • XPDL and BPEL were used to interchange and execute

Interactive task and workflow



BPM Studio supports Simulation.

BPM Studio Business Indicators


Snapshots of business indicators must be added to the workflow and this is a little awkward because it blurs the process model.

Good integration with BAM


Process Composer

Within BPM Studio you design templates and there you set the constraints which changes can be made within Process Composer.

Unstructured Processes

End Users can
  • Reassign, reroute, delegate tasks
  • Add users for a task

Business Rules


  • Decision tables
  • If-then rules
Can be changed in Process Composer.
Participants lists can be dynamically assigned using a Rule.

Enterprise Manager

Unified Security

Clustering

Labels:

Reacties

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 of servin
5 reacties
Meer lezen