Portable and dynamic distributed applications architecture
First Claim
1. A computer-accessible medium storing a global transaction information table for use by a dialog flow manager when processing a transaction, the global transaction information table comprising:
- an overhead containing a plurality of pointers as well as containing a plurality of fields for designating information about said transaction;
at least one of said plurality of pointers pointing to an entry in a transaction panel entries table;
at least one of said plurality of pointers pointing to an entry in a transaction language entries table; and
at least one of said plurality of pointers pointing to an entry in a transaction procedure entries table.
2 Assignments
0 Petitions
Accused Products
Abstract
A system and method is shown for enabling a plurality of computers and associated computer resources, some or all of which my be of heterogeneous configuration, to cooperatively process various application such that the execution is transparent to the user regardless of where the application is actually executing. This distributed applications architecture performs an information distribution service between multiple transaction processing systems by working with a transaction processor via communication channels to other hosts within the network and a dialog manager which uses a transaction processor via communication channels to other hosts within the network and a dialog manager which uses a transaction processor interface to communication with the transaction processor. The architecture employs a map service which provides an editor to create the maps for the application panels, a compiler to generate the maps into a linkable form, and linkable interpreter which translates the linkable form into the screen presentation format for that platform. To distribute an application, the source code for the procedures, views and panels are moved as a block to the new system. This is possible because once the application source code is complete, all application logic, user interface control tables, view definitions, and other application specific tables for one transaction definition are packaged by the present invention in a single load module on the system where the application will reside. The load module is then compiled using the target system'"'"'s compiler, link editor, and bind process. Thus, all environment-dependant variation of import/export are automatically integrated with the application at load module bind time, requiring no source code changes.
89 Citations
54 Claims
-
1. A computer-accessible medium storing a global transaction information table for use by a dialog flow manager when processing a transaction, the global transaction information table comprising:
-
an overhead containing a plurality of pointers as well as containing a plurality of fields for designating information about said transaction; at least one of said plurality of pointers pointing to an entry in a transaction panel entries table; at least one of said plurality of pointers pointing to an entry in a transaction language entries table; and at least one of said plurality of pointers pointing to an entry in a transaction procedure entries table. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53)
-
-
54. A transaction load module which is treated as an indivisible unit by a transaction processing system thereby ensuring load module integrity and synchronous installation of all components of a transaction, comprising:
-
a global transaction information table having a table of referenced internal procedures, a table of referenced external procedures, an input view associated with each of said internal procedures, an input view associated with each of said external procedures, an output view associated with each of said internal procedures, an output view associated with each of said external procedures, a profile view associated with each of said internal procedures, a profile view associated with each of said external procedures, a table of all referenced panels, a refresh procedure associated with each referenced panel, and an input procedure associated with each referenced panel; views associated with a specific transaction; panels associated with a specific transaction; transaction procedures; a set of resources used in conjunction with said transaction procedures; and a working storage for processing said specific transaction in light of said views, panels, procedures and resources; said table, views, panels, procedures, set of resources, and working storage being combined within in one load module.
-
Specification