
the NCM and NPM servers don't have to be the same box, if SAM and NPM could interact and not be on the same server, that might be very nice!
The server wouldn't have to be as powerful and you wouldn't have any worry about NPM interfering with SAM (one taking all the cpu or ram from the other).
Just a thought I wanted to throw out there so you guys could let it rattle around in your head over the next couple years (SAM 6.0?).
(and I figured developers might be a little more connected to the beta forum than the Feature Request forum)
uh, I guess I should have re-read that title.. this is *not* the right area.
Options for this deployment scenario currently exist today. The most obvious of course would be to leverage an additional poller and dedicate it to SAM. This is what most customers who are looking to separate services are doing. This way they retain all the benefits of a single instance, unified web console that's also easily compatible with the additional web server. The second option is to have two standalone instances, one dedicated to SAM, and the other to NPM and use the Enterprise Operations Console to provide a single pane of glass view into your entire infrastructure.