EP1027646A1 - Procede de configuration pour installations informatiques - Google Patents

Procede de configuration pour installations informatiques

Info

Publication number
EP1027646A1
EP1027646A1 EP98948814A EP98948814A EP1027646A1 EP 1027646 A1 EP1027646 A1 EP 1027646A1 EP 98948814 A EP98948814 A EP 98948814A EP 98948814 A EP98948814 A EP 98948814A EP 1027646 A1 EP1027646 A1 EP 1027646A1
Authority
EP
European Patent Office
Prior art keywords
parameter
file
value
definition file
parameters
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Withdrawn
Application number
EP98948814A
Other languages
German (de)
English (en)
Inventor
Ralph Rinschen
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Wincor Nixdorf International GmbH
Original Assignee
Wincor Nixdorf International GmbH
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Wincor Nixdorf International GmbH filed Critical Wincor Nixdorf International GmbH
Publication of EP1027646A1 publication Critical patent/EP1027646A1/fr
Withdrawn legal-status Critical Current

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44Arrangements for executing specific programs
    • G06F9/445Program loading or initiating
    • G06F9/44505Configuring for program initiating, e.g. using registry, configuration files

Definitions

  • the invention relates to a configuration method for data processing systems.
  • the Free Software Foundation provides under the name "GNU CFENGINE” a system developed by Mark Burgess for the administration of data processing systems, which is based on operating systems according to the POSIX standard. Version 1.4.1 of this software can be reached via ftp://ftp.germany.eu.net/ /pub/packages/gnu/cfengine-1.4.1. tar. gz and via any other mirror of "Free Software Foundation Inc.”, 59 Temple Place - Suite 330, Boston, MA 02111, USA.
  • "CFENGINE” is a system for managing a network of data processing systems. A special script language is used to describe the target configuration of a data processing system.
  • the associated Software is controlled by this script language in such a way that the target configuration described there is set.
  • the section "editfiles” is of particular importance. With “editfiles” a number of files can be brought to a target level.
  • the commands provided in CFENGINE make it possible to automatically inspect a configuration or parameter file and bring it to a desired target state. This is achieved by a number of commands, eg "AppendlfNoSuchLine", which inserts a line if it is not available.
  • An experienced system administrator is required, as can be seen from the last paragraph of the above section, which states: "It is suggested that you use these editing functions with caution.”.
  • parameters of different applications or their programs and parameter files are assigned based on the knowledge of the system administrator, who must be informed and trained to know the respective names and references of the parameters to one another. If modified software is installed, the control file for CFENGINE must be updated accordingly.
  • the invention is based on the observation that parameters of the respective applications or system components are often referred to differently, although they must be the same when the system is in operation.
  • the invention therefore uses a definition file in which the parameters of the system components are identified and localized and are given a name in such a way that parameters which have the same content, even if they are designated differently by the system components and are stored in different places, are given a uniform designation.
  • This name can then be chosen in the terminology and in relation to the field of application.
  • the user then defines his specific parameters for the overall system and saves them in a single configuration file.
  • the process updates the parameters of the system components using the definition and configuration files. This procedure also makes it easy to carry out a test run at which the parameter updater logs what changes should be made, but without already making these changes.
  • Fig. 2 shows the links between the data fields.
  • FIG. 1 schematically shows a parameter comparator 10 which processes a definition file 12 and a configuration file 14.
  • One or more parameter files (16) are created from the data stored there.
  • a parameter file is a file in which a number of values are stored by means of an associative method, ie addressed by key. These values are used by a program using the parameter file to define runtime parameters.
  • Such a parameter file 16 is shown schematically in FIG. 2 as a table, in which a key A is listed in the first column and the associated values E are contained in the second column. There are a number of different types after which these parameters are saved. In POSIX operating systems, these are the files also known as .re files, whose file names begin with a period. In the graphical user interface Windows 3.x from Microsoft, files with the extension '.INI' are used.
  • Section identifiers in square brackets and, apart from comment or blank lines, a parameter for each line, the line starting with a key value, followed by an equal sign and the set value.
  • Logically there is a tree structure in which the file name represents the root, the section designates a subsequent node, the keys represent the lowest nodes and the values represent the leaves.
  • parameters in the Windows NT operating system are also stored in a central database, the tree structure being represented by a dot as a separator via the syntax of a key.
  • the representation in FIG. 2 assumes a linearized tree in which, for example, the absolute name of the parameter is present in the key.
  • the type of storage whether as a binary file or in a readable form, whether linearized or with measures that accelerate access, can be chosen freely by the person skilled in the art applying the invention in accordance with the respective boundary conditions and other requirements. Whether all parameters are stored in a single database or the top sheets represent file names is of secondary importance for the invention.
  • the key A thus symbolically stands for the name of the parameter, its format and the location as well as the type of storage.
  • the tables involved are shown in simplified form in FIG. 2.
  • a parameter file 16 contains a number of parameters, represented as lines, with a key A and a value E. Furthermore, there is a definition file 12 which logically has three columns, namely a key A, a designation B and a standard value C. The keys are the same as used in the parameter file 16 and are therefore designated with A in both. There is also a configuration file 14, which conceptually has two columns A and D. The first column A again contains a key from the same entirety as the columns A of the parameter file 16 and the definition file 12. Associated with this is a target value D of the respective parameter designated by the key.
  • the method implemented by the parameter comparator 10 is based on the definition file. This is processed line by line and the triple is read from name A, description B and standard value C. Using the name A, the key A is searched for in the parameter file 16, indicated by the arrow 22, and the value E is read. If there is no entry with the key A, the standard value C is set as the value E and otherwise the value E is continued. The designation B is also searched for in the configuration file 14, symbolized in FIG. 2 by the connection 21. If the designation B is not found, the value C is used instead of the value D in the further steps. In terms of programming, it can make sense to keep copies of the files in memory and then to add the key B not found with the value D equal to the value C. However, it should be noted that the parameter comparator does not change the definition file or the configuration file; only the parameter file 16 is changed different. found, the value D is compared with the value E.
  • the value D takes precedence over the stored value E; i.e. the value D is entered in the parameter file 16 if it deviates from the value E.
  • the behavior of the parameter comparator 10 can also be described as follows: Set the value E under the key A in the parameter file 16 if the identifier B is also found in the configuration file 14. Otherwise, set the value C under the key A in the parameter file.
  • the detour via the identifier B ensures that the keys in the configuration file 14 can be selected freely and independently of the keys in the parameter file 16. This is because the latter are determined by the manufacturers of the products that use the parameter file 16.
  • the definition file 12 is created by a specialist who compiles the products and has precise knowledge of the required parameters A. The configuration file can then be maintained by a user who now finds the changed identifiers adapted to his terminology and does not have to take into account the component for which the value D is intended.
  • the definition file can also contain information about the permitted parameter values E from the configuration file.
  • the permitted parameter values E are the usual ben, as they are used in plausibility checks, for example, value ranges for numerical values and the like. If a target value D is not below the permitted values, the standard value C is entered in its place. The same applies if the entered value E is not permitted. This can happen if the user has changed the parameter value E by other means.
  • a message can be sent to an administrator using the means available in the respective operating system, for example mail or 'syslog'. The log file described below can also accommodate this message.
  • Every change to a parameter file 16 is noted in the log file 20.
  • the previous value is also entered here. It is not only possible to understand the changes. If an inadmissible value is found in the configuration file, which can be changed by the user, then in the case of a log file the previous value is taken from the log file, which probably delivers better results than the standard value C from the definition file 12.
  • a status file 19 is provided in a development of the invention. All changed or checked values of all affected parameter files 16 are stored in these. Not all parameters are saved, as is the case with the registry in Windows NT, but only those that are handled by the parameter comparator. This also allows a backup on systems like 'Windows for Workgroups 1 , where a backup of the parameter files is not provided. It also contains the last set or checked value so that changes can be made by the user with Edi- gates can be easily undone directly in the parameter files.
  • a control file 18 is provided. In this the mapping of the key A from the definition file 12 to the parameter file 16 is determined. Depending on the operating system, all parameters are stored in a single ('registry') database or in several text files ('. Ini').
  • the control file 18 uses a further indirect step in that the key A in the definition file 12 is broken down into two parts, the first of which deals with the control file 18 and the second is the key in the respective parameter file 16.
  • the key A in the definition file 12 is 'X25.CALL'; its value, a number, is irrelevant here.
  • the key 'X25' is used to search in the control file 18 and as a result, depending on the respective system, it is found that either a file 'C: ⁇ windows ⁇ x25.ini' in Windows text format or a '.ini' in the OS / 2 binary format, or a section 'HKEY / LOCAL_SYSTEM / SOFTWARE / NETWORK / PACKET / X25' should be used in a registry 'registry'.
  • the definition file 12 can thus be created and maintained independently of the respective system. Since the configuration file 14 still refers to the keys in the definition file 12, only the control file has to be exchanged when the operating system is changed.
  • the values are tested in the following order: value from the configuration file; original value; Default value from the definition file; Average or median for an ordered amount or first value for an unordered amount of the allowed values.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

