Abstract: A method and associated system for interfacing between a caller application and a service module. A service module builds a service module data structure pursuant to a previously received request. The request includes at least one caller application attribute describing the 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 requests serviced within the service module data structure, resulting in instantiating the generic service document. The generic service document is returned to the caller application. Building each service module attribute includes: constructing the generic service document and creating at least one container in the generic service document. Each container is respectively associated with each service module attribute in each mapping of at least one mapping.

Abstract: A method and system for interfacing between a caller application and a service module. A request for performing a transaction from the caller application is received. The request includes at least one caller application attribute describing the request. A service module data structure is built 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, which results in instantiating the generic service document. The generic service document is returned to the caller application.

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.

Abstract: A method and associated system for interfacing between a caller application and a service module. A service module builds a service module data structure pursuant to a previously received request. The request includes at least one caller application attribute describing the 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 requests serviced within the service module data structure, resulting in instantiating the generic service document. The generic service document is returned to the caller application. Building each service module attribute includes: constructing the generic service document and creating at least one container in the generic service document. Each container is respectively associated with each service module attribute in each mapping of at least one mapping.

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. Building each service module attribute includes: constructing the generic service document and creating at least one container in the generic service document. Each container is respectively associated with each service module attribute in each mapping of at least one mapping.

Abstract: A method and system for interfacing between a caller application and a service module. A request for performing a transaction from the caller application is received. The request includes at least one caller application attribute describing the request. A service module data structure is built 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, which results in instantiating the generic service document. The generic service document is returned to the caller application.

Abstract: A system and associated method for receiving an unlimited number of data items modified by a Web transaction. A processor requests a service from a Web-service program by sending the service program a set of data items and a client identifier. The Web-service program responds with a Web-interface program identifier and a user session identifier. The processor uses the session identifier, the Web-interface program identifier, and a storage location of the data items to open a session with a Web-interface program, during which the processor directs the Web-interface program to modify the data items and store them on a data storage device without interacting with the Web-service program. When the user session terminates, the processor requests from the Web-service program the modified data items and the Web-service program sends the data items to the processor without involvement of the Web-interface program.

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. Building each service module attribute includes: constructing the generic service document and creating at least one container in the generic service document. Each container is respectively associated with each service module attribute in each mapping of at least one mapping.

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.

Abstract: A system and associated method for receiving an unlimited number of data items modified by a Web transaction. A processor requests a service from a Web-service program by sending the service program a set of data items and a client identifier. The Web-service program responds with a Web-interface program identifier and a user session identifier. The processor uses the session identifier, the Web-interface program identifier, and a storage location of the data items to open a session with a Web-interface program, during which the processor directs the Web-interface program to modify the data items and store them on a data storage device without interacting with the Web-service program. When the user session terminates, the processor requests from the Web-service program the modified data items and the Web-service program sends the data items to the processor without involvement of the Web-interface program.

Abstract: The invention provides a method, system, and program product for processing an electronic document. In one embodiment, the invention includes determining a procedure applicable to the electronic document; defining at least one step of the procedure; in the case that the at least one step includes a plurality of steps, determining an order of the plurality of steps; determining whether the at least one step applies to the electronic document; applying an algorithm for carrying out the at least one step; applying a completion algorithm; determining whether the procedure includes an additional step for which an algorithm has not been applied; and in the case that the procedure includes an additional step for which an algorithm has not been applied: determining whether the additional step applies to the electronic document; applying an algorithm for carrying out the additional step; and applying a completion algorithm.

Abstract: A hybird Notes/DB2 environment provides a requisition catalog on the Web. Client browsers are connected to a GWA infrastructure including a first network dispatcher and a virtual cluster of Domino.Go servers. The network dispatcher sprays out browser requests among configured .nsf servers in virtual server cluster. Communications from this virtual server cluster are, in turn, dispatched by a second network dispatcher servers in a Domino cluster. External objects, primarily for a GUI, are served in a .dfs and include graphic files, Java files, HTML images and net.data macros. The catalog is built from supplier provided flat files. A front end is provided for business logic and validation, as also is a relation database backend. HTML forms are populated using relational database agents. A role table is used for controlling access both to Notes code and DB2 data. Large amounts of data is quickly transferred using an intermediate agent and window.

Abstract: The present provides a standard text method, system, and program product for configuring blocks of text and for defining the circumstances under which the blocks of text are to be displayed to users by multiple applications. The method comprises: providing a block of text to be published; selecting at least one application that will use the block of text; defining at least one business entity to which the block of text pertains; defining criteria under which the block of text will be used by each selected application; and repeating the above steps for each additional block of text to be published.

Abstract: A method, system and computer program product for communicating requests to multiple destinations in a business transaction are disclosed. A mass request is communicated to a processing center, the mass request including an identification portion and a content portion. The identification portion is used to obtain a parent attribute common to requests to all destinations. The content portion is parsed to generate multiple content strings corresponding to the multiple destinations. The parent attribute and each content string is combined to generate an individual request to a respective destination.

Abstract: Under the present invention, when a requestor submits a request for an item, a single, appropriate back-end system for processing the request is identified. Typically, the back-end system is identified based on the item requested and a location setting within the requestor's profile. The location setting generally indicates the requestor's geographic location and their job responsibility. Once a particular back-end system is identified, subsequent requests in the same order are limited to items that are associated with the identified back-end system. If the requester attempts to request an item that is not available via the identified back-end system, an error message is displayed.

Abstract: A method, system and computer program product for communicating requests to multiple destinations in a business transaction are disclosed. A mass request is communicated to a processing center, the mass request including an identification portion and a content portion. The identification portion is used to obtain a parent attribute common to requests to all destinations. The content portion is parsed to generate multiple content strings corresponding to the multiple destinations. The parent attribute and each content string is combined to generate an individual request to a respective destination.

Abstract: A method, system and computer program product for conducting an electronic business are disclosed. An attribute of a business partner is used to identify the business partner. Business partners having the same attribute will be grouped as a business partner group. The business partner group will be used in conducting a business transaction.

Abstract: A method, system and computer program product for providing user identification to multiple destinations in a business transaction are disclosed. A user registers with a processing center and communicates a request for providing identification information to multiple destinations thereto. Identification message attributes required by each of the multiple destinations are determined, and user identification information is retrieved by the processing center. The user identification information is combined with the identification message attributes to generate identification messages to the respective destinations.

Abstract: The invention provides a method, system, and program product for processing an electronic document. In one embodiment, the invention includes determining a procedure applicable to the electronic document; determining whether each step of the procedure applies to the electronic document; recording whether a step of the procedure applies to the electronic document; and reporting the recorded result.

Abstract: The invention provides a method, system, and program product for processing an electronic document. In one embodiment, the invention includes determining a procedure applicable to the electronic document; defining at least one step of the procedure; in the case that the at least one step includes a plurality of steps, determining an order of the plurality of steps; determining whether the at least one step applies to the electronic document; applying an algorithm for carrying out the at least one step; applying a completion algorithm; determining whether the procedure includes an additional step for which an algorithm has not been applied; and in the case that the procedure includes an additional step for which an algorithm has not been applied: determining whether the additional step applies to the electronic document; applying an algorithm for carrying out the additional step; and applying a completion algorithm.