GP.Managed File Transfer - Revision history

Jan Schoonderbeek: added dataprot mgmt as adjacent service & updated maturity

2015-04-23T12:41:27Z

added dataprot mgmt as adjacent service & updated maturity

← Older revision		Revision as of 12:41, 23 April 2015
Line 1:		Line 1:
	{{Maturity\|2}}		{{Maturity\|3}}
	{{Pageheaderbox4GP		{{Pageheaderbox4GP
	\|name=Managed File Transfer		\|name=Managed File Transfer
	\|sector=Business Support		\|sector=Business Support
	\|version=0.1		\|version=0.2
	\|owner=J.A.H. Schoonderbeek		\|owner=J.A.H. Schoonderbeek
	\|summary=This Pattern provides a means to transport loosely structured data from a source to one or more targets, either ad hoc or structurally..		\|summary=This Pattern provides a means to transport loosely structured data from a source to one or more targets, either ad hoc or structurally..
Line 106:		Line 106:
	* Storage space: enough space needs to be present to store the maximum volume of files that may reside at the facility at any given time (including exceptional times such as when one or more sources cannot accept files for any given reason, e.g. connectivity issues);		* Storage space: enough space needs to be present to store the maximum volume of files that may reside at the facility at any given time (including exceptional times such as when one or more sources cannot accept files for any given reason, e.g. connectivity issues);
	* Business continuity: when a technical problem or disaster impedes the MFT facility, files already accepted from the source but not yet delivered to (all) targets may be at risk of loss or corruption. The connection between the MFT facility and the File Storage service should correctly handle such events.		* Business continuity: when a technical problem or disaster impedes the MFT facility, files already accepted from the source but not yet delivered to (all) targets may be at risk of loss or corruption. The connection between the MFT facility and the File Storage service should correctly handle such events.
			}}
			{{Generic Pattern Adjacent Service Row
			\|service=GS.Data Protection Management
			\|choice=May
			\|reason=When data en route between sender and recipient(s) is residing in a Managed File Transfer facility, it needs to be protected from corruption and data loss, possibly even in the event of a total loss of the MFT facility itself. Adequate protection may be obtained by calling upon an external Data Protection Management service.
	}}		}}
	{{Generic Pattern Adjacent Service Row		{{Generic Pattern Adjacent Service Row

Jan Schoonderbeek: link to Message Formatting updated

2015-02-02T06:31:32Z

link to Message Formatting updated

← Older revision		Revision as of 06:31, 2 February 2015
Line 78:		Line 78:
	}}		}}
	{{Generic Pattern Composition Row		{{Generic Pattern Composition Row
	\|function=GF.Message ~~Client~~		\|function=GF.Message Formatting
	\|choice=May		\|choice=May
	\|reason=When the MFT facility makes use of a Message Handling services, then the Message ~~Client~~ functionality provides the interface to such a service.		\|reason=When the MFT facility makes use of a Message Handling services, then the Message Formatting functionality provides the interface to such a service.
	}}		}}
	{{Table Ending}}		{{Table Ending}}

Jan Schoonderbeek: corrected graphic size

2014-10-21T05:06:50Z

corrected graphic size

← Older revision		Revision as of 05:06, 21 October 2014
Line 15:		Line 15:
	\|graphic=GP.Managed_File_Transfer.png		\|graphic=GP.Managed_File_Transfer.png
	\|source=GP.		\|source=GP.
	\|size=~~706x511px~~		\|size=710px
	\|title=Generic Pattern Managed File Transfer		\|title=Generic Pattern Managed File Transfer
	\|kind=Generic		\|kind=Generic

Jan Schoonderbeek: added Messaging components

2014-10-21T05:01:58Z

added Messaging components

← Older revision		Revision as of 05:01, 21 October 2014
Line 14:		Line 14:
	{{Pattern Graphic		{{Pattern Graphic
	\|graphic=GP.Managed_File_Transfer.png		\|graphic=GP.Managed_File_Transfer.png
	\|size=~~706px~~		\|source=GP.
			\|size=706x511px
	\|title=Generic Pattern Managed File Transfer		\|title=Generic Pattern Managed File Transfer
	\|kind=Generic		\|kind=Generic
Line 75:		Line 76:
	\|choice=May		\|choice=May
	\|reason=When the MFT facility is required to deliver files to multiple targets, then this function models the handling of addressing and routing.		\|reason=When the MFT facility is required to deliver files to multiple targets, then this function models the handling of addressing and routing.
			}}
			{{Generic Pattern Composition Row
			\|function=GF.Message Client
			\|choice=May
			\|reason=When the MFT facility makes use of a Message Handling services, then the Message Client functionality provides the interface to such a service.
	}}		}}
	{{Table Ending}}		{{Table Ending}}
