Process driven messaging service: Difference between revisions

Revision as of 14:00, 4 April 2014

Revision as of 23:00, 13 April 2014

Line 1:

{{Orphan|date=Marchcopy 2014}}{{copyeditedit|for=grammar and capitalization|date=March 2014}}

A '''process driven messaging service''' ('''PDMS''') is a service that is process oriented and that exchanges messages/data calls. A PDMS is a service where jobs and triggers can be put together to create a work flow for a message.

Line 5:

[[Internet messaging platform|Messaging platforms]] are considered [[Critical Internet infrastructure|key Internet infrastructure elements]]. What used to be only referred to as a few message types like email and IM has evolved into a complex multi-media email, instant messaging, and related fixed and mobile messaging infrastructure. One can argue that everything transmitted on the Internet and wireless telecommunication links is a message of one sort or another.

PDMS exchanges messages for the purpose of all kind of messages/data calls between systems, applications and or human beings that is based upon [[event-driven process chain]]s.<ref name="Event Driven Process Chain">{{cite book|last=Hommes|first=Lambertus Johannes|title=The evaluation of business process modeling techniques|dateyear=2004|publisher=s.n.]|___location=[S.l.|isbn=90-9017698-5|pages=138-187138–187|url=http://repository.tudelft.nl/view/ir/uuid%3A1d209c45-4b2a-41f2-9e94-a54b8ee76d78/|archivedate=26042014|language=English|format=PDF|chapter=7}}</ref>

== Structure ==

Line 13:

=== Workflows ===

A workflow in PDMS is used to wrap triggers and/or jobs together to accomplish a flow of actions and events that can be invoked over and over again without repeating the configuration. What also should be noted is that a workflow is a container. A Workflow Process is a container for a group of Workflow Statuses and Actions, such as moving a record from one status to another.<ref name="Workflow Container">{{cite web|title=Rollbase in action|url=http://www.progress.com/~/media/Progress/Documents/Rollbase/Rollbase%20in%20Action/chapter10.pdf|work=Chapter 10|author=Progress Software Corporation|page=6|language=English|format=PDF}}</ref> Apart from triggers and jobs, it can contain groups or artifacts. These items that the workflow can contain are then available to all triggers and jobs within the workflow.

The concept of workflow can be seen as a template for a part of, or a whole business process. Workflows can with the help of triggers be invoked by a number of different reasons; for instance, when something happens in the ___domain or there is an explicit call to invoke.

Line 19:

When a workflow, its triggers and jobs are active the workflow is active and will be in a state where it waits to execute. A workflow will execute when a trigger gets triggered. That trigger will cause one or more jobs to be executed. The jobs can in turn execute more jobs. When all jobs have been executed the workflow will still be active, but nothing happens until it is triggered again.

When created, workflows expects the last part of the workflow to be added first. That last part would be a job. Also jobs and triggers wants to know the next step in the flow when they are created, meaning that they too advocate creating the workflow in reverse order.<ref name=Workflow>{{cite journal|last=UWE|first=ZDUN|coauthors=CARSTEN, SCHAHRAM|title=HENTRICH, DUSTDAR|journal=Modeling Process-Driven and Service-Oriented Architectures Using Patterns and Pattern Primitives|date=September 19, 2007|volume=Volume 1|issue=Issue 3|pages=23-2723–27|url=http://dl.acm.org/citation.cfm?doid=1281480.1281484|publisher=ACM, Inc.|___location=New York|language=English|format=PDF}}</ref>

=== Jobs ===

Line 26:

=== Triggers ===

A trigger represents something that has happened and causes jobs to execute. In a way we can think of it as what starts/executes a workflow. The objects components that define business logic and behaviour are called Triggers. You can create and configure any number of Triggers to perform automated and programmatic validation, notification, data manipulation and other activities upon record creation, update and deletion.<ref>{{cite book|title=Rollbase in Action|publisher=Progress Software Corporation|pages=266-289266–289|url=http://www.progress.com/~/media/Progress/Documents/Rollbase/Rollbase%20in%20Action/Rollbase_in_Action.pdf|language=English|format=PDF|chapter=10}}</ref>

=== Processes ===

Line 36:

== Technology/programming ==

PDMS is based upon [[Event-driven architecture|Event-Driven Architecture]] whereas the [[architectural pattern]] may be applied by the design and implementation of applications and systems which transmit events among [[Architectural pattern|loosely coupled software]] components and [[Service (systems architecture)|services]]. Unlike traditional information systems which work by issuing requests and waiting for responses, event-driven systems are designed to process events as they occur, allowing the system to observe, react dynamically, and issue personalized data depending on the recipient and situation.<ref name="Event Driven Architecture">{{cite book|title=Event Processing in Action 1st|date=September 2007|publisher=Manning Publications Co|___location=Greenwich, CT, USA|isbn=1935182218|author=Opher Etzion, Peter Niblett|language=English}}</ref>

== Providers ==