Dynamic Runtime Service Oriented Architecture

• US 20090292797A1
• Filed: 05/23/2008
• Published: 11/26/2009
• Est. Priority Date: 05/23/2008
• Status: Active Grant

• Current Assignee: Raytheon Company (Rtx Corporation)
• Original Assignee: Raytheon Company (Rtx Corporation)
• Inventors: Cromp, Robert F., Wren, James A.
• Granted Patent: US 7,783,782 B2
• Time in Patent Office: Days
• US Class Current: 709/223
• CPC Class Codes: G06Q 10/10 Office automation; Time management

Abstract

According to one embodiment, a dynamic access method for a service oriented architecture includes receiving a number of proxy endpoints from a business application, selecting one proxy endpoint from among the multiple proxy endpoints, and transmitting a request to an enterprise service bus (ESB). The request includes the one proxy endpoint for accessing the particular web service that it references.

Claims

1. A dynamic access method for a service oriented architecture comprising:

receiving a plurality of proxy endpoints from a business application, each of the plurality of proxy endpoints referencing each of a plurality of web services;

receiving one or more selection criteria from the business application, the selection criteria being associated with one or more characteristics of each of the plurality of web services;

determining one or more characteristics of each of the interfaces according to the one or more selection criteria;

selecting, according to the one or more characteristics, one proxy endpoint from among the plurality of proxy endpoints; and

transmitting a request including the one proxy endpoint to an enterprise service bus, the enterprise service bus operable to invoke the one web service pointed to by the one proxy endpoint.

2. The dynamic access method of claim 1, wherein the one or more characteristics are selected from the group consisting of a geographic location, a bit transfer rate, a quality of service (QoS), a response latency time, an average data throughput, and a minimum data throughput.

3. The dynamic access method of claim 1, further comprising restricting the plurality of proxy endpoints to those that conform to a specified policy.

4. The dynamic access method of claim 3, further comprising storing authorization information with each proxy endpoint in an internal UDDI registry, the authorization information describing an authorization level of each of a plurality of users.

5. The dynamic access method of claim 1, further comprising discovering the plurality of proxy endpoints from an internal UDDI registry and integrating, by a client toolkit, the plurality of proxy endpoints into the business application.

6. The dynamic access method of claim 5, further comprising restricting display of the plurality of proxy endpoints to those having sufficient authorization, the plurality of proxy endpoints being displayed on a user interface.

7. The dynamic access method of claim 1, further comprising receiving accounting information from the enterprise service bus and storing the accounting information in an internal UDDI registry.

8. Code embodied on a computer-readable medium, when executed by a computer operable to perform at least the following:

receive a plurality of proxy endpoints from a business application, each of the plurality of proxy endpoints referencing each of a plurality of web services;

receive one or more selection criteria from the business application, the selection criteria being associated with one or more characteristics of each of the plurality of web services;

determine one or more characteristics of each of the web services according to the one or more selection criteria;

select, according to the one or more characteristics, one proxy endpoint from among the plurality of proxy endpoints; and

transmit a request including the one proxy endpoint to an enterprise service bus, the enterprise service bus operable to invoke the one web service pointed to by the one proxy endpoint.

9. The code of claim 8, wherein the one or more characteristics are selected from the group consisting of a geographical location, a bit transfer rate, a quality of service (QoS), a response latency time, an average data throughput, and a minimum data throughput.

10. The code of claim 8, further operable to restrict the plurality of proxy endpoints to those that conform to a specified policy.

11. The code of claim 10, further operable to store authorization information with each proxy endpoint in an internal UDDI registry, the authorization information describing an authorization level of each of a plurality of users.

12. The code of claim 8, further operable to discover the plurality of proxy endpoints from an internal UDDI registry and integrate, by a client toolkit, the plurality of proxy endpoints into the business application.

13. The code of claim 12, further operable to restrict display of the plurality of proxy endpoints to those having sufficient authorization, the plurality of proxy endpoints being displayed on a user interface.

14. The code of claim 8, further operable to receive accounting information from the enterprise service bus and store the accounting information in an internal UDDI registry.

15. A dynamic runtime service oriented architecture comprising:

an authentication and authorization service coupled to an enterprise service bus and a business application, the authentication and authorization service operable to;

receive a plurality of proxy endpoints from the business application, each of the plurality of proxy endpoints referencing each of a plurality of web services;

receive one or more selection criteria from the business application, the selection criteria being associated with one or more characteristics of each of the plurality of interfaces;

determine one or more characteristics of each of the interfaces according to the one or more selection criteria;

select, according to the one or more characteristics, one proxy endpoint from among the plurality of proxy endpoints; and

transmit a request including the one proxy endpoint to the enterprise service bus to invoke the one web service pointed to by the one proxy endpoint.

16. The dynamic runtime service oriented architecture of claim 15, wherein the one or more characteristics are selected from the group consisting of a geographical location, a bit transfer rate, a quality of service (QoS), a response latency time, an average data throughput, and a minimum data throughput.

17. The dynamic runtime service oriented architecture of claim 15, further comprising a policy and web service manager coupled to an internal UDDI registry for storage of the plurality of proxy endpoints, the policy and web service manager operable to restrict storage of the plurality of proxy endpoints whose associated interfaces conform to a specified policy.

18. The dynamic runtime service oriented architecture of claim 17, wherein the policy and web service manager is operable to store authorization information with each web service in the internal UDDI registry, the authorization information describing an authorization level of each of a plurality of users.

19. The dynamic runtime service oriented architecture of claim 15, further comprising a client toolkit coupled to a discovery service, the client toolkit executed in a integrated development environment application and operable to receive the plurality of proxy endpoints discovered by the discovery service and integrate the proxy endpoints into the business application.

20. The dynamic runtime service oriented architecture of claim 19, further comprising a user interface, the authentication and authorization service operable to restrict display of the plurality of proxy endpoints on the user interface to those having sufficient authorization.

21. The dynamic runtime service oriented architecture of claim 15, further comprising a business manager coupled to the authentication and authorization service and the enterprise service bus, the business manager operable to receive accounting information associated with the one web service from the enterprise service bus and store the accounting information in an internal UDDI registry.