Information processing system architecture

• US 6,305,015 B1
• Filed: 07/01/1998
• Issued: 10/16/2001
• Est. Priority Date: 07/02/1997
• Status: Expired due to Term

• Current Assignee: Bull Sas (Atos SE)
• Original Assignee: Bull Sas (Atos SE)
• Inventors: Touzan, Jean-François, Lanquetin, Jean-Marie, Akriche, Jean, Leteinturier, Alain, Sitbon, Gérard
• Primary Examiner(s): Powell, Mark R.
• Assistant Examiner(s): ZHEN, WEI Y
• Application Number:
  US09/108,193
• Time in Patent Office: 1,203 Days
• Field of Search: 717/11, 717/1, 709/220, 709/221, 709/222, 713/100
• US Class Current: 717/168
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management

Abstract

An information processing system architecture comprising a set of software products subdivided into domains (21-23), each of which comprises at least one software product. Each domain (21-23) contains specific information comprising an identifier of the domain (21-23), its attributes, and data on the software products comprising it. These data allow the installation and/or the updating of the domains (21-23) in accordance with a set of rules. The software products are constituted of products that are fully integrated into the domains, which follow standard installation and/or updating rules common to the system, and of heterogeneous products from external sources whose packaging and installation and/or updating rules remain specific. A consistency check of the version can be carried out on all or some of these external products. The system (2) comprises at least two specific domains for the operating system (21) and the operations monitor (23) of the system (2).

Claims

1. An architecture for an information processing system, said system comprising a hardware platform (20) that cooperates with a set of software products, said set of software products being subdivided into subsets called domains (21-24), each domain having at least one of said software products (40-42), and an interface called a descriptor (3), said descriptor providing access to a specific determined information (30-32), said specific determined information including at least one identifier (30) of the domain and data (32) describing the software products in the corresponding domain, said descriptor for at least one of said domains further including first and/or second information, said first information relating to predetermined installation and updating rules common to the system and said second information relating to at least one of said software products which has specific installation and updating rules, said second information allowing a control by the system of said specific installation and updating rules, and means for installing and/or updating said domains (21-24) with reference to said specific determined information (30-32).

2. The architecture according to claim 1, wherein said identifier (30) comprises at least the information of the domain name and version.

3. The architecture according to claim 1, wherein said specific determined information also comprises at least one attribute associated with the corresponding domain and describing specific functional characteristics associated with the corresponding domain.

4. The architecture according to claim 3, wherein said at least one attribute represents, according to a predetermined scale of levels relating to said first and/or second information, a level of integration and control of said software products (P_0i through P_3j) of the corresponding domain (D_j).

5. The architecture according to claim 4, wherein said scale of levels includes an upper level (N₃) for which all of said software products in the corresponding domain relate only to said first information.

6. The architecture according to claim 4, wherein said scale of levels includes at least one intermediate level (N₀-N₂) for which at least one of said software products (P_0i through P_2j) in the corresponding domain relates to said second information.

7. The architecture according to claim 3, wherein the domain corresponding to said at least one attribute can have instances and said at least one attribute represents the combination of the number of said instances of domain (D_j) which can be installed and can coexist in said system (2), with or without the possibility of running said instances simultaneously.

8. The architecture according to claim 7, wherein said at least one attribute can be selected among a first attribute representative of only one installation of said corresponding domain (D_j) into the system (2) and only one execution, a second attribute representative of a multiple installation of said corresponding domain and only one execution, and a third attribute representative of multiple installation of said domain and a multiple execution.

9. The architecture according to claim 3, wherein said at least one attribute of said corresponding domain and points to at least one other domain whose presence within said system (2) is required for the operation of at least some of said software products of said corresponding domain (D_j).

10. The architecture according to claim 1, wherein said domains (D_j) have a four-level hierarchic structure, said software products (P_i) representing a first level and each comprising at least one module (M_i1-M_i3) representing a second level, each module (M_i1-M_i3) comprising at least one file set (FS_i1-FS_i32) representing a third level, and each file set (FS_i1-FS_i32) comprising at least one file (F_i11-F_i322) representing a fourth level, and wherein a determined file belongs to only one file set, a file set belonging to only one module and a module belonging to only one software product.

11. The architecture according to claim 10, wherein each of said domains (D_j) comprises at least one module containing a set of specific files for recording said domain identifier and said data on the software products comprising the domain.

12. The architecture according to claim 10, wherein said at least one file set includes said second information.

13. The architecture according to claim 10, wherein said file sets present in a corresponding domain (D_j) are non-contiguous to one another.