Dynamic, non-intrusive personalization of web services

• US 8,949,311 B2
• Filed: 07/23/2004
• Issued: 02/03/2015
• Est. Priority Date: 08/29/2003
• Status: Active Grant

• Current Assignee: Kyndryl Incorporated
• Original Assignee: International Business Machines Corporation
• Inventors: Perham, Michael, Laxminarayan, Chaitanya, Sanchez, Matthew, Yarbrough, Keith
• Primary Examiner(s): Donabed, Ninos
• Application Number:
  US10/898,633
• Publication Number:
  US 20050086330A1
• Time in Patent Office: 3,847 Days
• Field of Search: 709/203, 709/204, 709/205
• US Class Current: 709/203
• CPC Class Codes: G06F 9/44505 Configuring for program initiating, e.g. using registry, configuration files
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/306 User profiles
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04L 67/564 Enhancement of application control based on intercepted application data

Abstract

A method and apparatus to employ a service proxy to dynamically personalize Web service messages by automatically supplying the interface parameters used for communications between a Web service provider and its client businesses. The service proxy does this according to context parameters that the client businesses specifies during configuration set up at the Web service provider'"'"'s Web site and in messages used to communicate with one or more Web services. For simpler administration, the context variables may be organized in multiple kinds of hierarchies by which communications parameters specified at a higher level are automatically applied to categories at a lower level, although parameters specified directly for a lower-level category will override parameters from a higher category.

Claims

1. A method of automatically and dynamically supplying personalized communications parameters used for communications between a Web service and a source comprising:

executing a service proxy on a server computer, wherein the service proxy manages applying communications parameters to messages communicated across a computer network between one or more client applications and one or more Web services;

storing client communications parameters in a computer readable storage accessible to the service proxy by;

receiving at least one configuration of client-specified communications parameters wherein each configuration includes at least one interface variable and at least one context variable;

storing each configuration of client-specified communications parameters as an associated subscriber profile in the computer readable storage;

storing Web service provider configured information as at least one service profile in the computer readable storage accessible to the service proxy;

utilizing the service proxy to apply particular communications parameters to client application messages by;

receiving a client application incoming message, wherein the client application incoming message comprises a header having context information, and a body having a corresponding Web service request;

reading the context information from the client application incoming message;

utilizing the context information read from the client application incoming message to retrieve a selected subscriber profile from the computer readable storage;

utilizing the context information read from the client application incoming message to retrieve a selected service profile from the computer readable storage;

applying the particular communications parameters determined from the retrieved subscriber profile and from the retrieved service profile to transform the incoming message to personalize the client'"'"'s web service request, and

forwarding the client'"'"'s personalized web service request to the web service end point of the associated Web service by invoking the Web service to execute the request contained in that personalized client application message.

2. The method of claim 1 further comprising allowing the source to set up the context variables as at least one of:

web service variables;

user variables; and

channel variables.

3. The method of claim 2 wherein setting up the context variables as channel variables further comprises setting up the channel variables as at least one of:

faced variables for messages sent on behalf of a human operator; and

faceless variables for messages sent by machine-to-machine.

4. The method of claim 1 further comprising storing hierarchies as at least one of:

at least one web service hierarchy; and

at least one user hierarchy, such that the hierarchies permit inheritance of the communications parameters.

5. The method of claim 1 further comprising storing the subscriber profiles in the computer readable storage as at least one of:

interface parameters; and

context parameters.

6. The method of claim 1 further comprising predefining client application messages as:

a SOAP envelope comprising

a plurality of context headers, and

a message body.

7. The method of claim 1 further comprising storing hierarchies in the computer readable storage as at least one of:

at least one suite of applications;

at least one application within the suite of applications;

at least one business service related to the application; and

at least one web service related to the business service.

8. The method of claim 1 further comprising storing at least one hierarchy as a user hierarchy in the computer readable storage including at least one of:

an organization;

at least one group within the organization; and

at least one individual within the group.

9. The method of claim 1 further comprising executing a configuration interface that allows the source to set up communications parameters including at least one context variable as a user variable including at least one of:

an organization identifier;

a group identifier; and

an individual identifier.

10. The method of claim 3 wherein setting up the channel variables further comprises setting up the faced variables as a channel identification selected from the group consisting of a web browser;

and a handheld device.

11. The method of claim 3 wherein setting up the channel variables further comprises setting up the faceless variables as a channel identification selected from the group consisting of HTTP;

FTP;

a web service; and

EDI.

12. The method of claim 1 wherein further comprising predefining the formats of a plurality of client application messages by predefining the context headers of the client application messages as at least one of:

a web service header indicating the web service;

a user header indicating the user invoking the web service;

a timestamp header indicating the time the message was sent; and

a channel header indicating the transmission channel of the application message.

13. The method of claim 1 further comprising executing a configuration interface used by sources to set up the context variables as a timeframe.

14. The method of claim 1 further comprising executing a configuration interface used by sources to set up the interface variables that define as at least one of:

encryption level;

timeout; and

number of retries.

15. The method of claim 1 wherein applying the correct communications parameters determined from the retrieved subscriber profile and from the retrieved service profile to transform the incoming message to personalize the client'"'"'s web service request further comprises:

determining the context parameters of the incoming message;

retrieving the service profile for the web service to be invoked; and

applying specified interface parameters to the client application incoming message to personalize the client'"'"'s web service request.

16. The method according to claim 1 further comprising:

setting up WSDL documents for communicating context information to the personalization system.

17. A system to automatically and dynamically supply personalized communications parameters used for communications between a web service and a source comprising:

a server computer connected to a computer network;

a computer readable metadata storage, wherein the server computer is configured for communication with the computer readable metadata storage;

a configuration interface executed on the server computer, which is used by sources to set up communications parameters to be applied automatically to messages between client applications and associated Web services;

a service proxy executed on the server computer, wherein the service proxy manages applying communications parameters to messages communicated across the computer network between one or more client applications and one or more Web services;

wherein client communications parameters are stored by;

receiving a client-specified communications parameters configuration through the configuration interface,

storing each configuration of client-specified communications parameters as an associated subscriber profile in the computer readable metadata storage;

storing Web service provider configured information as at least one service profile in the computer readable metadata storage accessible to the service proxy;

utilizing the service proxy to apply particular communications parameters to client application messages using the service proxy by;

receiving a client application incoming message, wherein the client application incoming message comprises a header having context information, and a body having a corresponding Web service request;

reading the context information from the client application incoming message;

utilizing the context information read from the client application incoming message to retrieve a selected subscriber profile from the computer readable metadata storage;

utilizing the context information read from the client application incoming message to retrieve a selected service profile from the computer readable metadata storage;

applying the particular communications parameters determined from the retrieved subscriber profile and from the retrieved service profile to transform the incoming message to personalize the client'"'"'s web service request, and

forwarding the client'"'"'s personalized web service request to the web service end point of the associated Web service by invoking the Web service to execute the request contained in that personalized client application message.