Configuring Ports
For security reasons, you may need to change AtScale ports from the
default. You can make these configuration changes in atscale.yaml,
following the procedure below.
Before You Begin
For the following procedure, you must have an AtScale installation of version 7.4.0 or above.
Procedure
- 
If AtScale is not already running, then as the ATSCALE_USER user ( atscaleby default), run the installed AtScale'sconfigurator.sh scriptin--first-timemode. If you don't want to fully confgure yet, answer 'n' when prompted with 'Do you wish to apply this configuration? (y/N):'. This will generate the/opt/atscale/conf/atscale.yamlfile and exit before configuring services. :/opt/atscale/current/bin/configurator.sh --first-time
- 
Open /opt/atscale/conf/atscale.yaml.
- 
Edit /opt/atscale/conf/atscale.yamlto override port entries that need to be changed in the following sections:- engine.ports
- modeler.ports
- virtualization.supervisor
- virtualization.worker
- virtualization.listener.port
 The current port defaults are listed in the example below: engine:
 ports:
 http: "20502"
 remoting: "20507"
 modeler:
 ports:
 http: "20500"
 authorization: "20503"
 virtualization:
 virtualization_supervisor:
 ui_port: "10530"
 driver_port: "10531"
 manager_port: "10532"
 master_port: "10533"
 master_webui_port: "10534"
 virtualization_worker:
 worker_port: "10535"
 worker_webui_port: "10536"
 virtualization_listener:
 port: "10511"
- 
Run configurator.shto apply the configuration change:/opt/atscale/current/bin/configurator.sh --apply