Techniques for managing functional service definitions in an SOA development lifecycle
First Claim
Patent Images
1. A method comprising:
- receiving, by a computer system, a definition of a business process including a set of business tasks, the business process being a functional representation of a Service Oriented Architecture application;
receiving, by the computer system, a definition of a service solution component for a business task in the set of business tasks, the service solution component being a functional representation of a software service that fulfills the business task;
storing, by the computer system, the definition of the business process and the definition of the service solution component in a shared data store;
generating, based on the definition of the business process, a user interface identifying the set of business tasks and a set of software services associated with the set of business tasks;
receiving, via the user interface, a selection of a software service in the set of software services;
implementing a harvester, the harvester configured to;
collect service artifact metadata related to the selection of the software, the service artifact metadata comprising an asset graph that identifies relationships between the set of software services; and
publish the service artifact metadata to the shared data store;
automatically generating, based on the selection of the software service and the service artifact metadata related to the selected software service, a deployment plan for deploying the Service Oriented Architecture application, the deployment plan comprising;
information that identifies the selected software service;
the service artifact metadata related to the selected software service; and
deployment information comprising a location for deploying the selected software service; and
deploying the Service Oriented Architecture application to the location in accordance with the deployment information and the deployment plan.
1 Assignment
0 Petitions
Accused Products
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.
87 Citations
22 Claims
-
1. A method comprising:
-
receiving, by a computer system, a definition of a business process including a set of business tasks, the business process being a functional representation of a Service Oriented Architecture application; receiving, by the computer system, a definition of a service solution component for a business task in the set of business tasks, the service solution component being a functional representation of a software service that fulfills the business task; storing, by the computer system, the definition of the business process and the definition of the service solution component in a shared data store; generating, based on the definition of the business process, a user interface identifying the set of business tasks and a set of software services associated with the set of business tasks; receiving, via the user interface, a selection of a software service in the set of software services; implementing a harvester, the harvester configured to; collect service artifact metadata related to the selection of the software, the service artifact metadata comprising an asset graph that identifies relationships between the set of software services; and publish the service artifact metadata to the shared data store; automatically generating, based on the selection of the software service and the service artifact metadata related to the selected software service, a deployment plan for deploying the Service Oriented Architecture application, the deployment plan comprising; information that identifies the selected software service; the service artifact metadata related to the selected software service; and deployment information comprising a location for deploying the selected software service; and deploying the Service Oriented Architecture application to the location in accordance with the deployment information and the deployment plan. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17)
-
-
18. A non-transitory computer-readable storage medium having stored thereon program code executable by a computer system, the program code comprising:
-
code that causes a computer system to receive a definition of a business process including a set of business tasks, the business process being a functional representation of a Service Oriented Architecture application; code that causes the computer system to receive a definition of a service solution component for a business task in the set of business tasks, the service solution component being a functional representation of a software service that fulfills the business task; code that causes the computer system to store the definition of the business process and the definition of the service solution component in a shared data store; code that causes the computer system to generate, based on the definition of the business process, a user interface identifying the set of business tasks and a set of software services associated with the set of business tasks; code that causes the computer system to receive, via the user interface, a selection of a software service in the set of software services; code that causes the computer system to implement a harvester, the harvester configured to; collect service artifact metadata related to the selection of the software, the service artifact metadata comprising an asset graph that identifies relationships between the set of software services; and publish the service artifact metadata to the shared data store; code that causes the computer system to automatically generate, based on the selection of the software service and the service artifact metadata related to the selected software service, a deployment plan for deploying the Service Oriented Architecture application, the deployment plan comprising; information that identifies the selected software service; the service artifact metadata related to the selected software service; and deployment information comprising a location for deploying the selected software service; and code that causes the computer system to deploy the Service Oriented Architecture application to the location in accordance with the deployment information and the deployment plan. - View Dependent Claims (19, 20)
-
-
21. A system comprising:
-
a memory storing a plurality of instructions; and a processor configured to access the memory, wherein the processor is further configured to execute the plurality of instructions to at least; receive a definition of a business process including a set of business tasks, the business process being a functional representation of a Service Oriented Architecture application; receive a definition of a service solution component for a business task in the set of business tasks, the service solution component being a functional representation of a software service that fulfills the business task; store the definition of the business process and the definition of the service solution component in a shared data store; generate, based on the definition of the business process, a user interface identifying the set of business tasks and a set of software services associated with the set of business tasks; receive, via the user interface, a selection of a software service in the set of software services; implement a harvester, the harvester configured to; collect service artifact metadata related to the selection of the software, the service artifact metadata comprising an asset graph that identifies relationships between the set of software services; and publish the service artifact metadata to the shared data store; automatically generate, based on the selection of the software service and the service artifact metadata related to the selected software service, a deployment plan for deploying the Service Oriented Architecture application, the deployment plan comprising; information that identifies the selected software service; the service artifact metadata related to the selected software service; and deployment information comprising a location for deploying the selected software service; and deploy the Service Oriented Architecture application to the location in accordance with the deployment information and the deployment plan. - View Dependent Claims (22)
-
Specification