The patent badge is an abbreviated version of the USPTO patent document. The patent badge does contain a link to the full patent document.
The patent badge is an abbreviated version of the USPTO patent document. The patent badge covers the following: Patent number, Date patent was issued, Date patent was filed, Title of the patent, Applicant, Inventor, Assignee, Attorney firm, Primary examiner, Assistant examiner, CPCs, and Abstract. The patent badge does contain a link to the full patent document (in Adobe Acrobat format, aka pdf). To download or print any patent click here.
Patent No.:
Date of Patent:
Dec. 11, 2012
Filed:
Feb. 19, 2009
Michael Blum, Aidlingen, DE;
Peter Fischer, Filderstadt-Bonlanden, DE;
Hendrik Haddorp, Holzgerlingen, DE;
Stefan Hepper, San Jose, CA (US);
Stefan Liesche, Boeblingen, DE;
Michael Marks, Kirchheim-Teck, DE;
Thomas Stober, Boeblingen, DE;
Michael Blum, Aidlingen, DE;
Peter Fischer, Filderstadt-Bonlanden, DE;
Hendrik Haddorp, Holzgerlingen, DE;
Stefan Hepper, San Jose, CA (US);
Stefan Liesche, Boeblingen, DE;
Michael Marks, Kirchheim-Teck, DE;
Thomas Stober, Boeblingen, DE;
International Business Machines Corporation, Armonk, NY (US);
Abstract
A predetermined business task of a composite application can be fulfilled. The composite application can include a set of components. The composite application is instantiated by a template means and a predefined collaborative context module controls the interaction of the set of components during the runtime of the composite application. A set of components fulfilling individual services on individual different server systems is leveraged by the composite application. During the instantiation of the composite application from a template, the referenced components (as types) are instantiated leading to runtime instances of these components. The interaction of the different components is controlled on individual different server systems utilizing a primary context module. The primary context module communicates with an appropriate collaborative module implemented locally on the respective set of servers, where the local context modules act as secondary context modules in relation to the primary context modules. For each of the secondary context modules, local components communicate to control the interaction of components.