Liquid computing
First Claim
Patent Images
1. A system for communicating with a plurality of heterogeneous systems comprising:
- a processor;
a service bus, executing on the processor, interacting with a plurality of heterogeneous systems, wherein the service bus receives messages from one or more clients, and uses a plurality of adapters to interact with the heterogeneous systems, and wherein the service bus converts the messages into different protocols as used by the heterogeneous systems;
configuration information describing a core state for the service bus;
a service broker, on the service bus, which queues and forwards the messages from the clients to the heterogeneous systems, based on metadata in the messages, and wherein the heterogeneous systems can be included or excluded by changing information in the service broker;
a plurality of services hosted by the service bus, including one or more services which interact with a plurality of the heterogeneous systems, wherein each of the plurality of services defines a plurality of message processing stages includinga transformation stage which includes nested flow control structures to select a transformation to be performed that changes a context,a routing stage which combines flow control structures to define a single endpoint to route each of the messages to, anda publish stage which determines a set of endpoints and operations to publish the messages to, wherein changes to the context are isolated to each published endpoint; and
a service proxy hosted by the service bus that invokes an external service not hosted by the bus;
wherein the core state defines behavior of the service bus and maintains changes after the transformation finishes.
2 Assignments
0 Petitions
Accused Products
Abstract
Liquid computing can include using a service bus to interact with a number of heterogeneous systems.
105 Citations
23 Claims
-
1. A system for communicating with a plurality of heterogeneous systems comprising:
-
a processor; a service bus, executing on the processor, interacting with a plurality of heterogeneous systems, wherein the service bus receives messages from one or more clients, and uses a plurality of adapters to interact with the heterogeneous systems, and wherein the service bus converts the messages into different protocols as used by the heterogeneous systems; configuration information describing a core state for the service bus; a service broker, on the service bus, which queues and forwards the messages from the clients to the heterogeneous systems, based on metadata in the messages, and wherein the heterogeneous systems can be included or excluded by changing information in the service broker; a plurality of services hosted by the service bus, including one or more services which interact with a plurality of the heterogeneous systems, wherein each of the plurality of services defines a plurality of message processing stages including a transformation stage which includes nested flow control structures to select a transformation to be performed that changes a context, a routing stage which combines flow control structures to define a single endpoint to route each of the messages to, and a publish stage which determines a set of endpoints and operations to publish the messages to, wherein changes to the context are isolated to each published endpoint; and a service proxy hosted by the service bus that invokes an external service not hosted by the bus; wherein the core state defines behavior of the service bus and maintains changes after the transformation finishes. - View Dependent Claims (2, 3, 4, 5, 6, 7)
-
-
8. A system for communicating with a plurality of heterogeneous systems comprising:
-
a processor; a structure, executing on the processor, including service brokering for a plurality of heterogeneous systems and business level services for the heterogeneous systems, wherein the structure allows clients to interact with the heterogeneous systems, wherein the structure receives messages from one or more clients and converts the messages into different protocols as used by the heterogeneous systems; configuration information describing a core state for a service bus; a service broker, on a service bus, which queues and forwards the messages from the clients to the heterogeneous systems, based on metadata in the messages, and wherein the heterogeneous systems can be included or excluded by changing information in the service broker; a plurality of services provided by the structure, including one or more services which interact with a plurality of the heterogeneous systems, wherein each of the plurality of services defines a plurality of message processing stages including a transformation stage which includes nested flow control structures to select a transformation to be performed that changes a context, a routing stage which combines flow control structures to define a single endpoint to route each of the messages to, and a publish stage which determines a set of endpoints and operations to publish the messages to, wherein changes to the context are isolated to each published endpoint; and a service proxy hosted by the service bus that invokes an external service not hosted by the bus; wherein the core state defines behavior of the service bus and maintains changes after the transformation finishes. - View Dependent Claims (9, 10, 11)
-
-
12. A method for communicating between a plurality of heterogeneous systems, comprising:
-
receiving messages from one or more clients at a service bus interacting with a plurality of heterogeneous systems, wherein the service bus uses a plurality of adapters to interact with the heterogeneous systems; converting, by the service bus, the messages into different protocols as used by the heterogeneous systems; configuring a core state for the service bus; queuing and forwarding the messages, by a service broker on the service bus, from the clients to the heterogeneous systems, based on metadata in the messages, and wherein the heterogeneous systems can be included or excluded by changing information in the service broker; providing a plurality of services hosted by the service bus, including one or more services which interact with a plurality of the heterogeneous systems, wherein each of the plurality of services defines a plurality of message processing stages including a transformation stage which includes nested flow control structures to select a transformation to be performed that changes a context, a routing stage which combines flow control structures to define a single endpoint to route each of the messages to, and a publish stage which determines a set of endpoints and operations to publish the messages to, wherein changes to the context are isolated to each published endpoint; and providing a service proxy hosted by the service bus that invokes an external service not hosted by the bus; wherein the core state defines behavior of the service bus and maintains changes after the transformation finishes. - View Dependent Claims (13, 14, 15, 16, 17)
-
-
18. A non-transitory computer readable storage medium including instructions stored thereon for communicating between a plurality of heterogeneous systems, which when executed by a computer, cause the computer to perform the steps comprising:
-
receive messages from one or more clients at a service bus interacting with a plurality of heterogeneous systems, wherein the service bus uses a plurality of adapters to interact with the heterogeneous systems; convert, by the service bus, the messages into different protocols as used by the heterogeneous systems; configure a core state for the service bus; queue and forward the messages, by a service broker on the service bus, from the clients to the heterogeneous systems, based on metadata in the messages, and wherein the heterogeneous systems can be included or excluded by changing information in the service broker; provide a plurality of services hosted by the service bus, including one or more services which interact with a plurality of the heterogeneous systems, wherein each of the plurality of services defines a plurality of message processing stages including a transformation stage which includes nested flow control structures to select a transformation to be performed that changes a context, a routing stage which combines flow control structures to define a single endpoint to route each of the messages to, and a publish stage which determines a set of endpoints and operations to publish the messages to, wherein changes to the context are isolated to each published endpoint; and provide a service proxy hosted by the service bus that invokes an external service not hosted by the bus; wherein the core state defines behavior of the service bus and maintains changes after the transformation finishes. - View Dependent Claims (19, 20, 21, 22, 23)
-
Specification