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

• US 8,190,577 B2
• Filed: 01/27/2011
• Issued: 05/29/2012
• 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:
  US13/015,052
• Publication Number:
  US 20110119236A1
• Time in Patent Office: 488 Days
• Field of Search: 711161-162, 707609-673, 707802-812, 707999001-999005, 707/999.2, 707999201-999205
• 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 comprising:

a processor;

a central database containing central database content;

a first archiving module comprising a first archiving program and a staging database, the first archiving program being configured to collect at least some of the central database content and schema of the central database and to organize the collected at least some of the central database content and schema into the staging database, the first archiving module being configured to associate data comprising a database logical name and a database identifier with the collected at least some of the central database content and schema of the staging database and to archive the collected at least some of the central database content and schema of the staging database with the data as a first content archive file, the first archiving module providing the first content archive file with a first version identifier; and

,

a second archiving module configured to;

archive the first content archive file and associated supporting software into a first executable application archive file, wherein the first executable application archive file is adapted to be executed by an associated remote application server, said executing including executing the associated supporting software for accessing the first content archive file to access the at least some of the central database content by the database logical name and the database identifier, and

distribute the first executable application archive file to a plurality of associated application servers other than the central database server for executing the first executable application archive file including executing an instance of a database engine and the associated supporting software 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 of the central database content in a machine and operating system independent format, the database engine instance being configured to access the at least some of the central database content by the database logical name,

wherein the first archiving module is configured to provide an updated content archive file with a second version identifier different than the first version identifier of the first content archive file,

wherein the second archiving module is configured to distribute to the plurality of associated application servers the updated content archive file contained in an updated executable application archive file and having the 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 content 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 assign the first version identifier to the first content archive file to facilitate coordination of content updating during the controlled switchover.

3. The central database server as set forth in claim 2, wherein the staging database comprises:

a data collection module configured to collect data from sources other than the central database into the staging database.

4. The central database server as set forth in claim 1, wherein:

the first archiving module is adapted to create a Java archive (JAR); and

the second archiving module is adapted to create an Enterprise archive (EAR).

5. The central database server as set forth in claim 1, wherein:

the first archiving module is adapted to create a Java archive (JAR); and

the second archiving module is adapted to create an web archive (WAR).

6. The central database server as set forth in claim 1, wherein the first archiving module additionally archives schema of the central database into the first content archive file.

7. The central database server as set forth in claim 6, wherein the central database is a relational database and the supporting software comprises:

a database engine adapted to process the schema and central database content stored in the first content archive file as a relational database.

8. The central database server as set forth in claim 7, wherein the central database is a relational database and the supporting software further includes:

at least one application program adapted to access the database engine using at least one Java database connection (JDBC).

9. A method in a central database server, the method comprising:

storing central database content in a central database;

by a first archiving module comprising a first archiving program and a staging database, collecting at least some of the central database content and schema of the central database, organizing the collected at least some of the central database content and schema into the staging database, associating data comprising a database logical name and a database identifier with the collected at least some of the central database content and schema of the staging database, archiving the collected at least some of the central database content and schema of the staging database with the data as a first content archive file, and providing the first content archive file with a first version identifier;

by a second archiving module;

archiving the first content archive and associated supporting software into a first executable application archive file, wherein the first executable application archive file is adapted to be executed by an associated remote application server, said executing including executing the associated supporting software for accessing the first content archive file to access the at least some of the central database content by the database logical name and the database identifier, and,

distributing the first executable application archive file to a plurality of associated application servers other than the central database server for executing the first executable application archive file including executing an instance of a database engine and the associated supporting software 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 of the central database content in a machine and operating system independent format, the database engine instance being configured to access the at least some of the central database content by the database logical name;

providing, by the first archiving module, an updated content archive file with a second version identifier different than the first version identifier of the first content archive file; and

,

distributing, by the second archiving module to the plurality of associated application servers, the updated content archive file contained in an updated executable application archive file and having the 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 content archive file, and unblocking formation of new database connections.

10. The method according to claim 9, wherein the first archiving comprises assigning the version identifier to the first content archive file to facilitate coordination of content updating.

11. The method according to claim 10, further comprising collecting data from sources other than the central database into the staging database.

12. The method according to claim 9, further comprising:

creating a Java archive (JAR) by the first archiving module; and

,

creating an Enterprise archive (EAR) by the second archiving module.

13. The method according to claim 9, further comprising:

creating a Java archive (JAR) by the first archiving module; and

creating an web archive (WAR) by second archiving module.

14. The method according to claim 13, further comprising additionally archiving schema of the central database into the first content archive file.

15. The method according to claim 14, further comprising processing, by a relational database, the schema and central database content stored in the first content archive file as a relational database.

16. The method according to claim 15, further comprising accessing the database engine using at least one Java database connection (JDBC).