L'invention concerne un procédé pour l'exploitation d'une installation informatique dans lequel un programme d'harmonisation des paramètres actualise des jeux de paramètres de composantes système en se basant sur les fichiers suivants: un fichier de définition qui identifie les paramètres et un fichier de configuration qui détermine les paramètres au moyen de la désignation figurant dans le fichier de définition.
EP98948814A 1997-09-30 1998-08-20 Procede de configuration pour installations informatiques Withdrawn EP1027646A1 (fr)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
DE19743324A DE19743324A1 (de) 1997-09-30 1997-09-30 Konfigurierungsverfahren für Datenverarbeitungsanlagen
DE19743324 1997-09-30
PCT/DE1998/002447 WO1999017192A1 (fr) 1997-09-30 1998-08-20 Procede de configuration pour installations informatiques

Publications (1)

Publication Number Publication Date
EP1027646A1 true EP1027646A1 (fr) 2000-08-16

Family

ID=7844234

Family Applications (1)

Application Number Title Priority Date Filing Date
EP98948814A Withdrawn EP1027646A1 (fr) 1997-09-30 1998-08-20 Procede de configuration pour installations informatiques

Country Status (6)

Country Link
EP (1) EP1027646A1 (fr)
JP (1) JP2001518659A (fr)
CN (1) CN1272927A (fr)
AU (1) AU9531298A (fr)
DE (1) DE19743324A1 (fr)
WO (1) WO1999017192A1 (fr)

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6931523B1 (en) * 1999-12-09 2005-08-16 Gateway Inc. System and method for re-storing stored known-good computer configuration via a non-interactive user input device without re-booting the system
DE10203403B4 (de) * 2002-01-28 2005-01-27 Wincor Nixdorf International Gmbh Computersystem mit Gerätesteuerungen für Peripheriegeräte, die von einem Anwendungsserver genutzt werden, sowie einem Konfigurationsserver
US20050010388A1 (en) * 2003-07-11 2005-01-13 International Business Machines Corporation Dynamic online multi-parameter optimization system and method for autonomic computing systems
JP4516404B2 (ja) * 2004-10-28 2010-08-04 株式会社日立製作所 データベース構築方法、データベース構築システムおよびデータベース構築プログラム
EP1679630A3 (fr) * 2004-12-09 2006-08-30 Sysmex Corporation Procédé de définition des conditions de fonctionnement d'un appareil de mesure, procédé de gestion d'un résultat de mesure d'un appareil de mesure, système de mesure, appareil de traitement de données pour appareil de mesure, et support de stockage
DE102012106774A1 (de) 2012-07-25 2014-01-30 Endress + Hauser Gmbh + Co. Kg Verfahren zur Aufrechterhaltung der Funktionsfähigkeit eines Feldgerätes
CN203733106U (zh) * 2013-12-03 2014-07-23 上海移为通信技术有限公司 Mtk平台终端设备
WO2016004978A1 (fr) * 2014-07-08 2016-01-14 Siemens Aktiengesellschaft Dispositif de développement pour développer des installations techniques, système d'automatisation, dispositif de commande et procédé
DE102016008587B4 (de) * 2016-07-13 2024-02-15 Audi Ag Zugriff auf ein über einen Datenbus eines Kraftfahrzeugs übermittelbares Steuersignal

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5056001A (en) * 1989-12-20 1991-10-08 Ge Fanuc Automation North America, Inc. Method for configuring an input/output module coupled to a programmable logic controller
GB9215320D0 (en) * 1992-07-18 1992-09-02 Int Computers Ltd Configuration mechanism for a computer system
US5339432A (en) * 1992-10-13 1994-08-16 Microsoft Corporation Method and system for providing user control of device driver configuration

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See references of WO9917192A1 *

