System and method for integration of web services

• US 8,069,435 B1
• Filed: 10/24/2003
• Issued: 11/29/2011
• Est. Priority Date: 08/18/2003
• Status: Active Grant

• Current Assignee: Oracle America, Inc. (Oracle Corporation)
• Original Assignee: Oracle America, Inc. (Oracle Corporation)
• Inventors: Lai, Ray Y
• Primary Examiner(s): Bullock, Jr.; Lewis
• Assistant Examiner(s): WANG, JUE S
• Application Number:
  US10/692,913
• Time in Patent Office: 2,958 Days
• Field of Search: 717/103, 717/100, 717/108, 717/109, 709/203, 709/223
• US Class Current: 717/106
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services

Abstract

System and method for integrating Web Services using a Web Services Structured Methodology are described. Embodiments of a Web Services Structured Methodology may be used to integrate Web Services in Enterprise and Cross-Enterprise business systems, and to integrate legacy systems (e.g. legacy mainframe systems) with Web Services in Enterprise and Cross-Enterprise business systems. Embodiments may provide an integrated Web Services architecture design mechanism that may be used for Enterprise and Cross-Enterprise integration of Web Services. Embodiments may be used for Legacy Mainframe Integration and Interoperability with Web Services.

Claims

1. A system for integrating Web Services with business systems, comprising:

a processor; and

a memory comprising program instructions, wherein the program instructions are executable by the processor to implement a Web Services architecture design service configured to generate integrated Web Service architectures for integrating Web Services with business systems, wherein, to generate an integrated Web Service architecture for integrating a specific Web Service with a specific business system, the program instructions are executable by the processor to;

generate the integrated Web Service architecture comprising a plurality of heterogeneous components of the specific business system in accordance with one or more Web Services integration design patterns for integrating Web Services with business systems, wherein, to generate the integrated Web Service architecture, the program instructions are executable by the processor to;

generate one or more Use Cases for the integrated Web Service in accordance with the one or more Web Services integration design patterns, wherein each Use Case models a particular business scenario for the integrated Web Service;

generate a high-level architecture for the integrated Web Service in accordance with the one or more Web Services integration design patterns, wherein the high-level architecture identifies two or more entities of the integrated Web Service and the relationships and interactions among the entities; and

generate a logical architecture for the integrated Web Service according to the business scenarios modeled by the one or more Use Cases and in accordance with the one or more Web Services integration design patterns, wherein the logical architecture identifies two or more logical components of the integrated Web Service and the relationship among the two or more logical components according to a plurality of integration tiers, and wherein the logical architecture comprises two or more layers; and

provide output indicating the generated integrated Web Service architecture for integrating the specific Web Service with the specific business system.

2. The system as recited in claim 1, wherein, to generate the integrated Web Service architecture, the program instructions are further executable by the processor to:

define the plurality of integration tiers, one or more basic components, and one or more Web Services technologies for integration; and

define how each of the plurality of integration tiers communicates with others of the plurality of integration tiers.

3. The system as recited in claim 1, wherein the plurality of integration tiers comprises a client tier, a presentation tier, a business tier, an integration tier, and a resources tier.

4. The system as recited in claim 1, wherein, to generate the integrated Web Service architecture, the program instructions are further executable by the processor to:

define one or more Web Services technologies for integration; and

define integration of one or more Enterprise Application Interface (EAI) products with the one or more Web Services technologies.

5. The system as recited in claim 1, wherein the business system is an Enterprise business system.

6. The system as recited in claim 1, wherein the business system is a Cross-Enterprise business system.

7. The system as recited in claim 1, wherein the plurality of heterogeneous components of the business system includes one or more legacy mainframe systems.

8. The system as recited in claim 1, wherein the integrated Web Service architecture comprises:

a service provider configured to provide one or more services on an integrated Web Service business system implemented according to the integrated Web Service architecture; and

one or more service requesters configured to access the one or more services from the service provider via a network.

9. The system as recited in claim 8, wherein the integrated Web Service business system is a Business-to-Consumer system, wherein the service provider is a business service provider, and wherein the service requester is an end user.

