System and method for providing a java interface to an application view component

• US 20030110315A1
• Filed: 10/15/2002
• Published: 06/12/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,516,440 B2
• Time in Patent Office: Days
• US Class Current: 719/328
• 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

A Java-based interface can be used to allow a Java client or application to access an application view component. An application view component can provide an interface to an application or enterprise system, using a resource adapter to expose functionality in the enterprise system. A Java-based interface for the resource adapter can allow the Java client to access the application view component. The interface can be a design-time graphical user interface, which can include a set of Java server pages and can be Web-based. The interface can allow a Java client to access the application view component in order to accomplish a task such as creating, defining, deploying, and testing the application view component. Each of these tasks can have their own page in the interface, such as a Java server page.

Claims

1. A system for connecting a Java client application to an enterprise system, comprising:

an application view component adapted to provide an interface to the enterprise system for the Java client application;

a resource adapter adapted to expose functionality in the enterprise system to the Java client application, the resource adapter further adapted to define at least one of services and events in the enterprise system that are available to the Java client application; and

a Java-based interface for the resource adapter, Java-based interface adapted to allow the Java client application to access the application view component.

2. A system according to claim 1, wherein:

the Java-based interface is a design-time graphical user interface.

3. A system according to claim 1, wherein:

the Java-based interface includes a set of Java server pages.

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

a server hosting the resource adapter and the Java-based interface.

5. A system according to claim 1, wherein:

the Java-based interface is Web-based.

6. A system according to claim 1, wherein:

the Java-based interface is further adapted to allow the Java client application to access the application view component to do at least one of define, deploy, and test the application view component.

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

a Web application component adapted to allow the Java-based interface to be built using Java server pages.

8. A system according to claim 7, wherein:

the Web application component further comprises tools selected from the group consisting of JSP templates, a tag library, and a JavaScript library.

9. A system according to claim 1, wherein:

the resource adapter is an event adapter adapted to allow the enterprise system to initiate communication with the Java client application by triggering an event;

whereby the application view component can extract data about the event from the enterprise system through the event adapter and propagate the data to the Java client application.

10. A system according to claim 1, wherein:

the resource adapter is J2EE compliant.

11. A system according to claim 9, wherein:

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

12. A system according to claim 9, wherein:

the event adapter is further adapted to extract data about the event from the enterprise system, and makes that data available to the application view component.

13. A system according to claim 9, wherein:

the event adapter is further adapted to transform the data from a format specific to the enterprise system to an XML document.

14. 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.

15. A system according to claim 1, wherein:

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

16. A system according to claim 15, wherein:

the service adapter passes requests and responses as XML documents.

17. A system according to claim 15, wherein:

the service adapter invokes a service that allows asynchronous messaging between the application view and the enterprise system.

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

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

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

a call-back listener adapted to handle a response for the application view that is received from the enterprise system.

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

a JMS queue adapted to receive a request from the application view component and store the request until the request is passed to the enterprise system.

21. 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 enterprise system.

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

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

23. A system according to claim 22, wherein:

the run-time engine is further adapted to manage connections to the enterprise system.

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

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

25. A system according to claim 1, wherein:

Java-based interface is further adapted to allow the Java client application to access the application view component to do at least one of create, add services to, add events to, and edit the application view component.

26. A system according to claim 1, wherein:

the Java-based interface further comprises an application view console adapted to help a user access, organize, and edit any application view component for the enterprise system.

27. A system according to claim 1, wherein:

the Java-based interface is a design-time interface comprising a J2EE web application bundled as a .war file, the J2EE web application including at least one of .jsp, .html and image files.

28. A system according to claim 1, wherein:

the Java-based interface contains forms that can be processed using Java servlets.

29. A system according to claim 1, wherein:

the Java-based interface includes a plurality of Java server pages, each Java server page adapted to call a Java servlet to invoke a transaction in the enterprise system.

30. A system according to claim 1, wherein:

the Java-based interface includes Java server pages selected from the group consisting of display pages, login pages, confirm connection pages, application view administration pages, add event pages, add service pages, edit event pages, edit service pages, deploy application view pages, and summary pages.

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

a design-time framework adapted to provide a set of JSP templates for rapidly assembling a Java-based interface.

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

an application view descriptor adapted to provide at least one of connection parameters, list of events, list of services, log levels, and pool settings for the application view component.

33. A Java-based interface for invoking functionality in an underlying enterprise system, comprising:

means for allowing a Java client to access an application view component for a resource adapter; and

means for allowing the Java client to do at least one of define, deploy, test, create, add services to, add events to, and edit the application view component.

34. A computer-readable medium, comprising:

means for allowing a Java client to access an application view component for a resource adapter; and

means for allowing the Java client to do at least one of define, deploy, test, create, add services to, add events to, and edit the application view component.

35. A computer program product for execution by a server computer for providing a Java-based interface for invoking functionality in an underlying enterprise system, comprising:

computer code for allowing a Java client to access an application view component for a resource adapter; and

computer code for allowing the Java client to do at least one of define, deploy, test, create, add services to, add events to, and edit the application view component.

36. A computer system comprising:

a processor;

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

allow a Java client to access an application view component for a resource adapter; and

allow the Java client to do at least one of define, deploy, test, create, add services to, add events to, and edit the application view component.

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

a code segment including instructions to allow a Java client to access an application view component for a resource adapter; and

a code segment including instructions to allow the Java client to do at least one of define, deploy, test, create, add services to, add events to, and edit the application view component.