System and method for using Web services with an enterprise system

• US 20030105884A1
• Filed: 10/15/2002
• Published: 06/05/2003
• Est. Priority Date: 10/18/2001
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: BEA Systems Incorporated (Oracle Corporation)
• Inventors: Upton, Mitch
• Granted Patent: US 7,340,714 B2
• Time in Patent Office: Days
• US Class Current: 719/318
• CPC Class Codes: G06F 2209/544 Remote
• CPC Class Codes: G06F 9/541 via adapters, e.g. between incompatible applications
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications
• CPC Class Codes: G06Q 10/103 Workflow collaboration or project management
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing

Abstract

An application view control can be added to a Web service to allow the Web service to make requests into a resource such as an enterprise system through an integration system. The integration system can include a resource adapter that can invoke functionality in the enterprise system, as well as an application view component that acts as an interface through which the functionality can be exposed to the application view control. The application view component can allow the Web service to accomplish tasks such as subscribing to application view events. A callback object can be used to notify a client of the Web service that an event has occurred in the underlying resource.

This description is not intended to be a complete description of, or limit the scope of, the invention. Other features, aspects, and objects of the invention can be obtained from a review of the specification, the figures, and the claims.

Claims

1. A system for using Web services with a system resource, comprising:

a resource adapter adapted to expose functionality in a resource;

an application view component adapted to provide an interface to the resource through the resource adapter; and

an application view control adapted to allow a web service to access the resource using the application view component.

2. A system according to claim 1, further comprising:

a Web service adapted to access the resource through the application view control.

3. A system according to claim 2, wherein:

the resource adapter is further adapted to define at least one of services and events in the resource that are available to the Web service.

4. A system according to claim 1, further comprising:

at least one Java API adapted to be used by the application view control to allow a Web service to interact with the resource.

5. A system according to claim 4, wherein:

the at least one Java API is adapted to shield a developer of the Web service from implementation details of the resource.

6. A system according to claim 1, wherein:

the application view component allows services of the application view to be called both synchronously and asynchronously.

7. A system according to claim 1, wherein:

the application view component allows the Web service to subscribe to application view events.

8. A system according to claim 1, wherein:

the resource is selected from the group consisting of relational databases, enterprise systems, and enterprise applications.

9. A system according to claim 1, further comprising:

a Java interface to the application view component, wherein the application view control allows the Java interface to be invoked directly from the Web service.

10. A system according to claim 1, further comprising:

a callback object adapted to notify a client of the Web service that an event has occurred in the resource.

11. A system according to claim 10, further comprising:

a handler adapted to manage the callback object.

12. A system according to claim 1, further comprising:

an application server adapted to allow the Web service to receive XML and SOAP messages from the resource.

13. A system according to claim 12, wherein:

the application server is further adapted to route the messages automatically to the Web service.

14. A system according to claim 10, further comprising:

a timer control adapted to allow the Web service to periodically check the callback object.

15. A system according to claim 1, wherein:

the application view control is further adapted to provide a common model to interacting with any resource from within any Web service.

16. A system according to claim 1, wherein:

the application view control contains a plurality of methods useful for interacting with the resource.

17. A system according to claim 16, further comprising:

an XML map for at least one of the plurality of methods.

18. A system according to claim 17, further comprising:

a user interface adapted to allow a user to modify properties of at least one of the application view control, the plurality of methods for the application view control, and the XML map.

19. A system according to claim 1, wherein:

the application view has an identity property that can be exposed by the application view control.

20. A system according to claim 1, wherein:

the application view control can be regenerated to use a different application view component.

21. A system according to claim 1, further comprising:

the resource adapter is an event adapter adapted to allow the resource to initiate communication with the Web service by triggering an event;

whereby the application view component can extract data about the event from the resource through the event adapter and propagate the data to the Web service.

22. A system according to claim 1, wherein:

the resource adapter is J2EE compliant.

23. A system according to claim 1, wherein:

the application view component is further adapted to propagate data for the resource in an XML document.

24. A system according to claim 1, further comprising

a connector architecture mechanism adapted to provide at least one of connection pooling, transaction management, and security services for the resource adapter.

25. A system according to claim 1, wherein:

the resource adapter is a service adapter adapted to invoke a service in the resource, the service adapted to receive requests from the application view component and return responses to the application view component through the service adapter.

26. A system according to claim 1, further comprising:

a connection factory adapted to create connections for the resource adapter.

27. A system according to claim 1, further comprising:

a security mechanism adapted to map authorization information across the path of a request from the application view component through the resource adapter to the resource.

28. A system according to claim 1, further comprising:

a run-time engine adapted to host the resource adapter.

29. A system according to claim 1, further comprising:

an integration framework adapted to provide a Java-based interface for each resource adapter.

30. A system integrating a Web service with a resource, comprising:

means for exposing functionality in the resource;

means for providing an interface to the functionality in the resource; and

means for allowing a web service to access the functionality through the interface.

31. A computer-readable medium, comprising:

means for exposing functionality in the resource;

means for providing an interface to the functionality in the resource; and

means for allowing a web service to access the functionality through the interface.

32. A computer program product for execution by a server computer for integrating a Web service with an resource, comprising:

computer code for exposing functionality in the resource;

computer code for providing an interface to the functionality in the resource; and

computer code for allowing a web service to access the functionality through the interface.

33. A computer system comprising:

a processor;

object code executed by said processor, said object code configured to;

expose functionality in the resource;

provide an interface to the functionality in the resource; and

allow a web service to access the functionality through the interface.

34. A computer data signal embodied in a transmission medium, comprising:

a code segment including instructions to expose functionality in the resource;

a code segment including instructions to provide an interface to the functionality in the resource; and

a code segment including instructions to allow a web service to access the functionality through the interface.