A variety of settings define how your server runs and interacts with clients, databases, web services, and other applications and features. All default settings are configured at installation time. You can modify these settings whenever necessary.
To change a server setting:
| 1. | Go to Setup > Server Configuration. |
| 2. | Find the setting you need to change (defined below) and choose a setting. |
| 3. | Click Save to update the server. |
| Setting | Use this feature to: |
|---|---|
| XMLDB Endpoint |
Share an XMLDB with multiple servers by specifying the name of a host XMLDB . By default, the XMLDB for the logged on server is used. Default: |
| Automatic Client Download |
Enable the server to prompt Pipeline Pilot Client users to download and install a new client version if the currently installed client version is incompatible with the server. Default: Yes See Client Support |
| File Browsing |
Control what server folder locations are displayed in client file browsers.
Impersonation settings can also control access to folders by individual users. Default: Restricted |
| File Editing |
Control the folder locations where client file browsers can upload or modify files.
This setting is ignored when impersonation is enabled, since the user's own file system permissions are used instead is enabled, since the user's own file system permissions are used instead Default: Restricted |
| Unrestricted File Download |
Control the directories that are accessible without any authentication, as a semicolon-separated list. Default: [no setting, blank] |
| Job Directory Access |
Restrict job directory web access to the owner. When restricted, only the user that ran the job can access files in job directory via the web server interface. Default: Unrestricted |
| Maximum Number of CPUs to Use |
Set the maximum number of logical CPUs that Pipeline Pilot can use. Logical CPUs are those detected by the operating system, independent of whether that CPU is implemented as a physical processor, a multi-core processor or with hyperthreading. Default: [no setting, blank] To apply this setting, either restart the server or wait for a few jobs run, so that cached processes using the old setting are cleared out. |
| Expiration (days, hours or minutes) of Single Sign-on Credentials |
Set the inactivity timeout before credentials expire in the context of web browser-based-logon. Users must log on again, if their credentials expire due to inactivity. If a user logs on again before the expiration, the credentials are renewed and the inactivity clock is reset. Default: 30d |
| Retain Session Cookie beyond Web Browser Session |
Control how the logged on browser handles cookies.
Default: Yes |
| Session Salt |
Assign an additional password to encrypt contents of the session. Default: [no setting, blank] |
| Compress XMLDB |
Control how protocol and component files are saved in the XMLDB.
Default: Yes |
| Keep Alive |
Allow an HTTP connection to be re-used for several requests within a given timeout limit. This avoids the need to create a new connection between client and server for every request. The time-limit value is calculated automatically by Pipeline Pilot depending on the server's capabilities. It can vary from 10 s up to a maximum of 40 s. IMPORTANT! Only set Keep Alive to "No" if you are experiencing stability problems with clients (e.g., if some .NET clients do not handle Keep Alive correctly).
Default: Yes |
| Compress HTTP Messages |
Enable mod_deflate for Apache. (It is necessary to restart the server if this setting is changed.) Default: Yes See http://httpd.apache.org/docs/current/mod/mod_deflate.html |
| Server Port Usage |
Configure Pipeline Pilot for single port operation (typically applies to standalone server installations). Default ports used for Pipeline Pilot and Apache web server are:
See Configuring a Single Port Operation and Reconfiguring Ports |
| Allow Remote Administration |
Control remote access to the Admin Portal.
Default: Yes |
See Also: Monitoring Server Usage | Recommendations for CPU Usage