SYSTEM AND METHOD FOR EXTENSIBLE DATA INTERFACE FOR SHARED SERVICE MODULE
First Claim
1. A method for interfacing between a caller application and a service module, the method comprising:
- receiving a request for performing a transaction from the caller application, wherein the request comprises at least one caller application attribute describing the request;
subsequent to said receiving, building a service module data structure pursuant to said received request, wherein the service module data structure comprises a generic service document and at least one service module attribute, wherein the service module uses only the service module data structure such that the service module needs not manipulate said at least one caller application attribute in performing the transaction;
subsequent to said building, storing each service module attribute of said at least one service module attribute in a relational table of the service module data structure;
subsequent to said storing, servicing the request within the service module data structure, wherein said servicing results in instantiating the generic service document; and
subsequent to said servicing, returning the generic service document to the caller application,wherein said receiving, said building, said storing, said servicing, and said returning are performed by the service module.
1 Assignment
0 Petitions
Accused Products
Abstract
A system and associated method for interfacing between caller applications and a shared service module. Upon receiving a request for a transaction, the shared service module creates a separate data structure per request from a caller application and configures a caller identifier to uniquely identify the caller application. The separate data structure per request can be extended by the shared service module with additional attributes that may be used, without impacting the service application data model, in the request to support servicing the request. The shared service module generates a generic service document to return the result after servicing the request to the caller application.
-
Citations
20 Claims
-
1. A method for interfacing between a caller application and a service module, the method comprising:
-
receiving a request for performing a transaction from the caller application, wherein the request comprises at least one caller application attribute describing the request; subsequent to said receiving, building a service module data structure pursuant to said received request, wherein the service module data structure comprises a generic service document and at least one service module attribute, wherein the service module uses only the service module data structure such that the service module needs not manipulate said at least one caller application attribute in performing the transaction; subsequent to said building, storing each service module attribute of said at least one service module attribute in a relational table of the service module data structure; subsequent to said storing, servicing the request within the service module data structure, wherein said servicing results in instantiating the generic service document; and subsequent to said servicing, returning the generic service document to the caller application, wherein said receiving, said building, said storing, said servicing, and said returning are performed by the service module. - View Dependent Claims (2, 3, 4, 5)
-
-
6. A computer program product, comprising a computer usable storage medium having a computer readable program code embodied therein, said computer readable program code containing instructions that when executed by a processor of a computer system implement a method for interfacing between a caller application and a service module, the method comprising:
-
receiving a request for performing a transaction from the caller application, wherein the request comprises at least one caller application attribute describing the transaction; subsequent to said receiving, building a service module data structure pursuant to said received request, wherein the service module data structure comprises a generic service document and at least one service module attribute, wherein the service module uses only the service module data structure such that the service module needs not manipulate said at least one caller application attribute in performing the transaction; subsequent to said building, storing each service module attribute of said at least one service module attribute in a relational table of the service module data structure; subsequent to said storing, servicing the request within the service module data structure, wherein said servicing results in instantiating the generic service document; and subsequent to said servicing, returning the generic service document to the caller application, wherein said receiving, said building, said storing, said servicing, and said returning are performed by the service module. - View Dependent Claims (7, 8, 9, 10)
-
-
11. A computer system comprising a processor and a computer readable memory unit coupled to the processor, said memory unit containing instructions that when executed by the processor implement a method for interfacing between a caller application and a service module, the method comprising:
-
receiving a request for performing a transaction from the caller application, wherein the request comprises at least one caller application attribute describing the transaction; subsequent to said receiving, building a service module data structure pursuant to said received request, wherein the service module data structure comprises a generic service document and at least one service module attribute, wherein the service module uses only the service module data structure such that the service module needs not manipulate said at least one caller application attribute in performing the transaction; subsequent to said building, storing each service module attribute of said at least one service module attribute in a relational table of the service module data structure; subsequent to said storing, servicing the request within the service module data structure, wherein said servicing results in instantiating the generic service document; and subsequent to said servicing, returning the generic service document to the caller application, wherein said receiving, said building, said storing, said servicing, and said returning are performed by the service module. - View Dependent Claims (12, 13, 14, 15)
-
-
16. A process for supporting computer infrastructure, said process comprising providing at least one support service for at least one of creating, integrating, hosting, maintaining, and deploying computer-readable code in a computing system, wherein the code in combination with the computing system is capable of performing a method for interfacing between a caller application and a service module, the method comprising:
-
receiving a request for performing a transaction from the caller application, wherein the request comprises at least one caller application attribute describing the transaction; subsequent to said receiving, building a service module data structure pursuant to said received request, wherein the service module data structure comprises a generic service document and at least one service module attribute, wherein the service module uses only the service module data structure such that the service module needs not manipulate said at least one caller application attribute in performing the transaction; subsequent to said building, storing each service module attribute of said at least one service module attribute in a relational table of the service module data structure; subsequent to said storing, servicing the request within the service module data structure, wherein said servicing results in instantiating the generic service document; and subsequent to said servicing, returning the generic service document to the caller application, wherein said receiving, said building, said storing, said servicing, and said returning are performed by the service module. - View Dependent Claims (17, 18, 19, 20)
-
Specification