Configuring Pipeline Pilot Servers

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: %httproot%/scitegic/xmldb

See Sharing an XMLDB with Multiple Servers

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.

  • Unrestricted: Users can browse for files anywhere on the server.
  • Restricted: Users can only browse within the "scitegic/public" directory.
  • User folder only: Users can only browse within their own user folder.

Impersonation settings can also control access to folders by individual users.

Default: Restricted

See Adding File Browser Shortcuts 

File Editing

Control the folder locations where client file browsers can upload or modify files.

  • Unrestricted: Users can delete, move, and rename files and directories outside of their own "scitegic/public/users" file directory.
  • Restricted: Users can only modify files and directories within their own user directory.

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

See Adding File Browser Shortcuts 

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.

See Recommendations for CPU Usage

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

See Support for Security Issues

Retain Session Cookie beyond Web Browser Session

Control how the logged on browser handles cookies.

  • Yes: Sets an expiration on the session cookie, so that the cookie will be saved to disk until the time of expiration.
  • No: The cookie will not exist after the web browser session is closed.

Default: Yes

See Support for Security Issues

Session Salt

Assign an additional password to encrypt contents of the session.

Default: [no setting, blank]

See Support for Security Issues

Compress XMLDB

Control how protocol and component files are saved in the XMLDB.

  • Yes: Reduces the space occupied on your server for XMLDB file storage. (Compressed files are saved with the extension "xml.gz".)
  • No: Saves all files in the XMLDB at their default uncompressed size. (This setting requires more disk space on your server.)

Default: Yes

See Compressing an XMLDB

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:

  • HTTP Only: Primary server port. Always in use and supports Web Port, Pipeline Pilot Help Center, and all non-secure web services.
  • SSL Only: This port is managed by a security protocol (SSL). It is always in use and supports the Admin Portal and the locator web service that includes the user login procedure.

See Configuring a Single Port Operation and Reconfiguring Ports

Allow Remote Administration

Control remote access to the Admin Portal.

  • Yes: Enables remote access.
  • No: Disables remote access.

Default: Yes

See Support for Remove Administration Access

See Also: Monitoring Server Usage | Recommendations for CPU Usage