Process for monitoring execution of a command script

• US 5,805,884 A
• Filed: 04/10/1996
• Issued: 09/08/1998
• Est. Priority Date: 05/12/1995
• Status: Expired due to Term

• Current Assignee: Evidan
• Original Assignee: Bull Sas (Atos SE)
• Inventors: Champeval, Didier, Gobert, Daniel, Sitbon, Gerard
• Primary Examiner(s): Bowler, Alyssa H.
• Assistant Examiner(s): Nguyen, Dzung C.
• Application Number:
  US08/630,462
• Time in Patent Office: 881 Days
• Field of Search: 395/200.01, 395/385, 395/680, 395/681, 395/683, 395/684, 395/685, 395/200.31, 395/200.32, 364/DIG. 1
• US Class Current: 719/320
• CPC Class Codes: G06F 9/45512 Command shells
• CPC Class Codes: G06F 9/54 Interprogram communication

Abstract

A process for monitoring the acknowledgement of a request to execute a command script (script) through a non-guaranteed protocol (S.N.M.P.), in an information system (SI) in a network (RE) comprising a manager (GE) and agents (AG1) for executing commands, wherein the manager first sends the agent in charge of executing the command script a ticket request using a command (Get mrsGetTK) of the "get" type, and the agent returns (GetResponse) a ticket to the manager, the manager then sends the execution request to the agent using a command (Set mrsExecute cmd TK) of the "set" type, for which the ticket it a parameter, then the agent verifies the validity of the request and creates an instance for the execution of the command associated with the ticket and the manager then verifies proper reception of the request by scanning (Get mrsStatus) the instance using the agent. The instant invention is particularly applicable to heterogeneous information systems.

Claims

1. A process for monitoring an acknowledgement of a request for execution of a command script (script) through a protocol which is not guaranteed in a connectionless mode, in an information system (SI) having a plurality of heterogeneous platforms (PL. PLC1, and PLC2), a network (RE) for linking said platform and supporting said protocol, one of said platforms being a command platform (PL), having a manager (GE), the other of said platforms comprising agents (AG1, and AG2,) for executing commands, said process comprising the following steps:

A) sending a request (Get mrsGetTK) for an identification ticket using a command of the "get" type, from the manager (GE), to the agent (AG1) of the platform (PLC1) in charge of executing the command request and returning from the agent (AG1) (GetResponse) an identification ticket (TK) to the manager;

B) sending the request to execute the command (Set mrsExecute "cmd Tk") from the manager to the agent using a command of the "set" type, for which said ticket is a parameter, then verifying validity of the identification ticket by the agent and creating by said agent an instance for the execution of the command, which the agent associates with the identification ticket (TK), and

C) confirming by the manager proper reception of the request by scanning said instance (Get mrsStatus) by means of the agent and, using the identification ticket, monitoring the progress of the execution of the request.

2. The monitoring process according to claim 1, wherein the protocol is the S.N.M.P. type and the execution requests are the snmpset type for executing the command scripts, said process further including:

A) using a snmpget command for the identification ticket request by the manager (GE), and using the agent to return the identification ticket to the manager,

B) using a snmpset command to request execution of the command script by the manager (GE) to the agent (AG1), said identification ticket being a parameter of said snmpset command,

C) using said snmpget command by the manager to confirm proper reception of the request, and

D) as soon as the execution of the command script has terminated, using the manager to carry out an operation acknowledging said termination, by sending the agent a command (Set mrsControl "ack") of the "set" type with an appropriate acknowledgement value.