The number of Orchestrator mongrels can be increased, and they can also have the port listen on a different Apache port. This procedure is applicable to situations where a high volume of API calls to Orchestrator slows down the user interface.
C:\Program Files (x86)\Aspera\Orchestrator\www\var\config\
C:\Progam Files (x86)\Aspera\Orchestrator\apache\custom\
Aspera recommends naming this file custom_config.conf.
Listen port_number VirtualHost *:port_number ServerAdmin webmaster@localhost Alias /aspera/orchestrator/images "/opt/aspera/orchestrator/public/images" Alias /aspera/orchestrator/stylesheets "/opt/aspera/orchestrator/public/stylesheets" Alias /aspera/orchestrator/javascripts "/opt/aspera/orchestrator/public/javascripts" <Directory "/opt/aspera/orchestrator/public"> Options -Indexes -FollowSymLinks AllowOverride none Order allow,deny Allow from all </Directory> <Proxy balancer://orchestrator_cluster> Allow from all BalancerMember http://127.0.0.1:3000 BalancerMember http://127.0.0.1:3001 BalancerMember http://127.0.0.1:3002 BalancerMember http://127.0.0.1:3003 BalancerMember http://127.0.0.1:3004 </Proxy> ProxyPass /aspera/orchestrator/images ! ProxyPass /aspera/orchestrator/stylesheets ! ProxyPass /aspera/orchestrator/javascripts ! # send the proxy request # @web_root starts with / if not nil ProxyPass /aspera/orchestrator balancer://orchestrator_cluster/aspera/orchestrator RequestHeader set X_FORWARDED_PROTO "https" </VirtualHost>
The number of mongrels currently running in Orchestrator must match the number of BalancerMembers (load balancers); there are five BalancerMembers in the example above.
# asctl apache:restart
http://localhost:port_name/aspera/orchestrator/