Non-intrusive personalization of web services

• US 7,752,634 B1
• Filed: 04/30/2005
• Issued: 07/06/2010
• Est. Priority Date: 08/29/2003
• Status: Expired due to Fees

• Current Assignee: Kyndryl Incorporated
• Original Assignee: International Business Machines Corporation
• Inventors: Yarbrough, Keith, Tenenbaum, Jay Martin, Perham, Michael, Sanchez, Matthew, Laxminarayan, Chaitanya, Saxena, Manoj
• Primary Examiner(s): Cao; Diem K
• Application Number:
  US11/123,630
• Time in Patent Office: 1,893 Days
• Field of Search: 719/313, 709/219
• US Class Current: 719/320
• CPC Class Codes: G06F 9/44505 Configuring for program initiating, e.g. using registry, configuration files
• CPC Class Codes: H04L 67/306 User profiles
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 67/561 Adding application-functional data or data for application control, e.g. adding metadata
• CPC Class Codes: H04L 67/563 Data redirection of data network streams

Abstract

A method and apparatus to employ a service proxy to personalize service messages by automatically supplying the interface parameters used for communications between a Service provider and its client businesses. The service proxy does this according to context parameters that the client businesses specify during configuration of the messages used to communicate with one or more 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 supplying message-format parameters used for communications between a service and a client comprising:

setting up a personalization system by;

providing predefined communications parameters used for message communications between the service and the client;

setting up a service proxy on a server, the service proxy comprising a user configuration and a service configuration, the user configuration comprising at least one subscriber profile that represents data indicating selected ones of the communications parameters associated with the client, and the service configuration comprising at least one service profile that represents data indicating selected ones of the communications parameters utilized to determine configuration information that the service requires for use with a corresponding client application;

setting up a service registry that is utilized to store the at least one subscriber profile and the at least one service profile; and

setting up a configuration interface that is utilized for predefining ones of the communications parameters as a plurality of context variables and a plurality of interface variables;

wherein the personalization system is configured to be utilized to apply correct communications parameters to client application messages by;

receiving an incoming client application message by the service proxy;

retrieving a selected subscriber profile from the user configuration based upon the received incoming client application message;

selecting a service instance by matching the selected subscriber profile to a selected service profile from the service configuration;

applying correct communications parameters to the incoming client application message based upon the communications parameters specified in at least one of the selected subscriber profile and the selected service profile by determining context parameters of the incoming client application message, retrieving the service profile for the service to be invoked, and applying specified interface parameters to the incoming client application message to create a personalized service request of the client; and

forwarding the personalized service request of the client to the selected service instance.

2. The method of claim 1 wherein setting up a personalization system further comprises storing hierarchies in the service registry that associate context information contained in client application messages to corresponding communications parameters, the hierarchies configured to permit inheritance of the communication parameters from one hierarchy to another.

3. The method of claim 2 wherein storing hierarchies in the service registry further comprises storing at least one service hierarchy having context information relating to categories of service provided by a corresponding service provider and storing at least one user hierarchy having context information relating to categories that define the organization of an entity associated with the client.

4. The method of claim 2 wherein storing hierarchies in the service registry comprises storing:

at least one service hierarchy comprising at least one suite of applications;

at least one application within the suite of applications;

at least one business service related to the at least one application; and

at least one service related to the at least one business service.

5. The method of claim 2 wherein storing hierarchies in the service registry comprises storing:

at least one user hierarchy comprising an organization;

at least one group within the organization; and

at least one individual within the at least one group.

6. The method of claim 1 wherein the service is a Web service, and selecting a service instance comprises selecting a Web service end point by matching the selected subscriber profile to the selected service profile from the service configuration.

7. The method of claim 1 wherein the service is a CORBA remote object, and selecting a service instance comprises selecting a CORBA service.

8. The method of claim 1 wherein the service is a JAVA RMI remote object, and selecting a service instance comprises selecting a JAVA RMI service.

9. The method of claim 1 wherein setting up a configuration interface comprises setting up a configuration interface that is utilized for predefining ones of the communications parameters as a plurality of context variables and a plurality of interface variables, the plurality of context variables comprising service variables, user variables, and channel variables.

10. The method of claim 9 wherein the channel variables comprise faced variables for messages sent on behalf of a human operator and faceless variables for messages sent by machine-to-machine transmission.

