Apparatus and method for maintaining databases on application servers

• US 7,873,602 B2
• Filed: 09/03/2003
• Issued: 01/18/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:
  US10/653,833
• Publication Number:
  US 20050050071A1
• Time in Patent Office: 2,694 Days
• Field of Search: 707/204
• 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. An application server implemented in a computer-readable storage medium and configured to support a remote database adapted to receive database data pushed into the remote database by a central database server, the application server comprising:

a computer code execution environment adapted to execute self-contained application archive files; and

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 database application archive file being generated by;

organizing a staging database including i) content extracted from a 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;

second archiving 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 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 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 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 includes;

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

a refresh module operating responsive to the connection screening module determining that a newer version of the database application 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 newer version of the database application archive file, and

unblocking formation of new database connections.

2. The application server as set forth in claim 1, 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.

3. The application server as set forth in claim 2, wherein the content archive file is a Java archive (JAR) file contained in the database application archive file.

4. The application server as set forth in claim 3, 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.

5. The application server as set forth in claim 3, 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.

6. The application server as set forth in claim 1, 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.

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

8. The application server as set forth in claim 1, wherein the database engine instance is adapted to access the content archive file using a Java database connection (JDBC).

9. The application server as set forth in claim 1, wherein the computer code execution environment further includes:

an application program adapted to access the content archive file via the database engine.

10. The application server as set forth in claim 9, wherein the application program is selected from a group consisting of a Java servlet, Java server pages, and Enterprise Java Beans (EJB).

11. The application server as set forth in claim 1, wherein the computer code execution environment includes:

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

a refresh module operating responsive to the connection screening module determining that a newer version of the database application archive file is extant, the refresh module operating to transfer database connections from the first content archive file to the updated content archive file of the newer version of the database application archive file.

12. The application server of claim 1 configured to interface with the central database server implemented, the central database server comprising:

the central database containing central database content;

a first archiving module archiving at least some of the central database content into a content archive; and

a second archiving module archiving the content archive and supporting software into an executable application archive, wherein the executable application archive is adapted to be executed by a remote application server, said executing including executing the supporting software to access the content archive.

13. The application server as set forth in claim 12, wherein the central database is a relational database and the supporting software includes:

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

14. The application server as set forth in claim 13, 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).

15. The application server of claim 12 configured to interface with an instance of a distributed database implemented in a computer-readable medium, the instance comprising:

a database engine;

data content and schema providing a logical description of the data content, the data content and schema being arranged as one of;

database server files, and

an archive file;

wherein the database engine is adapted to provide;

read/write access to the data content conditional upon the data content and schema being arranged as database server files, and

read-only access to the data content conditional upon the data content and schema being arranged as an archive file.

16. A method for distributing database content between an associated central database server and a plurality of associated application servers, the method comprising:

using a first archiving module of the associated central database server, generating a first content archive file by organizing a staging database including;

i) at least some content of a central database residing on a central database server, the at least some content being in a machine and operating system independent format, ii) at least some schema of the central database as said content archive file, and iii) content from a source other than the central database;

providing the staging database with a logical name;

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

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

,

using a second archiving module of the associated central database server, generating a self-contained executable distribution archive file by second archiving;

i) said first content archive file of said first archiving, ii) an additional application module and iii) supporting software including a database engine, as said self-contained executable distribution archive file;

distributing the self-contained executable distribution archive file by the associated central database server to the plurality of associated application servers other than the central database server, the plurality of associated application servers each having an operating environment adapted to execute the self-contained executable distribution archive file including executing an instance of the database engine and the additional application module to reference the at least some content of the central database in the machine and operating system independent format archived in the first content archive file in accordance with the schema of the central database, the database engine being configured to access the content of the staging database by the logical name in a read only format; and

,

distributing 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 number different than the first version number, 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.

17. The method as set forth in claim 16, wherein said first archiving of at least some content of the central database includes:

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

18. The method as set forth in claim 17, wherein said second archiving of the content archive file and supporting software as said distribution archive file includes:

second archiving the content archive file and supporting software as one of an enterprise application archive (EAR) file and a web archive (WAR) file.

19. The method as set forth in claim 16, further including:

repeating the first archiving of at least some content, the second archiving of the content archive file and supporting software, and the distributing to effect an updating of the application servers.

20. A method for distributing database content between an associated central database server and a plurality of associated application servers, the method comprising:

using a first archiving module of the associated central database server;

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

providing the staging database with a logical name;

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

,

associating the first content archive file with a version identifier;

using a second archiving module of the central database server, second archiving;

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

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

distributing the distribution archive file by the associated central database server to the plurality of associated application servers other than the central database server, the plurality of application servers each having an operating environment adapted to execute 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 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

,

distributing 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.

21. The method as set forth in claim 20, wherein the first archiving of at least some content includes:

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

22. The method as set forth in claim 20, wherein said first archiving of at least some content includes:

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

23. The method as set forth in claim 22, wherein said second archiving of the content archive file and supporting software as a distribution archive file includes:

second archiving the content archive file and supporting software as one of an enterprise application archive (EAR) file and a web archive (WAR) file.

24. The method as set forth in claim 20, further including:

repeating the first archiving of at least some content, the second archiving of the content archive file and supporting software, and the distributing to effect an updating of the application servers.