10. The system as recited in claim 8, wherein the integrated Web Service business system is a Business-to-Business system, wherein the service provider is a business service provider, and wherein the service requester is a business server.

11. The system as recited in claim 1, wherein the Web Services integration design patterns include one or more Mainframe integration and interoperability design patterns.

12. The system as recited in claim 11, wherein the Mainframe integration and interoperability design patterns include one of a Synchronous Mainframe Web Services design pattern and an Asynchronous Mainframe Web Services design pattern.

13. The system as recited in claim 1, wherein the Web Services integration design patterns include one or more of:

an Application-to-Application design pattern;

a Standard Build design pattern;

a Hub-Spoke Replication design pattern;

a Federated Replication design pattern;

a Multi-Step Application integration design pattern; and

a Data Exchange design pattern.

14. The system as recited in claim 1, wherein the Web Services integration design patterns include one of a Closed Process integration design pattern and an Open Process integration design pattern.

15. The system as recited in claim 14, wherein the Web Services integration design patterns include one of a Service Consolidation-Broker integration design pattern and a Reverse Auction-Broker integration design pattern.

16. The system as recited in claim 1, wherein the two or more layers comprise two or more of:

a network layer configured to serve as an underlying network for integrated Web Services implemented according to the integrated Web Service architecture;

a transport layer for delivering messages between components of the integrated Web Services;

a service description language layer configured to describe service type and functionality of the integrated Web Services;

a transaction routing layer configured to route messages on the transport layer;

a service discovery layer configured to search for and locate the integrated Web Services;

a service negotiation layer configured to negotiate exchanges between service requesters and service providers implemented according to the integrated Web Service architecture;

a management layer configured for provisioning of the integrated Web Services and for monitoring and administration of the integrated Web Services;

a Quality of Service layer configured to provide reliability, scalability, and availability for the integrated Web Services;

a security layer configured to provide authentication, entitlement, and non-repudiation security on the transport layer; and

an Open Standards layer.

17. A system for generating integrated Web Service architectures, comprising:

a processor; and

a memory comprising program instructions, wherein the program instructions are executable by the processor to implement a Web Services architecture design service configured to generate integrated Web Service architectures for implementing integrated Web Service business systems, wherein, to generate an integrated Web Service architecture for implementing a specific integrated Web Service business system, the program instructions are executable by the processor to;

identify one or more logical components of the integrated Web Service architecture according to one or more use case requirements for the specific integrated Web Service business system and in accordance with one or more Web Services integration design patterns, and wherein each use case requirement specifies a particular business scenario for the integrated Web Service business system;

translate the one or more use case requirements for the specific integrated Web Service business system and one or more technical constraints for the specific integrated Web Service business system to determine a plurality of Web Service components for the integrated Web Service architecture, wherein the Web Service components include software components;

categorize the Web Service components into two or more related groups according to a Web Services architecture integration framework;

define a plurality of integration tiers for the integrated Web Service architecture and one or more Web Services technologies for the integrated Web Service architecture according to the Web Services architecture integration framework;

define how each of the plurality of integration tiers communicates with others of the plurality of integration tiers in the integrated Web Service architecture according to the Web Services architecture integration framework;

organize the groups of Web Service components according to the plurality of integration tiers and two or more layers of the integrated Web Service architecture;

apply one or more design patterns to the integrated Web Service architecture, wherein the one or more design patterns include one or more Web Services integration design patterns for integrating Web Services with business systems; and

provide output indicating the generated integrated Web Service architecture for implementing the specific integrated Web Service business system.

18. The system as recited in claim 17, wherein the integrated Web Service architecture comprises:

a service provider configured to provide one or more services on the integrated Web Service business system implemented according to the integrated Web Service architecture; and

one or more service requesters configured to access the one or more services from the service provider via a network.

19. The system as recited in claim 18, wherein the integrated Web Service business system is a Business-to-Consumer system, wherein the service provider is a business service provider, and wherein the service requester is an end user.

20. The system as recited in claim 18, wherein the integrated Web Service business system is a Business-to-Business system, wherein the service provider is a business service provider, and wherein the service requester is a business server.

