Wednesday, June 26, 2013

Multi-Site Deployment Issue




The reasons are clearly documented:

Multiple-Site configuration 





  • Close proximity of OpenSSO Enterprise servers in a LAN environment 
  • Underlying network infrastructure limitations exist. 
  • Operational domains are managed as independent units. 

Why is it so? What's the problem technically?





And thus, the following architecture is now made possible!




  1. Hello,

    the link to the openam-survival-tips is broken and I was not able to find it by searching on slideshare

    1. they changed the URL. I have updated the link. Try again

  2. What I did before is to spoof the session db hostname in the secondary site in its own /etc/hosts to point to its own session db. (provided there's no session sycnronization needed between sites, like for disaster recovery)

  3. Knowing about this "paid" patch, probably know why for the disappearance of the multi-site support in the roadmap for 10.2.

    For the new session DB model using OpenDJ (starting 10.1), it was in roadmap to support multi-site in 10.2
    See version 68 or before of the roadmap
    But was removed probably to only provide patch for support subscribers?

    1. I do not think it's a commercial thingy here. Most probably, some technical issue with OpenDJ sync. I'm just guessing here.