Protocol for controlling an execution process on a destination computer from a source computer

• US 7,237,222 B1
• Filed: 03/07/2002
• Issued: 06/26/2007
• Est. Priority Date: 03/07/2002
• Status: Active Grant

• Current Assignee: McAfee, LLC
• Original Assignee: McAfee, Inc. (McAfee, LLC)
• Inventors: Schlemmer, Andreas, Nedbal, Manuel, Fellner, Paul
• Primary Examiner(s): An; Meng-Al T.
• Assistant Examiner(s): Kang; Insun
• Application Number:
  US10/091,415
• Time in Patent Office: 1,937 Days
• Field of Search: 717100-178, 709/217, 709201-203, 709230-246, 719/203, 719/330, 718102-108
• US Class Current: 717/100
• CPC Class Codes: G06F 9/547 Remote procedure calls [RPC]; Web services
• CPC Class Codes: G06F 9/548 Object oriented; Remote method invocation [RMI] non-remote method invocation G06F9/449

Abstract

A data protocol permitting a source computer to initiate execution of an execution process on a destination computer uses XML data in which different complex data types correspond to different execution processes to be triggered. Parameter data to be used by the associated execution processes may be embedded within the corresponding complex data types.

Claims

1. A computer program product embodied on a tangible computer storage medium executed by a computer for triggering an operation at a destination computer using data transferred between a source computer and said destination computer, said computer program product comprising:

receiving code to receive at said destination computer operation specifying XML data sent by said source computer;

parsing code to parse said operation specifying XML data to identify one or more complex data types within said operation specifying XML data;

matching code to match each complex data type with an associated execution process available to said destination computer;

triggering code to trigger processing by each execution process associated with a complex data type within said operation specifying XML data; and

validating code to validate said operation specifying XML data received at said destination computer against schema data, where said schema data is sent to said destination computer from said source computer at the same time as said operation specifying XML data;

wherein said operation performed includes configuring said destination computer to execute a computer program;

wherein said execution process maps configuration data specified within said operation specifying XML data to a configuration data store of said destination computer;

wherein said configuration data store is one of;

a Windows Registry entry;

an INI file;

a DAPI store; and

a database entry;

wherein an identifier of said execution process within said complex data type includes at least one of;

data specifying a computer file to trigger said execution process;

data specifying a communication channel to trigger said execution process; and

data specifying an operating system command to trigger said execution process;

wherein said operation includes returning result data from said destination computer to said source computer in dependence upon said operation performed by said execution process;

wherein said result data includes data specifying existing configuration data of said destination computer;

wherein said execution process maps existing configuration data of said destination computer stored within said configuration data store of said destination computer to said result data to be returned to said source computer;

wherein said operation specifying XML data is parsed after validating said operation specifying XML data to extract at least one identifier for mapping said at least one identifier to an available execution process;

wherein said operation specifying XML data includes parameter data used by said execution process in said operation.

2. A computer program product as claimed in claim 1, wherein parameter data used by said execution process is represented by data within said complex data type of said execution process.

3. A computer program product as claimed in claim 1, wherein said operation performed includes making a call to an API available to said destination computer.

4. A computer program product as claimed in claim 1, wherein said result data is passed from said destination computer to said source computer as XML data.

5. A computer program product as claimed in claim 1, wherein said operation includes returning result data from said destination computer to said source computer in dependence upon whether or not said execution process is available to said destination computer.

6. A computer program product as claimed in claim 1, wherein an operation that may be performed by said destination computer includes installing a new execution process.

7. A computer program product as claimed in claim 1, wherein said operation specifying data is validated by said destination computer by comparing with a template defining valid data.

8. A computer program product as claimed in claim 1, further comprising validating said operation specifying XML data received at said destination computer against said schema data, where said schema data is present in said destination computer when said operation specifying XML data is sent.

