Browse Prior Art Database

Applying OS/2 multi-thread function for former data processing and objects

IP.com Disclosure Number: IPCOM000013330D
Original Publication Date: 2001-Feb-01
Included in the Prior Art Database: 2003-Jun-18
Document File: 3 page(s) / 116K

Publishing Venue

IBM

Abstract

Brief description : A system is disclosed that the use of multi-threaded application is designed for high performanced image workflow system in client-server environment. The technique is design concept of thread model for client application programming which automates: (1) Retrieving queued work item, (2) Pre-loading work item data including images from DB2 database (BLOB) into local disk, (3) Showing the image data and character data to user to get user's verify on client PC. The key point of this image work flow system is the use of 'pull model' with the OS/2 multi-threading programming. While the user review/modify image and its character data, following data pre-loading is performed by sub-thread which we call pre-loading thread. The pre-loading thread attempts to read the image and character data until it reaches limit count. The pre-loading thread also attempts to 'check-out' work flow instances (WFIs) until it reaches the maximum WFI count. (WFI is like container for the work item which is managed by work flow management software which we call WFM in this article.) Using this technique, user can review/modify image and character data continuously with no-wait. System overview: The system consists of application database server, a workflow server, and client workstations. The application database server is a huge database server which contains image and its character data. The workflow server maintains entire workflow instances and provides file directory for each WFI. Figure 1 shows systems overview. As described in previous section, the WFI is kind of container for some of business work items. Figure 2 shows ER diagram to describe relationship between work item, WFI and WFM. A WFI has two states such as 'checked-in' and 'checked-out'. And the WFI is assigned to one user when it is 'checked-out'. This type of exclusive control is performed by WFM.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 48% of the total text.

Page 1 of 3

Applying OS/2 multi-thread function for former data processing and objects

   Brief description :
A system is disclosed that the use of multi-threaded application is designed for high
performanced image workflow system in client-server environment. The technique is design
concept of thread model for client application programming which automates:

(1) Retrieving queued work item,
(2) Pre-loading work item data including images
from DB2 database (BLOB) into local disk,
(3) Showing the image data and character data to user to get user's verify on client PC.
The key point of this image work flow system is the use of 'pull model' with the OS/2
multi-threading programming. While the user review/modify image and its character data,
following data pre-loading is performed by sub-thread which we call pre-loading thread. The
pre-loading thread attempts to read the image and character data until it reaches limit count.
The pre-loading thread also attempts to 'check-out' work flow instances (WFIs) until it reaches
the maximum WFI count. (WFI is like container for the work item which is managed by work flow
management software which we call WFM in this article.) Using this technique, user can
review/modify image and character data continuously with no-wait.

   System overview:
The system consists of application database server, a workflow server, and client workstations.
The application database server is a huge database server which contains image and its character
data. The workflow server maintains entire workflow instances and provides file directory for
each WFI. Figure 1 shows systems overview. As described in previous section, the WFI is kind of
container for some of business work items. Figure 2 shows ER diagram to describe relationship
between work item, WFI and WFM.

   A WFI has two states such as 'checked-in' and 'checked-out'. And the WFI is assigned to one
user when it is 'checked-out'. This type of exclusive control is performed by WFM.

   Standing application program on client PC (disclosure points):
Typical workflow software provides an user interface which shows queued work list (WFI) view
for the user. And the user picks up one of them to check it out prior to start working, then WFM
starts application program associated with the WFI as an operating system process. This process
initiation causes performance overhead if:

- the unit of work item has to be processed in short time; or
- the user has to check out and work in same type of work item
like this application.

However the WFM of this system provides API to maintain WFI state by the client application
program. This is one of key points of this system that the application program itself controls
the starting and ending WFI by calling WFM APIs. See figure 3 for the relationship between
application program and WFM.

   The client application program is active whenever the user is working on the PC. We call it
'standing application' in this article. As described above, the standing application consists
of two threads:

   - Ma...