System and method for the creation and use of surrogate information system objects

• US 5,758,351 A
• Filed: 03/01/1995
• Issued: 05/26/1998
• Est. Priority Date: 03/01/1995
• Status: Expired due to Term

• Current Assignee: Computer Associates Think Inc. (Broadcom, Inc.)
• Original Assignee: Sterling Software, Inc. (Northrop Grumman Corporation)
• Inventors: Gibson, William, Turner, Steve, Marshall, David R., Dawson, William N., Hogan, Patrick M.
• Primary Examiner(s): Black, Thomas G.
• Assistant Examiner(s): LEWIS, CHERYL RENEA
• Application Number:
  US08/397,699
• Time in Patent Office: 1,182 Days
• Field of Search: 395/600, 395/161, 395/500, 395/650, 395/614, 707/104, 707/103, 707/3, 707/10, 345/348, 345/352, 345/347
• US Class Current: 1/1
• CPC Class Codes: G06F 9/465 Distributed object oriented systems remote method invocation [RMI] G06F9/548

Abstract

The present invention defines a consistent method and system for enabling components in an information system to invoke operations that may be distributed across multiple computing platforms, through the provision and use of executable operations whose behaviors are determined from information stored and extracted from a Catalog (164) using an Operation Definition Manager (82). The stored information is used by a Surrogate Object Definition Module (96) to define a Surrogate Object Type structure which enables execution of any of the operations described within it. A Surrogate Object Manager (94), along with an Operation Connection Manager (104, 118, 130 or 132), is provided which assists the user in developing applications by providing access to the definition of the input and output arguments of the operations included in the Surrogate Object Type structure (244). The present invention further includes an Operation Connection Manager (104, 118, 130 or 132) which, together with the Surrogate Object Manager (94), provides a consistent means for an Operation Requestor (92) to invoke an operation and exchange input and output arguments, independent of the intervening network communication protocol or the hardware platform type, operating system and database management system upon which the operation has been implemented.

Claims

1. A system for invoking an executable operation in a distributed system, comprising:

a Catalog for managing information including the executable operation, said information included in the executable operation including an associated operation type and an associated operation definition;

a Surrogate Object Definition Module coupled to the Catalog for presenting the information included in the executable operation to a user and for including the information included in to the executable operation in a Surrogate Object Type structure in accordance with instructions from the user;

a Surrogate Object Manager for interpreting the information in the Surrogate Object Type structure and for providing a set of functions, the set of functions operable to enable examination of the information in the Surrogate Object Type structure and to initiate execution of the executable operation by generating an Operation Activation structure in accordance with the associated operation definition in response to a request, the Operation Activation structure including data required for the execution of the executable operation;

an Operation Requestor, using the set of functions provided by the Surrogate Object Manager, operable to request generation of the Operation Activation structure, to store the data required for the execution of the executable operation in the Operation Activation structure and to generate the request to initiate execution of the executable operation in accordance with the data in the Operation Activation structure and to retrieve returned data from the Operation Activation structure upon completion of the execution of the executable operation; and

an Operation Connection Manager responsive to the Surrogate Object Manager for invoking execution of the executable operation in accordance with the information in the Operation Activation structure.

2. The system of claim 1 wherein the Surrogate Object Type structure comprises a set of linked data records of a predefined type.

3. The system of claim 1 further including an Application Development Tool operable to assist the user in constructing the Operation Requestor.

4. The system of claim 1 wherein the associated operation definition includes information defining input and output arguments of the executable operation and validation requirements of the input and output arguments of the executable operation.

5. The system of claim 1 wherein the Catalog includes:

an Operation Enrollment Module for accepting and storing the information related to the executable operation in a Catalog database and for equating the input and output arguments of the executable operation with arguments of another executable operation using common predicates;

a Catalog Manager for providing a set of access and data storage functions, the set of access and data storage functions enabling the user to add, update and delete records in the Catalog database; and

a Catalog Editor for maintaining the information in the Catalog database.

6. The system of claim 5 wherein the Surrogate Object Definition Module is operable to present the information related to the executable operation to the user in terms of the common predicates.

7. The system of claim 1 wherein the Surrogate Object Type structure includes instance mapping information, and the Surrogate Object Manager is further operable to equate the input and output arguments of the executable operation with values of a predicate included in a Surrogate Object Instance in accordance with the instance mapping information upon completion of the execution of the executable operation and means enabling access to Surrogate Object Instance data.

8. The system of claim 1 wherein the Surrogate Object Type structure is independent of the hardware platform, operating system, database management system and programming language used in implementing the executable operation.

9. The system of claim 1 wherein the Operation Connection Manager initiates the execution of the executable operation synchronously in response to the request from the Operation Requestor.

10. The system of claim 1 wherein the Operation Connection Manager initiates the execution of the executable operation asynchronously in response to the request from the Operation Requestor.

11. The system of claim 1 wherein the executable operation and the Operation Requestor are implemented in homogeneous operating environments.

12. The system of claim 1 wherein the executable operation and the Operation Requestor are implemented in heterogeneous operating environments.

13. A method for invoking an executable operation in a distributed processing system, comprising:

accepting information describing the executable operation, the information including an associated operation type;

storing the information describing the executable operation in a Catalog;

presenting the information related to the executable operation to a user;

accepting instructions from the user for incorporating the information describing the executable operation into a Surrogate Object Type structure;

providing a set of functions for interpreting the information in the Surrogate Object Type structure, for enabling examination of the information in the Surrogate Object Type structure and for initiating execution of the executable operation by generating an Operation Activation structure in accordance with the associated operation definition in response to a request from the user;

constructing an Operation Requestor operable to, using the functions, request generation of the Operation Activation structure, store data required for the execution of the executable operation in the Operation Activation structure, to generate the request to initiate execution of the executable operation in accordance with the data in the Operation Activation structure and to retrieve returned data from the Operation Activation structure upon completion of the executable operation; and

invoking execution of the executable operation in accordance with the information in the Operation Activation structure.

14. The method of claim 13 wherein the step of accepting information defining the associated operation type includes the step of accepting information defining the association of the executable operation with other executable operations with common execution and data passing protocols.

15. The method of claim 13 wherein the step of accepting information information defining the execution requirements of the executable operation includes the step of accepting information defining input and output arguments of the executable operation and validation requirements of the input and output arguments of the executable operation.

16. The method of claim 13, further comprising:

storing instance mapping information in the Surrogate Object Type structure; and

equating input and output arguments of the executable operation with predicate values included in a Surrogate Object instance in accordance with the instance mapping information in response to completion of the execution of the executable operation.

17. The method of claim 13, wherein the step of initiating the execution of the executable operation includes the step of initiating the execution of the executable operation synchronously in response to the request from the Operation Requestor.

18. The method of claim 13 wherein the step of initiating the execution of the executable operation includes the step of initiating the execution of the executable operation asynchronously in response to the request from the Operation Requestor.

19. The method of claim 13 wherein the step of initiating the execution of the executable operation includes the step of initiating the execution of the executable operation in a homogeneous operating environment with respect to the Operation Requestor.

20. The method of claim 13 wherein the step of initiating the execution of the executable operation includes the step of initiating the execution of the executable operation in a heterogeneous operating environment with respect to the Operation Requestor.