Line 100:		Line 106:
	* Storage space: enough space needs to be present to store the maximum volume of files that may reside at the facility at any given time (including exceptional times such as when one or more sources cannot accept files for any given reason, e.g. connectivity issues);		* Storage space: enough space needs to be present to store the maximum volume of files that may reside at the facility at any given time (including exceptional times such as when one or more sources cannot accept files for any given reason, e.g. connectivity issues);
	* Business continuity: when a technical problem or disaster impedes the MFT facility, files already accepted from the source but not yet delivered to (all) targets may be at risk of loss or corruption. The connection between the MFT facility and the File Storage service should correctly handle such events.		* Business continuity: when a technical problem or disaster impedes the MFT facility, files already accepted from the source but not yet delivered to (all) targets may be at risk of loss or corruption. The connection between the MFT facility and the File Storage service should correctly handle such events.
			}}
			{{Generic Pattern Adjacent Service Row
			\|service=GS.Message Handling
			\|choice=May
			\|reason=This service may be adjacent because of either of the following reasons:
			* files are transported in and/or out of the MFT facility via a messaging protocol;
			* the MFT facility uses Message Handling services to notify security, operational and business users about events in the facility, such as failure/success of file transfers.
	}}		}}
	{{Table Ending}}		{{Table Ending}}
	{{Text Footer GP}}		{{Text Footer GP}}

Jan Schoonderbeek: intermediate save

2014-10-20T13:17:29Z

intermediate save

