International Business Machines Corporation

National Institutes of Health, a Component of the US Dept. of Health & Human Services

Martin J Gale

Brian M O'Connell

Rick A Hamilton, Ii

Kulvir Singh Bhogal

Andrew R Jones

Bharat Veer Bedi

Andrew James Stanford-Clark

Lucas William Partridge

Erik H Katzen

Benjamin J Fletcher

David Locke

Ian Hughes

Matthew Geoffrey Roberts

Marc Stanley Carter

Rohit Bhasin

Keith R Walker

Jeffrey David Amsterdam

Graham White

Roland Albert Merrick

Peter J Johnson

Robert S Smart

Richard Mark Appleby

Neil George Young

Jason C Edmeades

Clare J Owens

Andy J Stanford-Clark

Andrew J F Bravery

Jane P Porter

Andrew J E Stanford-Clark

Andrew James Bravery

John Frederick Clarke

Philip J Thomas

Alexander Craig Filshie Russell

An approach to preemptive mobile data caching is provided, the approach involves retrieving user data associated with a user of a mobile computing device, retrieving external data associated with network service availability, predicting a location the user is travelling to based on the user data retrieved, determining a data security risk profile associated with the location predicted, based on the user data and the external data retrieved, determining data to be prefetched in advance of a user request for the data, wherein the data is determined based on an analysis of the user data retrieved, the location predicted and the data security risk profile and prefetching the data determined in advance of the user request for the data.

Security enabled predictive mobile data caching

An approach to preemptive mobile data caching is provided, the approach involves retrieving personal user data associated with a user of a mobile computing device, retrieving external data associated with network service availability, predicting a location the user is travelling to based on the personal user data retrieved, determining a data security risk profile associated with the location predicted, based on the personal user data and the external data retrieved, determining data to be prefetched in advance of a user request for the data, wherein the data is determined based on an analysis of the personal user data retrieved, the location predicted and the data security risk profile and prefetching the data determined in advance of the user request for the data.

Embodiments of the present invention provide an approach for a publisher-assisted, broker-based cache that can be utilized to reduce a volume of data (e.g., network traffic) delivered between a publisher and broker in a publication/subscription (pub/sub) environment. Specifically, in a typical embodiment, when a message is being generated on a publisher system, the publisher system will determine if the message includes a set of data that has a potential to be repeated in subsequent messages. Once such a set of data has been identified, the set of data will be associated/marked/tagged (e.g., in the message) with a unique identifier/cache key corresponding thereto (i.e., to yield a modified message). The modified message will be sent to a broker system, which will detect/locate the unique identifier, cache the corresponding data, and send the message along to any applicable subscriber systems. When a subsequent message that is supposed to contain the cached set of data is generated, the publisher system will instead substitute the unique identifier for the set of data to yield an abbreviated message and send the abbreviated message to the broker system. Upon receipt, the broker system will detect/locate the unique identifier, retrieve the corresponding set of data from the cache, replace the unique identifier with the set of data to yield a completed message, and then send the completed message to the applicable subscriber systems.

Publisher-assisted, broker-based caching in a publish-subscription environment

Embodiments of the present invention provide an approach for broker facilitated, publisher peer-to-peer (P2P) collaboration in a publish-subscription (pub/sub) environment. Specifically, in a typical embodiment, a broker system acts as an intermediary between publisher systems and subscriber systems in the pub/sub environment. Along these lines, the broker creates an administrative communication channel between known publisher systems and the broker system. Using this administrative communication channel, the broker system informs individual publisher systems about other publisher systems such that peer-to-peer communication channels between two or more publisher systems can be established. This can be accomplished using the broker system's knowledge of data being published by the individual publisher systems. Regardless, the publisher systems can then use information received from the broker system to: establish a P2P communication channel with one or more other publishers; identify a set of data that has commonality to the peers (and thus has a potential to be cached); and negotiate a caching schema/approach to store the data in a cache. The broker system may generate a set of cache key/unique identifiers and communicate the unique identifiers to at least one of the publisher peers, which will then share the unique identifiers among the peers. The set of data will then be cached (e.g., by a publisher system, a broker system and/or a subscriber system) using the unique identifiers.

Broker facilitated peer-to-peer publisher collaboration in a publish-subscription environment

Embodiments of the present invention provide an approach for a broker-assisted, publisher side cache that can be utilized to reduce a volume of data (e.g., network traffic) delivered between a publisher and broker in a publication/subscription (pub/sub) environment. Specifically, in a typical embodiment, when a message is received on a broker system from a publisher system, the broker system analyzes the message for potentially repetitive data. Such data can be determined from historical messages (e.g., determining that a certain set of data appeared in multiple messages and is thus flagged in a database or the like), a set of rules (e.g., if data set 'Y' appears, flag it as potentially repetitive), etc. Regardless, once such a set of data has been identified, a unique identifier/key corresponding thereto will be sent back to the publisher system and the set of data will be stored in a (data) cache. Upon receipt, the publisher system will cache/store the unique identifier in a (key) cache. Then, when the publisher system generates a future message that would contain the same set of data, the publisher system will substitute the unique identifier (as retrieved from the key cache) for the set of data to yield an abbreviated/truncated message. The abbreviated message would be sent to the broker system, which would: analyze the message; locate the unique identifier; retrieve the corresponding set of data from the (data) cache; replace the unique identifier with the set of data to yield a completed message; and then send the completed message to relevant subscriber system(s).

