Jan Schoonderbeek: linkfix

2012-11-12T06:40:49Z

linkfix

← Older revision		Revision as of 06:40, 12 November 2012
Line 10:		Line 10:
	{{PAgraphic		{{PAgraphic
	\|graphic=PAT.Message Handling.png		\|graphic=PAT.Message Handling.png
	\|source=Pattern ~~types~~.vsd		\|source=Pattern Types.vsd
	\|size=650px		\|size=650px
	\|title=Message Handling		\|title=Message Handling

Jan Schoonderbeek: start

2012-11-11T23:22:21Z

start

New page

{{Maturity|3}}
{{Pageheaderbox4PatternType
|PATname=Message Handling
|summary=Provides transport, storage and delivery of messages
|version=0.4
|owner=S.A.D. Jumelet
|sector=Infrastructure Sector Commons
}}
This Pattern handles transport, storage and delivery of messages between senders and recipients, which may be users, applications or other infrastructure facilities.
{{PAgraphic
|graphic=PAT.Message Handling.png
|source=Pattern types.vsd
|size=650px
|title=Message Handling
}}
{{Pattern Type Composition}}
{{Pattern Type Composition Row
|facility=BT.Message Engine
|choice=must
|reason=The Message Engine is the core facility of the Message Handling Pattern. It is responsible for receiving and sending messages, processing them (or delivering these messages to other facilities that process them), and making sure the messages are stored if they cannot continue on their way to the final recipient.
}}
{{Pattern Type Composition Row
|facility=BT.Name Resolution
|choice=may
|reason=This facility may be used to resolve high-level addresses of senders and receivers to corresponding lower-level addresses, e.g. from human readable mail addresses to IP addresses.
}}
{{Pattern Type Composition Row
|facility=BT.Message Distribution
|choice=must
|reason=This facility is used to direct messages to their destination, based on message addresses and/or message content. It enables a flexible usage of virtual paths (sometimes called Message Channels) between sender and receiver(s), without the necessity that senders have 'knowledge' of intermediate paths. On behalf of senders and receivers, this type of facility does need routing information, either automatically or configured.
}}
{{Pattern Type Composition Row
|facility=BT.Header Modification
|choice=may
|reason=In the process of message distribution, this facility can be used to change message headers to enable communication between senders and receivers that use different addressing formats.
}}
{{Pattern Type Composition Row
|facility=BT.Message Transformation
|choice=may
|reason=In the process of message distribution, this facility can be used to change message headers and/or content to enable communication between senders and receivers that use different message formats. Types of transformation encompass 'message splitting', 'message aggregation', 'message resequencing', 'message enrichment' and 'message content translation'.
}}
{{Pattern Type Composition Row
|facility=BT.Message Responding
|choice=may
|reason=This facility provides feed-back to message senders regarding the message sending and distribution process. For example, when a message is undeliverable, this facility reports failure of message delivery by formulating an appropriate message and sending it to the original message sender.
}}
{{Pattern Type Composition Row
|facility=BT.Message Store
|choice=must
|reason=Since this pattern must allow indirect communication between sender and receiver, messages need to be stored in the process of their transfer. The message store facility might have a temporary or a more long-term use, depending on it's location in the path of the message: intermediate stores along the way act as buffers only, but at the destination, a message may reside in the Message Store even after the client has read the message.
}}
{{Pattern Type Composition Row
|facility=BT.Archiving
|choice=may
|reason=This facility archives messages that are placed into the Message Store. This way, it is possible to conserve a copy of a messages for future reference.
}}
{{Pattern Type Composition Row
|facility=BT.Message Filtering
|choice=may
|reason=In the process of sending and receiving messages, it is possible to filter messages, based on a set of predefined rules or mechanisms. Basic filtering is done by checking headers, more advanced filtering may comprise payload or content filtering. If rule-based filtering is used, then the rules are stored in some sort of Permission Register.
}}
{{Pattern Type Composition Row
|facility=BT.Data Scanning
|choice=may
|reason=In the process of filtering messages, this facility might be used to scan message content, in order to support filtering decisions.
}}
{{Table Ending}}
{{Pattern Type Neighbors}}
{{Pattern_Type_Adjacent_PAT_Row
|pattern=PAT.Authentication+Authorization
|choice=may
|reason=This adjacent facility can server a number of purposes:
* to validate permissions of senders, before accepting messages from these senders;
* to authenticate and authorize clients that want to access the Message Store to access messages;
* to provide Message Filtering with appropriate filtering rules.
}}
{{Pattern_Type_Adjacent_PAT_Row
|pattern=PAT.Data Management
|choice=may
|reason=The storage of messages with a more permanent character benefits from the application of a Data Management solution, that stores messages in a structured and organized way.
}}
{{Table Ending}}
{{PATfooter}}

PAT.Message Handling - Revision history

Jan Schoonderbeek: linkfix

Jan Schoonderbeek: start