Process driven messaging service: Difference between revisions

Revision as of 18:26, 30 June 2014

Latest revision as of 19:35, 10 February 2020

(24 intermediate revisions by 13 users not shown)

Line 1:

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 workflow for a message.

{{copy edit|for=grammar and capitalization|date=March 2014}}

[[Internet messaging platform|Messaging platforms]] are considered [[Critical Internet infrastructure|key Internet infrastructure elements]].{{By Whatwhom|date=October used2014}}. toA beconcept onlythat referredonce to as a few message typesmainly likeencompassed email and IM has evolved intoto aembrace complex multi-media email, instant messaging, and related fixed and mobile messaging infrastructure. One can argue thatArguably, everything transmitted on the Internet and wireless telecommunication links is a message of one sort orare anothermessages.

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 workflow for a message.

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|year=2004|publisher=s.n.]|___location=[S.l.|isbn=90-9017698-5|pages=138–187|chapter-url=http://repository.tudelft.nl/view/ir/uuid%3A1d209c45-4b2a-41f2-9e94-a54b8ee76d78/|archivedate=26042014|chapter-format=PDF|chapter=7}}</ref>

[[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|year=2004|publisher=s.n.]|___location=[S.l.|isbn=90-9017698-5|pages=138–187|url=http://repository.tudelft.nl/view/ir/uuid%3A1d209c45-4b2a-41f2-9e94-a54b8ee76d78/|archivedate=26042014|format=PDF|chapter=7}}</ref>

== Structure ==

A process driven messaging service is a service where jobs and triggers can be put together to create a work flowworkflow for a message. Theand workthe flowworkflow can be seen as a process.

A workflow is executed when a trigger is prompted. The trigger causes the activation of one or more jobs which can, in turn, execute more jobs. The workflow will still be active even when all jobs have been executed, but nothing occurs until it is re-triggered.<ref name="Event Driven Architecture" />

=== 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 aA 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|format=PDF}}</ref> Other than triggers and jobs, it can contain groups or artifacts. The items that can be contained in the workflow are then available to all triggers and jobs within the workflow.

The concept of a workflow can be seen as a template for either part of, or a whole, business process. Workflows can be triggered for a number of different reasons, an example of which could be if something were to happen in the ___domain or there were to be an explicit call to invoke.

Line 19 ⟶ 17:

The workflow will be in a state awaiting execution when the workflow, its triggers, and its jobs are active.

When created, workflows require the last job to be added first, meaning jobs are to be listed in reverse order of execution. Jobs and triggers also require the reverse sequential listing of orders when created.<ref name=Workflow>{{cite journal|last=UWE|first=ZDUN|coauthorsauthor2=CARSTEN, SCHAHRAM|title=HENTRICH, DUSTDAR|journal=Modeling Process-Driven and Service-Oriented Architectures Using Patterns and Pattern Primitives|date=September 19, 2007|volume= 1|issue= 3|pages=23–27|url=http://dl.acm.org/citation.cfm?doid=1281480.1281484|publisher=ACM, Inc.|___location=New York|format=PDF}}</ref>

=== Jobs ===

A job creates something such as a task (e. g., sendsending a message) or affects Standard Objects (e.g. way metadata in a unit). It is a task describing what the system should do and can be several things. A job, when activated, can lead to the execution of another job (for instance: message delivery). It represents what a system does with the data, an activity within the system ___domain.

{{Expand section|date=March 2014}}

A job creates something such as a task (e. g., send a message) or affects Standard Objects (e.g. way metadata in a unit). It is a task describing what the system should do and can be several things. A job, when activated, can lead to the execution of another job (for instance: message delivery). It represents what a system does with the data, an activity within the system ___domain.

Jobs provide a means to encapsulate a process. A Job is a configuration representing input options, the steps in the process, a filter expression that matches the nodes where those steps will execute, and execution control parameters that specify if steps are run in parallel. One might find certain command executions are done repeatedly, and perhaps, represent what has become a routine procedure. Routine processes need to be encapsulated and become the basis for other routine procedures.

=== Triggers ===

A trigger—what starts/executes a workflow—prompts the execution of actions. The objectsobject's components that define business logic and behavior are called Triggerstriggers. You can create and configure any number of Triggerstriggers to perform automated and programmatic validation, notification, data manipulation, and other activities upon record creation, updating, and deletion.<ref>{{cite book|title=Rollbase in Action|publisher=Progress Software Corporation|pages=266–289|chapter-url=http://www.progress.com/~/media/Progress/Documents/Rollbase/Rollbase%20in%20Action/Rollbase_in_Action.pdf|format=PDF|chapter=10}}</ref>

=== Processes ===

A process starts at some point in the system. For example, when a trigger executes an instance of a workflow.

A process driven messaging service is often used when managing a more or less complex business processes.

Line 36 ⟶ 35:

== 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=1935182218978-1935182214|author=Opher Etzion, Peter Niblett}}</ref>

== ProvidersApplicable areas ==

Areas where PDMS can be used in isare System to System, [[Short Message Service#Application-to-Person (A2P) SMS|A2P]] with the difference that other message types can be included in the PDMS, Application to Application, System to Person, [[Machine-to-Machine|M2M]] and all kinds of messages/data calls between systems, applications and /or human beings that ispeople based upon [[Eventevent-driven process chain|event-driven processprocesses]]..

A process driven messaging service is a service based upon the methodology/service Process Driven Messaging Service where jobs and triggers can be put together to create a work flow for a message. The work flow can be seen as a process.

[http://www.mobileresponse.com Mobile Response] is a service that based its technology upon PDMS.

== Applicable Areas ==

Areas where PDMS can be used in is System to System, [[Short Message Service#Application-to-Person (A2P) SMS|A2P]] with the difference that other message types can be included in the PDMS, Application to Application, System to Person, [[Machine-to-Machine|M2M]] and all kinds of messages/data calls between systems, applications and or human beings that is based upon [[Event-driven process chain|event-driven process]]..

== See also ==

* [[Architectural pattern|Architectural Pattern]]

* [[Internet messaging platform|Internet Messaging Platform]]

* [[Short Message Service#Application-to-Personperson (A2P) SMS|Application-to-Personperson (A2P) SMS]]

* [[Critical Internet infrastructure]]

* [[Event-driven architecture]]

* [[Internet messaging platform|Internet Messaging Platform]]

* [[Architectural pattern|Architectural Pattern]]

* [[Critical Internet infrastructure]]

* [[Loose coupling]]

* [[Machine- to-Machine machine|Machine to machine (M2M)]]

* [[Short Message Service#Application-to-Person (A2P) SMS|Application-to-Person (A2P) SMS]]

* [[Process mining]]

* [[Machine-to-Machine|Machine to machine (M2M)]]

* [[Service (systems architecture)]]

* [[Workflow]]

== References ==