← Older revision		Revision as of 13:17, 20 October 2014
Line 7:		Line 7:
	\|summary=This Pattern provides a means to transport loosely structured data from a source to one or more targets, either ad hoc or structurally..		\|summary=This Pattern provides a means to transport loosely structured data from a source to one or more targets, either ad hoc or structurally..
	}}		}}
	A realization of this Pattern handles the reception and/or collection of ~~data in a loosely structured form ("~~files") from a source, and their delivery to and/or collection by one or more targets. It may also additionally modify the files by transcoding, encrypting/decrypting, (de)compressing, and/or it may provide means to modify the files in transit in other respects. Incoming and outgoing traffic may be regulated using predescribed rules and/or by schedules that act on times, periods or order. The Pattern requires use of an instance of Data Transport (and optionally Message Handling), since the data to be transported comes in and goes out over these services. Most data transfers will require the Managed File Transfer Pattern to authenticate itself to the source and/or target. Furthermore functionality can be present to provide logging of each file transfer for operational and security purposes.		Managed File Transfer (abbreviated MFT) indicates the automated transfer of data in a loosely structured form ("files") between IT facilities. These facilities can be owned by the organization, but an MFT instance may also be used to transfer files into or out of the organization, from or to external IT systems. Furthermore, human users may also make use of the MFT pattern to exchange data with other users and/or IT systems.
			A realization of this MFT Pattern handles the reception and/or collection of files from a source, and their delivery to and/or collection by one or more targets. It may also additionally modify the files by transcoding, encrypting/decrypting, (de)compressing, and/or it may provide means to modify the files in transit in other respects. Incoming and outgoing traffic may be regulated using predescribed rules and/or by schedules that act on times, periods or order. The Pattern requires use of an instance of Data Transport (and optionally Message Handling), since the data to be transported comes in and goes out over these services. Most data transfers will require the Managed File Transfer Pattern to authenticate itself to the source and/or target. Furthermore functionality can be present to provide logging of each file transfer for operational and security purposes.
	{{Pattern Realizes		{{Pattern Realizes
	\|service=GS.Managed File Transfer		\|service=GS.Managed File Transfer
Line 13:		Line 14:
	{{Pattern Graphic		{{Pattern Graphic
	\|graphic=GP.Managed_File_Transfer.png		\|graphic=GP.Managed_File_Transfer.png
	\|size=~~650px~~		\|size=706px
	\|title=Generic Pattern Managed File Transfer		\|title=Generic Pattern Managed File Transfer
	\|kind=Generic		\|kind=Generic
	}}		}}
	{{Generic Pattern Composition}}		{{Generic Pattern Composition}}
			{{Generic Pattern Composition Row
			\|function=GF.File Engine
			\|choice=Must
			\|reason=This function represents the core intelligence of the Managed File Transfer service. This function performs the collection or accepting of files from the source, and the transmission or offering of files to one or more targets.
			}}
			{{Generic Pattern Composition Row
			\|function=GF.Presentation Engine
			\|choice=Must
			\|reason=This function represents the transcoding that is required when a source offers a file in a different format and/or using a different transfer protocol from the format/protocol used by the file transfer's target(s). Furthermore, if the Pattern offers ad hoc file transfers to human users, then this function shapes the users' experience when using the Managed File Transfer service (e.g. a web environment for uploading and downloading the files).
			}}
			{{Generic Pattern Composition Row
			\|function=GF.Caching
			\|choice=Must
			\|reason=Any file in transit will be buffered in the Managed File Transfer facility while it is processing file transfer tasks such as transcoding. This transient storage of files inside the MFT facility needs attention because of three aspects:
			* Security: the storing of files needs to be secured to the level that's appropriate for the confidentiality required by the business and security department;
			* Storage space: enough space needs to be present to store the maximum volume of files that may reside in transient storage at the facility at any given time; an overflow to the adjacent service File Storage may be in order;
			* Business continuity: when a technical problem or disaster impedes the MFT facility, measures must be taken to account for files that were residing only in transient storage at the time of the problem.
			}}
	{{Generic Pattern Composition Row		{{Generic Pattern Composition Row
	\|function=GF.Rules Engine		\|function=GF.Rules Engine
	\|choice=~~Must~~		\|choice=May
	\|reason=This function represents the intelligence that ~~drives~~ extra manipulation of files in transit, advanced exception handling, logging and/or routing by the Pattern. Active collection of information on the files in transit, source and/or target(s) may lead to execution of (implicit or explicit) rules.		\|reason=This function represents the additional intelligence that can drive extra manipulation of files in transit, advanced exception handling, logging and/or routing by the Pattern. Active collection of information on the files in transit, source and/or target(s) may lead to execution of (implicit or explicit) rules.
	}}		}}
	{{Generic Pattern Composition Row		{{Generic Pattern Composition Row
Line 41:		Line 60:
	* Administering schedules for automated file transfers.		* Administering schedules for automated file transfers.
	Since the files transferred by the Pattern may be business critical and/or have a certain level of confidentiality, care must be taken to limit access to this function to authorized users.		Since the files transferred by the Pattern may be business critical and/or have a certain level of confidentiality, care must be taken to limit access to this function to authorized users.
			}}
			{{Generic Pattern Composition Row
			\|function=GF.Encryption
			\|choice=May
			\|reason=This function can be used to model the encryption/decryption that is associated with secure file transfer protocols, as well as the manipulation of files in transit, when the MFT is required to encrypt/decrypt files or file archives.
			}}
			{{Generic Pattern Composition Row
			\|function=GF.Reduction
			\|choice=May
			\|reason=This function can be used to model the compression that is often associated with file transfer protocols, as well as the manipulation of files in transit, when the MFT is required to compress/decompress files or file archives, or manipulate files that sit inside a file archive.
			}}
			{{Generic Pattern Composition Row
			\|function=GF.Distribution
			\|choice=May
			\|reason=When the MFT facility is required to deliver files to multiple targets, then this function models the handling of addressing and routing.
	}}		}}
	{{Table Ending}}		{{Table Ending}}
	{{Pattern Adjacent Services}}		{{Pattern Adjacent Services}}
			{{Generic Pattern Adjacent Service Row
			\|service=GS.Data Transport
			\|choice=Must
			\|reason=All files that an MFT facility handles come in and go out over a Data Transport service. Especially the transfer of files over one or more security delineations require attention, so the explicit modelling of Data Transport is recommended.
			}}
	{{Generic Pattern Adjacent Service Row		{{Generic Pattern Adjacent Service Row
	\|service=GS.Authentication+Authorization		\|service=GS.Authentication+Authorization
	\|choice=May		\|choice=May
	\|reason=The Pattern will likely be required to authenticate itself when collecting and/or delivering a file. Furthermore, the Pattern probably will require systems and users to authenticate themselves when they wish to transfer or collect files. Finally, access to the services provided by the Managed File Transfer Pattern must likely be limited to authorized personnel.		\|reason=The Pattern will likely be required to authenticate itself when collecting and/or delivering a file. Furthermore, the Pattern probably will require systems and users to authenticate themselves when they wish to transfer or collect files. Finally, access to the services provided by the Managed File Transfer Pattern must likely be limited to authorized personnel.
			}}
			{{Generic Pattern Adjacent Service Row
			\|service=GS.Facilities Monitoring
			\|choice=May
			\|reason=The logs of file transfers are of interest to security and operational personnel, as well as the business units that make use of Managed File Transfer. Connections with Facilities Monitoring services provide these monitoring services with the data with which they can provide their respective users the required insights and overview.
			}}
			{{Generic Pattern Adjacent Service Row
			\|service=GS.File Storage
			\|choice=Must
			\|reason=A file in transit will be stored in the Managed File Transfer facility when the target is required to actively fetch the file ("pull-out") instead of having the file delivered as soon as it enters the MFT from the source. This storage of files inside the MFT facility needs attention because of three aspects:
			* Security: the storing of files needs to be secured to the level that's appropriate for the confidentiality required by the business and security department;
			* Storage space: enough space needs to be present to store the maximum volume of files that may reside at the facility at any given time (including exceptional times such as when one or more sources cannot accept files for any given reason, e.g. connectivity issues);
			* Business continuity: when a technical problem or disaster impedes the MFT facility, files already accepted from the source but not yet delivered to (all) targets may be at risk of loss or corruption. The connection between the MFT facility and the File Storage service should correctly handle such events.
	}}		}}
	{{Table Ending}}		{{Table Ending}}
	{{Text Footer GP}}		{{Text Footer GP}}

Jan Schoonderbeek: Pattern started

2014-10-20T12:20:13Z

Pattern started

New page

{{Maturity|2}}
{{Pageheaderbox4GP
|name=Managed File Transfer
|sector=Business Support
|version=0.1
|owner=J.A.H. Schoonderbeek
|summary=This Pattern provides a means to transport loosely structured data from a source to one or more targets, either ad hoc or structurally..
}}
A realization of this Pattern handles the reception and/or collection of data in a loosely structured form ("files") from a source, and their delivery to and/or collection by one or more targets. It may also additionally modify the files by transcoding, encrypting/decrypting, (de)compressing, and/or it may provide means to modify the files in transit in other respects. Incoming and outgoing traffic may be regulated using predescribed rules and/or by schedules that act on times, periods or order. The Pattern requires use of an instance of Data Transport (and optionally Message Handling), since the data to be transported comes in and goes out over these services. Most data transfers will require the Managed File Transfer Pattern to authenticate itself to the source and/or target. Furthermore functionality can be present to provide logging of each file transfer for operational and security purposes.
{{Pattern Realizes
|service=GS.Managed File Transfer
}}
{{Pattern Graphic
|graphic=GP.Managed_File_Transfer.png
|size=650px
|title=Generic Pattern Managed File Transfer
|kind=Generic
}}
{{Generic Pattern Composition}}
{{Generic Pattern Composition Row
|function=GF.Rules Engine
|choice=Must
|reason=This function represents the intelligence that drives extra manipulation of files in transit, advanced exception handling, logging and/or routing by the Pattern. Active collection of information on the files in transit, source and/or target(s) may lead to execution of (implicit or explicit) rules.
}}
{{Generic Pattern Composition Row
|function=GF.Logging
|choice=May
|reason=This function is often included, as logs of file transfers are required not only by Operations, but also Security/Compliance. Furthermore, a business entity responsible for sending files, or one that expects incoming files, may require access to the logged information to verify data transfers.
}}
{{Generic Pattern Composition Row
|function=GF.Scheduling
|choice=May
|reason=Scheduling can serve to initiate file tranfers and/or internal maintenance tasks, on regular or predetermined times.
}}
{{Generic Pattern Composition Row
|function=GF.Controlling
|choice=Must
|reason=This function models the manner in which the Pattern's administrators, and possibly authorized clients, can administer file transfers. Among the administrative tasks can be the following:
* Administering file transfer end points;
* Administeringfile transfer tasks (which in turn make use of transfer end points);
* Administering schedules for automated file transfers.
Since the files transferred by the Pattern may be business critical and/or have a certain level of confidentiality, care must be taken to limit access to this function to authorized users.
}}
{{Table Ending}}
{{Pattern Adjacent Services}}
{{Generic Pattern Adjacent Service Row
|service=GS.Authentication+Authorization
|choice=May
|reason=The Pattern will likely be required to authenticate itself when collecting and/or delivering a file. Furthermore, the Pattern probably will require systems and users to authenticate themselves when they wish to transfer or collect files. Finally, access to the services provided by the Managed File Transfer Pattern must likely be limited to authorized personnel.
}}
{{Table Ending}}
{{Text Footer GP}}