Remote procedural call component management method for a heterogeneous computer network

• US 5,926,636 A
• Filed: 02/21/1996
• Issued: 07/20/1999
• Est. Priority Date: 02/21/1996
• Status: Expired due to Term

• Current Assignee: RPX Corporation
• Original Assignee: Adaptec Incorporated (Steel Partners Holdings LP)
• Inventors: Malik, Ajay, Battle, Thomas M., Ponnuswamy, Senthil K., Lam, Geoffrey T.
• Primary Examiner(s): Pan, Daniel H.
• Application Number:
  US08/603,531
• Time in Patent Office: 1,245 Days
• Field of Search: 395/683, 395/200.01, 395/800, 395/615, 395/670, 395/200.12, 395/200.15, 395/210.16, 395/672, 395/335, 395/326, 395/200.61, 395/200.57, 395/684 , 395/800.23, 395/200.79, 395/200.31, 395/200.62, 379/60, 379/45, 329/94.3, 329/60
• US Class Current: 719/313
• CPC Class Codes: G06F 9/547 Remote procedure calls [RPC]; Web services

Abstract

In response to a component management function call by a remote client application, the component management application programming interface (API) generates a message that identifies the called function and the version of the component management API. The component management API calls a local message transfer RPC command to send the message to a RPC command module. The RPC command module processes the local message transfer RPC command, and packages the message for transfer as a RPC over the heterogenous network. The RPC command module sends the packaged RPC to a network stack which in turn transmits the packaged RPC over the heterogenous network to a network stack in the server computer. The server network stack provides the packaged RPC to a server RPC command module that unpacks the RPC in a conventional manner to obtain the original message. The message is passed to a server component management API. The server component management API parses the message to determine the computer architecture of the client computer. With this information, server component management API reads the version specified in the message. If the specified version is incompatible with the version of the server component management API, a reply indicating the version incompatibility is transmitted to remote client application and otherwise the message is processed further by the server component management API.

Claims

1. A computer process for using remote procedure calls over a heterogeneous computer network comprising:

filling a message buffer in a first computer with information including a version of an application programming interface on said first computer by a client application, executing on said first computer, calling a management function in said application programming interface, wherein said first computer is on said heterogeneous computer network; and

issuing a message transfer remote procedure call by said application programming interface to transfer said message buffer over said heterogeneous computer network to a second computer;

wherein said local message transfer remote procedure call is used for management functions in said application programming interface;

said message transfer remote procedure call is used to tranfer all message buffers; and

said message transfer remote procedure call is independent of said information in said message buffer.

2. A computer process for using remote procedure calls over a heterogeneous computer network as in claim 1 wherein said filling said message buffer comprises aligning said information in said message buffer so that said information is one byte-aligned.

3. A computer process for using remote procedure calls over a heterogeneous computer network as in claim 1 further comprising:

comparing said version of said application programming interface in said message buffer with a version of an application programming interface on said second computer.

4. A computer process for using remote procedure calls over a heterogeneous computer network as in claim 3 wherein said comparing said version of said application programming interface in said message buffer with a version of an application programming interface on said second computer further comprises:

comparing a plurality of version identifiers of said application programming interface on said first computer with a plurality of version identifiers of said application programming interface on said second computer.

5. A computer process for using remote procedure calls over a heterogeneous computer network as in claim 3 further comprising:

continuing processing of information in said message buffer by said application programming interface on said second computer upon said comparing said version of said application programming interface in said message buffer with a version of an application programming interface on said second computer indicating that said versions are compatible.

6. A computer process for using remote procedure calls over a heterogeneous computer network as in claim 1 wherein said management function is an I/O management function and said application programming interface is a component management application programming interface.

7. A computer process for using remote procedure calls over a heterogeneous computer network comprising:

issuing a component management function call from a remote client application on a remote client computer to a remote client component management application programming interface on said remote client computer, wherein said remote client computer is on said heterogeneous computer network;

building a message in a buffer memory of said remote client computer by said remote client component management application programming interface wherein said message includes an identifier for the called component management function; and

a version of the remote client component management application programming interface; and

sending said message to a server computer on said heterogeneous computer network using a remote procedure call command module wherein said remote procedure call command module is independent of said called component management function.

8. A computer process for using remote procedure calls over a heterogeneous computer network as in claim 7 wherein said sending said message to a server computer on said heterogeneous computer network further comprises:

calling a local message transfer remote procedure call command by said client component management API to transfer said message from said remote client component management application programming interface to a remote client remote procedure call module (RPC)on said client computer.

9. A computer process for using remote procedure calls over a heterogeneous computer network as in claim 8 wherein said sending said message to a server computer on said heterogeneous computer network further comprises:

packaging said message for transfer over said heterogeneous computer network by said remote client RPC command module.

10. A computer process for using remote procedure calls over a heterogeneous computer network as in claim 9 wherein said sending said message to a server computer on said heterogeneous computer network further comprises:

transmitting said packaged message from said remote client RPC command module to a first network stack on said client computer;

transmitting said packaged message from said first network stack to a second network stack on a server computer; and

transmitting said packaged message from said second network stack to a server RPC command module on said server computer wherein said server RPC command module converts said packaged message back to said message.

11. A computer process for using remote procedure calls over a heterogeneous computer network as in claim 10 further comprising:

transferring said message from said server RPC command module to a server component management application programming interface on said server computer.

12. A computer process for using remote procedure calls over a heterogeneous computer network as in claim 11 further comprising:

reading a field in said message by said server component management application programming interface to determine whether an addressing format of said client computer is compatible with an addressing format of said server computer.

13. A computer process for using remote procedure calls over a heterogeneous computer network as in claim 12 further comprising:

converting said message to an addressing format compatible with said server computer upon said server component management application programming interface determining that the addressing format of said client computer is incompatible with said addressing format of said server computer.

14. A computer process for using remote procedure calls over a heterogeneous computer network as in claim 7 wherein said message is one byte-aligned.

15. A computer process for using remote procedure calls over a computer network comprising:

placing a command in a message buffer by a computer process executing on a first computer connected to said computer network

wherein said command is for another computer process executing on a second computer connected to said computer network; and

using a single remote procedure call to transfer all message buffers over said network computer network so that said single remote procedure call is used independent of the command in said message buffer and said single remote procedure call is used by said first computer to transfer said message buffer to said second computer.