Communication handler for flex integration with a secure application

• US 9,684,736 B2
• Filed: 01/29/2009
• Issued: 06/20/2017
• Est. Priority Date: 01/29/2009
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Kumar, Darshan, Sudhi, Ambili, Achar, Govindraja, Jhaveri, Pankesh
• Primary Examiner(s): LIN, SHEW FEN
• Application Number:
  US12/362,416
• Publication Number:
  US 20100191700A1
• Time in Patent Office: 3,064 Days
• CPC Class Codes: G06F 16/252 between a Database Management System and a front-end application
• CPC Class Codes: G06F 16/86 Mapping to a database

Abstract

Systems and methods are provided for a global communication handler to facilitate communication between an Flex application and an Enterprise Application Server (“EAS”) database. Data is obtained from the EAS database by the global communication handler, and the global communication handler instantiates at least one object that provides that data to a Flex application. The global communication handler also receives data from the Flex application, and writes that data to the EAS database.

Claims

1. A method to facilitate communication between a rich Internet application and a secure Enterprise Application System (EAS) database, comprising:

instantiating a rich Internet application that does not communicate with the secure EAS database;

instantiating a global communication handler application that communicates with the secure EAS database and the rich Internet application;

instantiating a global communication object that includes a secure application programming interface (API), an object that caches and provides a messaging plan to the rich Internet application, and an object that caches and provides analytical data to the secure EAS database;

retrieving, by the global communication handler application, a messaging plan including one or more messages of digital presentation content from the secure EAS database using the secure API;

caching the messaging plan in the global communication object;

providing the message plan to the rich Internet application;

receiving, by the global communication handler, analytical data from the rich Internet application;

caching the analytical data in the global communication object;

dynamically updating the cached analytical data in the global communication object during a session of the rich Internet application;

parsing the updated analytical data; and

after the session of the rich Internet application is over, writing, by the global communication handler application, the parsed analytical data to the secure EAS database using the secure API.

2. The method of claim 1, wherein the messaging plan includes information for a sales presentation.

3. The method of claim 1, wherein the EAS database is a life sciences database.

4. The method of claim 1, wherein the rich Internet application comprises a graphical user interface.

5. The method of claim 1, wherein all data received from and sent to the secure EAS database passes through the global communication handler.

6. The method of claim 1, wherein:

a format of the messaging plan is an extensible markup language (XML);

the global communication object is an ActiveX container provided by the secure EAS database;

the analytical data includes messages that were presented during the presentation, a message presentation sequence, and a time spent on each message; and

a format of the parsed analytical data is XML.

7. A non-transitory computer-readable medium having instructions stored thereon that, when executed by a processor, cause the processor to facilitate communication between a rich Internet application and a secure Enterprise Application System (EAS) database by:

instantiating a rich Internet application that does not communicate with the secure EAS database;

instantiating a global communication handler application that communicates with the secure EAS database and the rich Internet application;

instantiating a global communication object that includes a secure application programming interface (API), an object that caches and provides a messaging plan to the rich Internet application, and an object that caches and provides analytical data to the secure EAS database;

retrieving, by the global communication handler application, a messaging plan including one or more messages of digital presentation content from the secure EAS database using the secure API;

caching the messaging plan in the global communication object;

providing the message plan to the rich Internet application;

receiving, by the global communication handler, analytical data from the rich Internet application;

caching the analytical data in the global communication object;

dynamically updating the cached analytical data in the global communication object during a session of the rich Internet application;

parsing the updated analytical data; and

after the session of the rich Internet application is over, writing, by the global communication handler application, the parsed analytical data to the secure EAS database using the secure API.

8. The computer-readable medium claim 7, wherein the messaging plan includes information for a sales presentation.

9. The computer-readable medium of claim 7, wherein the EAS database is a life sciences database.

10. The computer-readable medium of claim 7, wherein the rich Internet application comprises a graphical user interface.

11. The non-transitory computer-readable medium of claim 7, wherein:

a format of the messaging plan is an extensible markup language (XML);

the global communication object is an ActiveX container provided by the secure EAS database;

the analytical data includes messages that were presented during the presentation, a message presentation sequence, and a time spent on each message; and

a format of the parsed analytical data is XML.

12. A system, comprising:

a secure Enterprise Application System (EAS) database;

a memory to store data and one or more software modules; and

a processor, coupled to the memory and the secure EAS database, configured to;

instantiate a rich Internet application that does not communicate with the secure EAS database;

instantiate a global communication handler application that communicates with the secure EAS database and the rich Internet application;

instantiate a global communication object that includes a secure application programming interface (API), an object that caches and provides a messaging plan to the rich Internet application, and an object that caches and provides analytical data to the secure EAS database;

retrieve, by the global communication handler application, a messaging plan including one or more messages of digital presentation content from the secure EAS database using the secure API;

cache the messaging plan in the global communication object;

provide the message plan to the rich Internet application;

receive, by the global communication handler, analytical data from the rich Internet application;

cache the analytical data in the global communication object;

dynamically update the cached analytical data in the global communication object during a session of the rich Internet application;

parse the updated analytical data; and

after the session of the rich Internet application is over, write, by the global communication handler application, the parsed analytical data to the secure EAS database using the secure API.

13. The system of claim 12, wherein the messaging plan includes information for a sales presentation.

14. The system of claim 12, wherein the database is a life sciences database.

15. The system of claim 12, wherein the rich Internet application comprises a graphical user interface.

16. The system of claim 12, wherein:

a format of the messaging plan is an extensible markup language (XML);

the global communication object is an ActiveX container provided by the secure EAS database;

the analytical data includes messages that were presented during the presentation, a message presentation sequence, and a time spent on each message; and

a format of the parsed analytical data is XML.