Techniques for automated generation of deployment plans in an SOA development lifecycle

• US 8,677,309 B2
• Filed: 04/28/2010
• Issued: 03/18/2014
• Est. Priority Date: 12/29/2009
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Xie, Nan, Srinivasamoorthy, Arvind, Sankaran, Ravindran, Garimella, Annaji, Kola, Purushotham, Annadi, Thirupathi Reddy, Craig, Mark James Glenn
• Primary Examiner(s): Zhen, Wei
• Assistant Examiner(s): Wu, Junchun
• Application Number:
  US12/769,006
• Publication Number:
  US 20110161914A1
• Time in Patent Office: 1,420 Days
• Field of Search: 717/101, 717/174
• US Class Current: 717/101
• CPC Class Codes: G06F 8/10 Requirements analysis; Specification techniques
• CPC Class Codes: G06F 8/36 Software reuse
• CPC Class Codes: G06F 8/60 Software deployment

Abstract

A framework (referred to herein as Application Integration Architecture, or AIA) that formalizes and orchestrates activities in an SOA development lifecycle. In one set of embodiments, AIA can capture development-related information in a shared data store and cause the information to flow in an automated or semi-automated manner from one lifecycle phase to the next as the lifecycle progresses. This information flow can, in turn, facilitate automations at each lifecycle phase for the responsible stakeholders (e.g., solution architects, developers, installation developers, etc.), thereby enforcing SOA best practices, enhancing development productivity, and ensuring the quality of the final SOA deliverables.

Claims

1. A method comprising:

storing, by a computer system in a shared data store, a definition of a business process including a set of business tasks, the business process being a functional representation of a Service Oriented Architecture (SOA) Application, wherein one or more of the set of business tasks comprises business logic that corresponds to the business process, and wherein the storing is performed during a first lifecycle phase of the SOA application corresponding at least in part to defining of the SOA application at least partially by the set of business tasks;

collecting, by the computer system, metadata pertaining to a software service that fulfills a business task in the set of business tasks, wherein the collecting is performed during a second lifecycle phase of the SOA application subsequent to the first lifecycle phase, the second lifecycle phase of the SOA application corresponding at least in part to associating the metadata with the software service that fulfills the business task;

generating, by the computer system, a hierarchy for the business process, the set of business tasks, and a set of software services, the set of software services comprising the software service, wherein the hierarchy organizes the set of business tasks comprising business logic for the business process, and one or more software services of the set of software services for implementing each task of the set of business tasks;

generating, by the computer system, a user interface, the user interface presenting the hierarchy with user-selectable options to add and/or remove business tasks and/or software services with respect to the business process;

receiving, via the user interface, a selection corresponding to the user-selectable options to add and/or remove business tasks and/or software services with respect to the business process;

generating, by the computer system, a deployment plan for the SOA application based on the definition of the business process, the selection, and the metadata; and

generating a deployment properties file that specifies one or more locations for deploying the SOA application, wherein the SOA application is deployed based on the deployment plan and the deployment properties file;

wherein the deployment plan and the deployment properties file are configured to be interpreted by an installation driver that automatically deploys SOA application content based at least in part on location information of the deployment properties file.

2. The method of claim 1 wherein the generating is performed during a third lifecycle phase of the SOA application subsequent to the second lifecycle phase.

3. The method of claim 1 wherein collecting the metadata comprises associating the metadata with the business task and storing the metadata in the shared data store.

4. The method of claim 3 wherein generating the deployment plan comprises:

retrieving the definition of the business process from the shared data store;

retrieving the metadata pertaining to the software service from the shared data store;

generating a bill of materials based on the metadata; and

generating the deployment plan based on the bill of materials.

5. The method of claim 4 further comprising creating a deployable package for the SOA application.

6. The method of claim 5 wherein the deployable package includes the deployment plan and one or more artifacts of the software service.

7. The method of claim 6 wherein the deployable package further includes the definition of the business process and the metadata pertaining to the software service.

8. The method of claim 1 wherein the deployment plan is expressed in Extensible Markup Language (XML).

9. A computer-readable storage medium, which is tangible and non-transitory, having stored thereon program code executable by a computer system, the program code comprising:

