SYSTEM, MESSAGING BROKER AND METHOD FOR MANAGING COMMUNICATION BETWEEN OPEN SERVICES GATEWAY INITIATIVE (OSGI) ENVIRONMENTS

• US 20140181233A1
• Filed: 03/01/2013
• Published: 06/26/2014
• Est. Priority Date: 12/21/2012
• Status: Active Grant

• Current Assignee: Software AG
• Original Assignee: Software AG
• Inventors: PEEV, Peter
• Granted Patent: US 9,398,109 B2
• Time in Patent Office: Days
• US Class Current: 709/213
• CPC Class Codes: G06F 9/54 Interprogram communication
• CPC Class Codes: G06F 9/546 Message passing systems or structures, e.g. queues
• CPC Class Codes: H04L 63/1416 Event detection, e.g. attack signature detection
• CPC Class Codes: H04L 67/125 involving control of end-device applications over a network
• CPC Class Codes: H04L 67/562 Brokering proxy services
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching

Abstract

Certain example embodiments relate to techniques for managing communication between a plurality of Open Services Gateway initiative (OSGi) environments. A system includes a messaging broker configured to receive a message from one of the OSGi environments, with the message including a call of a service provided by one of the other OSGi environments. The broker may be further configured to transfer the message to the other OSGi environment. The plural OSGi environments communicate only via the messaging broker.

Claims

1. A system for managing communication between a plurality of Open Services Gateway initiative (OSGi) environments, wherein the system (1) comprises:

a messaging broker configured to receive a message from one of the OSGi environments, wherein the message comprises a call of a service provided by one of the other OSGi environments, the message broker being further configured to transfer the message to the other OSGi environment;

wherein the plurality of OSGi environments communicate only via the messaging broker.

2. The system of claim 1, wherein the messaging broker is configured to receive a register request from an OSGi environment to register with the message broker.

3. The system of claim 2, wherein in response to the register request, the messaging broker is configured to provide a unique identifier to the requesting OSGi environment.

4. The system of claim 2, wherein in response to the registering of an OSGi environment, the messaging broker configured to notify all other OSGi environments.

5. The system of claim 1, wherein the OSGi environments are configured to transmit, via the messaging broker, a message comprising a list of provided services to at least one other OSGi environment.

6. The system of claim 1, further comprising an inbox cache for each OSGi environment, wherein the inbox cache configured to store messages comprising a call of a service provided by the respective OSGi environment.

7. The system of claim 1, wherein in response to a notification that a new OSGi environment is registered with the messaging broker, each OSGi environment is configured to create an outbox cache for the new OSGi environment, wherein the outbox cache is configured to store messages comprising a call of a service provided by the new OSGi environment.

8. The system of claim 6, wherein:

in response to a notification that a new OSGi environment is registered with the messaging broker, each OSGi environment is configured to create an outbox cache for the new OSGi environment, wherein the outbox cache is configured to store messages comprising a call of a service provided by the new OSGi environment; and

the inbox cache and the outbox cache(s) are stored locally on a computing system of the respective OSGi environment.

9. The system of claim 6, wherein:

in response to a notification that a new OSGi environment is registered with the messaging broker, each OSGi environment is configured to create an outbox cache for the new OSGi environment, wherein the outbox cache is configured to store messages comprising a call of a service provided by the new OSGi environment; and

the inbox cache and the outbox cache associated with a particular OSGi environment are stored in a single cache.

10. The system of claim 1,

wherein one of the OSGi environments is configured to place a message comprising a call of a service provided by another OSGi environment into an outbox cache associated with the other OSGi environment;

wherein the messaging broker is configured to transfer the message from the outbox cache associated with the other OSGi environment to an inbox cache of the other OSGi environment; and

wherein the messaging broker is configured to notify the other OSGi environment of the new message in the inbox cache.

11. The system of claim 1, wherein the messaging broker is configured to send received messages to a monitoring component, which enables a central recording, analysis, and/or replaying of the communication between the plurality of OSGi environments.

12. The system of claim 1, wherein functionality of the messaging broker is implemented by a Terracotta cache server and/or a server using Java Message Service (JMS).

13. The system of claim 1, wherein the plurality of OSGi environments communicate using Remote Services for OSGi (R-OSGi).

14. A method for managing communication between a plurality of Open Services Gateway initiative (OSGi) environments in a system according to claim 1.

15. A non-transitory computer readable storage medium tangibly storing a computer program comprising instructions for implementing a method in accordance with claim 14.

16. The system of claim 3, wherein in response to the registering of an OSGi environment, the messaging broker configured to notify all other OSGi environments.

17. The system of claim 9, wherein the single cache is stored on the messaging broker.