Integrated application that contains software modules coupled to a message bus

Patent metadata

Field	Value
Publication number	US-9600131-B2
Application number	US-201113149042-A
Country	US
Kind code	B2
Filing date	May 31, 2011
Priority date	May 31, 2011
Publication date	Mar 21, 2017
Grant date	Mar 21, 2017

Abstract

A method and system for providing an integrated application that includes software modules coupled to a message bus. The software modules include applications of different degrees of complexity and different number of components, such as management applications, service applications, and other similar applications. A computer system receives a first input that selects a user interface (UI) to access the integrated application. The selected UI can be a specific UI associated with a software module, or an orchestrator UI that unifies individual styles of the specific UIs. The computer system receives, via the selected UI, a second input to access a destination module among the software modules. If the selected UI is the orchestrator UI, the second input is forwarded to the destination module via the message bus. If the selected UI is a specific UI, the second input is sent to the destination module via the selected specific UI.

First claim

What is claimed is:

1. A method comprising:
receiving, by a processing device, a first input to select a user interface (UI) from one of a specific UI or an orchestrated UI to access an integrated application, the integrated application comprising one or more software components accessible via a message bus, the selected UI being one of specific UIs each having a respective different style associated with a respective one of the one or more software components or the orchestrator UI having a common style associated with each of the one or more software components, wherein at least one of the one or more software components is accessible via the one of the specific UIs and via the orchestrated UI;
receiving a second input via the selected UI to access a destination component among the software components;
determining whether or not to place the second input on the message bus in view of whether the selected UI is the orchestrator UI or the one of the specific UIs;
in response to the determining that the selected UI is the orchestrator UI, placing the second input on the message bus to allow retrieval of the second input by the destination component;
in response to the determining that the selected UI is the one of the specific UIs, sending, from the one of the specific UIs without using the message bus, the second input to the destination component; and
performing, by the processing device, operations of the destination component.

2. The method of claim 1 , further comprising:
receiving, by the processing device, a call through an application programming interface (API) gateway which unifies different APIs provided by the one or more software components; and
forwarding, by the processing device, the call to the destination component through the message bus.

3. The method of claim 1 , wherein performing operations of the destination component further comprises:
accessing a database using a schema specific to the destination component, the database storing data that is organized in multiple different schemas associated with the one or more software components.

4. The method of claim 1 , wherein the orchestrator UI uses a common format defined in a cascaded style sheet (CSS) to unify the individual styles of the specific UIs.

5. The method of claim 1 , wherein the one or more software components are written in different programming languages.

6. The method of claim 1 , wherein each of the one or more software components is a standalone software product that functions independently of other software components.

7. The method of claim 1 , wherein receiving the first input further comprises:
receiving sign-in credentials of a user; and
in response to determining that the sign-in credentials are authenticated, granting the user access to all of the one or more software components.

8. A system comprising:
a memory; and
a processing device, communicatively coupled to the memory, to:
receive a first input to select a user interface (UI) from one of a specific UI or an orchestrated UI access an integrated application, the integrated application comprising one or more software components accessible via a message bus, the selected UI being one of specific UIs each having a respective different style associated with a respective one of the one or more software components or the orchestrator UI having a common style associated with each of the one or more software components, wherein at least one of the one or more software components is accessible via the one of the specific UIs and via the orchestrated UI;
receive a second input via the selected UI to access a destination component among the software components;
determine whether or not to place the second input on the message bus in view of whether the selected UI is the orchestrator UI or the one of the specific UIs;
in response to determining that the selected UI is the orchestrator UI, place the second input on the message bus to allow retrieval of the second input by the destination component;
in response to determining that the selected UI is the one of the specific UIs, send, from the one of the specific UIs without using the message bus, the second input to the destination component; and
perform operations of the destination component.

9. The system of claim 8 , further comprising:
data storage to store data that is organized in multiple different schemas associated with the one or more software components.

10. The system of claim 8 , wherein the integrated application provides an application programming interface (API) gateway that unifies different APIs provided by the one or more software components.

11. The system of claim 8 , wherein the orchestrator UI uses a common format defined in a cascaded style sheet (CSS) to unify the individual styles of the specific UIs.

12. The system of claim 8 , wherein the one or more software components are written in different programming languages.

13. The system of claim 8 , wherein each of the one or more software components is a standalone software product that functions independently of other software components.

14. A non-transitory computer readable storage medium stored thereon instructions that, when executed by a processing device, cause the processing device to:
receive, by the processing device, a first input to select a user interface (UI) from one of a specific UI or an orchestrated UI access an integrated application that comprises one or more software components accessible via a message bus, the selected UI being one of specific UIs each having a respective different style associated with a respective one of the one or more software components or the orchestrator UI having a common style associated with each of the one or more software components, wherein at least one of the one or more software components is accessible via the one of the specific UIs and via the orchestrated UI;
receive a second input via the selected UI to access a destination component among the software components;
determine whether or not to place the second input on the message bus in view of whether the selected UI is the orchestrator UI or the one of the specific UIs;
in response to the determining that the selected UI is the orchestrator UI, place the second input on the message bus to allow retrieval of the second input by the destination component;
in response to the determining that the selected UI is the one of the specific UIs, send, from the one of the specific UIs without using the message bus, the second input to the destination component; and
perform operations of the destination component.

15. The non-transitory computer readable storage medium of claim 14 , the processing device further to:
receive a call through an application programming interface (API) gateway which unifies different APIs provided by the one or more software components; and
forward the call to the destination component through the message bus.

16. The non-transitory computer readable storage medium of claim 14 , wherein the processing device is further to:
access a database using a schema specific to the destination component, the database storing data that is organized in multiple different schemas associated with the one or more software components.

17. The non-transitory computer readable storage medium of claim 14 , wherein the orchestrator UI uses a common format defined in a cascaded style sheet (CSS) to unify the individual styles of the specific UIs.

18. The non-transitory computer readable storage medium of claim 14 , wherein the software components are writ

Assignees

• Rodriguez Jesus M
• Mccune Michael B
• Red Hat Inc

Inventors

• Rodriguez Jesus M
• Mccune Michael B

Classifications

• G06F8/38

  for implementing user interfaces · CPC title

• G06F3/048 Primary

  Interaction techniques based on graphical user interfaces [GUI] · CPC title

• G06F9/4443

  Physics · mapped topic

• G06F9/451 Primary

  Execution arrangements for user interfaces · CPC title