Timeline for Content Management System with a separate Publisher Server
Current License: CC BY-SA 3.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 11, 2013 at 15:28 | vote | accept | DanielGLB | ||
| Apr 11, 2013 at 7:33 | history | edited | Nuno Linhares♦ | CC BY-SA 3.0 |
Added some more clarity on publisher/transport relationship
|
| Apr 11, 2013 at 7:15 | history | edited | Nuno Linhares♦ | CC BY-SA 3.0 |
Added info on transport service
|
| Apr 10, 2013 at 21:35 | comment | added | DanielGLB | That's what I thought too. In fact this relationship is shown well in the server manager>Configuration>Services when start, stop or restart one of them (for example stop transport service causes the publisher service to stop too). So, in any case, both services should run in the same machine? | |
| Apr 10, 2013 at 18:52 | comment | added | Bart Koopman | If I remember correctly the transport service is connected to the publisher, so every publisher machine gets its own transport service as well. | |
| Apr 10, 2013 at 18:30 | comment | added | DanielGLB | Thanks @BartKoopman. About the transport service in this scenario it would be possible (and recommended) to place next to the publisher service (in the same machine)? | |
| Apr 10, 2013 at 17:13 | comment | added | Bart Koopman | I meant using the same process of installation as Nuno described, sorry that wasn't very clear. So I was referring to adding an extra publisher machine indeed. | |
| Apr 10, 2013 at 16:54 | comment | added | DanielGLB | Thanks @DominicCronin, I really love this site. UDP message... great information! Seems to be much more optimized for dealing with publish queue (helps decrease latency times) like you have said. | |
| Apr 10, 2013 at 16:48 | comment | added | DanielGLB | @BartKoopman excuse me, I am not sure what you mean by "another publisher using the same process", it is about multi-threating? Set another publisher server? Thanks again! | |
| Apr 10, 2013 at 16:33 | comment | added | DanielGLB | Thanks Nuno for your quick response. I really appreciate your time. Thinking in others scenarios I wonder if it would be possible (I have not seen anything about that in the documentation) to scale out also the transport service? Thanks again! | |
| Apr 10, 2013 at 15:49 | comment | added | Dominic Cronin | Perhaps also worth mentioning queue notification. When an item is queued for publishing (on the editorial CM server) a UDP message is sent to any CM servers that are running a publisher and configured for this (on by default). This informs the publisher that there are tasks on the queue to be processed, and removes the need to wait for the polling interval before the queued item is picked up. | |
| Apr 10, 2013 at 15:42 | comment | added | Bart Koopman | perhaps good to mention that adding yet another publisher using the same process is just as easy to double the publishing power again (or even just starting the publisher service on the CM box to deal with a temporary high publishing load). As Nuno mentioned the publisher services are already designed for dealing with multiple instances out of the box. | |
| Apr 10, 2013 at 14:47 | history | answered | Nuno Linhares♦ | CC BY-SA 3.0 |