Abstract: A method of providing annotations within a portal environment can include executing a portlet object having a tag, wherein the tag specifies an annotation service associated with an artifact presented by a graphical user interface of the portal environment. A visual identifier can be presented proximate to the artifact. The visual identifier can reference the annotation service. The method further can include creating an annotation using the annotation service responsive to the selection of the visual identifier.

Abstract: An end-user or administrator is allowed to couple portlets in a portal through user interface events taking place on the portal display itself. When the portal is displayed, if the user actuates a control corresponding to a property in a portlet, a menu of actions that can be performed with that data by other portlets is provided to the user. In addition to this “conventional” manner, an alternative manner of actuating the component is provided to the user such that if the user actuates the control in this alternative manner, the user is provided the option of making the chosen action “persistent,” so that the next time the control is actuated by the user, or the associated property is otherwise produced, the chosen action is performed automatically, without requiring the user to choose an action.

Abstract: A system and method is provided for integrating portlets. When viewing portlets within a portal container, a user is presented with a choice of one or more sources of data and, for each source, one or more actions that the user can take regarding the source. When an action is selected, it causes the source data to be transferred to one or more “target” portlets that have also been activated by the user. The set of actions available from a given source is automatically provided given the available target portlets. As each portlet is initialized, it informs a “broker” of the actions that the portlet supports along with the type of data that is used by the action. When a portal page is being constructed, each portlet identifies to the broker the sources of data within the portlet along with the values and data types corresponding to the sources.

Abstract: A user interface template that implements a task pattern for a model class and a model adapter that provides an interface for the application that conforms to the model class are identified. A user interface for the application is created from the identified user interface template and the identified model adapter. The user interface template may include a generic view and a generic controller. The model adapter may provide a business object interface, and may be configured to communicate with the application via a J2EE Connector Architecture (JCA) connector. The user interface template may define an abstract portlet, and creating a user interface includes creating a portlet instance that communicates with the application via the model adapter. The portlet instance may be configured using an application portlet builder portlet. The portlet builder may also identify the user interface template and the model adapter.

Abstract: An end-user or administrator is allowed to couple portlets in a portal through user interface events taking place on the portal display itself. When the portal is displayed, if the user actuates a control corresponding to a property in a portlet, a menu of actions that can be performed with that data by other portlets is provided to the user. In addition to this “conventional” manner, an alternative manner of actuating the component is provided to the user such that if the user actuates the control in this alternative manner, the user is provided the option of making the chosen action “persistent,” so that the next time the control is actuated by the user, or the associated property is otherwise produced, the chosen action is performed automatically, without requiring the user to choose an action.

Abstract: An end-user or administrator is allowed to couple portlets in a portal through user interface events taking place on the portal display itself. When the portal is displayed, if the user actuates a control corresponding to a property in a portlet, a menu of actions that can be performed with that data by other portlets is provided to the user. In addition to this “conventional” manner, an alternative manner of actuating the component is provided to the user such that if the user actuates the control in this alternative manner, the user is provided the option of making the chosen action “persistent,” so that the next time the control is actuated by the user, or the associated property is otherwise produced, the chosen action is performed automatically, without requiring the user to choose an action.

Abstract: A system and method is provided for integrating portlets. When viewing portlets within a portal container, a user is presented with a choice of one or more sources of data and, for each source, one or more actions that the user can take regarding the source. When an action is selected, it causes the source data to be transferred to one or more “target” portlets that have also been activated by the user. The set of actions available from a given source is automatically provided given the available target portlets. As each portlet is initialized, it informs a “broker” of the actions that the portlet supports along with the type of data that is used by the action. When a portal page is being constructed, each portlet identifies to the broker the sources of data within the portlet along with the values and data types corresponding to the sources.

Abstract: A system and method is provided for integrating portlets. When viewing portlets within a portal container, a user is presented with a choice of one or more sources of data and, for each source, one or more actions that the user can take regarding the source. When an action is selected, it causes the source data to be transferred to one or more “target” portlets that have also been activated by the user. The set of actions available from a given source is automatically provided given the available target portlets. As each portlet is initialized, it informs a “broker” of the actions that the portlet supports along with the type of data that is used by the action. When a portal page is being constructed, each portlet identifies to the broker the sources of data within the portlet along with the values and data types corresponding to the sources.

Abstract: Embodiments of the present invention address deficiencies of the art in respect to wiring components in a component based application and provide a method, system and computer program product for heuristically assembling components in a component based application. In one embodiment, a data processing system configured to assemble component based applications can include a component aggregation application including an application builder configured to assemble components into a component based application. The system further can include a property broker coupled to the component aggregation application and configured to apply a wiring scheme to selected components in a component based application. Finally, a collaborative heuristic integration matching engine (CHIME) can be coupled to the property broker and a data store of behaviorally derived data, the CHIME including program enabled to suggest components for assembly in a component based application based upon behaviorally derived data in the data store.

Abstract: Embodiments of the present invention address deficiencies of the art in respect to assembling an application using a component based model and provide a method, system and computer program product for re-wiring component based assemblies in a component based computing environment. In one embodiment, a data processing system for re-wiring component assemblies of component based user applications can include a component aggregation application configured to aggregate multiple components in an aggregation, a property broker coupled to the component aggregation application and configured to establish wires between selected ones of the components in the aggregation; and, re-wiring logic. The re-wiring logic can include program code enabled to re-wire selected ones of the components in the aggregation.

