Central database server apparatus and method for maintaining databases on application servers

• US 7,962,454 B2
• Filed: 09/24/2010
• Issued: 06/14/2011
• Est. Priority Date: 09/03/2003
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Debrunner, Daniel J.
• Primary Examiner(s): Saeed; Usmaan
• Application Number:
  US12/889,509
• Publication Number:
  US 20110022569A1
• Time in Patent Office: 263 Days
• Field of Search: None
• US Class Current: 707/661
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• CPC Class Codes: G06F 16/278 Data partitioning, e.g. horizontal or vertical partitioning

Abstract

A central database server (10) supports a central database (12) that contains central database content. A first archiving module (30) archives central database content into a content archive (32). A second archiving module (44) archives the content archive (32) and supporting software (18, 46) into an application archive (50). An application server (20) supports a computer code execution environment (60) for executing the application archive (50) to organize the content of the content archive (32) into a database on the application server (20).

Claims

1. A central database server configured to distribute database content between the central database server and a plurality of associated application servers, the central database server comprising:

a processor;

a central database containing central database content;

a first archiving module archiving at least some of the central database content into a first content archive file, the first archiving module being configured to;

organize a staging database including i) schema and at least some content of the central database residing on the central database server, and ii) content from a source other than the central database;

provide the staging database with a logical name;

first archive the staging database as the first content archive file, the at least some content of the central database being in a machine and operating system independent format; and

,

associate the first content archive file with a version identifier; and

,

a second archiving module archiving the first content archive file and supporting software into an executable application archive, wherein the executable application archive is adapted to be executed by a remote application server, the second archiving module being configured to archive;

i) the first content archive file of the first archiving, and

ii) the supporting software including a database engine and an additional application module, as a self-contained executable distribution archive file;

distribute the self contained executable distribution archive file to the plurality of associated application servers other than the central database server for executing the self-contained executable distribution archive file including executing an instance of the database engine and the additional application module on at least one of the plurality of associated application servers to organize the content of the first content archive file into a database in accordance with the at least some content of the central database in the machine and operating system independent format, the database engine and additional application module instance being configured to access the at least some content by the logical name in a read only fashion; and

,

distribute to the plurality of associated application servers an updated content archive file contained in an updated self-contained executable distribution archive file and having a second version identifier different than the first version identifier, the plurality of associated application servers being adapted to, responsive to receiving the updated content archive file, perform a controlled switchover from using the first content archive file to using the updated content archive file without terminating executing the instance of the database engine by blocking formation of new database connections, closing open database connections, booting the updated distribution archive file, and unblocking formation of new database connections.

2. The central database server as set forth in claim 1, wherein the first archiving module is configured to:

first archive at least some schema of the central database in the first content archive file, the supporting software being adapted to reference the archived schema when accessing content archived in the first content archive file.

3. The central database server as set forth in claim 1, wherein said first archiving module is configured to:

first archive the at least some content of the central database as a Java archive (JAR) file.

4. The central database server as set forth in claim 3, wherein the second archiving module is configured to archive the first content archive file and the supporting software as the self contained executable distribution archive file including second archiving the first content archive file and supporting software as one of an enterprise application archive (EAR) file and a web archive (WAR) file.

5. The central database server as set forth in claim 4, wherein the first and second archiving modules are configured to repeat the first archiving of at least some content, the second archiving of the first content archive file and supporting software, and the distributing to effect an updating of the application servers.

6. A central database server configured to push database content to an associated remote application server implemented in a computer-readable storage medium and configured to support a remote database adapted to receive the database content pushed into the remote database by the central database server, the central database server comprising:

a processor;

a central database containing central database content; and

,

first and second archiving modules configured to generate a self-contained executable database application archive file containing a first content archive file in a machine and operating system independent format, an additional application module, and a database engine configured to organize the first content archive file into a database,

the first archiving module being configured to generate the first content archive file by;

organizing a staging database including i) content extracted from the central database of the central database server and formatted in said machine and operating system independent format, ii) schema of the central database of the central database server, and iii) content from one or more sources other than the central database;

providing the staging database with a logical name;

first archiving the staging database as said first content archive file;

assigning a first version number to the first content archive file;

the second archiving module being configured to second archive i) said first content archive file, ii) the additional application module, and iii) computer code including said database engine as said self-contained executable database application archive file;

wherein the computer code execution environment of the associated remote application server is configured to execute the self-contained executable database application archive file including executing an instance of the additional application module and an instance of the database engine to organize the content of the first content archive file in the machine and operating system independent format into a database in accordance with said schema of the central database, the database engine instance and the additional application module instance being configured to access the contents of the staging database by the logical name in a read only fashion;

wherein the computer code execution environment of the associated remote application server is responsive to receiving an updated content archive file contained in an updated self-contained executable database application archive file and having a second version number different than the first version number of the first content archive file, to perform a controlled switchover from using the first content archive file to using the updated content archive file without terminating the execution of the database engine; and

,

wherein the computer code execution environment of the associated remote application server includes;

a connection screening module adapted to determine whether the first content archive file is a latest version; and

a refresh module operating responsive to the connection screening module determining that a newer version of the first content archive file is extant, the refresh module operating to perform the controlled switchover by;

blocking formation of new database connections,

closing open database connections,

booting the updated content archive file, and

unblocking formation of new database connections.

7. The central database server as set forth in claim 6, wherein:

the computer code execution environment is a Java 2 Enterprise Edition (J2EE) environment; and

the database application archive file is one of an Enterprise Application Archive (EAR) file and a Web archive (WAR) file.

8. The central database server as set forth in claim 7, wherein the first content archive file is a Java archive (JAR) file contained in the database application archive file.

9. The central database server as set forth in claim 8, wherein the schema stored in the database application archive file are stored in the Java archive (JAR) file contained in the database application archive file.

10. The central database server as set forth in claim 8, wherein contents of the Java archive (JAR) file include non-database content extracted from at least one non-database source, wherein the non-database content is organized by the schema stored in the database application archive file.

11. The central database server as set forth in claim 6, wherein:

said schema contained in said database application archive file is a portion of the schema of the central database of the central database server.

12. The central database server as set forth in claim 6, wherein the database engine instance is adapted to access the first content archive file using a content archive identifier contained in the database application archive file as the logical name.