May 8, 2008 at 2:45 am
Erik Bitemo is correct that you can only have one [first-level] Distributor, and rbarryyoung has already suggested the republish option to cascade Distributors, so that SHOULD be your solution for scaling.
Often the subscribers fall within geographic regions, so you might have
[font="Courier New"]Publisher Rome
Distributor Rome
sub1_1 London
sub1_2 New York
sub1_3 Singapore
sub1_4 Moskow
sub1_5 Nairobi
DistribUK London
sub1_1 Cardiff
sub1_2 Edinburgh ...
sub1_20 Manchester
DistribNA New York
sub2_1 Washington ...
sub2_20 Denver
DistribAP Singapore
sub3_1 Hong Kong
sub3_20 Tokyo[/font]
etc, so each of the 5 first-level subs would get 30 articles each and redistribute to final leaf subs
- but even if you are not geog dispersed the same principles would apply.
HTH
Dick
May 8, 2008 at 3:05 am
dbaker (5/8/2008)
Erik Bitemo is correct that you can only have one [first-level] Distributor, and rbarryyoung has already suggested the republish option to cascade Distributors, so that SHOULD be your solution for scaling.Often the subscribers fall within geographic regions, so you might have
[...cut...]
etc, so each of the 5 first-level subs would get 30 articles each and redistribute to final leaf subs
- but even if you are not geog dispersed the same principles would apply.
HTH
Dick
yes, thank you guys for the help, this is the solution we've implemented.
simply republishing data, and it seems to work.
the problem was: 150 publications on the same machine...too much for the hardware.
thanks again!
Viewing 2 posts - 16 through 16 (of 16 total)
You must be logged in to reply to this topic. Login to reply