Network Topology

The number of concurrent Civic Platform users provides the single best criterion that predicts system load (number of transactions, searches, and so forth). This section provides sample topologies for small (less than 50), medium (50 to 200) and large (more than 200) numbers of Civic Platform users.

Note: Transactions that originate from public users (Citizen Access or Accela Mobile apps users) create the same load on the Civic Platform back end as similar transactions that originate from Civic Platform users.

General Deployment Guidelines

  • If the agency intends to provide map services to Citizen Access users, the Accela GIS Server must be deployed in the same DMZ with the Citizen Access Server for better performance. Otherwise, the Accela GIS Server can be deployed in the Data Center along with the Civic Platform and GIS server back-end components as shown in the topology diagram.
  • If the agency intends to provide map services to Mobile Office users, the Accela GIS Server must be deployed in the same DMZ with the Mobile Office Server for better performance. Otherwise, the Accela GIS Server can be deployed in the Data Center along with the Civic Platform and GIS server back-end components as shown in the topology diagram.
  • If the agency uses the Accela Document Server, it requires its own database instance while the Accela Adhoc Report Server uses the Civic Platform database instance. The ADS database instance can be on its own database server, or shared with the Civic Platform database server (as shown in the diagram). You can consolidate these optional components on one or more physical (or virtual) hosts, depending on the requirements of your deployment.
  • There should only be one index server, as shown in the topology diagram.
  • The general recommendation is to deploy components such as Accela Document Server and Accela Adhoc Report Server on separate servers. If the agency decides to combine components with other servers, make sure that they are not combined with the Biz and Index servers, and that the host server has capacity for anticipated transaction data load.
  • The AGIS JavaScript service needs to reach the internet to retrieve ArcGIS Online services.
  • ESRI ArcGIS services need to be public facing in order for agency maps to be leveraged by the Mobile App clients.
  • For sizing recommendations, see JVM Process Memory Size Recommendations for Data Centers.