code that causes the computer system to store, in a shared data store, a definition of a business process including a set of business tasks, the business process being a functional representation of a Service Oriented Architecture (SOA) Application, wherein one or more of the set of the business tasks comprises business logic that corresponds to the business process, and wherein the storing is performed during a first lifecycle phase of the SOA application corresponding at least in part to defining of the SOA application at least partially by the set of business tasks;

code that causes the computer system to collect metadata pertaining to a software service that fulfills a business task in the set of business tasks;

code that causes the computer system to generate a hierarchy for the business process, the set of business tasks, and a set of software services, the set of software services comprising the software service, wherein the hierarchy organizes the set of business tasks comprising business logic for the business process, and one or more software services of the set of software services for implementing each task of the set of business tasks;

code that causes the computer system to generate a user interface, the user interface presenting the hierarchy with user-selectable options to add and/or remove business tasks and/or software services with respect to the business process;

code that causes the computer system to process a selection received via the user interface and corresponding to the user-selectable options to add and/or remove business tasks and/or software services with respect to the business process;

code that causes the computer system to generate a deployment plan for the SOA application based on the definition of the business process, the selection, and the metadata; and

code that causes the computer system to generate a deployment properties file that specifies one or more locations for deploying the SOA application, wherein the SOA application is deployed based on the deployment plan and the deployment properties file;

wherein the deployment plan and the deployment properties file are configured to be interpreted by an installation driver that automatically deploys SOA application content based at least in part on location information of the deployment properties file.

10. The computer-readable storage medium of claim 9 wherein the collecting is performed during a second lifecycle phase of the SOA application subsequent to the first lifecycle phase, the second lifecycle phase of the SOA application corresponding at least in part to associating the metadata with the software service that fulfills the business task.

11. The computer-readable storage medium of claim 10 wherein the generating is performed during a third lifecycle phase of the SOA application subsequent to the second lifecycle phase.

12. A system comprising:

one or more repositories;

a processing component coupled to the one or more repositories, the processing component configured to execute instructions retained by at least one of the one or more repositories to;

store a definition of a business process including a set of business tasks, the business process being a functional representation of a Service Oriented Architecture (SOA) Application, wherein one or more of the set of business tasks comprises business logic that corresponds to the business process, and wherein the storing is performed during a first lifecycle phase of the SOA application corresponding at least in part to defining of the SOA application at least partially by the set of business tasks;

collect metadata pertaining to a software service that fulfills a business task in the set of business tasks;

generate a hierarchy for the business process, the set of business tasks, and a set of software services, the set of software services comprising the software service, wherein the hierarchy organizes the set of business tasks comprising business logic for the business process, and one or more software services of the set of software services for implementing each task of the set of business tasks;

generate a user interface, the user interface presenting the hierarchy with user-selectable options to add and/or remove business tasks and/or software services with respect to the business process;

process a selection received via the user interface and corresponding to the user-selectable options to add and/or remove business tasks and/or software services with respect to the business process;

generate a deployment plan for the SOA application based on the definition of the business process, the selection, and the metadata; and

generating a deployment properties file that specifies one or more locations for deploying the SOA application, wherein the SOA application is deployed based on the deployment plan and the deployment properties file;

wherein the deployment plan and the deployment properties file are configured to be interpreted by an installation driver that automatically deploys SOA application content based at least in part on location information of the deployment properties file.

13. The system of claim 12 wherein the collecting is performed during a second lifecycle phase of the SOA application subsequent to the first lifecycle phase, the second lifecycle phase of the SOA application corresponding at least in part to associating the metadata with the software service that fulfills the business task.

14. The system of claim 13 wherein the generating is performed during a third lifecycle phase of the SOA application subsequent to the second lifecycle phase.

15. The system of claim 12 wherein:

the collecting the metadata comprises associating the metadata with the business task and storing the metadata in the shared data store; and

the processing component is further configured to;

retrieve the definition of the business process from the shared data store;

retrieve the metadata pertaining to the software service from the shared data store;

generate a bill of materials based on the metadata; and

generate the deployment plan based on the bill of materials.