Port Assignment with Central Configuration
If you are using the new central configuration file, port assignment is controlled via three properties:
- network.publicPort - The public entry port. The chosen port must be accessible by all servers which need to call the PrizmDoc RESTful APIs.
- network.clustering.clusterPort - The port PrizmDoc Servers use to communicate between each other when setup in a cluster. The port must be accessible by all servers in the cluster.
- network.internalStartingPort - The first of a series of 200 consecutive ports which the product can use for various internal micro-services which need to communicate between one another via HTTP. For example, when set to 19000, the product will use ports 19000 through 19199 for its own internal purposes. None of these ports need to be accessible from outside of the server.
Port Assignment with Legacy Configuration
If you are not using the new central configuration file, then port assignment is controlled largely through the watchdog.config file:
- Windows: C:\Prizm\PCCIS\Watchdog\watchdog.config
- Linux: /usr/share/prizm/pccis/Watchdog/watchdog.config
The two most important ports to assign are the sep_port and, if using multi-server mode, the cep_port:
- If you are running in single-server mode, make sure the port defined by sep_port is accessible to all servers which need to call the PrizmDoc RESTful APIs.
- If you are running in multi-server mode, make sure the port defined by sep_port is accessible by all other PrizmDoc Servers running in your cluster, and cep_port is accessible to all servers which need to call the PrizmDoc RESTful APIs.
Many existing services allow you to specify the specific port they run on in the watchdog.config file (this is a level of detail we are transitioning away from).
For internal services that don't allow you to control their specific port, the internal_starting_port property defines a range of 200 consecutive ports which the product may use dynamically for these services.