21. The system as recited in claim 17, wherein the two or more layers of the integrated Web Service architecture comprise two or more of:

a network layer configured to serve as an underlying network for Web Services implemented according to the integrated Web Service architecture;

a transport layer for delivering messages between components of the integrated Web Service architecture;

a service description language layer configured to describe service type and functionality of the integrated Web Service architecture;

a transaction routing layer configured to route messages on the transport layer;

a service discovery layer configured to search for and locate services in the integrated Web Service architecture;

a service negotiation layer configured to negotiate exchanges between service requesters and service providers implemented according to the integrated Web Service architecture;

a management layer configured for provisioning of the integrated Web Service architecture and for monitoring and administration of the integrated Web Service architecture;

a Quality of Service layer configured to provide reliability, scalability, and availability for the integrated Web Service architecture;

a security layer configured to provide authentication, entitlement, and non-repudiation security on the transport layer; and

an Open Standards layer.

22. The system as recited in claim 17, wherein the specific integrated Web Service business system is an Enterprise integrated Web Service.

23. The system as recited in claim 17, wherein the specific integrated Web Service business system is a Cross-Enterprise integrated Web Service.

24. The system as recited in claim 17, wherein the plurality of Web Service components of the integrated Web Service architecture include one or more legacy mainframe systems.

25. The system as recited in claim 17, wherein the program instructions are further executable by the processor to define integration of one or more Enterprise Application Interface (EAI) products with the one or more Web Services technologies.

26. The system as recited in claim 17, wherein the plurality of integration tiers comprises a client tier, a presentation tier, a business tier, an integration tier, and a resources tier.

27. The system as recited in claim 17, wherein the one or more Web Services integration design patterns include one or more of:

an Application-to-Application design pattern;

a Standard Build design pattern;

a Hub-Spoke Replication design pattern;

a Federated Replication design pattern;

a Multi-Step Application integration design pattern; and

a Data Exchange design pattern.

28. The system as recited in claim 17, wherein the design patterns include one of a Closed Process integration design pattern and an Open Process integration design pattern.

29. The system as recited in claim 17, wherein the design patterns include one of a Synchronous Mainframe Web Services design pattern and an Asynchronous Mainframe Web Services design pattern.

30. An integrated Web Services business system, comprising:

one or more computers configured to implement;

a plurality of heterogeneous business components of the integrated Web Services business system;

a plurality of integration tiers of the integrated Web Services business system, wherein the plurality of integration tiers comprises a client tier, a presentation tier, a business tier, an integration tier, and a resources tier; and

an integrated Web Service comprising one or more Web Services technologies for the integrated Web Services business system, wherein the integrated Web Service is configured to provide interoperability among the plurality of heterogeneous business components via a network;

wherein the integrated Web Services business system is configured and implemented according to an integrated Web Service architecture generated by a computer-implemented integrated Web Services architecture design service according to a structured integration methodology for designing and generating integrated Web Service architectures for integrating Web Services technologies with business systems comprising heterogeneous components such that;

a logical architecture for the integrated Web Service is defined according to business scenarios modeled by one or more Use Cases defined for the integrated Web Service, wherein each Use Case models a particular business scenario for the integrated Web Service, and wherein the logical architecture comprises two or more layers;

the plurality of heterogeneous business components are organized according to the plurality of integration tiers and the two or more layers of the logical architecture for the integrated Web Service; and

one or more design patterns including one or more Web Services integration design patterns for integrating Web Services with business systems are applied to the integrated Web Service architecture, wherein each design pattern models a particular structure that is applicable to the integrated Web Service.

31. The system as recited in claim 30, wherein the integrated Web Services business system further comprises one or more Enterprise Application Interface (EAI) products integrated with the one or more Web Services technologies.

32. The system as recited in claim 30, wherein the integrated Web Services business system is an Enterprise business system.

33. The system as recited in claim 30, wherein the integrated Web Services business system is a Cross-Enterprise business system.

34. The system as recited in claim 30, wherein the plurality of heterogeneous business components includes one or more legacy mainframe systems.

