On demand message based financial network integration middleware

• US 7,734,785 B2
• Filed: 07/14/2005
• Issued: 06/08/2010
• Est. Priority Date: 12/09/2004
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: zu Bexten, Elmar Meyer, Breiter, Gerd, Illgner-Kurz, Monika
• Primary Examiner(s): Dinh; Khanh Q
• Application Number:
  US11/721,202
• Publication Number:
  US 20090240797A1
• Time in Patent Office: 1,790 Days
• Field of Search: 709/220, 709/226, 709/228, 709/235, 370/216, 370/231
• US Class Current: 709/226
• CPC Class Codes: G06F 9/546 Message passing systems or structures, e.g. queues
• CPC Class Codes: G06Q 40/02 Banking, e.g. interest calculation or account maintenance credit or loans G06Q40/03

Abstract

The present invention relates to distributed networking, and in particularly to a message-based networking environment. More particularly, it relates to business applications, which access the network via some middleware within a predetermined load schedule. In order to alleviate the disadvantages of prior art it is proposed to perform, a method with the following sequence of steps: monitoring, metering the current workload, storing metered workload data in a first appropriate data store, store state information data about the plurality of currently used instances in a second appropriate data store, analyzing both, said stored, metered workload data and said state information for compliance with a predetermined quality-of-service policy, adapting the number of instances usable for satisfying the workload to the workload needs as required by said predetermined quality-of-service policy, wherein meta data of newly created instances are managed in a plurality of message stores, the data contents of which are frequently synchronized in order to decouple the plurality of client applications from bindings fixed during their operation to particular service instances.

Claims

1. A method for managing message-based workload in a networking environment, wherein multiple client applications use network resources via service instances of respective networked services, characterized by the steps of:

a) monitoring and metering the current workload of a client from a server,

b) storing metered workload data in a first appropriate data store,

c) storing state information about the plurality of currently used service instances in a second appropriate data store,

d) analyzing both said stored, metered workload data and said state information for compliance with a predetermined quality-of-service policy,

e) adapting the number of service instances usable for satisfying the workload needs as required by said predetermined quality-of-service policy,

f) managing metadata of said service instances in a message store, data contents of which are synchronized in order to decouple the plurality of client applications from bindings to particular service instances fixed during their operation,

g) wherein persistent processing databases containing relational and XML information are used for managing state information across the lifetime of transactions and correlation data between individual messages.

2. The method according to claim 1, wherein a plurality of message stores is used for managing said metadata.

3. The method according to claim 2, in which a single message store is hosted by a single message server.

4. The method according to claim 1, wherein the workload comprises message processing of financial services.

5. The method according to claim 1, wherein the step of adapting the number of usable service instances comprises a balancing across a predetermined pool of cloned instances.

6. The method according to claim 1, wherein the step of adapting the number of usable service instances comprises message queue manager clustering.

7. The method according to claim 1, wherein a workload prioritization is implemented based on message class differentiating.

8. The method according to claim 7, wherein within a message class a further prioritization is implemented based on message contents.

9. The method according to claim 1, wherein finite state machines (FSM) are used for managing state information across the lifetime of transactions and correlation data between individual messages.

10. A computer system for managing message-based workload in a networking environment, wherein multiple client applications use network resources via service instances of respective networked services characterized by:

a) means for monitoring and metering the current workload,

b) a first appropriate data store for storing metered workload data,

c) a second appropriate data store for storing state information about the plurality of currently used service instances,

d) means for analyzing both said stored, metered workload data and said state information for compliance with a predetermined quality-of-service policy,

e) means for adapting the number of service instances usable for satisfying workload needs as required by said predetermined quality-of-service policy,

f) a message store for managing metadata of said service instances, data contents of which are synchronized in order to decouple the plurality of client applications from bindings to particular service instances fixed during their operation,

g) means for processing databases containing relational and XML information are used for managing state information across the lifetime of transactions and correlation data between individual messages.

11. A computer program product comprising a computer storage medium embodying program instructions for managing message-based workload in a networking environment, wherein multiple client applications use network resources via respective networked services, said program instructions when loaded into and execute by a computer causing the computer to perform a method comprising the steps of:

a) monitoring and metering the current workload of a client from a server,

b) storing metered workload data in a first appropriate data store,

c) storing state information about the plurality of currently used service instances in a second appropriate data store,

d) analyzing both said stored, metered workload data and said state information for compliance with a predetermined quality-of-service policy, and

e) adapting the number of service instances usable for satisfying the workload to the workload needs as required by said predetermined quality-of-service policy, wherein metadata of said service instances are managed in a message store, data contents of which are synchronized in order to decouple the plurality of client applications from bindings to particular service instances fixed during their operation,

f) wherein persistent processing databases containing relational and XML information are used for managing state information across the lifetime of transactions and correlation data between individual messages.

12. The computer program product according to claim 11 wherein said program instructions further comprises instructions for using a plurality of message stores for managing said metadata.

13. The computer program product according to claim 12 in which a single message store is hosted by a single message server.

14. The computer program product according to claim 11 wherein the workload comprises message processing of financial networks.

15. The computer program product according to claim 11 wherein the program instructions for performing the step of adapting the number of usable instances comprises instructions for balancing across a predetermined pool of cloned instances.

16. The computer program product according to claim 11 wherein the program instructions for adapting the number of usable instances comprises instructions for performing message queue manager clustering.

17. The computer program product according to claim 11 wherein workload prioritization is implemented based on message class differentiating.