Process driven messaging service: Difference between revisions

Revision as of 18:44, 8 March 2014

Latest revision as of 19:35, 10 February 2020

(59 intermediate revisions by 24 users not shown)

Line 1:

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

{{AFC submission|d|nn|declinets=20140305121838|decliner=Anupmehra|ts=20140212132034|u=Rod.bishti|ns=5|small=yes}}{{AFC submission|d|reason|3=You ''must'' provide [[WP:Sourcing]] to [[WP:Reliable sources]]. If you read these two links, you'll have a much easier time publishing an article.|declinets= 20140122165008|decliner= MatthewVanitas|ts=20140122152411 |u=Rod.bishti|ns=5}}

{{afc comment|1=See also, [[WP:REFB]] & [[WP:NOR]]. [[User:Anupmehra|<font size="3"><span style="font-family:Old English Text MT;color:black">Anupmehra</span></font>]] -[[User talk:Anupmehra|<font size="3"><span style="font-family:Monotype Corsiva;color:black">Let's talk!</span></font>]] 12:18, 5 March 2014 (UTC)}}

[[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/|chapter-format=PDF|chapter=7}}</ref>

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

== Structure ==

[[Internet_messaging_platform|Messaging platforms]] are considered one of few [[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.

A process driven messaging service is a service where jobs and triggers can be put together to create a workflow for a message and the workflow 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" />

PDMS exchanges messages for the purpose of and all kind of messages/data calls between systems, applications and or human beings that is based upon [[Event-driven_process_chain|event-driven process]].<ref name="Event Driven Process Chain">{{cite book|last=Hommes|first=Lambertus Johannes|title=The evaluation of business process modeling techniques|date=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|language=English|format=PDF|chapter=7}}</ref>

=== 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. 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}}</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.

=== Structure ===

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

A process driven messaging service is a service were jobs and triggers can be put together to create a work flow for a message. The work flow can be seen as a process.

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|author2=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>

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.

==== WorkflowsJobs ====

A job creates something such as a task (e. g., sending 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.

[[File:workflow.png|frameless|Workflow]]

A workflow iin 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 all configuration. What also should note that a workflow is a container. It can apart from triggers and jobs contain groups or, artifacts. These items that the workflow can contain are then available to all triggers and jobs within the workflow.

=== Triggers ===

The concept of workflow can be seen as a template for a part of, or a whole business process.

A trigger—what starts/executes a workflow—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|chapter=10}}</ref>

Workflows can with the help of triggers be invoked by a number of different reasons. For example when something happens in the ___domain or an explicit call to invoke.

=== Processes ===

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.

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.

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-27|url=http://dl.acm.org/citation.cfm?doid=1281480.1281484|publisher=ACM, Inc.|___location=New York|language=English|format=PDF}}</ref>

With a well developed process driven messaging platform, all triggers and jobs can be exposed in a public API (application programming interface), and it will then be possible to create the process in the API.

==== Jobs ====

== Technology/programming ==

A job is an activity in a workflow. It represents something that a system do with the data, an activity in the system ___domain.

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

==== TriggersApplicable areas ====

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

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.

* [[Architectural pattern]]

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

==== Processes ====

* [[Critical Internet infrastructure]]

* [[Event-driven architecture]]

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

* [[Internet messaging platform]]

* [[Loose coupling]]

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

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

* [[Process mining]]

With a well developed process driven messaging platform all triggers and jobs can be exposured in a public API (application programming interface) and it will be possible to create the process in the API.

* [[Service (systems architecture)]]

* [[Workflow]]

Example of processes that can be managed in a process driven messaging platform.

=== Technology/programming ===

PDMS is based upon [[Event-driven_architecture|Event-Driven Architecture]] whereas the [[Architectural_pattern|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]].

=== Providers ===

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

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.

Mobile Response is a service that based its technology upon PDMS.

=== Applicable Areas ===

Areas whereas PDMS can be used in is System to System, [[Short_Message_Service#Application-to-Person_.28A2P.29_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 kind of messages/data calls between systems, applications and or human beings that is based upon [[Event-driven_process_chain|event-driven process]].

=== See also ===

* [[Internet_messaging_platform|Internet Messaging Platform]]

* [[Event-driven_architecture|Event-driven architecture]]

* [[Architectural_pattern|Architectural Pattern]]

* [[Critical_Internet_infrastructure|Critical Internet infrastructure]]

* [[Loose_coupling|Loose coupling]]

* [[Short_Message_Service#Application-to-Person_.28A2P.29_SMS|Application-to-Person (A2P) SMS]]

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

== References ==

{{Reflist}}

[[Category:Message transfer agents]]

<references />

[[Category:Enterprise application integration]]

[[Category:Text messaging]]

[[Internet_messaging_platform]]

[[Category:Mobile telecommunications standards]]

[[Event-driven_architecture]]

[[Architectural_pattern]]

[[Critical_Internet_infrastructure]]

[[Loose_coupling]]

[[Critical_Internet_infrastructure]]

[[Event-driven_process_chain]]

[[Short_Message_Service#Application-to-Person_.28A2P.29_SMS]]

[[Machine-to-Machine]]

[[Service_(systems_architecture)}}]]