System for transactional processing between an information processing server and a plurality of workstations

• US 5,596,750 A
• Filed: 06/08/1993
• Issued: 01/21/1997
• Est. Priority Date: 06/09/1992
• Status: Expired due to Fees

• Current Assignee: Bull Sas (Atos SE)
• Original Assignee: Bull Sas (Atos SE)
• Inventors: Li, Jianzhong, Abdelmoumni, Mohammed, Brunon, Jean-Philippe
• Primary Examiner(s): Kriess, Kevin A.
• Assistant Examiner(s): Richey, Michael T.
• Application Number:
  US08/071,766
• Time in Patent Office: 1,323 Days
• Field of Search: 395/650, 395/700, 395/600, 364/281.3, 364/281.8, 364/282.1, 364/284.3, 364/974
• US Class Current: 718/101
• CPC Class Codes: G06F 9/466 Transaction processing
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing
• CPC Class Codes: Y10S 707/99948 Application of database or data structure, e.g. distributed, multimedia, or image

Abstract

A system for transactional processing between an information processing server (3) and a plurality of workstations (2) between which the jobs corresponding to activities constituting procedures are executed, the system including, on the server side, a scheduler module for scheduling the progress of the jobs; a dispatcher module (31) for performing the distribution of the tasks which are based on the relationship between a role and an actor; a signaler module (34) for preserving a trail of times events and receiving information from the scheduler (30) and from a coordinator module (31); a message box (35) exchanging signals on the one hand with the dispatcher (33) and signaler (34) modules, and on the other hand with a module (36) for communication with the workstations and a data management module for the work flow (370), the system including on the part of the workstation a communications layer (27), a message management layer (26) corresponding to the work flow, a layer (24) including various sets of interfaces of applications programming, a management services layer (25), and a user interface layer (20, 21).

Claims

1. A system for transactional processing, comprising:

an information processing server (3) and at least one workstation (2) between which jobs corresponding to activities defined by procedures are executed, the server including a relational data base (37) for communicating with a message box (35), a scheduler module (30) for scheduling the execution of the jobs, said scheduler module being operable upon the completion of an activity to define a next activity and create at least one task necessary to complete the next activity;

a dispatcher module (33) for communicating between the scheduler and the message box for performing distribution of the task which is based on information defining a role and an actor stored in the relational data base which assigns a task to the actor, said dispatcher module being operable to selectively assign a task to the actor based on the work load of the system;

a notifier module (34) for communicating between the scheduler, a coordinator and the message box for preserving a log of system times and events, said notifier module being operable to receive information from the scheduler module (30) and from a coordinator module (31) which performs internal management monitoring of the server;

the message box (35) being operable to exchange signals between the dispatcher (33) and signaler (34) modules;

a communication module (36) for communication with the workstation;

a data management module (370) for managing the work flow; and

further wherein the workstation includes a communications layer (27), a message management layer (26) corresponding to work flow, an applications layer (24) including applications programming interfaces, a management services layer (25), and a user interface layer (20,

     21).

2. The system of claim 1, wherein the interface layer, applications layer and management service layer each include a plurality of modules therein which have no interaction between one another.

3. The system of claim 1, wherein the data management module (370) manages static tables and dynamic tables stored in the relational data base.

4. The system of claim 3, wherein the static tables include procedure definition and activity definition data, data on the organization of actors and roles, and data on the distribution of activities defining a distribution table.

5. The system of claim 3, wherein the dynamic tables include open-ended data representing the progress of the jobs and tasks.

6. The system of claim 3, wherein the dynamic tables include a circulation table, a job data vector table JDV-JDV, activity data vector table ADV-ADV, and SCHED-STATEP, SCHED-STATUSP, SCHED-JOBS, SCHED-TASKP tables.

7. The system of transactional processing of claim 4, wherein the static tables include a procedure description table SCHED-PROCEDURE, for description of procedure data JDV-PDDEF, a reference table for description of references of the data stored in an external data base (EDA-ORA), an activities table for description of activities SCHED-ACTIVITY, a precedence table defining precedences SCHED-PRECEDENCE, and organization tables defining the organization of the system ORGA-ACTOR, ORGA-ROLE, ORGA-R-OFF-ACT.

8. The system of claim 4, wherein an activity includes an identifier of the activity, a procedure to which the activity is connected and a list of actions each including an initialization command and a validation command.

