Process driven messaging service: Difference between revisions

Revision as of 03:53, 20 February 2015

Latest revision as of 19:35, 10 February 2020

(8 intermediate revisions by 4 users not shown)

Line 3:

[[Internet messaging platform|Messaging platforms]] are considered [[Critical Internet infrastructure|key Internet infrastructure elements]]{{By whom|date=October 2014}}. A concept that once mainly encompassed email and IM has evolved to embrace complex multi-media email, instant messaging, and related fixed and mobile messaging infrastructure. Arguably, everything transmitted on the Internet and wireless telecommunication links are messages.

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=26March 012004|chapter-format=PDF|chapter=7}}</ref>

== Structure ==

Line 11:

=== 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 25:

=== Triggers ===

A trigger — whattrigger—what starts/executes a workflow — promptsworkflow—prompts the execution of actions. The object's components that define business logic and behavior 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, 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 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>

== Applicable Areasareas ==

Areas where PDMS can be used are 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 people based upon [[event-driven process chain|event-driven processes]].

== See also ==

* [[Architectural pattern|Architectural Pattern]]

* [[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]]

* [[Loose coupling]]

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

* [[Process mining]]

* [[Service (systems architecture)]]

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

* [[Workflow]]