9. A computer program product as claimed in claim 1, wherein said validating of said operation specifying XML data and said schema data transmitted from said source computer to said destination computer at the same time generates a validation result.

10. A computer program product as claimed in claim 9, wherein said validation result triggers at least one of a valid configuration response and an invalid configuration response.

11. A computer program product as claimed in claim 10, wherein said invalid configuration response generates an error message.

12. A computer program product as claimed in claim 10, wherein said valid configuration response starts execution of an associated computer program.

13. A computer program product embodied on a tangible computer storage medium executed by a computer for triggering an operation at a destination computer using data transferred between a source computer and said destination computer, said computer program product comprising:

data forming code to form at said source computer operation specifying XML data containing one or more complex data types; and

transmitting code to transmit from said source computer to said destination computer said operation specifying XML data;

wherein each complex data type within said operation specifying XML data corresponds to an execution process available to said destination computer to be triggered to operate;

wherein said operation performed includes configuring said destination computer to execute a computer program;

wherein said execution process maps configuration data specified within said operation specifying XML data to a configuration data store of said destination computer;

wherein said configuration data store is one of;

a Windows Registry entry;

an INI file;

a DAPI store; and

a database entry;

wherein an identifier of said execution process within said complex data type includes at least one of;

data specifying a computer file to trigger said execution process;

data specifying a communication channel to trigger said execution process; and

data specifying an operating system command to trigger said execution process;

wherein said operation includes returning result data from said destination computer to said source computer in dependence upon said operation performed by said execution process;

wherein said result data includes data specifying existing configuration data of said destination computer;

wherein said execution process maps existing configuration data of said destination computer stored within said configuration data store of said destination computer to said result data to be returned to said source computer;

wherein said operation specifying XML data is parsed after validating said operation specifying XML data to extract at least one identifier for mapping said at least one identifier to an available execution process;

wherein said operation specifying XML data includes parameter data used by said execution process in said operation;

wherein schema data is transmitted from said source computer to said destination computer at the same time as said operation specifying XML data.

14. A computer program product as claimed in claim 13, wherein parameter data used by said execution process is represented by data within said complex data type of said execution process.

15. A computer program product as claimed in claim 13, wherein said operation performed includes making a call to an API available to said destination computer.

16. A computer program product as claimed in claim 13, wherein said result data is passed from said destination computer to said source computer as XML data.

17. A computer program product as claimed in claim 13, wherein said operation includes returning result data from said destination computer to said source computer in dependence upon whether or not said execution process is available to said destination computer.

18. A computer program product as claimed in claim 13, wherein an operation that may be performed by said destination computer includes installing a new execution process.

19. A computer program product as claimed in claim 13, wherein said operation specifying data is validated by said destination computer by comparing with a template defining valid data.

20. A method of triggering an operation at a destination computer using data transferred between a source computer and said destination computer, said method comprising the steps of:

receiving at said destination computer operation specifying XML data sent by said source computer;

parsing said operation specifying XML data to identify one or more complex data types within said operation specifying XML data;

matching each complex data type with an associated execution process available to said destination computer;

triggering processing by each execution process associated with a complex data type within said operation specifying XML data; and

validating said operation specifying XML data received at said destination computer against schema data, where said schema data is sent to said destination computer from said source computer at the same time as said operation specifying XML data;

wherein said operation performed includes configuring said destination computer to execute a computer program;

wherein said execution process maps configuration data specified within said operation specifying XML data to a configuration data store of said destination computer;

wherein said configuration data store is one of;

a Windows Registry entry;

an INI file;

a DAPI store; and

a database entry;

wherein an identifier of said execution process within said complex data type includes at least one of;

data specifying a computer file to trigger said execution process;

data specifying a communication channel to trigger said execution process; and

data specifying an operating system command to trigger said execution process;

wherein said operation includes returning result data from said destination computer to said source computer in dependence upon said operation performed by said execution process;

wherein said result data includes data specifying existing configuration data of said destination computer;

