Method for assisting the administration of a distributed application based on a binary configuration file in a computer system

• US 7,020,677 B1
• Filed: 12/28/1998
• Issued: 03/28/2006
• Est. Priority Date: 12/30/1997
• Status: Expired due to Term

• Current Assignee: Bull Sas (Atos SE)
• Original Assignee: Bull Sas (Atos SE)
• Inventors: Dia, Mama Saidou, Baillif, Christian
• Primary Examiner(s): An, Meng-Al T.
• Assistant Examiner(s): Vo, Lilian
• Application Number:
  US09/380,250
• Time in Patent Office: 2,647 Days
• Field of Search: 709/101, 709/224, 709/227, 709/100, 709/200, 709/400, 709/201, 709/208, 709/220, 707/201, 718/101, 719/318
• US Class Current: 709/201
• CPC Class Codes: G06F 11/1417 Boot up procedures
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management

Abstract

The present invention relates to a process for assisting in the administration of a distributed application of a transaction processing manager based on a binary configuration file (TUXCONFIG), characterized in that said process comprises:

• • decompiling the active configuration file of the master machine (Mm),
  • retrieving information from the decompiled configuration file of the master machine, and
  • checking the consistency of said application running on said given machine.

Information related to at least one listener module is displayed and includes at least the name of the application, the logical name of the machine (LMID) on which the application is run, the identification of the user (UID) of said application, the address used by the listener module (NLSADDR), the access path to the network of the application, and the access path to a log file of said listener module (LLFPN). If the tlog file containing information on the application running on a given machine does not exist, the file is automatically generated in order to be able to used the file during the next startup of the listener modules.

Claims

1. An automated process for assisting in the administration of a distributed application of a transaction processing manager, based on a binary configuration file said process comprising:

decompiling the active configuration file of the master machine,

retrieving information related to said distributed application from the decompiled configuration file of the master machine,

checking the consistency of said application running on at least one of several machines, wherein said process is performed by a computer program, and wherein the step for checking the consistency of said application comprises comparing the information obtained from the binary configuration file of the master machine and the information obtained from said current application running on a given machine;

managing at least one listener module of any machine from another machine, wherein the managing is capable of starting or stopping one or more of the listener modules based on the binary configuration file and activating the one or more listener modules, wherein the distributed application is started after the starting of the one or more listener modules and the at least one listener module receives information from another machine; and

automatically generating a file containing information on said application running on a given machine when the file does not exist in the given machine in order to be able use it during a next startup of the listener modules.

2. A process according to claim 1, further comprising extracting directly from an active configuration file of the master machine information related to said distributed application.

3. A process according to claim 1, wherein said administration of listener modules consists of comprises starting and stopping at least one listener module, displaying information related to at least one listener module, changing a log of at least one listener module, checking a script of at least one listener module and/or updating the script of at least one listener module.

4. A process according to claim 1, further comprising a step for starting and stopping a listener module running on a first machine, said step for starting and stopping being carried out by an administrator using a second machine distinct from the first machine, but belonging to the same network as the first machine.

5. A process according to claim 1, further comprising a step for simultaneously activating several listener modules.

6. A process according to claim 1, further comprising a step for decompiling an active configuration file of the master machine.

7. A process according to claim 1, including a graphical interface comprising at least one icon, at least one menu and at least one dialog box for implementing a start and stop of a listener module and a retrieval of information and checking the consistency of said application running on a given machine.

8. A process according to claim 1, wherein information related to at least one listener module is displayed and comprises at least a name of said application, a logical name of the machine on which said application is run, an identification of a user of said application, an address used by the listener module, an access path to the network of said application, and an access path to a log file of said listener module.

9. A process according to claim 3, wherein information related to at least one listener module is displayed and comprises at least a name of said application, a logical name of the machine on which said application is run, an identification of a user of said application, an address used by the listener module (NLSADDR), an access path to the network of said application, and an access path to a log file of said listener module.

10. A process according to claim 4, wherein information related to at least one listener module is displayed and comprises at least a name of said application, a logical name of the machine on which said application is run, an identification of a user of said application, an address used by the listener module, an access path to the network of said application, and an access path to a log file of said listener module.

11. A process according to claim 5, wherein information related to at least one listener module is displayed and comprises at least a name of said application, a logical name of the machine on which said application is run, an identification of a user of said application, an address used by the listener module, an access path to the network of said application, and an access path to a log file of said listener module.

12. A process according to claim 7, wherein the at least one menu of the graphical interface is structured in tree form and activation of a menu results in a display of a list of values of a current configuration, selectable by a user.

13. A process according to claim 7, wherein information related to at least one listener module is displayed and comprises at least a name of said application, a logical name of the machine on which said application is run, an identification of a user of said application, an address used by the listener module, an access path to the network of said application, and an access path to a log file of said listener module.

14. A process according to claim 12, wherein information related to at least one listener module is displayed and comprises at least a name of said application, a logical name of the machine on which said application is run, an identification of the user of said application, an address used by the listener module, an access path to the network of said application, and an access path to a log file of said listener module.

15. A process according to claim 13, wherein information related to at least one listener module is displayed and comprises at least a name of said application, a logical name of the machine on which said application is run, an identification of a user of said application, an address used by the listener module, an access path to the network of said application, and an access path to a log file of said listener module.