| |  | Worker Machines VM:Webgateway worker machines (also called workers) are separate VM userids that VM:Webgateway uses to run the following types of programs: - Filters
- You must run filters on worker machines; you cannot define a filter to run on the VM:Webgateway service virtual machine (SVM).
A worker machine assumes the permissions of the VM:Webgateway SVM when the worker runs a filter. - CGI programs
- You can run CGI programs on worker machines or on the VM:Webgateway SVM. By running CGI programs on a worker machine instead of the VM:Webgateway SVM, you free up SVM resources for other tasks, increasing system throughput. Worker machines also provide tighter security when VM:Webgateway runs CGI programs stored in user pages, because the CGI program is limited to the permissions of the userid that owns the CGI program rather than the permissions of the VM:Webgateway SVM.
A worker machine assumes the permissions of the VM:Webgateway SVM when the worker runs a CGI program served from the server root domain, and it assumes the permissions of the userid that owns a user page when the worker runs a CGI program being served from a user page. VM:Webgateway allocates a worker when a web browser user requests one of the following types of files: - Static file that requires filtering
- CGI program that runs on a worker
VM:Webgateway knows whether a file is a static file that requires filtering or a CGI program that runs on a worker based on the content filetype you assign to the file. For a CMS file, the content filetype is the file's CMS filetype. For a BFS file, the content filetype is the file's BFS extension. The VM:Webgateway system administrator defines content filetypes. To use workers, a VM:Webgateway system administrator must set up VM:Webgateway to use worker machines. After the system administrator sets up workers, VM:Webgateway operators can manage the workers. |
