MOM architecture (Cloud) - Historique des versions

Syfre le 10 mars 2020 à 07:05

2020-03-10T07:05:19Z

2020-03-10T07:05:05Z

2019-10-28T15:13:38Z

2019-10-28T15:12:57Z

2019-02-07T09:28:16Z

Queues

2019-02-07T09:19:13Z

Configuration

2019-02-07T07:04:58Z

2017-02-27T10:26:51Z

2017-02-27T09:55:08Z

Queues

2017-02-27T09:54:47Z

@@ Ligne 71 : / Ligne 71 : @@
 [[Category:Architecture]]
 [[Category:File d'attente]]
-[[Category:Vesrion900]]
+[[Category:Version900]]

@@ Ligne 71 : / Ligne 71 : @@
 [[Category:Architecture]]
 [[Category:File d'attente]]
-[[Category:Latest]]
+[[Category:Vesrion900]]

← Version précédente		Version du 28 octobre 2019 à 15:13
Ligne 63 :		Ligne 63 :

	It may be selected and configured at the Folder level in the administration.		It may be selected and configured at the Folder level in the administration.
		+
		+	See also :
		+
		+	* [[Message_de_traitement_(file_d%27attente)\|Messages]]

	[[Category:Cloud]]		[[Category:Cloud]]

@@ Ligne 66 : / Ligne 66 : @@
 [[Category:Cloud]]
 [[Category:Architecture]]
 [[Category:Latest]]

← Version précédente		Version du 7 février 2019 à 09:28
Ligne 50 :		Ligne 50 :

	{{tip\|Azure infrastructure offers two queue services, Azure Service bus and Azure queue storage. The later is used because of it's better latency.}}		{{tip\|Azure infrastructure offers two queue services, Azure Service bus and Azure queue storage. The later is used because of it's better latency.}}
		+
		+	==Messages==
		+	[[Message_de_traitement_(file_d%27attente)\|Messages]] are pieces of information exchanged using queues, in general a message content information to trigger a task.
		+
		+	A message content the type of task to be executed and the task's parameters.
		+
		+	==Tasks==
		+	Tasks are processing actions executed on receiving a message.

	==Configuration==		==Configuration==

@@ Ligne 52 : / Ligne 52 : @@
 ==Configuration==
-The MOM architecture replace the scheduler and business processes (workflow) available in On Premise deployments.
+The MOM architecture could replace the scheduler and business processes (workflow) available in On Premise deployments.
-−
-It must be selected and configured at the Folder level in the administration.
-−
-Note that in a multi tenancy deployment the MOM architecture is the only option available because the scheduler service and the Business processes service can't be started.
 [[Category:Cloud]]
 [[Category:Architecture]]
 [[Category:Latest]]

@@ Ligne 5 : / Ligne 5 : @@
 [[image:Cloud-architecture-mom-overview.png]]
-===Asynchronous operations===
+==Asynchronous operations==
 When the MOM architecture is used, the front services execute user actions as asynchronous tasks.
@@ Ligne 21 : / Ligne 21 : @@
 Because transparent asynchronous task require a minimum latency, the queue used for these tasks is separate and listeners used a shorter polling rate.
-===Queues===
+==Queues==
 The MOM architecture rely on a set of message queues.
@@ Ligne 51 : / Ligne 51 : @@
 {{tip|Azure infrastructure offers two queue services, Azure Service bus and Azure queue storage. The later is used because of it's better latency.}}
-===Configuration===
+==Configuration==
 The MOM architecture replace the scheduler and business processes (workflow) available in On Premise deployments.

@@ Ligne 34 : / Ligne 34 : @@
 |-
 |TASKP
-|This queue is used for scheduling of task.
+|This queue is used for scheduling of tasks.
 |-
 |TASK
@@ Ligne 46 : / Ligne 46 : @@
 |-
 |EVENTS
-|This queue is used for event processing.
+|This queue is used for events processing.
 |}

@@ Ligne 23 : / Ligne 23 : @@
 ===Queues===
 The MOM architecture rely on a set of message queues.
 Queue are specialized by task nature :
@@ Ligne 28 : / Ligne 30 : @@
 {|class="wikitable"
 |-
-!Virtual Queue name
+!Logical Queue name
 !Used for
 |-
@@ Ligne 48 : / Ligne 50 : @@
 {{tip|Azure infrastructure offers two queue services, Azure Service bus and Azure queue storage. The later is used because of it's better latency.}}
 [[Category:Cloud]]
 [[Category:Architecture]]