Portable business process deployment model across different application servers

• US 8,954,952 B2
• Filed: 11/30/2007
• Issued: 02/10/2015
• Est. Priority Date: 11/30/2007
• Status: Active Grant

• Current Assignee: Red Hat, Inc. (International Business Machines Corporation)
• Original Assignee: Red Hat, Inc. (International Business Machines Corporation)
• Inventors: Guizar, Alejandro
• Primary Examiner(s): Chen, Xi D
• Application Number:
  US11/998,508
• Publication Number:
  US 20090144729A1
• Time in Patent Office: 2,629 Days
• Field of Search: None
• US Class Current: 717/174
• CPC Class Codes: G06F 8/60 Software deployment

Abstract

A method and apparatus for providing portability of a business process deployment model across different application servers. In one embodiment, a method may include determining which application server will be used for deploying a business process as a web application, and invoking an implementation framework of application server interfaces that corresponds to this application server. The method may further include utilizing the invoked implementation framework to obtain application server information needed for deploying the business process as a web application, and generating a web application package using the application server information.

Claims

1. A method comprising:

receiving, by a process definition tool of a business process management (BPM) system, a definition of a business process, wherein the definition uses a business process execution language (BPEL) and comprises a BPEL process definition document and a web services description language (WSDL) interface document;

storing, by the processing definition tool, the definition of the business process in a BPM database of the BPM system;

determining, by a deployment server of the BPM system and from the definition of the business process, an application server of a plurality of application servers to which the business process will be deployed as a web application;

invoking a first implementation framework of a plurality of implementation frameworks, wherein the first implementation framework is associated with the application server, and wherein each of the plurality of implementation frameworks is associated with a different application server type of the plurality of application servers;

obtaining, by a processing device, application server information for deploying the business process as the web application using the first implementation framework, wherein the first implementation framework accesses application server classes in a deployment layer of the application server to obtain the application server information, wherein the application server information is used by a J2EE web services deployment model to deploy the business process as a web application and comprises binding information for a web service produced by the business process, the binding information comprising a transport layer to be used for messages sent by the web service;

generating, by a BPM process engine of the BPM system, a web application package for the business process using the application server information; and

deploying the web application package to the application server.

2. The method of claim 1 wherein the plurality of application servers comprises a plurality of different application server types.

3. The method of claim 1 wherein the plurality of the application servers comprises different versions of an application server type.

4. The method of claim 1 wherein the application server information comprises a location of each web service produced by the business process.

5. The method of claim 4 wherein obtaining the application server information comprises:

sending a request for a web service location to a first application server class maintaining web service location information; and

sending a request for web service binding information to a second application server class maintaining web service binding information.

6. The method of claim 1 wherein the web service binding information further comprises at least one of a format of messages to be sent by a web service or a protocol to be used for sending the messages.

7. The method of claim 1 wherein

the definition of the business process specifies one or more partner links and one or more roles associated with the partner links.

8. The method of claim 7 wherein generating the web application package comprises:

building a port component for each partner link associated with a role; and

building a web archive for the web application using port components created for the partner links.

9. The method of claim 8 wherein building the port component comprises:

generating WSDL implementation documents using the definition of the business process, the WSDL implementation documents comprising an interface document, a SOAP binding document for each web service produced by the BPEL process, and a service element document; and

generating Java mapping artifacts using the WSDL implementation documents.

10. The method of claim 9 wherein the SOAP binding document and the service element document are generated using the application server information that includes a location of each web service and SOAP protocol details for each web service.

11. A system comprising:

a memory; and

a processing device, coupled to the memory, the processing device to;

receive, by a process definition tool of a business process management (BPM) system, a definition of a business process, wherein the definition uses a business process execution language (BPEL) and comprises a BPEL process definition document and a web services description language (WSDL) interface document;

store, by the processing definition tool, the definition of the business process in a BPM database of the BPM system;