9. The system of claim 8, wherein the actions include the type of action, a name of the action, and arguments constituted by the data of the vector JDV and ADV.

10. The system of claim 1, wherein the management service layer (25) includes the following:

a job creation management service;

an administration management service;

a coordination management service; and

a service for management of the execution of the activity.

11. The system of claim 8, wherein an activity includes a prefix (PR) for calling on a presentation and interaction software furnishing an interface for the activity.

12. The system of claim 1, further including an administrator module which performs the function of modeling, creation, testing and matching of the modules of the system.

13. The system of claim 12, wherein the data management module (37) has the function of attaching appropriate data to specific jobs, creating vector JDV, managing integrity of the data, and retrieving and accessing user data bases.

14. The system of claim 13, wherein the management service layer includes an activity execution management module (252) having the following functions:

reading an activity description file;

reading and writing job data used in the activity;

reading and writing corresponding task data used in the activity and controlling right of access to the job data; and

starting an appropriate presentation form for the activity and executing actions corresponding to the activity in a guided manner.

15. The system of claim 14, wherein the management service layer includes a tasks management module which executes the following functions:

receiving an offered task;

accepting an offered task;

searching for corresponding data of a job vector in the server;

completion of a task;

restoration of the updated job vector to the server;

redirection of a task to a different actor or a different activity;

calling up the activity of execution of a corresponding task by the user interface; and

processing and locally preserving data corresponding to the tasks, and the task history.

16. The system of claims 12, wherein the coordinator module includes the functions of data editing and control of the jobs.

17. The system of claim 1 wherein the dispatcher module (33) performs three main functions:

assigning a user the tasks that have just been created by the scheduler;

assigning a new user a task that has just be rejected; and

performing distribution and circulation of the activities among the users.

18. The system of claim 1, characterized in that the notifier module (34) includes a recall function for recalling an event from the log when a predetermined time has expired and a delay function for delaying the starting of an event for a predetermined period of time.

19. The system of of claim 1 wherein the message box (35) includes a first data table which contains the description of the messages, and a second data table which stores the addressees of the messages.

20. The system of claim 1 wherein the data management module (37) has the function of attaching appropriate data to specific jobs, creating vector JDV, managing integrity of the data, and retrieving and accessing user data bases.

21. The system of claim 1, wherein the management service layer includes an activity execution management module having the following functions:

reading an activity description file;

reading and writing job data used in the activity;

reading and writing corresponding task data used in the activity and controlling right of access to the job data; and

starting an appropriate presentation form for the activity and executing actions corresponding to the activity in a guided manner.

22. The system of claim 1, wherein the management service layer includes a tasks management module which executes the following functions:

receiving an offered task;

accepting an offered task;

searching for corresponding data of a job vector in the server;

completion of a task;

restoration of the updated job vector to the server;

redirection of a task to a different actor or a different activity;

calling up the activity of execution of a corresponding task by the user interface; and

processing and locally preserving data corresponding to the tasks, and the task history.

23. The system of claim 1, wherein the coordinator module includes the functions of data editing and control of the jobs.

24. The system of claim 16, wherein the dispatcher module performs three main functions:

assigning a user the tasks that have just been created by the scheduler;

assigning a new user a task that has just be rejected; and

performing distribution and circulation of the activities among the users.

25. The system of claim 17, characterized in that the signaler module includes a recall function for recalling an event from the log when a predetermined time has expired and a delay function for delaying the starting of an event for a predetermined period of time.

26. The system of of claim 19, wherein the message box includes a first data table which contains the description of the messages, and a second data table which stores the addressees of the messages.

27. The system of claim 1, wherein the scheduler module (30) is operable to create a job and assign said job a unique number, to define status information for said job and perform initializations, said scheduler module further being operable to finalize work through a job completion facility when all activities for a job have been done and to verify, through a verification facility, all predecessors of possible successors of a completed activity.

28. The system of claim 1, wherein modules of one layer of the workstation have no interaction among themselves.

29. The system of claim 17, wherein the dispatcher includes a first function to indicate the status of the task in a "sched" job table as "OFFERED" and enable sending of a message to a user intended to perform the job, and a second function changing the status in the sched job table to "rejected" and indicating when the dispatcher has received said message when a user rejects a task that the user cannot execute.

30. The system of claim 19, wherein the second data table stores other information, including status of messages, said status comprising:

TO READ, signifying that the message is available;

READ, signifying that the message has been read; and

TO DELETE, signifying that the message has been deleted.