Interfacing between a caller application and a service module
First Claim
1. A method for interfacing between a caller application and a service module, said method comprising:
- receiving, by a processor of a computer system, 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, said processor building a service module data structure pursuant to the 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 need not manipulate the at least one caller application attribute in performing the transaction;
subsequent to said building, said processor storing each service module attribute of the at least one service module attribute in a relational table of the service module data structure;
subsequent to said storing, said processor servicing the request within the service module data structure, wherein said servicing results in instantiating the generic service document; and
subsequent to said servicing, said processor returning the generic service document to the caller application;
said service module being executed by the processor to perform said receiving the request, said building the service module data structure, said storing each service module attribute, said servicing the request, and said returning the generic service document,wherein said storing comprises;
determining a category of a first service module attribute of the at least one service module attribute;
subsequent to said determining the category, determining a level of the first service module attribute;
subsequent to said determining the level, storing in the relational table a first container of at least one container, said first container being pursuant to the category and the level of the first service module attribute that is associated with the first container; and
subsequent to said storing the first container, repeating to perform said determining the category, said determining the level, and said storing the first container after setting the first container with a next container in the relational table until all containers are stored in the relational table.
1 Assignment
0 Petitions
Accused Products
Abstract
A method and associated system for interfacing between a caller application and a service module. Upon receiving a request for performing a transaction that includes at least one caller application attribute describing the request, the service module builds a service module data structure pursuant to the received request. The service module data structure includes a generic service document and at least one service module attribute. Each service module attribute is stored in a relational table of the service module data structure. The request is serviced within the service module data structure, resulting in instantiating the generic service document. The generic service document is returned to the caller application. Storing each service module attribute in the relational table includes: determining a category and a level of a first service module attribute; and storing in the relational table a first container pursuant to the category and the level.
-
Citations
19 Claims
-
1. A method for interfacing between a caller application and a service module, said method comprising:
-
receiving, by a processor of a computer system, 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, said processor building a service module data structure pursuant to the 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 need not manipulate the at least one caller application attribute in performing the transaction; subsequent to said building, said processor storing each service module attribute of the at least one service module attribute in a relational table of the service module data structure; subsequent to said storing, said processor servicing the request within the service module data structure, wherein said servicing results in instantiating the generic service document; and subsequent to said servicing, said processor returning the generic service document to the caller application; said service module being executed by the processor to perform said receiving the request, said building the service module data structure, said storing each service module attribute, said servicing the request, and said returning the generic service document, wherein said storing comprises; determining a category of a first service module attribute of the at least one service module attribute; subsequent to said determining the category, determining a level of the first service module attribute; subsequent to said determining the level, storing in the relational table a first container of at least one container, said first container being pursuant to the category and the level of the first service module attribute that is associated with the first container; and subsequent to said storing the first container, repeating to perform said determining the category, said determining the level, and said storing the first container after setting the first container with a next container in the relational table until all containers are stored in the relational table. - View Dependent Claims (2, 3, 4, 5, 6, 7)
-
-
8. A computer program product, comprising a computer readable storage device having computer readable program code stored therein, said computer readable storage device not being a signal, said program code configured to be executed by a processor of a computer system to implement a method for interfacing between a caller application and a service module, said method comprising:
-
said processor 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, said processor building a service module data structure pursuant to the 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 need not manipulate the at least one caller application attribute in performing the transaction; subsequent to said building, said processor storing each service module attribute of the at least one service module attribute in a relational table of the service module data structure; subsequent to said storing, said processor servicing the request within the service module data structure, wherein said servicing results in instantiating the generic service document; and subsequent to said servicing, said processor returning the generic service document to the caller application; said service module being executed by the processor to perform said receiving the request, said building the service module data structure, said storing each service module attribute, said servicing the request, and said returning the generic service document, wherein said storing comprises; determining a category of a first service module attribute of the at least one service module attribute; subsequent to said determining the category, determining a level of the first service module attribute; subsequent to said determining the level, storing in the relational table a first container of at least one container, said first container being pursuant to the category and the level of the first service module attribute that is associated with the first container; and subsequent to said storing the first container, repeating to perform said determining the category, said determining the level, and said storing the first container after setting the first container with a next container in the relational table until all containers are stored in the relational table. - View Dependent Claims (9, 10, 11, 12, 13)
-
-
14. A computer system comprising a processor, a memory coupled to the processor, and a computer readable storage device coupled to the processor, said storage device containing program code configured to be executed by the processor via the memory to implement a method for interfacing between a caller application and a service module, said method comprising:
-
said processor 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, said processor building a service module data structure pursuant to the 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 need not manipulate the at least one caller application attribute in performing the transaction; subsequent to said building, said processor storing each service module attribute of the at least one service module attribute in a relational table of the service module data structure; subsequent to said storing, said processor servicing the request within the service module data structure, wherein said servicing results in instantiating the generic service document; and subsequent to said servicing, said processor returning the generic service document to the caller application; said service module being executed by the processor to perform said receiving the request, said building the service module data structure, said storing each service module attribute, said servicing the request, and said returning the generic service document, wherein said storing comprises; determining a category of a first service module attribute of the at least one service module attribute; subsequent to said determining the category, determining a level of the first service module attribute; subsequent to said determining the level, storing in the relational table a first container of at least one container, said first container being pursuant to the category and the level of the first service module attribute that is associated with the first container; and subsequent to said storing the first container, repeating to perform said determining the category, said determining the level, and said storing the first container after setting the first container with a next container in the relational table until all containers are stored in the relational table. - View Dependent Claims (15, 16, 17, 18, 19)
-
Specification