35. The system as recited in claim 30, wherein the integrated Web Services business system further comprises:

a service provider configured to provide one or more services on the integrated Web Services business system; and

one or more service requesters configured to access the one or more services from the service provider via the network.

36. The system as recited in claim 35, wherein the integrated Web Service business system is a Business-to-Consumer system, wherein the service provider is a business service provider, and wherein the service requester is an end user.

37. The system as recited in claim 35, wherein the integrated Web Service business system is a Business-to-Business system, wherein the service provider is a business service provider, and wherein the service requester is a business server.

38. The system as recited in claim 30, wherein the design patterns include one of a Synchronous Mainframe Web Services design pattern and an Asynchronous Mainframe Web Services design pattern.

39. The system as recited in claim 30, wherein the design patterns include one or more of:

an Application-to-Application design pattern;

a Standard Build design pattern;

a Hub-Spoke Replication design pattern;

a Federated Replication design pattern;

a Multi-Step Application integration design pattern;

a Data Exchange design pattern;

a Closed Process integration design pattern;

an Open Process integration design pattern;

a Service Consolidation-Broker integration design pattern; and

a Reverse Auction-Broker integration design pattern.

40. A system for integrating Web Services with business systems, comprising:

computer-implemented means for obtaining one or more use case requirements, wherein each use case requirement specifies a particular business scenario for an integrated Web Service, and wherein at least one of the one or more use case requirements is defined in accordance with at least one Web Services integration design pattern;

computer-implemented means for generating an integrated Web Services architecture in accordance with the one or more use case requirements and in accordance with one or more design patterns including one or more Web Services integration design patterns, wherein the integrated Web Services architecture integrates a Web Service with a business system comprising a plurality of heterogeneous components;

computer-implemented means for applying a Web Services structured methodology and the one or more design patterns to the integrated Web Service architecture to identify a plurality of integrated Web Service components including one or more of the business system components and to organize the integrated Web Service components according to the integrated Web Service architecture, wherein the plurality of integrated Web Service components are organized according to two or more integration tiers and two or more layers of the integrated Web Service architecture;

wherein said computer-implemented means for applying a Web Services structured methodology and the one or more design patterns to the generated integrated Web Service architecture comprises means for providing integration and interoperability with the integrated Web Service architecture for existing business functionality of the business system;

computer-implemented means for providing output indicating the generated integrated Web Service architecture for integrating the Web Service with the business system; and

means for implementing the integrated Web Service comprising the plurality of integrated Web Service components organized according to the integrated Web Service architecture.

41. The system as recited in claim 40, wherein the business system is one of an Enterprise business system and a Cross-Enterprise business system.

42. The system as recited in claim 40, wherein the plurality of integrated Web Service components includes one or more legacy mainframe systems of the business system.

43. A method for integrating Web Services with business systems, comprising:

generating, by an integrated Web Services architecture design mechanism implemented on one or more computers and in accordance with one or more Web Services integration design patterns for integrating Web Services with business systems, an integrated Web Service architecture for integrating a specific Web Service with a specific business system, wherein the integrated Web Service architecture comprises a plurality of heterogeneous components of the specific business system, wherein said generating an integrated Web Service architecture comprises;

generating one or more Use Cases for the integrated Web Service in accordance with the one or more Web Services integration design patterns, wherein each Use Case models a particular business scenario for the integrated Web Service;

generating a high-level architecture for the integrated Web Service in accordance with the one or more Web Services integration design patterns, wherein the high-level architecture identifies entities of the integrated Web Service and the relationships and interactions among the entities; and

generating a logical architecture for the integrated Web Service according to the business scenarios modeled by the one or more Use Cases and in accordance with the one or more Web Services integration design patterns, wherein the logical architecture identifies two or more logical components of the integrated Web Service and the relationship among the two or more logical components according to a plurality of integration tiers, and wherein the logical architecture comprises two or more layers;

providing output indicating the generated integrated Web Service architecture for integrating the specific Web Service with the specific business system; and