wherein said execution process maps existing configuration data of said destination computer stored within said configuration data store of said destination computer to said result data to be returned to said source computer;

wherein said operation specifying XML data is parsed after validating said operation specifying XML data to extract at least one identifier for mapping said at least one identifier to an available execution process;

wherein said operation specifying XML data includes parameter data used by said execution process in said operation.

21. A method as claimed in claim 20, wherein parameter data used by said execution process is represented by data within said complex data type of said execution process.

22. A method as claimed in claim 20 wherein said operation performed includes making a call to an API available to said destination computer.

23. A method as claimed in claim 20, wherein said result data is passed from said destination computer to said source computer as XML data.

24. A method as claimed in claim 20, wherein said operation includes returning result data from said destination computer to said source computer in dependence upon whether or not said execution process is available to said destination computer.

25. A method as claimed in claim 20, wherein an operation that may be performed by said destination computer includes installing a new execution process.

26. A method as claimed in claim 20, wherein said operation specifying data is validated by said destination computer by comparing with a template defining valid data.

27. A method of triggering an operation at a destination computer using data transferred between a source computer and said destination computer, said method comprising the steps of:

forming at said source computer operation specifying XML data containing one or more complex data types; and

transmitting from said source computer to said destination computer said operation specifying XML data;

wherein each complex data type within said operation specifying XML data corresponds to an execution process available to said destination computer to be triggered to operate;

wherein said operation performed includes configuring said destination computer to execute a computer program;

wherein said execution process maps configuration data specified within said operation specifying XML data to a configuration data store of said destination computer;

wherein said configuration data store is one of;

a Windows Registry entry;

an INI file;

a DAPI store; and

a database entry;

wherein an identifier of said execution process within said complex data type includes at least one of;

data specifying a computer file to trigger said execution process;

data specifying a communication channel to trigger said execution process; and

data specifying an operating system command to trigger said execution process;

wherein said operation includes returning result data from said destination computer to said source computer in dependence upon said operation performed by said execution process;

wherein said result data includes data specifying existing configuration data of said destination computer;

wherein said execution process maps existing configuration data of said destination computer stored within said configuration data store of said destination computer to said result data to be returned to said source computer;

wherein said operation specifying XML data is parsed after validating said operation specifying XML data to extract at least one identifier for mapping said at least one identifier to an available execution process;

wherein said operation specifying XML data includes parameter data used by said execution process in said operation;

wherein schema data is transmitted from said source computer to said destination computer at the same time as said operation specifying XML data.

28. A method as claimed in claim 27, wherein parameter data used by said execution process is represented by data within said complex data type of said execution process.

29. A method as claimed in claim 27, wherein said operation performed includes making a call to an API available to said destination computer.

30. A method as claimed in claim 27, wherein said result data is passed from said destination computer to said source computer as XML data.

31. A method as claimed in claim 27, wherein said operation includes returning result data from said destination computer to said source computer in dependence upon whether or not said execution process is available to said destination computer.

32. A method as claimed in claim 27, wherein an operation that may be performed by said destination computer includes installing a new execution process.

33. A method as claimed in claim 27, wherein said operation specifying data is validated by said destination computer by comparing with a template defining valid data.

34. Apparatus for triggering an operation at a destination computer using data transferred between a source computer and said destination computer, said apparatus comprising:

receiving logic to receive at said destination computer operation specifying XML data sent by said source computer;

parsing logic to parse said operation specifying XML data to identify one or more complex data types within said operation specifying XML data;

matching logic to match each complex data type with an associated execution process available to said destination computer;

triggering logic to trigger processing by each execution process associated with a complex data type within said operation specifying XML data; and

validating logic to validate said operation specifying XML data received at said destination computer against schema data, where said schema data is sent to said destination computer from said source computer at the same time as said operation specifying XML data;

wherein said operation performed includes configuring said destination computer to execute a computer program;

