Centrally Hosted Regional Deployment, More than One Instance of AgilePoint Server

This diagram shows an example of a regional AgilePoint NX deployment with a more than one instance of AgilePoint Server.

Figure: Centrally Hosted Regional Deployment More Instances
Centrally Hosted Regional Deployment More Instances

Main Points

  • Users from other regional teams do not have access to your region's processes since each instance gets its own database instance. This gives you strict control over your processes.
  • Because each team has its own AgilePoint Server, business time calculation and holiday schedule can be effectively controlled for each region. As such, you will not have a task due on a holiday.
  • Physical hardware cost can be controlled since all teams can share same physical hardware but at same time maintain their own database instance.
  • In case you prefer to have centralized upgrades for all teams then this is a good option since you can run upgrade once on the server and all instances get upgraded.
  • Upgrades cannot be planned independently so all teams need to plan for upgrades together.
  • Offshore teams can notice some level of performance decrease if the network connection to remote server is not good.