Differences between revisions 1 and 5 (spanning 4 versions)
Revision 1 as of 2010-05-31 12:08:46
Size: 2119
Editor: abr
Comment:
Revision 5 as of 2010-05-31 14:19:50
Size: 3246
Editor: abr
Comment:
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
= Task TITLE = = Task Update Tracker =
Line 8: Line 8:
 Title::  Title:: Task Update Tracker
Line 23: Line 23:


The goal of this task is to establish the Update Tracker mechanism in DOMS. The update tracker will provide the following functionality to DOMS
1. Request Entry Pids changed since a given date.


== Design ==

The Update tracker will consist of a number of components.

 1. A database, called DB.
 1. A JMS client
 1. The update tracker service.

The database will have two tables.
 1. Entry Pid - Date changed - View Name: Associates each entry pid/view name combo with a changed date
 2. Object Pid - Entry Pid - View Name: Associates each pid in DOMS with a entry pid/view name combo.

There are two main flows in the service

 1. Update:
  1. JMS client will be notified upon change to an object
  1. The object pid is looked up to a set of entry pid/ view name combos.
  1. Each of these combos is looked up, and the corresponding entry has date changed updated.
  1. If the change was in RELS-EXT:
   1. For each view for the entry object
   1. Request the view from ECM
   1. Update the pid-entry-view table
 1. Lookup
  1. Lookup in the first table




Task Update Tracker

Title
Task Update Tracker

State
Not started

Time used

Time estimated

Description

The goal of this task is to establish the Update Tracker mechanism in DOMS. The update tracker will provide the following functionality to DOMS 1. Request Entry Pids changed since a given date.

Design

The Update tracker will consist of a number of components.

  1. A database, called DB.
  2. A JMS client
  3. The update tracker service.

The database will have two tables.

  1. Entry Pid - Date changed - View Name: Associates each entry pid/view name combo with a changed date
  2. Object Pid - Entry Pid - View Name: Associates each pid in DOMS with a entry pid/view name combo.

There are two main flows in the service

  1. Update:
    1. JMS client will be notified upon change to an object
    2. The object pid is looked up to a set of entry pid/ view name combos.
    3. Each of these combos is looked up, and the corresponding entry has date changed updated.
    4. If the change was in RELS-EXT:
      1. For each view for the entry object
      2. Request the view from ECM
      3. Update the pid-entry-view table
  2. Lookup
    1. Lookup in the first table

Sub tasks

Title State Time used Time estimated

Documentation

Progress history

Iteration Time used Status Notes Tasks adressed

Tasks/25 (last edited 2010-06-09 09:26:42 by abr)