Abstract: Methods and apparatus are provided for run-time user control of system-generated content. A user is presented with the system-generated content and can configure one or more rules at run-time. The rules identify one or more automated actions to perform upon the system-generated content when one or more conditions are satisfied. The automated actions are executed upon the system-generated content when the one or more conditions are satisfied. The exemplary automated actions may comprise transform, retrieve, update and alert. The conditions can specify, for example, when to perform the automated actions. Active tags may optionally be attached to or embedded directly in the system-generated content or in a document containing the system-generated content. Tools are optionally provided to allow a user to manage active tags.

Abstract: A portal summary controller stores detected usage of at least one instance of at least one portlet application within at least one portal page at each of a plurality of different times. Responsive to a trigger to generate a summary portal page, the portal summary controller dynamically creates a summary portal page displaying a separate instance of the at least one portlet application for at least one of each of the plurality of different times specified according to the separate usage stored at each of the plurality of different times, such that the summary portal page provides a summary of at least a selection of previous usage of the at least one portal page. The trigger to generate a summary portal page includes a user selecting which previous stored portal usage, including usage of individual portlet applications, to summarize in the summary portal page, such that the summary portal page renders a summary of only that content selected by the user.

Abstract: A portal summary controller stores detected usage of at least one instance of at least one portlet application within at least one portal page at each of a plurality of different times. Responsive to a trigger to generate a summary portal page, the portal summary controller dynamically creates a summary portal page displaying a separate instance of the at least one portlet application for at least one of each of the plurality of different times specified according to the separate usage stored at each of the plurality of different times, such that the summary portal page provides a summary of at least a selection of previous usage of the at least one portal page. The trigger to generate a summary portal page includes a user selecting which previous stored portal usage, including usage of individual portlet applications, to summarize in the summary portal page, such that the summary portal page renders a summary of only that content selected by the user.

Abstract: A portal summary controller stores detected usage of at least one instance of at least one portlet application within at least one portal page at each of a plurality of different times. The portal summary controller dynamically creates a summary portal page displaying a separate instance of the at least one portlet application for at least one of each of the plurality of different times specified according to the detected usage separately stored at each of the plurality of different times, wherein the summary portal page provides a summary of at least a selection of a previous usage of the at least one portal page comprising each separate instance of the at least one portlet application that functions as if placed on the at least one portal page.

Abstract: A portal summary controller monitors usage metadata indicating current usage of at least one portlet within at least one portal page for one of multiple events specified to trigger storage of the usage metadata. Responsive to detecting one of the multiple events within the usage metadata which triggers storage, the portal summary controller stores the detected usage metadata at a current time of at least one instance of at least one portlet application within the at least one portal page.

Abstract: A mechanism is provided for applying individual user-generated deployment events to a grouping of bookmarked deployable Web archive files. The mechanism allows a user of a bookmarking service for deployable Web archive files to group bookmarked Web archive files according to criteria, such as tag names, and to perform actions, such as a deploy action, to all members of the group in a single user-generated event. The mechanism allows a user to perform a search of portlets meeting specified criteria. The user may then select portlets from the result set for deployment as a group. The mechanism also allows a user of the bookmarking service to tag pre-configured portlet groupings, or portal tabs. Users may choose to deploy not just a tagged portlet, but an entire tab of portlets in a single deployment action. The mechanism may also allow a user to deploy a collection of portal tabs.

Abstract: A portal summary controller stores detected usage of at least one instance of at least one portlet application within at least one portal page at each of a plurality of different times. The portal summary controller dynamically creates a summary portal page displaying a separate instance of the at least one portlet application for at least one of each of the plurality of different times specified according to the detected usage separately stored at each of the plurality of different times, wherein the summary portal page provides a summary of at least a selection of a previous usage of the at least one portal page comprising each separate instance of the at least one portlet application that functions as if placed on the at least one portal page.

