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;
said servicing comprising prior to said returning the generic service document;
performing the transaction;
subsequent to said performing the transaction, retrieving each mapping of at least one mapping in a mapping table of the service module data structure; and
subsequent to said retrieving, reloading each container of at least one container from the relational table into respective containers of the generic service document according to each retrieved mapping, wherein a first container of the at least one container is pursuant to a category and a level of a first service module attribute that is associated with the first container.
0 Assignments
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, which includes. 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. Servicing the request includes: servicing comprising: performing the transaction; reloading containers from the relational table into respective containers of the generic service document; and returning the generic service document to the caller application.
-
Citations
16 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; said servicing comprising prior to said returning the generic service document; performing the transaction; subsequent to said performing the transaction, retrieving each mapping of at least one mapping in a mapping table of the service module data structure; and subsequent to said retrieving, reloading each container of at least one container from the relational table into respective containers of the generic service document according to each retrieved mapping, wherein a first container of the at least one container is pursuant to a category and a level of a first service module attribute that is associated with the first container. - View Dependent Claims (2, 3, 4)
-
-
5. 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:
-
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; said servicing comprising prior to said returning the generic service document; performing the transaction; subsequent to said performing the transaction, retrieving each mapping of at least one mapping in a mapping table of the service module data structure; and subsequent to said retrieving, reloading each container of at least one container from the relational table into respective containers of the generic service document according to each retrieved mapping, wherein a first container of the at least one container is pursuant to a category and a level of a first service module attribute that is associated with the first container. - View Dependent Claims (6, 7, 8)
-
-
9. 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:
-
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; said servicing comprising prior to said returning the generic service document; performing the transaction; subsequent to said performing the transaction, retrieving each mapping of at least one mapping in a mapping table of the service module data structure; and subsequent to said retrieving, reloading each container of at least one container from the relational table into respective containers of the generic service document according to each retrieved mapping, wherein a first container of the at least one container is pursuant to a category and a level of a first service module attribute that is associated with the first container. - View Dependent Claims (10, 11, 12)
-
-
13. 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 computer system, wherein the code in combination with the computer system is configured to perform 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; said servicing comprising prior to said returning the generic service document; performing the transaction; subsequent to said performing the transaction, retrieving each mapping of at least one mapping in a mapping table of the service module data structure; and subsequent to said retrieving, reloading each container of at least one container from the relational table into respective containers of the generic service document according to each retrieved mapping, wherein a first container of the at least one container is pursuant to a category and a level of a first service module attribute that is associated with the first container. - View Dependent Claims (14, 15, 16)
-
Specification