Doorgaan naar hoofdcontent

Oracle BPM Suite 11g overview

Introduction

This blog item gives a short overview of the Oracle BPM Suite 11g. 
If you as an architect, developer or sales person do no want to read all documentation, this can be a good starting point :-)

More thorough documentation can be found here.

Component Overview

The BPM Suite contains the following components.

As can be seen, the suite is layered on the Oracle SOA Suite and they share the following components

Oracle BPM Studio

Tool within JDeveloper to create and simulate business models using BPMN 2.0.

Oracle Business Process Composer

Web-base application that enables business users to collaborate with developers and designers.
A catalog of services, tasks and rules can be created in Studio and this catalog can be included in project templates, which can then be used to create new projects within 
Business Process Composer. Here Business Rules can be edited at run time.

Oracle Metadata Service (MDS)

MDS Repository used to store information about deployed applications, used to share projects and project templates.

Oracle BPM projects are deployed as SOA Composite applications on the BPM Engine.

Oracle BPM Engine

It runs BPMN and BPEL processes, which are separate components but they share the same process core (i.e. security, audit trails, invoke services, persistence).

Oracle Human Workflow

This component contains functionality for:
  • Task routing to users, groups or application roles
  • Management of deadlines,escalations and notifications related to a task
  • Task Forms (including workspace and portals)
  • Organization,filtering, prioritization,dispatching rules
Oracle ADF can be used to develop custom Task Forms.

Oracle Business Rules

This component lets you automate policies, computations and reasoning in an agile way.
Of course it is the trick when to use this component to get that agility.

Oracle Enterprise Manager

This web-based application is used to control and manager applications running on the SOA Suite.

Process Participants applications

Oracle BPM Workspace and Oracle Process Spaces are used by process participants.

Workspace (old BEA) gives you the opportunity to:
  • View running process instances
  • Work/View task lists
  • Out-of-the-box dashboards
  • Custom made dashboards
  • Manage organizations and roles

Process Spaces is a collaborative workspace that gives you some Social Media, built on top of Web Center Spaces.
Labels:

Reacties

  1. Harald van der Weel13 januari 2011 om 18:46

    It is still completely unclear to me what is the value of both Business Process Composer and Oracle BPM Studio in the same product stack.

    Those two products have such a huge overlap. Is it a way of selling more licences?

    BeantwoordenVerwijderen
  2. Roger van de Kimmenade14 januari 2011 om 11:25

    Process Composer is targeted at process owners, business users and business analysts. BPM Studio at process analysts/architects and developers. Both of these tools are role based and provide different users a different view based on Role. They share artifacts through the use of Meta Data Store (MDS). At runtime business users may adapt business rules.

    So in my view it is separation of concerns.

    BeantwoordenVerwijderen

Een reactie posten

Populaire posts van deze blog

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

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

Cloud to Cloud Application Integration

A lot of applications have integration possibilities, so do cloud applications. The question I got from a customer is whether to have a point-to-point integration with Cloud applications or to go through their ESB solution. This blog describes some considerations. Context The customer has a HRM application in which job vacancies are managed. Furthermore that system also handles the full applicant process flow. They also have another cloud application that handles the job vacancies. This application posts the jobs to social sites and other channels to promote the vacancies. Furthermore this application has some intelligence for job seekers to advice some new vacancies based on previous visits or profiles. The job vacancies need to be sent to the Vacancies application and applicant information needs to be sent to the HRM application, when a job seeker actually applies for a job. Furthermore status information about the job application is als...
11 reacties
Meer lezen