Also Published As

Publication number Publication date
AU9531298A (en) 1999-04-23
JP2001518659A (ja) 2001-10-16
WO1999017192A1 (fr) 1999-04-08
DE19743324A1 (de) 1999-04-08
CN1272927A (zh) 2000-11-08

Similar Documents

Publication Publication Date Title
DE69712560T2 (de) System zur Konfiguration von vorkonfigurierten Programmen auf vernetzten offenen Systemen in einer verteilten Umgebung und Verfahren zur Durchführung dieses Systems
DE69202575T2 (de) Verfahren und vorrichtung zur reduktion der datenmenge fuer die softwareinstallierung.
DE69502381T2 (de) Verfahren und vorrichtung zum steuern des zugriffs auf eine datenbank
DE69428400T2 (de) Verfahren zur Konfigurationsverwaltung
EP3480672B1 (fr) Procédé de détection et d'affichage d'accès d'opérateur à des objets de traitement ainsi que système d'exploitation
EP0829046B1 (fr) Methode et systeme d'actualisation des programmes-utilisateurs ainsi que des ordinateurs utilisateurs dans un reseau d'ordinateurs
DE10048942A1 (de) Verfahren und System zur Wartung von Software über ein Netz
DE4305522C2 (de) Einrichtung zur rechnergestützten Diagnose eines aus Modulen bestehenden technischen Systems
EP1430369B1 (fr) Acces dynamique a des ressources d'automatisation
DE10309246B4 (de) Verfahren für das Event Management
EP1638028A2 (fr) Génération assistée par ordinateur et gestion de changement pour interfaces utilisateur
DE19847201A1 (de) System und Verfahren zur Verwendung eines RAM-Laufwerks
DE60002618T2 (de) Verfahren und Analysewerkzeug zur Fehlerortung in einem Rechner
EP1027646A1 (fr) Procede de configuration pour installations informatiques
EP1701266A1 (fr) Appareil de test pour vérifier un traitment par lots
EP3364257B1 (fr) Procédé de fonctionnement d'un système d'ingénierie pour un système d'automatisation de processus industriel et programme de commande
EP1637956A1 (fr) Génération d'ensembles de données anonymisées et actualisables destinés aux tests et dévéloppement
EP1261917A2 (fr) Procede de garantie de compatibilite et procede de securite des donnees dans un systeme informatique distribue presentant plusieurs systemes informatiques partiels
WO2010034548A1 (fr) Module de test et procédé destiné à tester un intergiciel de mapping o/r
EP1536328A2 (fr) Système de traitement de données avec la gestion automatisable et procédé pour la gestion automatisée d'un système de traitement de données
DE102005008519B4 (de) Verfahren zum Überwachen eines Verzeichnisses in einem Drucksystem, Computerprogramm-Produkt und Drucksystem zum Ausführen dieses Verfahrens
EP1436673B1 (fr) Determination automatique de parametres
EP1033647A2 (fr) Méthode pour transporter un système logiciel à des autres plates-formes
EP1376383A2 (fr) Mèthode de traitement de données d'entré et de sortie pour une analyse statistique et mèthode pour éliminer de données rédondantes
DE19926370A1 (de) System zur Dokumentation, Archivierung und zum Auffinden wiederverwendbarer Software-Komponenten

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20000303

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AT CH DE ES FR GB LI SE

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: WINCOR NIXDORF GMBH & CO KG

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION HAS BEEN WITHDRAWN

18W Application withdrawn

Withdrawal date: 20010801