Good question! I would like to know any hints too?!

For example, one would need to install new Product Update for large scale testing. The same server as production would be natural option, if there is a way to have new and old simultaniosly on the same OS.

Why would you want to do this?
By the way, mongodb runs on a specific port. So, if you had to use two different mongodb instances you'd have to use two different ports, and each Syracuse server would have to specify the correct port in the set up screens.

I'm still confused why you have this requirement.
Bob

Another example would be Sage HR installation. Sage X3 is on PU8 or PU9 Syracuse. But Sage HR is still on Syracuse v7.1. Can we have X3 and HR on the same production server and how?

Just a thought here, what if you needed to do windows patching for Sage HR, and that blew up the Sage HR server for some unknown reason (we'll blame on Bill Gates and Microsoft)? That would also obliterate Sage X3. To me that seems risky in that you are compounding, and co-mingling your risk.

Cheers,
Bob

Bob,

We understand that there are third party risks even within vendor supported solutions.

You answered MogoDB part of the original question. But, to my mind, general question is still open.

I would expect someone to verify any of following options:

1) Statement by Sage like: "This is unsupported configuration, experiment and use at your own risk!"
2) Guideline by Sage like: "do this and that, then you are safe..."
3) Guideline by someone else: "We did this and that, works like a clock! Try! Beware of this and that..."
4) Statement by Sage or someone else: "This is not possible due to this and that! We experimented for weeks and could not overcome 'this'/'these' obstacle(s)!"

Regards,