|
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>
Rajan Kumar (born 25 February 1990), known popularly by his pen name Raj, is an Indian , lyricist and dedicated person.[1] Born in a small town Ekdari, East Champaran district in Bihar India . He started his career as a worker and moved towards in education at the age of 12 yr. film Ekdari.
== Structure ==
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.
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" />
=== 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 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|format=PDF}}</ref> Apart from triggers and jobs, it can contain groups or artifacts. These items that the workflow can contain are then available to all triggers and jobs within the workflow.
The concept of workflow can be seen as a template for a part of, or a whole business process. Workflows can with the help of triggers be invoked by a number of different reasons; for instance, when something happens in the ___domain or there is an explicit call to invoke.
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 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= 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 ===
{{Expand section|date=March 2014}}
A job is something that makes something, a task (e. g., send a message) or affect Standard Objects (e.g. way metadata in a unit). It is a task that describes what the system should do. A job can be several things that make something. A job can lead to an other job. For example, send a message or update anything. It represents something that a system do with the data, an activity in the system ___domain.
=== Triggers ===
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. The objects components that define business logic and behaviour 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, update and deletion.<ref>{{cite book|title=Rollbase in Action|publisher=Progress Software Corporation|pages=266–289|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.
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.
== Technology/programming ==
| 