determine, by a deployment server of the BPM system and from the definition of the business process, an application server of a plurality of application servers to which the business process will be deployed as a web application;

invoke a first implementation framework from a plurality of implementation frameworks, wherein the first implementation framework is associated with the application server, and wherein each of the plurality of implementation frameworks is associated with a different application server type of the plurality of application servers;

obtain application server information for deploying the business process as the web application using the first implementation framework, wherein the first implementation framework accesses application server classes in a deployment layer of the application server to obtain the application server information, wherein the application server information is used by a J2EE web services deployment model to deploy the business process as a web application and comprises binding information for a web service produced by the business process, the binding information comprising a transport layer to be used for messages sent by the web service;

generate, by a BPM process engine of the BPM system, a web application package for the business process using the application server information; and

deploy the web application package to the application server.

12. The system of claim 11 wherein the plurality of application servers comprises a plurality of different application server types.

13. The system of claim 11 wherein the application server information comprises a location of each web service produced by the business process.

14. The system of claim 13 wherein to obtain the application server information, the processing device further to:

send a request for a web service location to a first application server class maintaining web service location information; and

send a request for web service binding information to a second application server class maintaining web service binding information.

15. The system of claim 11 wherein the web service binding information further comprises at least one of a format of messages to be sent by a web service or a protocol to be used for sending the messages.

16. The system of claim 11 wherein

the definition of the business process specifies one or more partner links and one or more roles associated with the partner links.

17. The system of claim 16 wherein to generate the web application package, the processing device further to:

build a port component for each partner link associated with a role; and

build a web archive for the web application using port components created for the partner links.

18. The system of claim 17 wherein to build the port component, the processing device further to:

generate WSDL implementation documents using the definition of the business process, the WSDL implementation documents comprising an interface document, a SOAP binding document for each web service produced by the BPEL process, and a service element document, the SOAP binding document and the service element document being generated using the application server information that includes a location of each web service and SOAP protocol details for each web service; and

generate Java mapping artifacts using the WSDL implementation documents.

19. A non-transitory computer-readable storage medium including data that, when accessed by a processing device, cause the processing device to perform operations comprising:

receiving, by a process definition tool of a business process management (BPM) system, a definition of a business process, wherein the definition uses a business process execution language (BPEL) and comprises a BPEL process definition document and a web services description language (WSDL) interface document;

storing, by the processing definition tool, the definition of the business process in a BPM database of the BPM system;

determining, by a deployment server of the BPM system and from the definition of the business process, an application server of a plurality of application servers to which the business process will be deployed as a web application;

invoking a first implementation framework of a plurality of implementation frameworks, wherein the first implementation framework is associated with the application server, and wherein each of the plurality of implementation frameworks is associated with a different application server type of the plurality of application servers;

obtaining, by the processing device, application server information for deploying the business process as the web application using the first implementation framework, wherein the first implementation framework accesses application server classes in a deployment layer of the application server to obtain the application server information, wherein the application server information is used by a J2EE web services deployment model to deploy the business process as a web application and comprises binding information for a web service produced by the business process, the binding information comprising a transport layer to be used for messages sent by the web service;

generating, by a BPM process engine of the BPM system, a web application package for the business process using the application server information; and

deploying the web application package to the application server.

20. The non-transitory computer-readable storage medium of claim 19 wherein the plurality of application servers comprises a plurality of different application server types.

21. The non-transitory computer-readable storage medium of claim 19 wherein the application server information comprises a location of each web service produced by the business process.

22. The non-transitory computer-readable storage medium of claim 21 wherein obtaining the application server information comprises:

sending a request for a web service location to a first application server class maintaining web service location information; and

sending a request for web service binding information to a second application server class maintaining web service binding information.

23. The non-transitory computer-readable storage medium of claim 19 wherein the web service binding information further comprises at least one of a format of messages to be sent by a web service or a protocol to be used for sending the messages.