International Business Machines Corporation

Malcolm C Ong

Christina Karen Lauridsen

Lauren Gabriellle Wilcox

Marshall Allen Lamb

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.

Summarizing portlet usage in a portal page

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.

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. Subsequent to storing separate detected usage metadata at multiple 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 multiple different times specified according to the separate usage metadata stored at each of the multiple different times, such that the summary portal page provides a summary of at least a selection of previous usage metadata selected by a user of the at least one portal page based on usage metadata stored responsive to trigger events.

Summarizing portlet usage captured responsive to trigger events in a portal page

In some embodiments a mechanism creates a bookmark of a deployable web archives. In some embodiments, the bookmark includes deployment and runtime information of current and prior invocations of the deployable web archive, at least one user- and/or author-defined external specified tag describing the deployable web archive, and/or reference/link/access information to the deployable web archives.

Growing community of inventors

Pflugerville, TX, United States of America

Malcolm C Ong