implementing the specific Web Service integrated with the specific business system according to the integrated Web Service architecture.

44. The method as recited in claim 43, wherein said generating an integrated Web Service architecture comprises:

defining the plurality of integration tiers, one or more basic components, and one or more Web Services technologies for integration; and

defining how each of the plurality of integration tiers communicates with others of the plurality of integration tiers.

45. The method as recited in claim 43, wherein the plurality of integration tiers comprises a client tier, a presentation tier, a business tier, an integration tier, and a resources tier.

46. The method as recited in claim 43, wherein said generating an integrated Web Service architecture further comprises:

defining one or more Web Services technologies for integration; and

defining integration of one or more Enterprise Application Interface (EAI) products with the one or more Web Services technologies.

47. The method as recited in claim 43, wherein the business system is an Enterprise business system.

48. The method as recited in claim 43, wherein the business system is a Cross-Enterprise business system.

49. The method as recited in claim 43, wherein the plurality of heterogeneous components of the business system includes one or more legacy mainframe systems.

50. The method as recited in claim 43, wherein the integrated Web Service architecture comprises:

a service provider configured to provide one or more services on an integrated Web Service business system implemented according to the integrated Web Service architecture; and

one or more service requesters configured to access the one or more services from the service provider via a network.

51. The method as recited in claim 50, wherein the integrated Web Service business system is a Business-to-Consumer system, wherein the service provider is a business service provider, and wherein the service requester is an end user.

52. The method as recited in claim 50, wherein the integrated Web Service business system is a Business-to-Business system, wherein the service provider is a business service provider, and wherein the service requester is a business server.

53. The method as recited in claim 43, wherein the Web Services integration design patterns include one of a Synchronous Mainframe Web Services design pattern and an Asynchronous Mainframe Web Services design pattern.

54. The method as recited in claim 43, wherein the Web Services integration design patterns include one or more of:

an Application-to-Application design pattern;

a Standard Build design pattern;

a Hub-Spoke Replication design pattern;

a Federated Replication design pattern;

a Multi-Step Application integration design pattern;

a Data Exchange design pattern;

a Closed Process integration design pattern;

an Open Process integration design pattern;

a Service Consolidation-Broker integration design pattern; and

a Reverse Auction-Broker integration design pattern.

55. The method as recited in claim 43, wherein the two or more layers comprise two or more of:

a network layer configured to serve as an underlying network for integrated Web Services implemented according to the integrated Web Service architecture;

a transport layer for delivering messages between components of the integrated Web Services;

a service description language layer configured to describe service type and functionality of the integrated Web Services;

a transaction routing layer configured to route messages on the transport layer;

a service discovery layer configured to search for and locate the integrated Web Services;

a service negotiation layer configured to negotiate exchanges between service requesters and service providers implemented according to the integrated Web Service architecture;

a management layer configured for provisioning of the integrated Web Services and for monitoring and administration of the integrated Web Services;

a Quality of Service layer configured to provide reliability, scalability, and availability for the integrated Web Services;

a security layer configured to provide authentication, entitlement, and non-repudiation security on the transport layer; and

an Open Standards layer.

56. A method for generating integrated Web Service architectures, comprising:

identifying, by an integrated Web Services architecture design mechanism implemented on one or more computers, one or more logical components of an integrated Web Service architecture for implementing a specific integrated Web Service business system according to one or more use case requirements for the specific integrated Web Service business system and in accordance with one or more Web Services integration design patterns, and wherein each use case requirement specifies a particular business scenario for the integrated Web Service business system;

translating, by the integrated Web Services architecture design mechanism, the one or more use case requirements for the specific integrated Web Service business system and one or more technical constraints for the specific integrated Web Service business system to determine a plurality of Web Service components for the integrated Web Service architecture, wherein the Web Service components include software components;

categorizing, by the integrated Web Services architecture design mechanism, the Web Service components into two or more related groups according to a Web Services architecture integration framework;

defining, by the integrated Web Services architecture design mechanism, a plurality of integration tiers for the integrated Web Service architecture and one or more Web Services technologies for the integrated Web Service architecture according to a Web Services architecture integration framework;