Abstract: A portal summary controller stores detected usage of at least one instance of at least one portlet application within at least one portal page at each of a plurality of different times. Responsive to a trigger to generate a summary portal page, the portal summary controller dynamically creates a summary portal page displaying a separate instance of the at least one portlet application for at least one of each of the plurality of different times specified according to the separate usage stored at each of the plurality of different times, such that the summary portal page provides a summary of at least a selection of previous usage of the at least one portal page. The trigger to generate a summary portal page includes a user selecting which previous stored portal usage, including usage of individual portlet applications, to summarize in the summary portal page, such that the summary portal page renders a summary of only that content selected by the user.

Abstract: A portal summary controller monitors usage metadata indicating current usage of at least one portlet within at least one portal page for one of multiple events specified to trigger storage of the usage metadata. Responsive to detecting one of the multiple events within the usage metadata which triggers storage, the portal summary controller stores the detected usage metadata at a current time of at least one instance of at least one portlet application within the at least one portal page.

Abstract: A mechanism is provided for providing control over personalization of portal content. The mechanisms provide new tag types and management of these tags to be used in association with a portal application. Applications of the new tag types comprise filtering of new content in the form of recommendations or search results and filtering of accessed content in the form of session summaries. Users may specify user context or state via one or more profile tags or enhanced profile attributes. Users may generate new rules for displayed portlets or portlet recommendation lists. User defined rules may be based on existing available rule-building capabilities and user-defined context tags or enhanced profile attributes and private or public portlet or portal page tags. The portal summary service may configure generation of portal session summary data according to user-defined context, portlet or portal tags, and rules.

Abstract: A portal summary controller monitors usage metadata indicating current usage of at least one portlet within at least one portal page for one of multiple events specified to trigger storage of the usage metadata. Responsive to detecting one of the multiple events within the usage metadata which triggers storage, the portal summary controller stores the detected usage metadata at a current time of at least one instance of at least one portlet application within the at least one portal page.

Abstract: A mechanism is provided for applying individual user-generated deployment events to a grouping of bookmarked deployable Web archive files. The mechanism allows a user of a bookmarking service for deployable Web archive files to group bookmarked Web archive files according to criteria, such as tag names, and to perform actions, such as a deploy action, to all members of the group in a single user-generated event. The mechanism allows a user to perform a search of portlets meeting specified criteria. The user may then select portlets from the result set for deployment as a group. The mechanism also allows a user of the bookmarking service to tag pre-configured portlet groupings, or portal tabs. Users may choose to deploy not just a tagged portlet, but an entire tab of portlets in a single deployment action. The mechanism may also allow a user to deploy a collection of portal tabs.

Abstract: Methods and apparatus are provided for run-time user control of system-generated content. A user is presented with the system-generated content and can configure one or more rules at run-time. The rules identify one or more automated actions to perform upon the system-generated content when one or more conditions are satisfied. The automated actions are executed upon the system-generated content when the one or more conditions are satisfied. The exemplary automated actions may comprise transform, retrieve, update and alert. The conditions can specify, for example, when to perform the automated actions. Active tags may optionally be attached to or embedded directly in the system-generated content or in a document containing the system-generated content. Tools are optionally provided to allow a user to manage active tags.

Abstract: A portal summary controller stores detected usage of at least one instance of at least one portlet application within at least one portal page at each of a plurality of different times. Responsive to a trigger to generate a summary portal page, the portal summary controller dynamically creates a summary portal page displaying a separate instance of the at least one portlet application for at least one of each of the plurality of different times specified according to the separate usage stored at each of the plurality of different times, such that the summary portal page provides a summary of at least a selection of previous usage of the at least one portal page. The trigger to generate a summary portal page includes a user selecting which previous stored portal usage, including usage of individual portlet applications, to summarize in the summary portal page, such that the summary portal page renders a summary of only that content selected by the user.

Abstract: A portal summary controller monitors usage metadata indicating current usage of at least one portlet within at least one portal page for one of multiple events specified to trigger storage of the usage metadata. Responsive to detecting one of the multiple events within the usage metadata which triggers storage, the portal summary controller stores the detected usage metadata at a current time of at least one instance of at least one portlet application within the at least one portal page.