Say you want to take your publishing instance offline, do some maintenance, then bring it back online again and catch it up on any activation requests that occured while it was offline. I thought to disable the replication agent but if one does that it seems the replication queue goes with it and you don't get activations requets queued up to process when you re-enable the replication agent.
I've read that is possible to configure the replication agent with an invalid target hostname:port for it's target publishing instance but that this method should only be used over a short outage. I'm talking about an outage a bit over 24 hours.