defining, by the integrated Web Services architecture design mechanism, how each of the plurality of integration tiers communicates with others of the plurality of integration tiers in the integrated Web Service architecture according to the Web Services architecture integration framework;

organizing, by the integrated Web Services architecture design mechanism, the groups of Web Service components according to the plurality of integration tiers and two or more layers of the integrated Web Service architecture;

applying, by the integrated Web Services architecture design mechanism, one or more design patterns to the integrated Web Service architecture, wherein the one or more design patterns include one or more Web Services integration design patterns for integrating Web Services with business systems; and

providing, by the integrated Web Services architecture design mechanism, output indicating the generated integrated Web Service architecture for implementing the specific integrated Web Service business system.

57. The method as recited in claim 56, wherein the integrated Web Service architecture comprises:

a service provider configured to provide one or more services on the integrated Web Service business system implemented according to the integrated Web Service architecture; and

one or more service requesters configured to access the one or more services from the service provider via a network.

58. The method as recited in claim 57, wherein the integrated Web Service business system is a Business-to-Consumer system, wherein the service provider is a business service provider, and wherein the service requester is an end user.

59. The method as recited in claim 57, wherein the integrated Web Service business system is a Business-to-Business system, wherein the service provider is a business service provider, and wherein the service requester is a business server.

60. The method as recited in claim 56, wherein the two or more layers of the integrated Web Service architecture comprise two or more of:

a network layer configured to serve as an underlying network for Web Services implemented according to the integrated Web Service architecture;

a transport layer for delivering messages between components of the integrated Web Service architecture;

a service description language layer configured to describe service type and functionality of the integrated Web Service architecture;

a transaction routing layer configured to route messages on the transport layer;

a service discovery layer configured to search for and locate services in the integrated Web Service architecture;

a service negotiation layer configured to negotiate exchanges between service requesters and service providers implemented according to the integrated Web Service architecture;

a management layer configured for provisioning of the integrated Web Service architecture and for monitoring and administration of the integrated Web Service architecture;

a Quality of Service layer configured to provide reliability, scalability, and availability for the integrated Web Service architecture;

a security layer configured to provide authentication, entitlement, and non-repudiation security on the transport layer; and

an Open Standards layer.

61. The method as recited in claim 56, wherein the specific integrated Web Service business system is an Enterprise integrated Web Service.

62. The method as recited in claim 56, wherein the specific integrated Web Service business system is a Cross-Enterprise integrated Web Service.

63. The method as recited in claim 56, wherein the plurality of Web Service components of the integrated Web Service architecture include one or more legacy mainframe systems.

64. The method as recited in claim 56, further comprising defining integration of one or more Enterprise Application Interface (EAI) products with the one or more Web Services technologies.

65. The method as recited in claim 56, wherein the plurality of integration tiers comprises a client tier, a presentation tier, a business tier, an integration tier, and a resources tier.

66. The method as recited in claim 56, wherein the one or more Web Services integration design patterns include one or more of:

an Application-to-Application design pattern;

a Standard Build design pattern;

a Hub-Spoke Replication design pattern;

a Federated Replication design pattern;

a Multi-Step Application integration design pattern;

a Data Exchange design pattern;

a Closed Process integration design pattern;

an Open Process integration design pattern;

a Service Consolidation-Broker integration design pattern; and

a Reverse Auction-Broker integration design pattern.

67. A computer-accessible storage medium storing program instructions, wherein the program instructions are computer-executable to implement:

generating, in accordance with one or more Web Services integration design patterns for integrating Web Services with business systems, an integrated Web Service architecture for integrating a specific Web Service with a specific business system, wherein the integrated Web Service architecture comprises a plurality of heterogeneous components of the specific business system, wherein said generating an integrated Web Service architecture comprises;

generating one or more Use Cases for the integrated Web Service in accordance with the one or more Web Services integration design patterns, wherein each Use Case models a particular business scenario for the integrated Web Service;

generating a high-level architecture for the integrated Web Service in accordance with the one or more Web Services integration design patterns, wherein the high-level architecture identifies entities of the integrated Web Service and the relationships and interactions among the entities; and