Abstract: A method of providing annotations within a portal environment can include executing a portlet object having a tag, wherein the tag specifies an annotation service associated with an artifact presented by a graphical user interface of the portal environment. A visual identifier can be presented proximate to the artifact. The visual identifier can reference the annotation service. The method further can include creating an annotation using the annotation service responsive to the selection of the visual identifier.

Abstract: Under the present invention, a request for web content is received from a user in a proxy portlet of a portal server. In response, the proxy portlet will obtain markup for the web content from the appropriate web application(s). Upon receipt, metadata corresponding to the markup will be analyzed to identify a set of (e.g., one or more) data values in the markup, as well as locations in the markup for inserting visual controls for the set of data values. Thereafter, additional markup for the visual controls will be generated and inserted into the markup for the web content at the identified locations without rewriting the web application(s). The portal page will then be aggregated and served to the end user.

Abstract: Methods, systems, and computer program products for programmatically determining whether components of a program are suitable for deployment in particular locations such as at the edge of a network. In preferred embodiments, program characteristics and operating environment characteristics, along with information about their interactions, are programmatically combined at deployment time to determine whether application components are edgeable. The disclosed approach enables people such as programmers (who are familiar with the program characteristics) and systems administrators (who are familiar with the operating environment characteristics) to each provide some control over the edgeability determination, along with other systems experts (who know how these features interact). Alternatively, this information or portions thereof may be supplied programmatically.

Abstract: The present invention provides a method, computer program product, and apparatus for allowing an end-user or administrator to couple portlets in a portal through user interface events taking place on the portal display itself. When the portal is displayed, if the user actuates a control corresponding to a property in a portlet, a menu of actions that can be performed with that data by other portlets is provided to the user. In addition to this “conventional” manner, an alternative manner of actuating the component is provided to the user such that if the user actuates the control in this alternative manner, the user is provided the option of making the chosen action “persistent,” so that the next time the control is actuated by the user, or the associated property is otherwise produced, the chosen action is performed automatically, without requiring the user to choose an action.

Abstract: A user interface template that implements a task pattern for a model class and a model adapter that provides an interface for the application that conforms to the model class are identified. A user interface for the application is created from the identified user interface template and the identified model adapter. The user interface template may include a generic view and a generic controller. The model adapter may provide a business object interface, and may be configured to communicate with the application via a J2EE Connector Architecture (JCA) connector. The user interface template may define an abstract portlet, and creating a user interface includes creating a portlet instance that communicates with the application via the model adapter. The portlet instance may be configured using an application portlet builder portlet. The portlet builder may also identify the user interface template and the model adapter.

Abstract: Code restructuring or reordering based on profiling information and memory hierarchy is provided by constructing a Program Execution Graph (PEG) corresponding to a level of the memory hierarchy, partitioning this PEG to reduce estimated memory overhead costs below an upper bound, and constructing a PEG for a next level of the memory hierarchy from the partitioned PEG. The PEG is constructed from control flow and frequency information from a profile of the program to be restructured. The PEG is a weighted undirected graph comprising nodes representing basic blocks and edges representing transfer of control between pairs of basic blocks. The weight of a node is the size of the basic block it represents and the weight of an edge is the frequency of transition between the pair of basic blocs it connects.

Abstract: A system and method is provided for integrating portlets. When viewing portlets within a portal container, a user is presented with a choice of one or more sources of data and, for each source, one or more actions that the user can take regarding the source. When an action is selected, it causes the source data to be transferred to one or more “target” portlets that have also been activated by the user. The set of actions available from a given source is automatically provided given the available target portlets. As each portlet is initialized, it informs a “broker” of the actions that the portlet supports along with the type of data that is used by the action. When a portal page is being constructed, each portlet identifies to the broker the sources of data within the portlet along with the values and data types corresponding to the sources.

Abstract: Methods, systems, and computer program products for programmatically determining whether components of a program are suitable for deployment in particular locations such as at the edge of a network. In preferred embodiments, program characteristics and operating environment characteristics, along with information about their interactions, are programmatically combined at deployment time to determine whether application components are edgeable. The disclosed approach enables people such as programmers (who are familiar with the program characteristics) and systems administrators (who are familiar with the operating environment characteristics) to each provide some control over the edgeability determination, along with other systems experts (who know how these features interact). Alternatively, this information or portions thereof may be supplied programmatically.

Abstract: A publish/subscribe data processing broker apparatus has: a means for receiving from a publisher application data messages published on a subject-specific stream by the publisher application; and a means for distributing the received published data messages to a subscriber application which has requested to receive messages on the stream upon which the published messages were published, the means for distributing including a plurality of connected distribution agent data processing units; wherein one of the streams is reserved for messages published by a publishing distribution agent data processing unit and intended for receipt by a subscribing distribution agent data processing unit located adjacent the publishing distribution agent data processing unit or intended for receipt by a subscriber application located adjacent the publishing distribution agent data processing unit.

Abstract: Code restructuring or reordering based on profiling information and memory hierarchy is provided by constructing a Program Execution Graph (PEG) corresponding to a level of the memory hierarchy, partitioning this PEG to reduce estimated memory overhead costs below an upper bound, and constructing a PEG for a next level of the memory hierarchy from the partitioned PEG. The PEG is constructed from control flow and frequency information from a profile of the program to be restructured. The PEG is a weighted undirected graph comprising nodes representing basic blocks and edges representing transfer of control between pairs of basic blocks. The weight of a node is the size of the basic block it represents and the weight of an edge is the frequency of transition between the pair of basic blocks it connects. The nodes of the PEG are partitioned or clustered into clusters such that the sum of the weights of the nodes in any cluster is no greater than an upper bound.