Execution control system

• US 5,608,894 A
• Filed: 10/19/1994
• Issued: 03/04/1997
• Est. Priority Date: 03/18/1994
• Status: Expired due to Fees

• Current Assignee: Fujitsu Limited
• Original Assignee: Fujitsu Limited
• Inventors: Takahashi, Masumi, Kawakami, Kumiko, Akagawa, Yasuko
• Primary Examiner(s): Teska, Kevin J.
• Assistant Examiner(s): Frejd, Russell W.
• Application Number:
  US08/325,056
• Time in Patent Office: 867 Days
• Field of Search: 395/500, 395/600, 395/700, 395/325, 395/153, 364/200, 364/DIG. 1 MS File, 364/DIG. 2 MS File
• US Class Current: 717/162
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management

Abstract

An execution control system includes: shared reference information including procedure information to be referred to by software components when an execution request information is issued by a software component; and control means which refers to the shared reference information on the basis of the execution request information issued by the software component, combines software components, and controls the execution of the software components.

Claims

1. An execution control system which controls execution of software components and message exchanging between software components for software components issuing execution request information, comprising:

shared reference information containing procedure information to be referred to by said software components when any of said software components issues execution request information; and

control means for referring to said shared reference information when execution request information is issued by any of said software components, for combining necessary ones of said software components in response to the issued execution request information, and for controlling execution of the combined necessary ones of said software components.

2. The execution control system as claimed in claim 1, wherein said control means receives execution request information, issued by one software component and specifying a destination software component, and said control means further comprises:

means, responsive to receipt of the execution request information issued by said one software component and specifying a destination software component, for;

referring to said shared reference information on the basis of said execution request information and obtaining a result from said shared reference information, and

delivering, on the basis of the result obtained from the shared reference information, said execution request information to the destination software component specified by said execution request information.

3. The execution control system as claimed in claim 1, wherein said shared reference information is specified at the time of customization.

4. The execution control system as claimed in claim 1, wherein execution request information issued by software components specifies destination software components, and destination information of destination software components is appended, at the time of customization, to execution request information exchanged between software components, and the resultant information is delivered to said control means.

5. The execution control system as claimed in claim 1, wherein said control means further comprises:

means for specifying said shared reference information at the time of customization such that a plurality of software components are combined into one process, or such that the same software component is assigned in common to a plurality of processes.

6. The execution control system as claimed in claim 2, wherein said control means comprises:

means for receiving execution request information issued by a software component originating a request and specifying a destination software component;

means for referring to said shared reference information on the basis of said execution request information; and

means for;

delivering said execution request information by a function, when the software component originating the request and the destination software component are in the same process;

delivering said execution request information via a message queue, when the software component originating the request and the destination software component are in different processes within the same apparatus, and

delivering said execution request information via a socket when the software component originating the request and the destination software component are accommodated in different apparatuses.

7. The execution control system as claimed in claim 2, wherein said control means further comprises:

means for delivering a process result yielded by a destination software component that is executed on the basis of execution request information issued by a software component, the delivery being performed on the basis of the execution request information such that;

when the execution request information indicates that the process result is not necessary, the software component issuing the execution request information is not notified of the process result,

when the software component issuing the execution request information and the destination software component are within the same process, delivery is performed via an argument when a function is returned,

when the software component issuing the execution request information and the destination software component are in different processes within the same apparatus, delivery is performed via a message queue, and

when the software component issuing the execution request information and the destination software component are accommodated in different apparatuses, delivery is performed via a socket.

8. The execution control system as claimed in claim 2, wherein said control means further comprises:

means for delivering a process result yielded by a destination software component that is executed on the basis of execution request information issued by a software component, the delivery being performed, such that;

when the software component issuing the execution request information requires non-synchronization, the software component issuing the execution request information proceeds without waiting for the process result from the destination software component, the process result being delivered separately,

when the software component issuing the execution request information and the destination software component are accommodated in the same apparatus, delivery is performed via a message queue, and

when the software component issuing the software request and the destination software component are accommodated in different apparatuses, delivery is performed via a socket.

9. The execution control system as claimed in claim 1, wherein software components exchange messages therebetween, a software component issuing a message being defined as a transmitting software component and a software component receiving the message being defined as a receiving software component, the execution control system controlling a plurality of applications, an application being defined as a stream of successive messages exchanged between software components, and said shared reference information includes information corresponding to the number of applications of the plurality of applications.

10. The execution control system as claimed in claim 9, wherein said control means further comprises:

means for referring to said shared reference information; and

means for controlling message exchanging between a transmitting software component and a corresponding, receiving software component by compensating for differences in interfaces of the transmitting software component and of the corresponding, receiving software component.

11. The execution control system as claimed in claim 10, wherein said control means further comprises:

means for converting the format of the message sent from the transmitting software component so as to adapt to the reception format of the corresponding, receiving software component.

12. The execution control system as claimed in claim 10, wherein said control means further comprises:

means for editing the message sent from the transmitting software component by referring to the shared reference information, and for sending the edited message to the corresponding, receiving software component.

13. The execution control system as claimed in claim 11, wherein the message sent from the transmitting software component is sent to said control means for routing to said corresponding, receiving software component.

14. The execution control system as claimed in claim 11, wherein the message sent from the transmitting software component comprises a destination, a message code, a message and an interface.

15. The execution control system as claimed in claim 11, wherein said control means further comprises:

means for receiving a plurality of messages from the transmitting software component and for sending the plurality of messages to the receiving software component.

16. The execution control system as claimed in claim 11, wherein said control means further comprises:

means for receiving a message from a transmitting software component to be received by a plurality of receiving software components, the message including an interface;

means for editing the interface of said message;

means for reproducing said message to obtain a copy of the message for each of the plurality of receiving software components; and

means for sending the copies to the receiving software components.

17. The execution control system as claimed in claim 11, wherein said control means further comprises:

means for regarding a stream of information from the transmitting software component as an application; and

means for monitoring messages from the moment when an application start message is received to the moment when an application end message is received so that information other than that defined in said shared reference information is not accepted as a valid message.

18. The execution control system as claimed in claim 11, wherein said control means further comprises:

means for regarding a stream of messages from the transmitting software component as an application;

means for monitoring the messages until a monitoring time defined in said shared reference information expires such that, during the monitoring period, the received information is regarded as valid messages and information, other than that defined in said shared reference information, is not accepted.

19. The execution control system as claimed in claim 1, further comprising:

a main system;

a standby system, said shared reference information defining combinations of software components and applications as statuses having valid/invalid states;

means for managing the valid invalid states of the statuses; and

said control means further comprising means for switching operation between the main system and the standby system by referring to said shared reference information.

20. The execution control system as claimed in claim 19, wherein said control means changes information relating to valid/invalid states of the status defined in said shared reference information when processing is switched from said main system to said standby system, or from said standby system to said main system.

21. An execution control system for controlling applications defined as a stream of successive messages exchanged between software components, a software component issuing a message being defined as a transmitting software component and a software component receiving the message being defined as the receiving software component, the execution control system comprising:

shared reference information containing information regarding the applications; and

control means for referring to the shared reference information when exchanging messages between a transmitting software component and a corresponding, receiving software component.

22. The execution control system as claimed in claim 21, wherein the control means further comprises:

means for referring to the shared reference information, and

means for controlling message exchanging between a transmitting software component and a corresponding, receiving software component by compensating for differences in interfaces of the transmitting software component and of the receiving software component.

23. The execution control system as claimed in claim 22, wherein the control means further comprises:

means for converting the format of a message sent from a transmitting software component so as to adapt to the reception format of the corresponding, receiving software component.

24. The execution control system as claimed in claim 22, wherein the control means further comprises:

means for editing a message sent from a transmitting software component by referring to the shared reference information, and for sending the edited message to the corresponding, receiving software component.

25. The execution control system as claimed in claim 23, wherein a message sent from a transmitting software component is sent to the control means for routing to the corresponding, receiving software component.

26. The execution control system as claimed in claim 23, wherein a message sent from a transmitting software component comprises a destination, a message code, a message and an interface.

27. The execution control system as claimed in claim 23, wherein the control means further comprises:

means for receiving a plurality of messages from the transmitting software component and for sending the plurality of messages to the corresponding, receiving software component.

28. The execution control system as claimed in claim 23, wherein the control means further comprises:

means for receiving a message from a transmitting software component to be received by a plurality of receiving software components, the message including an interface;

means for editing the interface of the message;

means for reproducing the message to obtain a copy of the message for each of the plurality of receiving software components; and

means for sending the copies to the receiving software components.

29. The execution control system as claimed in claim 23, wherein the control means further comprises:

means for regarding a stream of information from a transmitting software component as an application; and

means for monitoring messages from a moment when an application start message is received to a moment when an application end message is received and so that information, other than that defined in the shared reference information, is not accepted as a valid message.

30. The execution control system as claimed in claim 23, wherein the control means further comprises:

means for regarding a stream of messages from a transmitting software component as an application; and

means for monitoring messages until a monitoring time defined in the shared reference information expires such that, during the monitoring period, the received information is regarded as valid messages, and information other than that defined in the shared reference information is not accepted.

31. An execution control system which controls the processing of software components and applications, an application being a stream of successive messages exchanged between software components, the execution control system comprising:

a main system;

a standby system;

shared reference information defining combinations of software components and applications as statuses having valid and invalid states;

means for managing the valid and invalid states of the statuses; and

control means for switching operation between the main system and the standby system by referring to the shared reference information.

32. The execution control system as claimed in claim 31, wherein the control means changes information relating to valid and invalid states of the status defined in the shared reference information when processing is switched from the main system to the standby system or from the standby system to the main system.