# US 2008/0189679 A1 · Method and system for creating, deploying, and utilizing a service > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2008/0189679 A1 - Document ID: US20080189679A1 - Status: Published application - Kind: A1 - Application number: 12/023,488 - Filed: 2008-01-31 - Published: 2008-08-07 - Earliest claimed: 2007-02-05 - Inventors: JARED RODRIGUEZ; Jack KENNEDY; Mike WEAVER - Web page: https://patentgrep.com/patent/US20080189679A1 ## CPC - G06F 8/34: Graphical or visual programming - G06F 8/60: Software deployment - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract A system and method of utilizing a service, comprising: designing the service in a visual modeling environment such that low level machine centric and/or platform dependent programming language is not used, the service capable of being implemented across an enterprise; and deploying the service in a plurality of technology infrastructures within the enterprise in a manner that interacts with enterprise software and/or other technology infrastructures by tailoring the service for each such infrastructure. ## Claims ### Claim 1 A method of utilizing a service, comprising: a. designing the service in a visual modeling environment such that low level machine centric and/or platform dependent programming language is not used, the service capable of being implemented across an enterprise; and b. deploying the service in a plurality of technology infrastructures in a manner that interacts with enterprise software and/or other technology infrastructures within the enterprise by tailoring the service for each such infrastructure. ### Claim 2 (depends on 1) The method of claim 1, wherein the capabilities of the service comprise: a. transaction control; b. fault tolerance; c. exception handling; d. logic execution e. logging integration; f. runtime registry publication; g. enterprise service bus publication; h. or any combination thereof. ### Claim 3 (depends on 1) The method of claim 1, wherein the service allows interaction of multiple supporting software platforms within atomicity, consistency, isolation, and durability (ACID) based transactions. ### Claim 4 (depends on 1) The method of claim 1, wherein the service is capable of being deployed in a fault tolerant environment. ### Claim 5 (depends on 1) The method of claim 1, wherein the service is capable of model-based exception handling. ### Claim 6 (depends on 1) The method of claim 1, wherein the service is capable of logging integration with the enterprise software and/or the other technology infrastructures within the enterprise. ### Claim 7 (depends on 1) The method of claim 1, wherein the service is capable of being published to runtime registries and/or enterprise service buses. ### Claim 8 (depends on 1) The method of claim 1, wherein the technical infrastructure of the deployment environment is capable of being extended and/or customized such that: a. any type of technical environments can be plugged into the deployment environment for use; and/or b. multiple technical infrastructures can be plugged into the deployment environment simultaneously for use. ### Claim 9 (depends on 1) The method of claim 1, wherein the modeling environment is capable of being extended and/or customized such that: a. new components can be plugged into the modeling environment to enable the creation and modification of new entities within the model; and/or b. new components can be plugged into the modeling environment to enable the generation, of source code by the modeling environment ### Claim 10 (depends on 1) The method of claim 1, wherein the service utilizes Rich Internet application capabilities. ### Claim 11 (depends on 10) The method of claim 10, wherein the Rich Internet application capabilities comprise rich dynamic user interfaces. ### Claim 12 (depends on 11) The method of claim 11, wherein the rich dynamic user interfaces are: synchronous and/or asynchronous. ### Claim 13 A method of utilizing a service, comprising: a. designing a service in a visual modeling environment such that low level machine centric and/or platform dependent programming language is not used, the service utilizing Rich Internet application capabilities; and b. deploying the service in a plurality of technology infrastructures in a manner that utilizes the Rich Internet application capabilities by tailoring the service for each such infrastructure. ### Claim 14 (depends on 13) The method of claim 13, wherein the Rich Internet application capabilities comprise rich dynamic user interfaces. ### Claim 15 (depends on 14) The method of claim 14, wherein the rich dynamic user interfaces are: a. synchronous; and/or b. asynchronous. ### Claim 16 (depends on 1) The method of claim 1, wherein only changed items in the service are deployed. ### Claim 17 (depends on 1) The method of claim 1, wherein previous deployment states from previously deployed services are capable of being restored. ### Claim 18 (depends on 1) The method of claim 1, wherein the service is validated to check for errors and/or issues in design and/or implementation. ### Claim 19 (depends on 1) The method of claim 1, wherein dependencies between various components in services are provided in the visual modeling environment. ### Claim 20 (depends on 1) The method of claim 1, wherein the service is tailored to the technology infrastructure where the service is executed. ### Claim 21 (depends on 1) The method of claim 1, wherein different versions of the service and/or a part of the service can be built, accessed, utilized, and/or edited by the user. ### Claim 22 (depends on 1) The method of claim 1, wherein the different users can build, utilize, access, and/or edit the service and/or a part of the service at the same time. ### Claim 23 (depends on 1) The method of claim 1, wherein the service and/or a part of the service can be combined and/or orchestrated with other services and/or parts of the service in the visual modeling environment. ### Claim 24 (depends on 1) The method of claim 1, wherein the designing comprises: a. creating a project model, the project model including a project name and the service; and b. creating a runtime framework representing a location and resources of a technology infrastructure which will receive a project created from the project model. ### Claim 25 (depends on 24) The method of claim 24, wherein the service includes implementation details, comprising: a. a data object; b. a data store; c. an exception definition; d. a logic model; e. a web model; or f. any combination thereof. ### Claim 26 (depends on 24) The method of claim 24, wherein the deploying comprises: a. building a project utilizing the project model; b. delivering the project to technology infrastructure utilizing the runtime framework. ### Claim 27 A system for utilizing a service, comprising a computer with an application for: a. designing the service in a visual modeling environment such that low level machine centric and/or platform dependent programming language is not used, the service capable of being implemented across an enterprise; and b. deploying the service in a plurality of technology infrastructures in a manner that interacts with enterprise software and/or other technology infrastructures within the enterprise by tailoring the service for each such infrastructure. ### Claim 28 (depends on 27) The system of claim 27, wherein the enterprise class capabilities comprise: a. transaction control; b. fault tolerance; c. exception handling; d. logging integration; e. runtime registry publication; or f. enterprise service bus publication; or g. logic execution; or h. any combination thereof. ### Claim 29 (depends on 27) The system of claim 27, wherein the service allows interaction of multiple supporting software platforms within atomicity, consistency, isolation, and durability (ACID) based transactions. ### Claim 30 (depends on 27) The system of claim 27, wherein the service is capable of being deployed in a fault tolerant environment. ### Claim 31 (depends on 27) The system of claim 27, wherein the service is capable of model-based exception handling. ### Claim 32 (depends on 27) The system of claim 27, wherein the service is capable of logging integration with the existing enterprise system and/or other technology infrastructures. ### Claim 33 (depends on 27) The system of claim 27, wherein the service is capable of being published to runtime registries and/or enterprise service buses. ### Claim 34 (depends on 27) The system of claim 27, wherein the modeling environment and the deployment are capable of being extended and/or customized. ### Claim 35 (depends on 27) The system of claim 27, wherein the service utilizes Rich Internet application capabilities. ### Claim 36 (depends on 35) The system of claim 35, wherein the Rich Internet application capabilities comprise rich dynamic user interfaces. ### Claim 37 (depends on 36) The system of claim 36, wherein the rich dynamic user interfaces are: a. synchronous; and/or b. asynchronous. ### Claim 38 A system of utilizing a service, comprising a computer with an application for: a. designing a service in a visual modeling environment such that low level machine centric and/or platform dependent programming language is not used, the service utilizing Rich Internet application capabilities; and b. deploying the service in a plurality of technology infrastructures in a manner that utilizes the Rich Internet application capabilities by tailoring the service for each such infrastructure. ### Claim 39 (depends on 38) The system of claim 38, wherein the Rich Internet application capabilities comprise rich dynamic user interfaces. ### Claim 40 (depends on 39) The system of claim 39, wherein the rich dynamic user interfaces are: a. synchronous; and/or b. asynchronous. ### Claim 41 (depends on 27) The system of claim 27, wherein the designing comprises: a. creating a project model utilizing the project model including a project name and the service; and b. creating a runtime framework representing a location and resources of a technology infrastructure which will receive the project model. ### Claim 42 (depends on 41) The system of claim 41, wherein the service includes implementation details, comprising: a. a data object; b. a data store; c. an exception definition; d. a logic model; e. a web model; or f. any combination thereof. ### Claim 43 (depends on 40) The system of claim 40, wherein the deploying comprises a. building a project utilizing the project model; b. delivering the project model to the technology infrastructure utilizing the runtime framework. ### Claim 44 (depends on 27) The system of claim 27, wherein only changed items in the service are deployed. ### Claim 45 (depends on 27) The system of claim 27, wherein previous deployment states from previously deployed services are capable of being restored. ### Claim 46 (depends on 27) The system of claim 27, wherein the service is validated to check for errors and/or issues in design or implementation. ### Claim 47 (depends on 27) The system of claim 27, wherein dependencies between various components in services are provided in the visual modeling environment. ### Claim 48 (depends on 27) The system of claim 27, wherein the service is tailored to the technology infrastructure where the service is executed. ### Claim 49 (depends on 27) The system of claim 27, wherein different versions of the service and/or a part of the service can be built, utilized, accessed, and/or edited by the user. ### Claim 50 (depends on 27) The system of claim 27, wherein the different users can build, utilize, access, and/or edit the service and/or a part of the service at the same time. ### Claim 51 (depends on 27) The system of claim 27, wherein the service and/or a part of the service can be combined and/or orchestrated with other services and/or parts of the service in the visual modeling environment. ### Claim 52 (depends on 21) The method of claim 21, wherein different parts of the service can be versioned independently of each other. ### Claim 53 (depends on 49) The system of claim 49, wherein different parts of the service can be versioned independently of each other.