Central strategy management component for providing semantic-free administration functions for a system of applications

• US 8,510,711 B2
• Filed: 05/29/2007
• Issued: 08/13/2013
• Est. Priority Date: 05/30/2006
• Status: Active Grant

• Current Assignee: Siemens Healthcare GMBH (Siemens AG)
• Original Assignee: Siemens AG
• Inventors: Dorn, Karlheinz, Schlke, Andreas
• Primary Examiner(s): DENG, ANNA CHEN
• Application Number:
  US11/802,984
• Publication Number:
  US 20070283320A1
• Time in Patent Office: 2,268 Days
• Field of Search: 717/120, 717/121
• US Class Current: 717/120
• CPC Class Codes: G06F 9/5083 Techniques for rebalancing the load in a distributed system

Abstract

A strategy mechanism is disclosed, including at least one business program component and a strategy management component which, as a single executable program object, makes a plurality of at least two administration functions available to the at least one business program component. In at least one embodiment, the program code for implementing the administration functions is realized in the strategy management component in such a way that the at least one business program component itself need not contain any program code for realizing the administration functions. Further, the program code in the strategy management component is generically realized such that all business program components running in the software system can use the administration functions.

Claims

1. A semantic-free and central strategy mechanism for managing concurrently running medical imaging applications of a system including software code stored on a non-transitory computer readable medium and being executed by a processor, the central strategy mechanism comprising:

at least one business program component stored on the non-transitory computer readable medium and being concurrently executed by the processor; and

a strategy management component which, as a single executable program object stored on the non-transitory computer readable medium and being executed by the processor, makes at least two administration functions available to the at least one business program component, program code necessary for implementing the at least two administration functions being realized in the strategy management component in such a way that the at least one business program component need not contain any program code for realizing the at least two administration functions, and the program code in the strategy management component being generically realized such that all business program components concurrently running in the system can use the at least two administration functions, the strategy management component and the at least one business program component each being executed in a different and separate executable, one of the at least two administration functions include application load distribution management, the at least two administration functions are configured to be transferred to the strategy management component.

2. The strategy mechanism as claimed in claim 1, wherein the business program components do not contain any program code which is required for supervision in relation to central service mechanisms.

3. The strategy mechanism as claimed in claim 1, wherein another one of the at least two administration functions are selected from job management, resource management, component management, business task management and taskflow management.

4. The strategy mechanism as claimed in claim 1, wherein another one of the at least two administration function is a job management, wherein a central queue is used for all business program components and the job management is performed by the strategy management component in order to connect at least one back-end processing job to the business program components.

5. The strategy mechanism as claimed in claim 1, wherein another one of the at least two administration function is resource management, intended for centralized resource administration for the business program components.

6. The strategy mechanism as claimed in claim 5, wherein the resource management is intended for limiting the number of concurrently running instances of a business program component to a predetermined value.

7. The strategy mechanism as claimed in claim 1, wherein another one of the at least two administration function is a taskflow management, intended for starting up and shutting down, suspending and resuming taskflows or a number of business program components, and for their runtime monitoring.

8. The strategy mechanism as claimed in claim 1, wherein another one of the at least two administration function is a component management, intended for starting up and shutting down business program components, and for their runtime monitoring.

9. The strategy mechanism as claimed in claim 1, wherein the strategy management component includes a flexible communication layer for the communication between the strategy management component and the business program components.

10. The strategy mechanism as claimed in claim 1, wherein the strategy management component is implemented such that at least one of an error frequency and a lack of errors in the strategy management component is a mathematically demonstrable variable.

11. The strategy mechanism as claimed in claim 2, wherein another one of the at least two administration functions are selected from job management, resource management, business task management and taskflow management.

12. A method for centrally controlling semantic-free administration functions of concurrently running medical imaging applications, the method comprising:

executing the administration functions of the medical imaging applications within a process, at least one interwork being connectable between a plurality of computers using a strategy management component such that concurrently executing administration functions of the medical imaging application operate independently of the at least one interwork and are connectable between a plurality of computers, the strategy management component and the administration functions of the medical imaging applications being executed in a different and separate executable, the administration functions of the medical imaging applications include application load distribution management, the administration functions of the medical imaging applications are configured to be transferred to the strategy management component.

13. The method as claimed in claim 12, wherein the administration functions of medical imaging applications include application resource management, wherein a plurality of different instances of a specific application are to run concurrently.

14. The method as claimed in claim 12, wherein the administration functions of the medical imaging applications include application startup/shutdown/suspend/resume/stop management.

15. The method as claimed in claim 12, wherein the administration functions of the medical imaging application include lock management.

16. The method as claimed in claim 12, wherein the administration functions of the medical imaging applications include application flow management.

17. The method as claimed in claim 12, wherein the administration functions of the medical imaging applications include application job queue management.

18. A non-transitory computer readable medium including program segments for, when executed on a computer device, causing the computer device to implement the method of claim 12.