Network Ports
Civic Platform implements standard web communication protocols (HTTP/HTTPS, SSL, and so forth). Use the commonly available communication speed, 1 Gbps for example, for your network communication speed.
The following Civic Platform Configuration Parameters table shows the network communication ports between external Accela hosts. The administrator who installs Civic Platform uses the same configuration checklist (included in the Civic Platform Installation Guide) before running the Civic Platform installer.
Component | Parameter: (with Example Values) | Your Value |
---|---|---|
General Recommendation | Have a total of approximately 6 IP addresses
available. Note: The actual total of IP addresses depends on whether
the Accela core services are installed on separate servers or a
multi-homed server.
|
|
ColdFusion MX Web Server |
|
|
Web Server |
|
|
Application Server |
|
|
Index Server |
|
|
ARW Server |
|
|
ARW Server with Oracle Database |
|
|
ARW Server with MS SQL Server Database |
|
|
Oracle Database Server |
|
|
Jetspeed Oracle Database Server |
|
|
MS SQL Server Database Server |
|
|
ADS Server |
|
|
ADS Server with Oracle Database |
|
|
ADS Server with MS SQL Server Database |
|
|
- For the ColdFusion MX web server, Web Server, Index server, and ADS server - The Port Bind Base is the base number for all other ports except HTTP and HTTPS ports. The value should typically be a single-digit or double-digit between 1~65 (such as 2, 3, etc.), and becomes the ‘thousands’ prefix for all other pre-defined values. The ‘Port Bind Base’ concept applies to the setup of other Accela products. Each Accela product if installed on the same server should have a unique base.
- For the Web server and Report server - If the server is on the same host as the application server, they have the same IP address, use a different HTTP port number and HTTPS port number from the ones used for the application server (Setting Up Multiple-Homed Servers).
- For the Application server - Application server clients specify port 3080 as the default port for communicating with the application server. Reserve JBoss binding port base 3 for the application server.
- For the Accela IVR server - Use unique port numbers for multiple Tomcat instances.
- For the Accela Gateway server - Accela Mobile Gateway can support multiple application servers. Each supported application server uses a different IP address or port.
This Internal Communication Ports table lists internal communication ports between the Civic Platform application server and other system servers.
Ports | Servers |
---|---|
<base>080 | Biz, CFMX, Web, ADS servers (for http) |
<base>443 | Biz, CFMX, Web, ADS servers (for https) |
<base>445 | Biz, Index servers (for Java Messaging Service) |
<base>447 | Biz, Index servers (for Java Remote Method Invocation) |
<base>099 | Biz, Index server, CFMX, Web, ADS servers (for Java Naming Provider) |
Setting Up Multiple-Homed Servers
Best practices recommend installing Civic Platform using a multi-homed configuration with a physical connection between the host to multiple IP addresses (on the same or different networks). For multiple Accela products on a single physical server, the recommendation is to set up a multi-homed environment with multiple virtual IP addresses. Each Accela service requires a unique TCP/IPv4 address.