PAT.Application Hosting - Revision history

Jan Schoonderbeek: updated pres eng optional

2013-08-16T05:20:09Z

updated pres eng optional

← Older revision		Revision as of 05:20, 16 August 2013
Line 20:		Line 20:
	}}		}}
	{{Pattern Type Composition}}		{{Pattern Type Composition}}
			{{Pattern Type Composition Row
			\|facility=BT.Application Engine
			\|choice=must
			\|reason=This BBT delivers the core functionality of the pattern.
			}}
	{{Pattern Type Composition Row		{{Pattern Type Composition Row
	\|facility=BT.Presentation Engine		\|facility=BT.Presentation Engine
	\|choice=~~must~~		\|choice=may
	\|reason=This BBT delivers an important part of the core functionality of any application hosting solution: the presentation of the application to the client. The technology used here must match those available at the client (e.g. HTTP implies browser, X Window implies X Server etc)		\|reason=This BBT delivers an important part of the core functionality of any application hosting solution: the presentation of the application to the client - although an Application Hosting facility may be deployed behind a separate facility that takes care of this. The technology used here must match those available at the client (e.g. HTTP implies browser, X Window implies X Server etc)
	}}		}}
	{{Pattern Type Composition Row		{{Pattern Type Composition Row
Line 29:		Line 34:
	\|choice=may		\|choice=may
	\|reason=When combining multiple hosted applications, Presentation Aggregation may serve to share (presentation-specific) functionality.		\|reason=When combining multiple hosted applications, Presentation Aggregation may serve to share (presentation-specific) functionality.
	}}
	~~{{Pattern Type Composition Row~~
	~~\|facility=BT.Application Engine~~
	~~\|choice=must~~
	~~\|reason=This BBT delivers the core functionality of the pattern.~~
	}}		}}
	{{Pattern Type Composition Row		{{Pattern Type Composition Row

Jan Schoonderbeek: finally added message coordination

2013-03-18T12:22:03Z

finally added message coordination

← Older revision		Revision as of 12:22, 18 March 2013
Line 49:		Line 49:
	\|choice=may		\|choice=may
	\|reason=The Application Hosting facility should preferably be managed by a centralized facility, but if this is not possible or feasible, then a means must be offered to manage the facility itself - and the Control Interface offers this means. Note that this facility is limited to the Application Hosting facility, and cannot directly manage the applications running on the Application Hosting facility.		\|reason=The Application Hosting facility should preferably be managed by a centralized facility, but if this is not possible or feasible, then a means must be offered to manage the facility itself - and the Control Interface offers this means. Note that this facility is limited to the Application Hosting facility, and cannot directly manage the applications running on the Application Hosting facility.
			}}
			{{Pattern Type Composition Row
			\|facility=BT.Message Coordination
			\|choice=may
			\|reason=If an Application Hosting facility is to be able to offer its applications the possibility to send out messages (such as e-mail), then this function acts as intermediary between the application and the message handling service
	}}		}}
	{{Table Ending}}		{{Table Ending}}

Jan Schoonderbeek: link fixes

2013-01-10T07:40:35Z

link fixes

