Abstract: The sharing of objects may be executed by performing various share type administrations. Objects may be shared directly to a site or may be made available indirectly for reuse by a site. The objects shared and made available for reuse may be added to the site to which they are shared and made available for reuse. References to the objects shared and made available for reuse are stored in repositories in response to, and in accordance with, the share type administration performed. The storage of the references to objects is based on privileges associated with at least one of a repository, a site and a user. Objects made available for reuse by, and shared to, a site may be made unavailable for reuse by, and unshared to, the site through the execution of a share type administration.

Abstract: The sharing of objects may be executed by performing various share type administrations. Objects may be shared directly to a site or may be made available indirectly for reuse by a site. The objects shared and made available for reuse may be added to the site to which they are shared and made available for reuse. References to the objects shared and made available for reuse are stored in repositories in response to, and in accordance with, the share type administration performed. The storage of the references to objects is based on privileges associated with at least one of a repository, a site and a user. Objects made available for reuse by, and shared to, a site may be made unavailable for reuse by, and unshared to, the site through the execution of a share type administration.

Abstract: The sharing of objects may be executed by performing various share type administrations. Objects may be shared directly to a site or may be made available indirectly for reuse by a site. The objects shared and made available for reuse may be added to the site to which they are shared and made available for reuse. References to the objects shared and made available for reuse are stored in repositories in response to, and in accordance with, the share type administration performed. The storage of the references to objects is based on privileges associated with at least one of a repository, a site and a user. Objects made available for reuse by, and shared to, a site may be made unavailable for reuse by, and unshared to, the site through the execution of a share type administration.

Abstract: The sharing of objects may be executed by performing various share type administrations. Objects may be shared directly to a site or may be made available indirectly for reuse by a site. The objects shared and made available for reuse may be added to the site to which they are shared and made available for reuse. References to the objects shared and made available for reuse are stored in repositories in response to, and in accordance with, the share type administration performed. The storage of the references to objects is based on privileges associated with at least one of a repository, a site and a user. Objects made available for reuse by, and shared to, a site may be made unavailable for reuse by, and unshared to, the site through the execution of a share type administration.

Abstract: The sharing of objects may be executed by performing various share type administrations. Objects may be shared directly to a site or may be made available indirectly for reuse by a site. The objects shared and made available for reuse may be added to the site to which they are shared and made available for reuse. References to the objects shared and made available for reuse are stored in repositories in response to, and in accordance with, the share type administration performed. The storage of the references to objects is based on privileges associated with at least one of a repository, a site and a user. Objects made available for reuse by, and shared to, a site may be made unavailable for reuse by, and unshared to, the site through the execution of a share type administration.

Abstract: The sharing of objects may be executed by performing various share type administrations. Objects may be shared directly to a site or may be made available indirectly for reuse by a site. The objects shared and made available for reuse may be added to the site to which they are shared and made available for reuse. References to the objects shared and made available for reuse are stored in repositories in response to, and in accordance with, the share type administration performed. The storage of the references to objects is based on privileges associated with at least one of a repository, a site and a user. Objects made available for reuse by, and shared to, a site may be made unavailable for reuse by, and unshared to, the site through the execution of a share type administration.

Abstract: Disclosed are embodiments of a method, system and computer program product for deploying components of a site between systems in a portal framework. In one embodiment, file assets as well as non-file assets of at least one component of a site designated for export are stored as an export file. Non-file assets may be constructed as an extensible markup language fragment, such as an XML fragment, having a predetermined structure. In one embodiment, the site comprises a collection of software objects that can be manipulated by a set of users having assigned privileges defined by permissions associated with each software object in the collection of software objects. The export file is transferred to a remote system such as a web portal. The assets, which are configured to operate on the remote system, are extracted from the export file to a plurality of locations on the remote system.

Abstract: The deployment of components may be executed by performing various deployment type administrations. Components of a system may be exported and imported by storing assets of the components to a file and transferring the assets to another system for extraction. The extracted assets are configured to be operable on the system to which it is transferred. The assets include file assets and non-file assets. The non-file assets may be constructed as an extensible markup language fragment, such as an XML fragment, having a predetermined structure.

Abstract: The sharing of objects may be executed by performing various share type administrations. Objects may be shared directly to a site or may be made available indirectly for reuse by a site. The objects shared and made available for reuse may be added to the site to which they are shared and made available for reuse. References to the objects shared and made available for reuse are stored in repositories in response to, and in accordance with, the share type administration performed. The storage of the references to objects is based on privileges associated with at least one of a repository, a site and a user. Objects made available for reuse by, and shared to, a site may be made unavailable for reuse by, and unshared to, the site through the execution of a share type administration.