wherein said execution process maps configuration data specified within said operation specifying XML data to a configuration data store of said destination computer;

wherein said configuration data store is one of;

a Windows Registry entry;

an INI file;

a DAPI store; and

a database entry;

wherein an identifier of said execution process within said complex data type includes at least one of;

data specifying a computer file to trigger said execution process;

data specifying a communication channel to trigger said execution process; and

data specifying an operating system command to trigger said execution process;

wherein said operation includes returning result data from said destination computer to said source computer in dependence upon said operation performed by said execution process;

wherein said result data includes data specifying existing configuration data of said destination computer;

wherein said execution process maps existing configuration data of said destination computer stored within said configuration data store of said destination computer to said result data to be returned to said source computer;

wherein said operation specifying XML data is parsed after validating said operation specifying XML data to extract at least one identifier for mapping said at least one identifier to an available execution process;

wherein said operation specifying XML data includes parameter data used by said execution process in said operation.

35. Apparatus as claimed in claim 34, wherein parameter data used by said execution process is represented by data within said complex data type of said execution process.

36. Apparatus as claimed in claim 34, wherein said operation performed includes making a call to an API available to said destination computer.

37. Apparatus as claimed in claim 34, wherein said result data is passed from said destination computer to said source computer as XML data.

38. Apparatus as claimed in claim 34, wherein said operation includes returning result data from said destination computer to said source computer in dependence upon whether or not said execution process is available to said destination computer.

39. Apparatus as claimed in claim 34, wherein an operation that may be performed by said destination computer includes installing a new execution process.

40. Apparatus as claimed in claim 34, wherein said operation specifying data is validated by said destination computer by comparing with a template defining valid data.

41. Apparatus for triggering an operation at a destination computer using data transferred between a source computer and said destination computer, said apparatus comprising:

data forming logic to form at said source computer operation specifying XML data containing one or more complex data types;

transmitting logic to transmit from said source computer to said destination computer said operation specifying XML data;

wherein each complex data type within said operation specifying XML data corresponds to an execution process available to said destination computer to be triggered to operate;

wherein said operation performed includes configuring said destination computer to execute a computer program;

wherein said execution process maps configuration data specified within said operation specifying XML data to a configuration data store of said destination computer;

wherein said configuration data store is one of;

a Windows Registry entry;

an INI file;

a DAPI store; and

a database entry;

wherein an identifier of said execution process within said complex data type includes at least one of;

data specifying a computer file to trigger said execution process;

data specifying a communication channel to trigger said execution process; and

data specifying an operating system command to trigger said execution process;

wherein said operation includes returning result data from said destination computer to said source computer in dependence upon said operation performed by said execution process;

wherein said result data includes data specifying existing configuration data of said destination computer;

wherein said execution process maps existing configuration data of said destination computer stored within said configuration data store of said destination computer to said result data to be returned to said source computer;

wherein said operation specifying XML data is parsed after validating said operation specifying XML data to extract at least one identifier for mapping said at least one identifier to an available execution process;

wherein said operation specifying XML data includes parameter data used by said execution process in said operation;

wherein schema data is transmitted from said source computer to said destination computer at the same time as said operation specifying XML data.

42. Apparatus as claimed in claim 41, wherein parameter data used by said execution process is represented by data within said complex data type of said execution process.

43. Apparatus as claimed in claim 41, wherein said operation performed includes making a call to an API available to said destination computer.

44. Apparatus as claimed in claim 41, wherein said result data is passed from said destination computer to said source computer as XML data.

45. Apparatus as claimed in claim 41, wherein said operation includes returning result data from said destination computer to said source computer in dependence upon whether or not said execution process is available to said destination computer.

46. Apparatus as claimed in claim 41, wherein an operation that may be performed by said destination computer includes installing a new execution process.

47. Apparatus as claimed in claim 41, wherein said operation specifying data is validated by said destination computer by comparing with a template defining valid data.