up to Managing distribution on the server side
The table distTarget describes a collection of like data to be distributed.
mysql> select * from distTarget where dist_group = 'MD01' and stage = 'warp'; +-----------+------------+---------+-------+-------+---------+---------+ | target_id | dist_group | filter | stage | clean | state | comment | +-----------+------------+---------+-------+-------+---------+---------+ | 742 | MD01 | g.00000 | warp | 0 | enabled | NULL | | 744 | MD01 | i.00000 | warp | 0 | enabled | NULL | | 743 | MD01 | r.00000 | warp | 0 | enabled | NULL | | 746 | MD01 | y.00000 | warp | 0 | enabled | NULL | | 745 | MD01 | z.00000 | warp | 0 | enabled | NULL | +-----------+------------+---------+-------+-------+---------+---------+ 5 rows in set (0.00 sec)
Targets are created by the disttool. For example the first target in the list above might have been created by the command
disttool -definetarget -dist_group MD01 -filter g.00000 -stage warp
There is a script in the ipp tree tools/maketargets which makes it easy to add multiple targets.
perl definetargets --dist_group M31 --stage all --dbname new
(Use with care. The command above creates 35 targets. 7 stages x 5 filters)
Note: Until recently (2009-10-14) targets were specified by label. We decided that labels were too numerous and that we wanted the flexibility to change labels from time to time (To manage cleanup and update processing for example).
The dist_group may be set either by the -definebyquery command that defines the run or by the -updaterun mode of the various ipp tools
