Two-phase deployment framework

This application claims priority to U.S. Provisional Application No. 60/794,243 entitled “Two-phase Deployment Framework” filed Apr. 21, 2006, which is incorporated herein by reference.

Systems for complex applications can be run off of multiple server machines. Changes can be deployed to the multiple server machines at the same time so that each machine has the same setup. It is desired that the changes to the servers be done in a two-phase manner such that the changes can be rolled back if not all of the servers are able to commit the changes.

FIG. 1 is an example of a two-phase deployment framework of one embodiment of the present invention.

FIGS. 2A-2C illustrate a two-phase commit.

FIGS. 3A-3C illustrate a two-phase rollback.

FIG. 4 illustrates a two-phase deployment framework used with an application server.

FIGS. 5A-5C illustrates a two-segment two-phase deployment.

FIGS. 6A-6C illustrates a combined two-phase deployment.

FIG. 1 shows a two-phase deployment framework 102 . Components, such as configuration components 104 , application components 106 and service bus component 108 , can register with the two-phase deployment framework 102 to do two-phase deployment of different types of objects. The components can include listeners 110 , 112 and 114 at different machines 116 , 118 and 120 . The system can do a two-phase deployment including the different type of objects.

FIGS. 2A-2C show an example of a two-phase commit operation. In FIG. 2A , the framework 102 sends prepare messages to the machines 116 , 118 and 120 . The prepare message in this example concerns two types of objects, configuration and applications. The prepare message can include or be associated with change to the conformation and application. The listeners can determine whether the changes can be committed by the machine. For example, a config listener can check to see whether the match can set the new config. In FIG. 2A , an OK (ready) message is sent by all the machines. In FIG. 2C the two-phase deployment framework 102 sends a commit message to each of the machines and the changes are committed.

FIGS. 3A-3B show a rollback. In step 3 A, prepare messages are sent to each of the machines. In step 3 B, machine 120 responds with a NOT OK, or doesn't respond at all. In step 3 C, the two-phase deployment framework 102 sends rollback message to machines 116 , 118 and 120 .

The use of the two-phase deployment framework 102 also allows new types of objects to be added to the two-phase system by registering with the framework and adding a listener. The listener can do what is needed to operate in a two-phase manner with respect to that type of objects. The two-phase deployment framework 102 can include an interface 122 for allowing new components to register with the framework 102 .

FIG. 4 shows an example of the two-phase deployment framework used with an application server. Application server 402 on machine 404 can serve as the master. The components can include configuration for the application servers and application, to run on the application server. For example, in one case, the configuration is to be changed to accommodate a new application to run on the machines. The two-phase deployment framework, allows the configuration and the new application to be loaded as an atomic unit.

One embodiment of the present invention comprises a two-phase deployment of configuration for an application server 402 . The configuration is sent to each machine. Each machine sending a ready indication, such as an OK message, once the configuration is reached. The system can then commit the application server configuration change.

The new configuration can be transferred as an enterprise bean and maintained as a file at each machine.

The two-phase deployment framework can allow multiple types of objects to be used in the two-phase deployment. If instead of using a two-phase deployment framework, there were multiple two-phase systems, one for each type of objects, then one object could commit when the other has rolled back. FIGS. 5A-5C illustrate this problem of two-phase deployment systems that do not interact. This problem is avoided in the combined system of FIGS. 6A-6C that uses a two-phase deployment framework.

One embodiment may be implemented using a conventional general purpose or a specialized digital computer or microprocessor(s) programmed according to the teachings of the present disclosure, as will be apparent to those skilled in the computer art. Appropriate software coding can readily be prepared by skilled programmers based on the teachings of the present disclosure, as will be apparent to those skilled in the software art. The invention may also be implemented by the preparation of integrated circuits or by interconnecting an appropriate network of conventional component circuits, as will be readily apparent to those skilled in the art.

One embodiment includes a computer program product which is a storage medium (media) having instructions stored thereon/in which can be used to program a computer to perform any of the features presented herein. The storage medium can include, but is not limited to, any type of disk including floppy disks, optical discs, DVD, CD-ROMs, micro drive, and magneto-optical disks, ROMs, Rams, EPROM's, EPROM's, Drams, Rams, flash memory devices, magnetic or optical cards, Nano systems (including molecular memory ICs), or any type of media or device suitable for storing instructions and/or data stored on any one of the computer readable medium (media), the present invention includes software for controlling both the hardware of the general purpose/specialized computer or microprocessor, and for enabling the computer or microprocessor to interact with a human user or other mechanism utilizing the results of the present invention. Such software may include, but is not limited to, device drivers, operating systems, execution environments/containers, and user applications.

The foregoing description of preferred embodiments of the present invention has been provided for the purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations will be apparent to one of ordinary skill in the relevant arts. For example, steps performed in the embodiments of the invention disclosed can be performed in alternate orders, certain steps can be omitted, and additional steps can be added. The embodiments were chosen and described in order to best explain the principles of the invention and its practical application, thereby enabling others skilled in the art to understand the invention for various embodiments and with various modifications that are suited to the particular use contemplated. It is intended that the scope of the invention be defined by the claims and their equivalents.