Content deleted Content added
Rod.bishti (talk | contribs) No edit summary |
→Workflows: see WP:NOTED, MOS:NOTED, and WP:OPED |
||
| (89 intermediate revisions by 26 users not shown) | |||
Line 1:
A '''process driven messaging service''' ('''PDMS''') is
[[
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 is services that are process oriented and that exchange messages/data calls. An 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
A workflow
A [[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.
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.
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.
▲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.
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>
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
▲==== Processes ====
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>
▲A process starts at some point in the system. For example when a trigger executes an instance of a workflow.
Areas
▲A process driven messaging service is often used when managing a more or less complex business processes.
* [[Short Message Service#Application-to-person (A2P) SMS|Application-to-person (A2P) SMS]]
* [[Critical Internet infrastructure]]▼
* [[Event-driven architecture]]▼
* [[Internet messaging platform]]
* [[Loose coupling]]▼
* [[Machine to machine|Machine to machine (M2M)]]
* [[Process mining]]
* [[Service (systems architecture)]]
* [[Workflow]]
== References ==
▲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.
{{Reflist}}
[[Category:Message transfer agents]]
[[Category:Enterprise application integration]]
[[Category:Text messaging]]
▲=== Technology/programming ===
[[Category:Mobile telecommunications standards]]
▲=== Providers ===
▲=== Applicable Areas ===
▲Areas whereas PDMS can be used in is System to System, A2P with the difference that other message types can be included in the PDMP, Application to Application, System to Person, M2M and all kind of messages/data calls between systems, applications and or human beings that is based upon event-driven process.
▲=== See also ===
▲* Event-driven architecture
▲* Architectural Pattern
▲* Critical Internet infrastructure
▲* Loose coupling
| |||