Best Practicies: Centralized Deployment Scenario
I want to share some knowledge from the upcoming Best Practices document.
As you might know from the ActiveRoles Sever Quick Start Guide document there are some typical deployment scenarios. Let’s talk about the centralized one.
Centralized scenario means that all ARS instances are deployed at single data center (say, in North America) and they manage all lo
cal and remote sites/domains (EMEA and APAC, for example), as shown at the picture:
In this case ARS instance in Notrh America (NA) data center (or few for load balancing) are sharing single database. Management History database will provide 7 day history of changes and is stored as part of configuration database.
As you can see, ARS Service and Web Interface are installed either on separate servers or co-located at one physical server.
EMEA and APAC delegated administrators logon to main NA’s Web Interface connected with NA’s administration service that, in turn, utilize Operation DCs of the region the administrator come from. This model allows the change to happen immediately in the origin region.
This deployment is reccomended for medium- sized companies, or companies with centralized help desk.
In our next post we would provide some best practices on deploying ARS in de-centralized environment with help desk spread across geographical locations.