Adding Mongrel Processes for a New Apache Port

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.

Edit orchestrator.yml (the Orchestrator configuration file) to increase the number of mongrels.
1. Open orchestrator.yml from the following location:
```
opt/aspera/var/config/orchestrator/
```
2. Locate the option max_mongrels and increase it to the desired integer.
3. Restart Orchestrator, using the procedure in Restarting Orchestrator.

Create a virtual host for Orchestrator inside the configuration file for Apache.

Create a file in the following directory:
```
/opt/aspera/common/apache/custom
```
Aspera recommends naming this file custom_config.conf.

Add the following configuration content to the file:

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>

Note:

The number of mongrels currently running in Orchestrator must match the number of BalancerMembers (load balancers); there are five BalancerMembers in the example above.

Open the configuration file for Apache to confirm that the custom directory is loaded. The configuration file is found in the following location:
```
/opt/aspera/common/apache/ashttpd.conf
```

Note: Repeat this step as needed to add more ports to the configuration.

Restart Apache with the following command:
```
# asctl apache:restart
```
Test the results of the prodedure.
1. Open Orchestrator from the following URL:
```
http://localhost:port_name/aspera/orchestrator/
```
  Note: Replace localhost with the machine IP if accessing Orchestrator from a remote node.
2. Log in with a valid user ID and password.
  You are redirected to the Work Orders page.