distributed EM

Some countries (ahem; Canada and the USA) are huge. I'm talking HUGE. Thousands and thousands of miles.

​Some companies have sites in multiple countries, all over the globe. That's even more of a challenge than being limited to just one country's geography.

Wouldn't it make sense to offer an Enterprise Manager which can span long distances, even over relatively slow networks?

One could have, for example, five EM repositories replicating each other (not instantly of course), with multiple OMS sites. Need not be one OMS per repository, could be 2-3 OMS sites per repository. Each OMS would know where all the repositories are and decide which one to use depending on availability and performance of the link to each repository (like what Internet routers do when they decide where to send packets).

One EM agent on each target host.

Thousands of monitored hosts.

Each user connected to an OMS, when selecting a host to work on, would then connect directly to the agent of the monitored host they are working on with info sent to the OMS now and then for such things as status updates and changes made. Probably the agent on the host could handle that. This would be to avoid routing packets all over the place, just send them where they need to go.

Don't care about clustering, really, but some organizations or businesses might insist on having that for each repository and each OMS since EM is used to manage most of the infrastructure. Most sites wouldn't need this though, especially if they are running on UNIX. ​

​How about it?​

• Patrice My profiles: [image: Facebook] <http://www.facebook.com/home.php?#!/profile.php?id=100000206805521>[image: LinkedIn] <http://ca.linkedin.com/pub/patrice-boivin/a/933/5a9>[image: Twitter] <http://www.twitter.com/PatriceBoivin>

--
http://www.freelists.org/webpage/oracle-l