Transaction model for deployment operations

• US 7,747,698 B2
• Filed: 05/25/2004
• Issued: 06/29/2010
• Est. Priority Date: 05/25/2004
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Kovachka-Dimitrova, Monika M., Angelova, Rumiana G.
• Primary Examiner(s): Mesfin; Yemane
• Assistant Examiner(s): Cloud; Joiya M
• Application Number:
  US10/854,729
• Publication Number:
  US 20050278274A1
• Time in Patent Office: 2,226 Days
• Field of Search: 707/1, 709/218
• US Class Current: 709/218
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57

Abstract

A system and method are described for performing deployment operations according to a transaction model. In one embodiment, a request to initiate a transaction to perform a deploy service operation is received. In response to the request, the transaction is initiated at a container. The transaction is then committed to a database if the transaction is successful. The successful transaction reflects the deploy service operation being completed at the container.

Claims

1. A method comprising:

executing a transaction including an operation to deploy a first deployment services and a second deployment services;

deploying the first deployment services at a first container corresponding to a first software application associated with a first programming engine, the first deployment services relating to deploying and running of the first software application at an application server of a primary computer system of a plurality of computer systems;

deploying the second deployment services at a second container corresponding to a second software application associated with a second programming engine, the second deployment services relating to deploying and running of the second software application at the application server of the primary computer system, the first deployment services being compatible with the first container and incompatible with the second container, the second deployment services being compatible with the second container and incompatible with the first container, the first container being incompatible with the second container due to the first programming engine being incompatible with the second programming engine;

establishing, via a deployment container interface, bi-directional communication between the first container and the second container such that the first container is capable of accessing the second deployment services at the second container, and the second container is capable of accessing the first deployment services at the first container;

determining whether a deployment error occurred during an execution of one of the deployment services;

in response to determining a deployment error did not occur, committing the execution of the one of the deployment services at the respective container; and

in response to determining a deployment error occurred, rolling back the execution of the transaction to a state previous to the operation.

2. The method of claim 1, wherein the first and second deployment services include a start operation, a stop operation, a remove operation, and an update operation.

3. The method of claim 1, further comprising sending a notification signal of the deployment of the first and second deployment services on the primary computer system to one or more secondary computer systems of the plurality of computer systems.

4. The method of claim 3, further comprising initiating a deployment transaction at one or more application servers associated with the one or more secondary computer systems allowing one or more software applications deployed at the one or more application servers to access the first and second deployment services at the primary computer system.

9. The method of claim 1, wherein the first container includes a Java 2 Enterprise Edition (J2EE) container, and wherein the second container includes an Advanced Business Application Programming (ABAP) container.

12. The method of claim 1, wherein the first programming engine includes a J2EE programming engine, and wherein the second programming engine includes an ABAP programming engine.

5. A system comprising:

a server computer system in a network of server computer systems, the server computer system including an application server to

execute a transaction including an operation to deploy a first deployment services and a second deployment services;

deploy the first deployment services transaction at a first container corresponding to a first software application associated with a first programming engine, the first deployment services relating to deploying and running of the first software application at an application server of a primary computer system of a plurality of computer systems;

deploy the second deployment services at a second container corresponding to a second software application associated with a second programming engine, the second deployment services relating to deploying and running of the second software application at the application server of the primary computer system, the first deployment services being compatible with the first container and incompatible with the second container, the second deployment services being compatible with the second container and incompatible with the first container, the first container being incompatible with the second container due to the first programming engine being incompatible with the second programming engine;

establish, via a deployment container interface, bi-directional communication between the first container and the second container such the first container is capable of accessing the second deployment services at the second container, and the second container is capable of accessing the first deployment services at the first container;

determine whether a deployment error occurred during an execution of one of the deployment services;

in response to determining a deployment error did not occur, commit the execution of the one of the deployment services at the respective container; and

in response to determining a deployment error occurred, roll back the execution of the transaction to a state previous to the operation.

10. The system of claim 5, wherein the first container includes a Java 2 Enterprise Edition (J2EE) container, and wherein the second container includes an Advanced Business Application Programming (ABAP) container.

13. The system of claim 5, wherein the first programming engine includes a J2EE programming engine, and wherein the second programming engine includes an ABAP programming engine.

6. A machine-readable storage medium comprising instructions which, when executed, cause a machine to:

execute a transaction including an operation to deploy a first deployment services and a second deployment services;

deploy the first deployment services at a first container corresponding to a first software application associated with a first programming engine, the first deployment services relating to deploying and running of the first software application at an application server of a primary computer system of a plurality of computer systems;

deploy the second deployment services at a second container corresponding to a second software application associated with a second programming engine, the second deployment services relating to deploying and running of the second software application at the application server of the primary computer system, the first deployment services being compatible with the first container and incompatible with the second container, the second deployment services being compatible the second container and incompatible with the first container, the first container being incompatible with the second container due to the first programming engine being incompatible with the second programming engine;

establish, via a deployment container interface, bi-directional communication between the first container and the second container such the first container is capable of accessing the second deployment services at the second container, and the second

container is capable of accessing the first deployment services at the first container;

determine whether a deployment error occurred during an execution of one of the deployment services;

in response to determining a deployment error did not occur, commit the execution of the one of the deployment services at the respective container; and

in response to determining a deployment error occurred, roll back the execution of the transaction to a state previous to the operation.

7. The machine-readable storage medium of claim 6, wherein the first and second deployment services include a start operation, a stop operation, a remove operation, and an update operation.

8. The machine-readable storage medium of claim 6, wherein the instructions when executed, further cause the machine to provide a notification signal of the deployment of the first and second deployment services on the primary computer system to one or more secondary computer systems of the plurality of computer systems.

11. The machine-readable storage medium of claim 6, wherein the first container includes a Java 2 Enterprise Edition (J2EE) container, and wherein the second container includes an Advanced Business Application Programming (ABAP) container.

14. The machine-readable medium of claim 6, wherein the first programming engine includes a J2EE programming engine, and wherein the second programming engine includes an ABAP programming engine.