Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: Embodiments of the systems and methods described herein provide a plurality of entry templates that can be designed to direct and govern potentially unskilled users, clerks, or automated entry processes in the entry and manipulation of content. According to an embodiment, an entry template can include information as to where to store content, how to store content, default values for the actual content and metadata relating to the content, associated additional content, security access to some or all of the same, or any combinations of the foregoing or similar information. According to another embodiment, the entry template may include one or more associated workflow processes such that when content is entered using the template, the workflow processes launch and move the content or related metadata to designated individuals or computer programs for designated actions.