Service-oriented architecture

• US 20070011126A1
• Filed: 03/21/2006
• Published: 01/11/2007
• Est. Priority Date: 03/21/2005
• Status: Abandoned Application

• Current Assignee: Primitive Logic, Inc. (Logic20/20 Inc.)
• Original Assignee: Primitive Logic, Inc. (Logic20/20 Inc.)
• Inventors: Robinson, Stewart, Conner, Peter
• Application Number:
  US11/388,624
• Publication Number:
  US 20070011126A1
• Time in Patent Office: Days
• US Class Current: 706/47
• CPC Class Codes: G06Q 10/00 Administration; Management
• CPC Class Codes: G06Q 50/10 Services
• CPC Class Codes: H04L 61/4541 Directories for service discovery
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]

Abstract

A Service-oriented architecture (SOA) and accompanying method. In one embodiment, the SOA includes one or more service requesters coupled to one or more service providers via a bus. The bus includes runtime-binding functionality to facilitate interaction between the one or more service requesters and the one or more service providers. A registry, which stores information pertaining to a service provided by the one or more service providers, communicates with one or more service providers and/or requesters and the bus. In a more specific embodiment, bus includes a Service-Integration Bus (SIB) that includes a Service-Factory (SF) module for facilitating implementing the runtime binding functionality and for selectively invoking the service. Functionality of the SOA is strategically organized into various tiers and layers, including a requester tier, a provider tier, a business-process services tier, an infrastructure-services tier, an SIB layer, a persistence layer, and so on, to optimize system reusability, adaptability, and other desirable properties. A service interface pattern is described whereby a change in service implementation does not require modification to the manner in which the service is invoked by a requester

Claims

1. A Service-Oriented Architecture (SOA) comprising:

a first tier, which includes a requester of a service;

a second tier, which includes a provider of a service; and

a first layer interfacing the first tier and the second tier, wherein the first layer includes

a registry adapted to store information pertaining to the service; and

a first module adapted to employ the information to facilitate interaction between the requester and the provider.

2. The SOA of claim 1, wherein the first module includes:

a Service Factory (SF).

3. The SOA of claim 2, wherein the information includes:

a definition of the service.

4. The SOA of claim 2, wherein the service factory includes:

runtime binding functionality for associating the service requested by the requester with a proxy, wherein the proxy is adapted to interface the requester with the provider, thereby obviating the need for the requester to be specifically modified to accept services directly from the provider.

5. The SOA of claim 2, wherein the service factory includes:

a service-invocation module for selectively invoking the service in response to a request issued by the requester.

6. The SOA of claim 2, wherein the requester includes:

a first legacy system.

7. The SOA of claim 6, further including:

a first business integration module interfacing the first legacy system with the registry.

8. The SOA of claim 2, wherein the provider includes:

a second legacy system.

9. The SOA of claim 8, further including:

a second business integration module interfacing the second legacy system with the registry.

10. The SOA of claim 2, wherein the first layer further includes:

a service router adapted to facilitate publishing the information to the registry.

11. The SOA of claim 2, wherein the proxy includes:

a programming object.

12. The SOA of claim 1, wherein the first layer includes:

a Service Integration Bus (SIB).

13. The SOA of claim 12, wherein the SIB includes:

a Service Gateway (SG).

14. The SOA of claim 13, wherein the SG includes:

one or more routines for performing runtime mediation for one or more requesters that include one or more consumers of a Web service, to enable the consumers to employ a service that is not a Web service.

15. The SOA of claim 14, wherein the SIB further includes:

a service-management module adapted to monitor and/or manage one or more service providers.

16. The SOA of claim 14, wherein the SIB further includes:

a first versioning module for selectively controlling which version of a service a specific service requester employs in response to a service request.

17. The SOA of claim 12, further including:

a business-process services tier.

18. The SOA of claim 17, wherein the first tier includes:

a consumer tier, and wherein the second tier includes a producer tier.

19. The SOA of claim 18, wherein the business-process services tier includes:

one or more modules adapted to manage communications between the consumer tier and the producer tier.

20. The SOA of claim 18, further including:

an infrastructure-services tier.

21. The SOA of claim 20, further including:

a persistence layer coupled between the consumer tier, the producer tier, and the infrastructure-services tier.

22. The SOA of claim 21, wherein the persistence layer includes:

versioning functionality.

23. The SOA of claim 21, wherein the persistence layer further includes:

a content management module, and wherein the content management module is further incorporated in the infrastructure-services tier.

24. The SOA of claim 23, wherein the persistence layer further includes:

a relationship-management module.

25. The SOA of claim 23, wherein the persistence layer further includes:

a data-integration module.

26. The SOA of claim 21, wherein the consumer tier includes:

a first business-integration layer or module adapted to facilitate interfacing one or more service requesters with one or more service providers.

27. The SOA of claim 26, wherein the one or more service requesters include:

one or more legacy applications.

28. The SOA of claim 21, wherein the producer tier includes:

a second business-integration layer or module adapted to facilitate interfacing one or more service providers with one or more service requesters.

29. The SOA of claim 28, wherein the one or more service providers include:

one or more legacy applications.

77. The method of claim 6, wherein the Service Integration Bus includes:

an open source implementation.

78. The method of claim 7, wherein the open source implementation includes:

Web Services Invocation Framework.

30. A Service-Oriented Architecture (SOA) comprising:

a first tier that includes a consumer;

a second tier that includes a producer; and

an interface between the consumer and the producer, wherein the interface includes;

a service-invocation tier and

a service interface in communication with the service-invocation tier.

31. The SOA of claim 31, wherein the interface includes a Service Integration Bus (SIB), which includes the service-invocation tier and the service interface.

32. The SOA of claim 31, further including:

a registry in communication with the service interface.

33. The SOA of claim 32, wherein the registry includes:

one or more definitions published by one or more producers, wherein the one or more producers are included in the second tier.

34. The SOA of claim 33, wherein the definitions include:

Web Services Definition Language (WSDL).

35. The SOA of claim 33, wherein the one or more definitions include:

one or more of the following types of definitions;

Web-Service (WS);

Enterprise Java Beans (EJB);

Java Messaging Services (JMS);

Java 2 Enterprise Edition (J2EE) for WS, EJB, JMS, and/or J2EE services, respectively.

36. The SOA of claim 31, wherein the interface further includes:

first means for determining information associated with a service offered by the producer and

second means for employing the information when the service is implemented to create an entity with which the consumer may communicate without directly communicating with the producer.

37. The SOA of claim 36, wherein the entity includes:

a proxy.

38. The SOA of claim 37 wherein the proxy is adapted for use by a service requester.

39. The SOA of claim 37, wherein the first means includes:

a service-invocation module in communication with a registry.

40. The SOA of claim 36, wherein the second means includes:

a Service Factory (SF).

41. The SOA of claim 40, wherein the SF includes:

a runtime binding module.

42. The SOA of claim 31, wherein the bus includes:

a Service-Integration Bus (SIB)

43. The SOA of claim 42, wherein the SIB includes:

the interface.

44. The SOA of claim 43, wherein the SIB includes:

a business-integration tier, wherein the business-integration tier interfaces one or more consumer legacy applications with one or more services, and/or interfaces one or more producer legacy applications with one or more consumers.

45. The SOA of claim 31, wherein the one or more consumers include:

zero or more consumer legacy applications.

46. The SOA of claim 31, wherein the one or more producers include:

zero or more producer legacy applications.

47. A Service-Oriented Architecture (SOA) comprising:

one or more service consumers;

one or more service producers;

a bus coupled between the one or more service consumers and the one or more service producers, wherein the bus includes

runtime binding functionality to facilitate interaction between the one or more service requesters and the one or more service providers; and

a registry in communication with the one or more service requesters and the bus.

48. The SOA of claim 47, wherein the one or more service producers communicate with the registry.

49. The SOA of claim 47, wherein the bus includes:

a Service-Integration Bus (SIB).

50. The SOA of claim 49, wherein the SIB includes:

a Service-Factory (SF) module.

51. The SOA of claim 49, wherein the SF module includes:

first means for selectively invoking a service provided by a service producer in response to a request from a service consumer.

52. The SOA of claim 51, wherein the first means further includes:

a runtime binding module in communication with a dynamic service-invocation module.

53. The SOA of claim 49, wherein the SIB further includes:

a Service Gateway (SG).

54. The SOA of claim 49, wherein the runtime binding functionality includes:

second means for associating requests from the one or more service consumers with one or more services provided by the one or more services producers.

55. The SOA of claim 47, wherein the one or more service consumers include:

a legacy consumer that includes a first legacy application.

56. The SOA of claim 55, further including:

a first business-integration layer or module coupled between the first legacy application and a service producer.

57. The SOA of claim 56, wherein the first business-integration layer or module is coupled between the first legacy application and the SIB, wherein the SIB is coupled between the legacy consumer and the service producer.

58. The SOA of claim 47, wherein the one or more service producers include:

a legacy producer that includes a second legacy application.

59. The SOA of claim 58, further including:

a second business-integration layer or module coupled between the second legacy application and the SIB.

60. A Service-oriented architecture (SOA) comprising:

a service requester;

a service provider;

a registry; and

a Service Integration Bus (SIB) interfacing the service requester, the service provider, and/or the registry, wherein the SIB includes a Service-Factory module.

61. The SOA of claim 60, wherein the SF module is in communication with the registry.

62. The SOA of claim 61, wherein the registry includes:

published information pertaining to services published by the service provider.

63. The SOA of claim 62, wherein the published information includes:

service definitions.

64. The SOA of claim 63, wherein the service definitions are specified via Web Services Design Language (WSDL).

65. The SOA of claim 61, wherein the SF includes:

a runtime-binding module capable of facilitating runtime binding of services with the published information.

66. The SOA of claim 65, wherein the runtime-binding module implements consumer-side runtime binding.

67. The SOA of claim 61, wherein the SF includes:

a service-invocation module.

68. The SOA of claim 61, wherein the SIB further includes:

a service gateway.

69. The SOA of claim 68, wherein the service gateway includes:

one or more routines for providing mediation to shield a consumer from one or more implementation details of a service.

70. A method for implement a Service-Oriented Architecture (SOA) comprising:

interfacing one or more service requesters with one or more service providers via a bus;

implementing runtime binding functionality in the bus to facilitate interaction between the one or more service requesters and the one or more service providers; and

using a registry to communicate information pertaining to the one or more services requesters and/or the one or more service providers to the bus.

71. A method for designing a software system, the method comprising:

defining one or more tiers, wherein a tier organizes one or more service requestors or service providers; and

defining one or more layers, wherein a layer acts as an interface for an exchange of information within the software system.

72. The method of claim 71, wherein a tier includes:

a presentation services tier.

73. The method of claim 71, wherein a tier includes:

a business process services tier.

74. The method of claim 71, wherein a tier includes:

a business services tier.

75. The method of claim 71, wherein a tier includes:

an infrastructure services tier.

76. The method of claim 71, wherein a layer includes:

a service integration bus.

79. The method of claim 71, wherein a layer includes:

a persistence layer.

80. The method of claim 71, wherein a layer includes:

a business registry.

81. A method for designing a software system, the method comprising:

defining four tiers, wherein a tier organizes one or more service requestors or service providers, wherein the tiers include infrastructure services, business services, business process services, and presentation services; and

defining four layers, wherein a layer acts as an interface for an exchange of information within the software system, wherein the layers include a persistence layer using enterprise object management, a service integration bus, a registry and a business integration layer.

82. A method for designing a software system, the method comprising:

defining four tiers, wherein a tier organizes one or more service requesters or service providers, wherein the tiers include infrastructure services, business services, business process services, and presentation services; and

defining two or more layers, wherein a layer acts as an interface for an exchange of information within the software system, wherein the layers include a persistence layer and a service integration bus.

83. A method for implementing a service for use by a requester in a service oriented architecture, the method comprising:

establishing an interface mapping, wherein the interface mapping translates a request from the requester and provides the request to the service.

84. The method of claim 83, wherein providing the request to the service includes:

defining a service facade derived from information provided by the service.

85. The method of claim 83, wherein the request from the requestor includes a data transfer object.

86. The method of claim 83, wherein the request is provided to the service by using a business object.

87. A method for handling a request for a particular service, wherein the request is made by a requester, the method comprising the following steps executed by a processor:

using an interface mapping to receive the request;

mapping the request to a service facade, wherein the service facade is associated with the particular service; and

using the particular service to provide the request.

88. The method of claim 87, wherein the interface mapping includes a service interface and a copy of the service facade.

89. The method of claim 87, wherein the requester obtains services from the particular service via a predetermined requesting procedure, the method further comprising:

determining that a service facade associated with the particular service has changed; and

modifying a copy of the service facade within the interface mapping so that the requester does not have to modify the predetermined requesting procedure in order to continue to obtain the particular service.

90. The system as substantially described herein.