Method for extracting personalization information from web activity

• US 6,961,766 B2
• Filed: 04/24/2001
• Issued: 11/01/2005
• Est. Priority Date: 04/24/2001
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Diamond, David Lane, Janosik, John Louis Jr., Rubino, Michael
• Primary Examiner(s): Najjar, Saleh
• Application Number:
  US09/841,280
• Publication Number:
  US 20020156836A1
• Time in Patent Office: 1,652 Days
• Field of Search: 709/223, 709/224
• US Class Current: 709/224
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/561 Adding application-functional data or data for application control, e.g. adding metadata
• CPC Class Codes: H04L 67/564 Enhancement of application control based on intercepted application data
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]

Abstract

An Internet gateway server for dynamically loading a database with data extracted from selected header fields and the body of inbound and outbound HTTP messages exchanged between one or more servers and the Web browsers which connect with those servers. The gateway server or “WebJacket” is interposed in the communications pathway between the server(s) and client(s) receiving each of inbound messages from a client and forwarding the received inbound messages to the server(s). The WebJacket extracts a first selected set of data contained in predetermined ones of said inbound messages and storing this incoming message data in predetermined locations in a relational database. The WebJacket further receives, stores and forwards each outbound message from the server(s) and extracts a second selected set of data from the outbound messages. To speed performance, the WebJacket uses multithreaded processes to forward each message to its destination before or while the content of that message is being posted into the database. The specific information to be saved from each message, and the database location where it is to reside, is specified by configuration data accepted from a user in advance of handling the messages. When the message content is not sufficient to uniquely each client that initiated a given request/response exchange, client identification data in inserted into the outbound message in a “set-cookie” header instruction so that all messages to or from a given client may thereafter be identified. The configuration data identifies messages which already include cookie data which is adequate to identify the client.

Claims

1. The method of gathering and storing in a relational database selected content extracted from inbound HTTP request messages sent to a Web server from remotely located Web browsers via the Internet, and further storing in said relational database selected content extracted from outbound HTTP response messages sent from said Web server to said remotely located Web browsers, said method comprising the steps of:

providing a gateway server coupled to said relational database and interposed in the communications pathway between said Web server and the Internet and utilizing said gateway server to perform the steps of;

receiving each of said inbound request messages from one of said Web browsers and forwarding each of said inbound request messages to said Web server,

extracting a first selected set of data contained in predetermined request data fields in each of said inbound request messages and storing said first set of data in corresponding addressable request data storage locations in said relational database, said request data storage locations being defined by schema for said relational database,

receiving each of said outbound response messages from said Web server and forwarding each such outbound response message to one of said Web browsers,

extracting a second selected set of data contained in predetermined response data fields in each or said outbound response messages and storing said second set of data in corresponding addressable response data storage locations defined by a schema for said relational database,

whereby said relational database is populated with information which describes the past use of said server.

2. The method set forth in claim 1 wherein said step of receiving and forwarding each of said inbound request messages is performed before or concurrently with said step of extracting data contained in predetermined ones of said inbound request messages.

3. The method set forth in claim 2 wherein said step of receiving and forwarding each of said outbound messages is performed before or concurrently with said step of extracting data contained in predetermined ones of said outbound messages.

4. The method set forth in claim 1 further including the step of accepting configuration data which identifies said predetermined request data fields and said predetermined response data fields containing said first and said second sets of data.

5. The method set forth in claim 1 further including the step of accepting configuration data which identifies said predetermined request data fields and said corresponding request data storage locations, and which further identifies said predetermined response data fields and said corresponding response data storage locations.

6. The method set forth in claim 1 wherein said step of receiving each of said inbound messages from a client and forwarding said inbound messages to said server includes the step of forwarding selected ones of said inbound messages to a second server, and wherein the step of receiving outbound messages from said server includes the step of receiving outbound messages from said second server.

7. The method set forth in claim 1 wherein said step of receiving each of said outbound messages from said server and forwarding each such outbound message to a client includes the step of inserting client identification data into said outbound message before said outbound message is forwarded to said client.

8. The method set forth in claim 7 further including the step of accepting cookie configuration data from a user, and wherein said step of inserting client information into said outgoing method is performed only on selected messages identified by said cookie configuration data.

9. Apparatus for transferring data to a relational database from HTTP request and response messages exchanged via the Internet comprising, in combination:

A Web server connected to the Internet for receiving HTTP request messages via the Internet and returning HTTP response messages via the Internet,

a Web browser connected to the Internet for sending HTTP request messages to said Web server via the Internet and for receiving HTTP response messages from said Web server via the Internet,

each of said HTTP request messages and each of said HTTP response messages including a plurality of named fields containing data; and

a gateway server for transferring data from said request and response messages to said relational database, said gateway server being connected to relay said HTTP request messages from said Web browser to said Web server without changing their content and further being connected to relay said HTTP response messages from said Web server back to said Web browser, said gateway server including means for extracting field data from said named fields of said HTTP request and response messages and posting said field data into corresponding storage locations designated to receive said field data extracted from said named fields, said corresponding storage locations being defined by a schema for said relational database.

10. Apparatus for transferring data to a relational database from HTTP request and response messages exchanged via the Internet as set forth in claim 9 wherein said gateway server further includes means for generating cached HTTP response messages in response to selected ones of said HTTP request messages by retrieving cached data from said relational database that was previously extracted from previously relayed HTTP response messages, including means for forming said HTTP cached response messages from said cached data, and for returning said HTTP cached response messages via the Internet to the Web browsers that transmitted said selected ones of said HTTP request messages.

11. Apparatus for transferring data to a relational database from HTTP request and response messages exchanged via the Internet as set forth in claim 9 further comprising an interface for accepting configuration data from an administrator that specifies said named fields of said HTTP messages from which said field data is to be extracted and further designates said corresponding storage locations which are to receive said field data from said named fields.

12. Apparatus for transferring data to a relational database from HTTP request and response messages exchanged via the Internet as set forth in claim 11 wherein said gateway server further includes means generating cached HTTP response messages in response to selected ones of said HTTP request messages by retrieving cached data from said relational database that was previously extracted from previously relayed HTTP response messages, including means for forming said HTTP cached response messages from said cached data, and for returning said HTTP cached response messages to the Web browsers that transmitted said selected ones of said HTTP request messages.