Methods, systems, and software for providing service integration framework
A preferred embodiment of the subject invention comprises a system for implementing computer network services and applications, comprising a front-end component comprising one or more applications; a back-end component comprising one or more services; and an abstraction layer component operable to communicate with the front-end and back-end components. In another preferred embodiment, the subject invention comprises a system for linking applications and services, comprising: a vendor connectivity component; a business integration component; a security component; a utility component; and a back end connectivity component.
1. A non-transitory computer system for implementing computer network services and applications, comprising:
a front-end component comprising one or more applications; a back-end component comprising one or more services; and
an abstraction layer component operable to communicate with said front-end component and said back-end component, the abstraction layer comprising:
a first component operable to receive a first request from the one or more applications, identify a service of the one or more services in response to the first request, and return a description of the identified service to the one or more applications;
a second component operable to receive context information and a second request from the one or more applications, the context information identifying the one or more applications and a user of the one or more applications, the second request comprising the description of the identified service and representing a request to exchange business information between the one or more applications and the identified service,
a third component operable to determine whether the one or more applications and the user identified in the context information are authorized to access the identified service, and
a fourth component operable to facilitate, in response to the second request, an exchange of the business information between the one or more applications and the identified service if the one or more applications and the user are authorized.
2. A system as in claim 1 , wherein said abstraction layer component is operable to provide de-coupling of services provided by said back-end component.
3. A system as in claim 1 , wherein said abstraction layer component is operable to provide de-coupling of applications in said front-end component.
4. A system as in claim 1 , wherein said abstraction layer component is operable to provide single sign on for substantially all of said applications.
5. A system as in claim 1 , wherein said abstraction layer component is operable to provide built-in entitlements.
6. A system as in claim 1 , wherein said abstraction layer component is operable to provide system wide error reporting.
7. A system as in claim 1 , wherein the second component is a business integration component operable to provide call context information.
8. A system of claim 1 , wherein said first component is a vendor connectivity component operable to provide service location and activation capabilities using one or more standards interfaces.
9. A system as in claim 1 , wherein said third component is a security-component is operable to provide identity management that accepts a single sign on from the user and uses the single sign on to identify the user to each of the one or more services and each of the one or more applications.
10. A system as in claim 1 , wherein said abstraction layer component further comprises a utility component operable to enable auditing as system boundaries to manage service level agreements and method level metering.
11. A system as in claim 1 , wherein said back end connectivity component is operable to provide standardization of back end services such that each of the one or more software applications in the front-end component accesses each of the one or more services in the back-end component by communicating through the abstraction layer component.
12. A system as in claim 1 , wherein said abstraction layer component uses application templates to provide standardization of business services.
13. A system as in claim 1 , wherein said abstraction layer component is operable to provide one or more standardized interfaces to back end services.
14. A system as in claim 1 , wherein said abstraction layer component is operable to provide standardization of back end services.
15. A system as in claim 1 , wherein said abstraction layer component is operable to provide one or more standardized interfaces to external consumers and providers.
16. A system as in claim 1 , wherein said abstraction layer component comprise a single deployment platform.