generating a logical architecture for the integrated Web Service according to the business scenarios modeled by the one or more Use Cases and in accordance with the one or more Web Services integration design patterns, wherein the logical architecture identifies two or more logical components of the integrated Web Service and the relationship among the two or more logical components according to a plurality of integration tiers, and wherein the logical architecture comprises two or more layers; and

providing output indicating the generated integrated Web Service architecture for integrating the Web Service with the business system.

68. The computer-accessible storage medium as recited in claim 67, wherein, in said generating an integrated Web Service architecture, the program instructions are further computer-executable to implement:

defining the plurality of integration tiers, one or more basic components, and one or more Web Services technologies for integration; and

defining how each of the plurality of integration tiers communicates with others of the plurality of integration tiers.

69. The computer-accessible storage medium as recited in claim 67, wherein the plurality of integration tiers comprises a client tier, a presentation tier, a business tier, an integration tier, and a resources tier.

70. The computer-accessible storage medium as recited in claim 67, wherein, in said generating an integrated Web Service architecture, the program instructions are further computer-executable to implement:

defining one or more Web Services technologies for integration; and

defining integration of one or more Enterprise Application Interface (EAI) products with the one or more Web Services technologies.

71. The computer-accessible storage medium as recited in claim 67, wherein the business system is an Enterprise business system.

72. The computer-accessible storage medium as recited in claim 67, wherein the business system is a Cross-Enterprise business system.

73. The computer-accessible storage medium as recited in claim 67, wherein the plurality of heterogeneous components of the business system includes one or more legacy mainframe systems.

74. The computer-accessible storage medium as recited in claim 67, wherein the integrated Web Service architecture comprises:

a service provider configured to provide one or more services on an integrated Web Service business system implemented according to the integrated Web Service architecture; and

one or more service requesters configured to access the one or more services from the service provider via a network.

75. The computer-accessible storage medium as recited in claim 74, wherein the integrated Web Service business system is a Business-to-Consumer system, wherein the service provider is a business service provider, and wherein the service requester is an end user.

76. The computer-accessible storage medium as recited in claim 74, wherein the integrated Web Service business system is a Business-to-Business system, wherein the service provider is a business service provider, and wherein the service requester is a business server.

77. The computer-accessible storage medium as recited in claim 67, wherein the Web Services integration design patterns include one of a Synchronous Mainframe Web Services design pattern and an Asynchronous Mainframe Web Services design pattern.

78. The computer-accessible storage medium as recited in claim 67, wherein the Web Services integration design patterns include one or more of:

an Application-to-Application design pattern;

a Standard Build design pattern;

a Hub-Spoke Replication design pattern;

a Federated Replication design pattern;

a Multi-Step Application integration design pattern;

a Data Exchange design pattern;

a Closed Process integration design pattern;

an Open Process integration design pattern;

a Service Consolidation-Broker integration design pattern; and

a Reverse Auction-Broker integration design pattern.

79. The computer-accessible storage medium as recited in claim 67, wherein the two or more layers comprise two or more of:

a network layer configured to serve as an underlying network for integrated Web Services implemented according to the integrated Web Service architecture;

a transport layer for delivering messages between components of the integrated Web Services;

a service description language layer configured to describe service type and functionality of the integrated Web Services;

a transaction routing layer configured to route messages on the transport layer;

a service discovery layer configured to search for and locate the integrated Web Services;

a service negotiation layer configured to negotiate exchanges between service requesters and service providers implemented according to the integrated Web Service architecture;

a management layer configured for provisioning of the integrated Web Services and for monitoring and administration of the integrated Web Services;

a Quality of Service layer configured to provide reliability, scalability, and availability for the integrated Web Services;

a security layer configured to provide authentication, entitlement, and non-repudiation security on the transport layer; and

an Open Standards layer.

80. A computer-accessible storage medium storing program instructions, wherein the program instructions are computer-executable to implement:

identifying one or more logical components of an integrated Web Service architecture for implementing a specific integrated Web Service business system according to one or more use case requirements for the specific integrated Web Service business system and in accordance with one or more Web Services integration design patterns, and wherein each use case requirement specifies a particular business scenario for the integrated Web Service business system;

translating the one or more use case requirements for the specific integrated Web Service business system and one or more technical constraints for the specific integrated Web Service business system to determine a plurality of Web Service components for the integrated Web Service architecture, wherein the Web Service components include software components;

categorizing the Web Service components into two or more related groups according to a Web Services architecture integration framework;

defining a plurality of integration tiers for the integrated Web Service architecture and one or more Web Services technologies for the integrated Web Service architecture according to a Web Services architecture integration framework;

defining how each of the plurality of integration tiers communicates with others of the plurality of integration tiers in the integrated Web Service architecture according to the Web Services architecture integration framework;

organizing the groups of Web Service components according to the plurality of integration tiers and two or more layers of the integrated Web Service architecture; and

applying one or more design patterns to the integrated Web Service architecture, wherein the one or more design patterns include one or more Web Services integration design patterns for integrating Web Services with business systems; and

providing output indicating the generated integrated Web Service architecture for implementing the specific integrated Web Service business system.

81. The computer-accessible storage medium as recited in claim 80, wherein the integrated Web Service architecture comprises:

a service provider configured to provide one or more services on the integrated Web Service business system implemented according to the integrated Web Service architecture; and

one or more service requesters configured to access the one or more services from the service provider via a network.

82. The computer-accessible storage medium as recited in claim 81, wherein the integrated Web Service business system is a Business-to-Consumer system, wherein the service provider is a business service provider, and wherein the service requester is an end user.

83. The computer-accessible storage medium as recited in claim 81, wherein the integrated Web Service business system is a Business-to-Business system, wherein the service provider is a business service provider, and wherein the service requester is a business server.

84. The computer-accessible storage medium as recited in claim 80, wherein the two or more layers of the integrated Web Service architecture comprise two or more of:

a network layer configured to serve as an underlying network for Web Services implemented according to the integrated Web Service architecture;

a transport layer for delivering messages between components of the integrated Web Service architecture;

a service description language layer configured to describe service type and functionality of the integrated Web Service architecture;

a transaction routing layer configured to route messages on the transport layer;

a service discovery layer configured to search for and locate services in the integrated Web Service architecture;

a service negotiation layer configured to negotiate exchanges between service requesters and service providers implemented according to the integrated Web Service architecture;

a management layer configured for provisioning of the integrated Web Service architecture and for monitoring and administration of the integrated Web Service architecture;

a Quality of Service layer configured to provide reliability, scalability, and availability for the integrated Web Service architecture;

a security layer configured to provide authentication, entitlement, and non-repudiation security on the transport layer; and

an Open Standards layer.

85. The computer-accessible storage medium as recited in claim 80, wherein the specific integrated Web Service business system is an Enterprise integrated Web Service.

86. The computer-accessible storage medium as recited in claim 80, wherein the specific integrated Web Service business system is a Cross-Enterprise integrated Web Service.

87. The computer-accessible storage medium as recited in claim 80, wherein the plurality of Web Service components of the integrated Web Service architecture include one or more legacy mainframe systems.

88. The computer-accessible storage medium as recited in claim 80, wherein the program instructions are further computer-executable to implement defining integration of one or more Enterprise Application Interface (EAI) products with the one or more Web Services technologies.

89. The computer-accessible storage medium as recited in claim 80, wherein the plurality of integration tiers comprises a client tier, a presentation tier, a business tier, an integration tier, and a resources tier.

90. The computer-accessible storage medium as recited in claim 80, wherein the one or more Web Services integration design patterns include one or more of:

an Application-to-Application design pattern;

a Standard Build design pattern;

a Hub-Spoke Replication design pattern;

a Federated Replication design pattern;

a Multi-Step Application integration design pattern;

a Data Exchange design pattern;

a Closed Process integration design pattern;

an Open Process integration design pattern;

a Service Consolidation-Broker integration design pattern; and

a Reverse Auction-Broker integration design pattern.