GP.Application Hosting - Revision history

Jan Schoonderbeek: link to Message Formatting updated

2015-02-02T06:33:22Z

link to Message Formatting updated

← Older revision		Revision as of 06:33, 2 February 2015
Line 22:		Line 22:
	{{Pattern Graphic		{{Pattern Graphic
	\|graphic=GP.Application Hosting.png		\|graphic=GP.Application Hosting.png
			\|source=GP.
	\|size=675px		\|size=675px
	\|title=Application Hosting		\|title=Application Hosting
Line 35:		Line 36:
	\|function=GF.Presentation Engine		\|function=GF.Presentation Engine
	\|choice=May		\|choice=May
	\|reason=This function delivers important support to the core functionality of any application hosting solution: the presentation of the application to the consumer. Note, however, that an Application Hosting service may be deployed behind a separate service that takes care of this. The technology used here must match those available at the service's consumer (e.g. HTTP implies browser, X Window implies X Server etc).		\|reason=This function delivers important support to the core functionality of any application hosting solution: the presentation of the application to the consumer. Note, however, that an Application Hosting service may be deployed behind a separate service that takes care of this. The technology used here must match those available at the service's consumer (e.g. HTTP implies browser, X Window implies X Server etc).
	}}		}}
	{{Generic Pattern Composition Row		{{Generic Pattern Composition Row
Line 53:		Line 54:
	* when transactions that are processed by the solution are interdependent with transactions taking place in other services;		* when transactions that are processed by the solution are interdependent with transactions taking place in other services;
	* when multiple instances of one business application need to be hosted AND the transactions that the solution must process are interdependent.		* when multiple instances of one business application need to be hosted AND the transactions that the solution must process are interdependent.

	}}		}}
	{{Generic Pattern Composition Row		{{Generic Pattern Composition Row
	\|function=GF.Message ~~Client~~		\|function=GF.Message Formatting
	\|choice=May		\|choice=May
	\|reason=If an Application Hosting facility is to be able to offer its hosted applications the possibility to send out and/or receive messages (such as e-mail), then this function acts as intermediary between the application and the message handling service		\|reason=If an Application Hosting facility is to be able to offer its hosted applications the possibility to send out and/or receive messages (such as e-mail), then this function acts as intermediary between the application and the message handling service
	}}		}}
	{{Generic Pattern Composition Row		{{Generic Pattern Composition Row
Line 64:		Line 64:
	\|choice=Must		\|choice=Must
	\|reason=When allowing consumers (such as users and/or administrators) the ability to change the configuration of the Application Hosting service, special care may be required to prevent unauthorized access to applications hosted and/or data accessed by the Pattern.		\|reason=When allowing consumers (such as users and/or administrators) the ability to change the configuration of the Application Hosting service, special care may be required to prevent unauthorized access to applications hosted and/or data accessed by the Pattern.
	Note that this function is limited to the Application Hosting facility, and cannot directly manage the applications running on the Application Hosting facility.		Note that this function is limited to the Application Hosting facility, and cannot directly manage the applications running on the Application Hosting facility.
	}}		}}
	{{Table Ending}}		{{Table Ending}}
Line 71:		Line 71:
	\|service=GS.Authentication+Authorization		\|service=GS.Authentication+Authorization
	\|choice=May		\|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.		\|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.
	}}		}}
	{{Generic Pattern Adjacent Service Row		{{Generic Pattern Adjacent Service Row
Line 86:		Line 86:
	\|service=GS.Message Handling		\|service=GS.Message Handling
	\|choice=May		\|choice=May
	\|reason=This service 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.		\|reason=This service 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}}		{{Table Ending}}
	{{Text Footer GP}}		{{Text Footer GP}}

Jan Schoonderbeek: New GP

2014-12-31T20:32:19Z

New GP

New page

{{Maturity|4}}
{{Pageheaderbox4GP
|name=Application Hosting
|sector=Business Support
|version=0.3
|owner=Jan Schoonderbeek
|summary=The Application Hosting function can accommodate (business) application services.
}}
The Application Hosting function can accommodate (business) application services. This entails:
* the runtime environment that the hosted applications can use;
* a means to expose or publish the application services' results to its users;
* the connectivity that consumers of the application's services require for access;
* and optionally, extra functionality to service the application services.

Examples of application services that can be hosted are:
* Applications that are used in a web environment, e.g. Java or .Net applications - in this case the Application Hosting service is provided by an "application server" such as a Tomcat or GlassFish;
* Binary applications, e.g. Windows or Apple applications - the Application Hosting service is then realized with a "server";
* Virtual Machines, such as virtual servers or desktops - the Application Hosting service is then realized by virtualization hosts.
{{Pattern Realizes
|service=GS.Application Hosting
}}
{{Pattern Graphic
|graphic=GP.Application Hosting.png
|size=675px
|title=Application Hosting
|kind=Generic
}}
{{Generic Pattern Composition}}
{{Generic Pattern Composition Row
|function=GF.Application Engine
|choice=Must
|reason=This delivers the core functionality of the Pattern.
}}
{{Generic Pattern Composition Row
|function=GF.Presentation Engine
|choice=May
|reason=This function delivers important support to the core functionality of any application hosting solution: the presentation of the application to the consumer. Note, however, that an Application Hosting service may be deployed behind a separate service that takes care of this. The technology used here must match those available at the service's consumer (e.g. HTTP implies browser, X Window implies X Server etc).
}}
{{Generic Pattern Composition Row
|function=GF.Presentation Aggregation
|choice=May
|reason=When combining multiple hosted applications, Presentation Aggregation may serve to share (presentation-specific) functionality.
}}
{{Generic Pattern Composition Row
|function=GF.Scheduling
|choice=May
|reason=While the service Application Hosting usually responds to consumer request, it may be convenient to have the service also respond to other triggers. The Scheduling function can model this capability.
}}
{{Generic Pattern Composition Row
|function=GF.Transaction Coordination
|choice=May
|reason=This function can provide the needed coordination in either of the following situations:
* when transactions that are processed by the solution are interdependent with transactions taking place in other services;
* when multiple instances of one business application need to be hosted AND the transactions that the solution must process are interdependent.

}}
{{Generic Pattern Composition Row
|function=GF.Message Client
|choice=May
|reason=If an Application Hosting facility is to be able to offer its hosted applications the possibility to send out and/or receive messages (such as e-mail), then this function acts as intermediary between the application and the message handling service
}}
{{Generic Pattern Composition Row
|function=GF.Controlling
|choice=Must
|reason=When allowing consumers (such as users and/or administrators) the ability to change the configuration of the Application Hosting service, special care may be required to prevent unauthorized access to applications hosted and/or data accessed by the Pattern.
Note that this function is limited to the Application Hosting facility, and cannot directly manage the applications running on the Application Hosting facility.
}}
{{Table Ending}}
{{Pattern Adjacent Services}}
{{Generic Pattern Adjacent Service Row
|service=GS.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.
}}
{{Generic Pattern Adjacent Service Row
|service=GS.Data Management
|choice=May
|reason=Should the Application Hosting pattern need to offer hosted applications the ability to store strictly structured data, or should it require this for itself, then it should include or connect with an instance of this service.
}}
{{Generic Pattern Adjacent Service Row
|service=GS.File Storage
|choice=May
|reason=Should the Application Hosting pattern need to offer hosted applications the ability to store loosely structured data, or should it require this for itself, then it should include or connect with an instance of this service.
}}
{{Generic Pattern Adjacent Service Row
|service=GS.Message Handling
|choice=May
|reason=This service 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}}
{{Text Footer GP}}