Document Example

A document management system safe-stores a document so that subsequent processing is recoverable. Then

• permanently stores the document on a central Data Base Management System,
• indexes the key elements,
• catalogs retrieval information and
• notifies interested parties.

 

Traditionally this involves a set of processes that:   Stores the document on a safe-store [RAID] so that it can be retrieved if any subsequent processing fails. Then: Permanently stores the document in a central Data Base Management System.   Develops an index on key elements in the document and stores these in a central master index.   Stores retrieval information about the document in a central catalog. Notifies any concerned users of the new document.

---

The problem with this approach is:

Each process is serial. The second process cannot start until the first is complete. The third process cannot start until the second is complete.

Multi threading^* the request solves this problem but it creates an even worse problem: How to manage these threads^*.

• What if a thread^* hangs, abnormally terminates, needs a new process itself or the System cannot handle any more threads^*?
• What if no reply is necessary or the reply should be sent somewhere else?
• What if the request takes longer than the user can wait or the 'hot' request needs immediate processing?
• What if an intermediate back out is necessary?
• What is the status of this request?
• What is the status of a prior request?
• Where is the congestion?

Tymeac^™ is the solution.

Tymeac^™ is a method of controlling threads^* that are asynchronous.

---

The same request using Tymeac™ involves a process that: Stores the document on a safe-store [RAID] so that it can be retrieved if any subsequent processing fails. Then: Invokes a method on the Tymeac™ Server. Tymeac™ brokers the request to four asynchronous-process queues, (with associated, well-managed threads*), and returns the result to the caller. This may be a synchronous request where the caller waits until all asynchronous threads* finish processing. This may be an asynchronous request where the caller receives an "in progress" message.  The actual processing takes place as a background event   * These are tasks for the CICS® version.