11. The method of claim 1 wherein setting up a service proxy further comprises setting up at least one personalization engine and at least one invocation engine, wherein the personalization engine is utilized by the service proxy to match communications parameters from the selected subscriber profile to communications parameters associated with the corresponding selected service profile based upon context parameters contained in a corresponding client application message, and the invocation engine is utilized by the service proxy to forward the personalized service request of the client to the service and to activate the service instance to execute the personalized service request of the client.

12. The method of claim 1 wherein the subscriber profile comprises interface parameters and context parameters.

13. The method of claim 1 wherein the client application messages comprise a SOAP envelope comprising a plurality of context headers and a message body.

14. The method of claim 1 wherein providing predefined communications parameters used for message communications between the service and the client comprises defining JAVA RMI interfaces for client application messages.

15. The method of claim 1 wherein providing predefined communications parameters used for message communications between the service and the client comprises defining CORBA IDL interfaces for client application messages.

16. The method of claim 1 wherein the personalization system is further configured to be utilized for:

accepting an outgoing message response from the selected service instance by the service proxy;

applying correct communications parameters to the outgoing message response based upon at least one of the selected subscriber profile and the selected service profile associated with the corresponding incoming client application message;

creating a correctly formatted reply message to the client application incoming message from the outgoing message response; and

forwarding the correctly formatted reply message to the client.

17. The method of claim 16 wherein applying correct communications parameters to the outgoing message response comprises:

determining context parameters of the outgoing message response;

retrieving the selected service profile;

applying specified interface parameters to the outgoing message response; and

sending the correctly formatted response to the client.

18. The method of claim 1 wherein the personalization system is further utilized for storing client communication parameters by receiving a client-specified configuration through the configuration interface.

19. A system for automatically supplying message-format parameters used for communications between a service and a client comprising:

a personalization system comprising;

predefined communications parameters used for message communications between the service and the client;

a service proxy on a server, the service proxy comprising a user configuration and a service configuration, the user configuration comprising at least one subscriber profile that represents data indicating selected ones of the communications parameters associated with the client, and the service configuration comprising at least one service profile that represents data indicating selected ones of the communications parameters utilized to determine configuration information that the service requires for use with a corresponding client application;

a service registry that is utilized to store the at least one subscriber profile and the at least one service profile; and

a configuration interface that is utilized for predefining ones of the communications parameters as a plurality of context variables and a plurality of interface variables;

wherein the personalization system is configured to be utilized to;

receive incoming client application messages by the service proxy;

retrieve a selected subscriber profile from the user configuration based upon the received incoming client application message;

select a service instance by matching the selected subscriber profile to a selected service profile from the service configuration;

apply correct communications parameters to the incoming client application message based upon the communications parameters specified in at least one of the selected subscriber profile and the selected service profile by determining context parameters of the incoming client application message, retrieving the service profile for the service to be invoked, and applying specified interface parameters to the incoming client application message to create a personalized service request of the client; and

forward the personalized service request of the client to the selected service instance.

20. A computer program product for automatically supplying message-format parameters used for communications between a service and a client comprising:

a computer usable storage medium having computer usable program code embodied therewith, the computer usable program code comprising;

computer usable program code configured to implement a personalization system comprising;

computer usable program code configured to implement predefined communications parameters used for message communications between the service and the client;

computer usable program code configured to implement a service proxy on a server, the service proxy comprising a user configuration and a service configuration, the user configuration comprising at least one subscriber profile that represents data indicating selected ones of the communications parameters associated with the client, and the service configuration comprising at least one service profile that represents data indicating selected ones of the communications parameters utilized to determine configuration information that the service requires for use with a corresponding client application;

computer usable program code configured to interact with a service registry that is utilized to store the at least one subscriber profile and the at least one service profile; and

computer usable program code configured to implement a configuration interface that is utilized for predefining ones of the communications parameters as a plurality of context variables and a plurality of interface variables; and

computer usable program code configured to allow the personalization system to apply correct communications parameters to client application comprising;

computer usable program code configured to receive an incoming client application message by the service proxy;

computer usable program code configured to retrieve a selected subscriber profile from the user configuration based upon the received incoming client application message;

computer usable program code configured to select a service instance by matching the selected subscriber profile to a selected service profile from the service configuration;

computer usable program code configured to apply correct communications parameters to the incoming client application message based upon the communications parameters specified in at least one of the selected subscriber profile and the selected service profile by determining context parameters of the incoming client application message, retrieving the service profile for the service to be invoked, and applying specified interface parameters to the incoming client application message to create a personalized service request of the client; and

computer usable program code configured to forward the personalized service request of the client to the selected service instance.