International Business Machines Corporation

Scott P Mills

Brett Edward Morris

Lauren Anne Mayes

Daniel S Whelan

Mann Chang

Michael J Mitchell

Vladimir Fridman

James A Iuliano

Eric T Dybdahl

Richard J Howarth

Embodiments of the invention provide techniques for incorporating functionality of a first web application into a second web application composed and managed by a component-based application framework, such as JSF. For example, the web pages of an existing application may be displayed to the user of a web application composed in the JSF framework, thus enabling the user to access the functionality of the secondary web application in a transparent and seamless manner. Further, the web application may be displayed using AJAX technology, in which page updates are performed asynchronously to user interactions. Embodiments of the invention may allow an application based on a component-based application framework to access functionality of a secondary web application, without requiring the applications to communicate directly.

Accessing external functionality within a component-based web application

Provided are techniques for managing, importing, and exporting teamspace templates and teamspaces in content repositories. A file is created using a teamspace template and associated metadata at a first content repository. The file is exported from the first content repository to a second content repository, wherein the file can be used to create a teamspace instance at the second content repository.

Managing, importing, and exporting teamspace templates and teamspaces in content repositories

Provided are techniques for self-provisioning a teamspace instance. A teamspace template including one or more teamspace characteristics and one or more user roles is generated. A teamspace instance is provisioned from a snapshot of the generated teamspace template using the one or more teamspace characteristics and the one or more user roles.

Self provisioning and applying role-based security to teamspaces in content repositories

Systems and methods access non-compatible content repositories that are not natively accessible to a content management system. A metadata registry maintains metadata about content stored in both compatible and non-compatible repositories. For content in a non-compatible repository, the metadata indicates a repository interface capable of accessing the non-compatible repository. The content manager communicates with the repository interfaces to access the content in non-compatible repositories. The content manager may receive a request for content in a non-compatible repository, refer to the metadata registry to select a repository interface to employ, transmit a request for the requested content to the selected repository interface, and receive the requested content from the repository interface. A repository interface registry maintains information about available repository interfaces. Entries may be added to either the metadata registry and the repository interface registry, thus allowing the systems and methods to be extended to be able to access additional non-compatible repositories.

System and method for accessing non-compatible content repositories

Systems access non-compatible content repositories that are not natively accessible to a content management system. A metadata registry maintains metadata about content stored in both compatible and non-compatible repositories. For content in a non-compatible repository, the metadata indicates a repository interface capable of accessing the non-compatible repository. The content manager communicates with the repository interfaces to access the content in non-compatible repositories. The content manager may receive a request for content in a non-compatible repository, refer to the metadata registry to select a repository interface to employ, transmit a request for the requested content to the selected repository interface, and receive the requested content from the repository interface. A repository interface registry maintains information about available repository interfaces. Entries may be added to either the metadata registry and the repository interface registry, thus allowing the systems to be extended to be able to access additional non-compatible repositories.

Growing community of inventors

Sammamish, WA, United States of America

Scott P Mills