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 flowworkflow for a message. ▼{{Orphan|date=March 2014}}{{copyedit|for=grammar and capitalization|date=March 2014}}
Infrastructure[[Internet messaging platform|Messaging Elementsplatforms]] . Whatare usedconsidered to[[Critical beInternet onlyinfrastructure|key referredInternet toinfrastructure aselements]]{{By awhom|date=October few2014}}. A concept that messageonce 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 work flow for a message.
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 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| chapter-url=http://repository.tudelft.nl/view/ir/uuid%3A1d209c45-4b2a-41f2-9e94-a54b8ee76d78/| archivedate=26042014|language=English|chapter-format=PDF|chapter=7}}</ref> ▼[[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.
▲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>
== Structure ==
A process driven messaging service is a service werewhere 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 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.<ref name="Event Driven Architecture" /> ▼
▲A workflow willis executeexecuted when a trigger getsis triggeredprompted. ThatThe trigger willcauses the causeactivation of one or more jobs to be executed. The jobswhich can , in turn , execute more jobs. WhenThe allworkflow jobswill havestill beenbe executedactive theeven workflowwhen willall stilljobs behave activebeen executed, but nothing happensoccurs until it is re-triggered again.<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 Workflowworkflow Processprocess is a container for a group of Workflowworkflow Statusesstatuses and Actionsactions, 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> ApartOther fromthan triggers and jobs, it can contain groups or artifacts. TheseThe items that thecan workflowbe cancontained containin 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 aeither part of, or a whole, business process. Workflows can with the help of triggers be invokedtriggered byfor a number of different reasons;, foran instance,example whenof which could be if something happenswere to happen in the ___domain or there iswere to be an explicit call to invoke.
The workflow will be in a state awaiting execution when the workflow, its triggers, and its jobs are active.
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 expectsrequire the last part of the workflowjob to be added first., Thatmeaning lastjobs partare wouldto be alisted job.in Alsoreverse jobsorder of execution. Jobs and triggers wantsalso to knowrequire the nextreverse stepsequential inlisting theof floworders when they are created, meaning that they too advocate creating the workflow in reverse order.<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=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 ===
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.
{{Expand section|date=March 2014}}
A job is an activity in a workflow. It represents something that a system do with the data, an activity in 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 triggertrigger—what represents something that has happened and causes jobs to execute. Instarts/executes a wayworkflow—prompts wethe can thinkexecution of it as what starts/executes a workflowactions. The objectsobject's components that define business logic and behaviourbehavior 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, updateupdating, and deletion.<ref>{{cite book|title=Rollbase in Action|publisher=Progress Software Corporation|pages=266-289266–289|chapter-url=http://www.progress.com/~/media/Progress/Documents/Rollbase/Rollbase%20in%20Action/Rollbase_in_Action.pdf|language=English|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.
With a well developed process driven messaging platform, all triggers and jobs can be exposuredexposed in a public API (application programming interface), and it will then be possible to create the process in the API.
== 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|language=English}}</ref>
== ProvidersApplicable areas ==
Areas whereaswhere 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 kindkinds 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 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 (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 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 ==
* [[Architectural pattern |Architectural Pattern]] ▼* [[Internet messaging platform|Internet Messaging Platform]] ▼* [[Short Message Service#Application-to- Personperson (A2P) SMS|Application-to- Personperson (A2P) SMS]] ▼* [[Event-driven architecture]] ▼▲* [[Architectural pattern|Architectural Pattern]]
* [[Critical Internet infrastructure]]
▲* [[Event-driven architecture]]
▲* [[Internet messaging platform |Internet Messaging Platform]]
* [[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 ==
{{Reflist}}
[[Category:Message transfer agents]]
{{uncategorized|date=March 2014}}
[[Category:Enterprise application integration]]
[[Category:Text messaging]]
[[Category:Mobile telecommunications standards]]
| 