← Older revision		Revision as of 07:40, 10 January 2013
Line 21:		Line 21:
	{{Pattern Type Composition}}		{{Pattern Type Composition}}
	{{Pattern Type Composition Row		{{Pattern Type Composition Row
	\|facility=BT~~.SE~~.Presentation		\|facility=BT.Presentation Engine
	\|choice=must		\|choice=must
	\|reason=This BBT delivers an important part of the core functionality of any application hosting solution: the presentation of the application to the client. The technology used here must match those available at the client (e.g. HTTP implies browser, X Window implies X Server etc)		\|reason=This BBT delivers an important part of the core functionality of any application hosting solution: the presentation of the application to the client. The technology used here must match those available at the client (e.g. HTTP implies browser, X Window implies X Server etc)
	}}		}}
	{{Pattern Type Composition Row		{{Pattern Type Composition Row
	\|facility=BT~~.SE~~.Presentation Aggregation		\|facility=BT.Presentation Aggregation
	\|choice=may		\|choice=may
	\|reason=When combining multiple hosted applications, Presentation Aggregation may serve to share (presentation-specific) functionality.		\|reason=When combining multiple hosted applications, Presentation Aggregation may serve to share (presentation-specific) functionality.
	}}		}}
	{{Pattern Type Composition Row		{{Pattern Type Composition Row
	\|facility=BT~~.SE~~.Application Engine		\|facility=BT.Application Engine
	\|choice=must		\|choice=must
	\|reason=This BBT delivers the core functionality of the pattern.		\|reason=This BBT delivers the core functionality of the pattern.
	}}		}}
	{{Pattern Type Composition Row		{{Pattern Type Composition Row
	\|facility=BT~~.MW~~.Scheduler		\|facility=BT.Scheduler
	\|choice=may		\|choice=may
	\|reason=While application hosting usually responds to client request, it may be convenient to have the application also respond to other triggers; the Scheduler BBT provides the capability for this.		\|reason=While application hosting usually responds to client request, it may be convenient to have the application also respond to other triggers; the Scheduler BBT provides the capability for this.
	}}		}}
	{{Pattern Type Composition Row		{{Pattern Type Composition Row
	\|facility=BT~~.MW~~.Transaction Coordination		\|facility=BT.Transaction Coordination
	\|choice=may		\|choice=may
	\|reason=When multiple instances of one business application are necessary AND the transactions that the facility must process are interdependent, then this BBT can provide the necessary coordination.		\|reason=When multiple instances of one business application are necessary AND the transactions that the facility must process are interdependent, then this BBT can provide the necessary coordination.
	}}		}}
	{{Pattern Type Composition Row		{{Pattern Type Composition Row
	\|facility=BT~~.SE~~.Control Interface		\|facility=BT.Control Interface
	\|choice=may		\|choice=may
	\|reason=The Application Hosting facility should preferably be managed by a centralized facility, but if this is not possible or feasible, then a means must be offered to manage the facility itself - and the Control Interface offers this means. Note that this facility is limited to the Application Hosting facility, and cannot directly manage the applications running on the Application Hosting facility.		\|reason=The Application Hosting facility should preferably be managed by a centralized facility, but if this is not possible or feasible, then a means must be offered to manage the facility itself - and the Control Interface offers this means. Note that this facility is limited to the Application Hosting facility, and cannot directly manage the applications running on the Application Hosting facility.

Jan Schoonderbeek: linkfix

2012-11-12T06:40:07Z

linkfix

← Older revision		Revision as of 06:40, 12 November 2012
Line 15:		Line 15:
	{{PAgraphic		{{PAgraphic
	\|graphic=PAT.Application Hosting.png		\|graphic=PAT.Application Hosting.png
	\|source=Pattern ~~types~~.vsd		\|source=Pattern Types.vsd
	\|size=600px		\|size=600px
	\|title=Application Hosting pattern type		\|title=Application Hosting pattern type

Jan Schoonderbeek: start

2012-11-11T23:22:21Z

start

New page

{{Maturity|3}}
{{Pageheaderbox4PatternType
|PATname=Application Hosting
|summary=Accommodates (business) applications and services
|version=0.2
|owner=S.A.D. Jumelet
|sector=Infrastructure Sector Business Support
}}
Application hosting provides a set of facilities to accommodate (business) application services. Accommodation entails
* the runtime environment that the applications can use
* a means to expose or publish the application services' results using web protocols
* the connectivity that consumers of the application's services require for access
* and optionally, extra functionality to service the application services.
Authentication/authorization is optionally included in the pattern type, but should preferably be performed using the pattern Access Security, as most necessary security functions are located in this pattern.
{{PAgraphic
|graphic=PAT.Application Hosting.png
|source=Pattern types.vsd
|size=600px
|title=Application Hosting pattern type
}}
{{Pattern Type Composition}}
{{Pattern Type Composition Row
|facility=BT.SE.Presentation
|choice=must
|reason=This BBT delivers an important part of the core functionality of any application hosting solution: the presentation of the application to the client. The technology used here must match those available at the client (e.g. HTTP implies browser, X Window implies X Server etc)
}}
{{Pattern Type Composition Row
|facility=BT.SE.Presentation Aggregation
|choice=may
|reason=When combining multiple hosted applications, Presentation Aggregation may serve to share (presentation-specific) functionality.
}}
{{Pattern Type Composition Row
|facility=BT.SE.Application Engine
|choice=must
|reason=This BBT delivers the core functionality of the pattern.
}}
{{Pattern Type Composition Row
|facility=BT.MW.Scheduler
|choice=may
|reason=While application hosting usually responds to client request, it may be convenient to have the application also respond to other triggers; the Scheduler BBT provides the capability for this.
}}
{{Pattern Type Composition Row
|facility=BT.MW.Transaction Coordination
|choice=may
|reason=When multiple instances of one business application are necessary AND the transactions that the facility must process are interdependent, then this BBT can provide the necessary coordination.
}}
{{Pattern Type Composition Row
|facility=BT.SE.Control Interface
|choice=may
|reason=The Application Hosting facility should preferably be managed by a centralized facility, but if this is not possible or feasible, then a means must be offered to manage the facility itself - and the Control Interface offers this means. Note that this facility is limited to the Application Hosting facility, and cannot directly manage the applications running on the Application Hosting facility.
}}
{{Table Ending}}
{{Pattern Type Neighbors}}
{{Pattern_Type_Adjacent_PAT_Row
|pattern=PAT.Data Storage
|choice=may
|reason=Should the Application Hosting facility need to offer hosted applications the ability to store unstructured data, then inclusion of this pattern is needed.
}}
{{Pattern_Type_Adjacent_PAT_Row
|pattern=PAT.Data Management
|choice=may
|reason=Should the Application Hosting facility need to offer hosted applications the ability to store structured data, then inclusion of this pattern is needed.
}}
{{Pattern_Type_Adjacent_PAT_Row
|pattern=PAT.Authentication+Authorization
|choice=may
|reason=When authentication/authorization (A&A) is needed and cannot be (fully) catered for in an Access Security pattern, then the A&A facility is necessary. Authorization can be paired with Application Hosting relatively easy, but application of authorization is more secure if it takes place earlier in the traffic stream from client to application - hence the usage of Access Security --including A&A-- is preferable.
}}
{{Pattern_Type_Adjacent_PAT_Row
|pattern=PAT.Message Handling
|choice=may
|reason=This facility offers the means to deliver data to applications, and/or to enable applications to send data out. It may provide asynchronous messaging (like email or XML messages), synchronous messaging (like SOAP messages over HTTP or RPC) or both.
}}
{{Table Ending}}
{{PATfooter}}