Publisher-based message data caching in a publish-subscription environment

Embodiments of the present invention provide an approach for an enhanced pub/sub environment whereby a peer group of publishers is defined and can collaborate to determine when to cache data being sent to a common broker or brokers. Specifically, in a typical embodiment, configuration data or the like will be read to define a peer group among the publisher systems in the pub/sub messaging environment. Once such a group has been identified, communication therebetween will be established. Once cacheable data has been identified, a unique identifier/set of cache keys will be generated corresponding thereto and associated with the set of data. A message comprising the set of data and corresponding unique identifier will then be sent to a broker system (e.g., from the publisher system(s)), which will store (or have stored) the set of data in a cache, and pass the underlying message along to applicable subscriber system(s).

Peer-to-peer collaboration of publishers in a publish-subscription environment

In general, embodiments of the present invention provide an approach for caching potentially repetitive data in a publication-subscription (pub/sub) environment. Specifically, in a typical embodiment, when a message is received on a broker system from a publisher system, the broker system analyzes the message for potentially repetitive data. Once such a set of data has been identified, the set of data will be cached, and a unique identifier/tag corresponding thereto will be sent to the publisher system and to applicable subscribers. Thereafter, any subsequent message including the same data will contain the unique identifier in place of the cached data (i.e., an abbreviated message). The abbreviated message can be sent from the publisher system to the broker system, and then onto the subscriber system, which will retrieve the data from the shared cache and replace the unique identifier with the cached data to yield a complete message.

Shared cache for potentially repetitive message data in a publish-subscription environment

An approach for caching potentially repetitive message data in a publication/subscription messaging environment is provided. Specifically, when a message is received on a broker system from a publisher system, the broker system analyzes the message for potentially repetitive data. Once such a set of data has been identified, a unique identifier/key corresponding thereto will be sent back to the publisher system and the set of data will be stored in a (data) cache. Upon receipt, the publisher system will cache/store the unique identifier in a (key) cache. Then, when the publisher system generates a future message that would contain the same set of data, the publisher system will substitute the unique identifier (as retrieved from the key cache) for the set of data to yield an abbreviated/truncated message.

Publisher-based message data cashing in a publish-subscription environment

An approach for a publisher-assisted, broker-based cache that can be utilized to reduce a volume of data delivered between a publisher and broker is provided. Specifically, when a message is being generated on a publisher system, the publisher system will determine if the message includes a set of data that has a potential to be repeated in subsequent messages. An identified set of data will be associated/marked/tagged with a unique identifier corresponding thereto. The modified message will be sent to a broker system, which will detect/locate the unique identifier, cache the corresponding data, and send the message along to any applicable subscriber systems. When a subsequent message that is supposed to contain the cached set of data is generated, the publisher system will substitute the unique identifier for the set of data to yield an abbreviated message and send the abbreviated message to the broker system.

Portlet processing for portal applications aggregating content from sources is provided. This processing may include client intervention and publish/subscribe system use. Topic information used for rendering may be obtained by using a subscription/publisher methodology targeting clients for receipt of the topic information. The topic information from a publish/subscribe system may be inserted into placeholders on a portal page, the placeholders previously created at the client for receipt of the topic information by the client.

System for processing requests to portlets

A solution for managing messaging is provided in which an event related to a publisher is identified. In response to the event, a transaction is initiated for processing the event, the event is processed within the transaction, and the transaction is committed after the event is processed. During processing, data corresponding to the event is provided for use by a set of subscribers to the event, and data related to the set of subscribers is identified. In an embodiment, a message broker in a publication and subscribe messaging environment implements the solution in order to be capable of providing the data related to the set of subscribers to the publisher. Use of the transaction ensures that the data related to the set of subscribers accurately represents the set of subscribers at the time that the data corresponding to the event was provided.

Identifying subscriber data while processing publisher event in transaction

A system for use in an environment having a remote computer system, a user associated with the remote computer system, and an error detection component for detecting errors associated with the remote computer system comprises a storage component for computer programs that performing diagnostics errors associated with the remote computer system, and a search component, responsive to a first error being detected, for searching the storage component for a first computer program associated with the first error. If a first computer program is found, a presentation component presents a first option to the user, wherein the first option is associated with selection of the first computer program. If the user selects the first computer program, an execution component executes the first computer program on the remote computer system.

Diagnostics for remote computer systems

One or more policies to be applied to a set of one or more messages in a message oriented middleware are defined. Metrics of the message oriented middleware are monitored. Application of a policy in response to a trigger condition being satisfied is initiated. Application of the policy applies actions across the set of one or more messages.

Growing community of inventors

Eastleigh, United Kingdom

Martin J Gale