Process Server Parameters

This parameter controls how the output is written to the output file. Set the value to true if you want the output to be appended to the output file; if you set this to false, the output file will be overwritten.

This parameter allows restricting the retrieval of job log files. You can specify the following options: true or 0 -> The QPJOBLOG is retrieved without checking the file size false or -1 -> The QPJOBLOG is not retrieved. Any positive number -> The QPJOBLOG file is retrieved only if it is smaller than the file size that is given

The DataRootDirectory should point to a file system that is served by a local device driver. In other words, not a NFS or Microsoft Windows network share. The reason for this is that the file tree needs to be as reliable as possible, as some parts are used for a database (of messages and file state).

For most services this indicates where the job will run, and indicates a server name or such as well as the lookup for credentials. For the PlatformAgentService this only defines a domain used to look up credentials, and this can be set to (for instance) a domain name or other group of servers sharing the same credentials.

• ${InstallDirectory}
• ${ProcessServer}
• ${HostName}
• ${SystemId}

• ${ProcessServer}
• ${HostName}
• ${SystemId}
• ${JobId}
• ${FileSeparator}
• ${JobOwner}
• ${DateTime}
• ${JobDefinitionOwner}
• ${JobDefinition}
• ${JobDefinitionPartition}
• ${ProcessServer}
• ${ProcessServerPartition}
• ${Queue}
• ${QueuePartition}
• ${JobApplication}
• ${JobApplicationPartition}
• ${JobFileName}
• ${JobFileOrder}
• ${FormatExtension}

Default on Microsoft Windows : ${InstallDirectory}\var\${SystemId}\${ProcessServer}

Default on UNIX : ${InstallDirectory}/var/${SystemId}/${ProcessServer}

Default on HP OpenVMS : ${InstallDirectory}[var.${SystemId}.${ProcessServer}]

Default on Java platforms : ${InstallDirectory}

The DataRootDirectory should point to a file system that is served by a local device driver. In other words, not a NFS or Microsoft Windows network share. The reason for this is that the file tree needs to be as reliable as possible, as some parts are used for a database (of messages and file state).

• ${InstallDirectory}
• ${ProcessServer}
• ${HostName}
• ${SystemId}

Default on Microsoft Windows : ${InstallDirectory}\var\${SystemId}\${ProcessServer}

Default on UNIX : ${InstallDirectory}/var/${SystemId}/${ProcessServer}

Default on HP OpenVMS : ${InstallDirectory}[var.${SystemId}.${ProcessServer}]

Default on Java platforms : ${InstallDirectory}

The value All is the default, automatic job description change is active for all job definitions. The value StandardOnly restricts the job description change only to built-in job definitions (job definitions with System_ prefix). The value None disables job description changes.

The DataRootDirectory should point to a file system that is served by a local device driver. In other words, not a NFS or Microsoft Windows network share. The reason for this is that the file tree needs to be as reliable as possible, as some parts are used for a database (of messages and file state).

The value All is the default, automatic job description change is active for all job definitions. The value StandardOnly restricts the job description change only to built-in job definitions (job definitions with System_ prefix). The value None disables job description changes.

• ${InstallDirectory}
• ${ProcessServer}
• ${HostName}
• ${SystemId}

Default on Microsoft Windows : ${InstallDirectory}\var\${SystemId}\${ProcessServer}

Default on UNIX : ${InstallDirectory}/var/${SystemId}/${ProcessServer}

Default on HP OpenVMS : ${InstallDirectory}[var.${SystemId}.${ProcessServer}]

Default on Java platforms : ${InstallDirectory}

The DataRootDirectory should point to a file system that is served by a local device driver. In other words, not a NFS or Microsoft Windows network share. The reason for this is that the file tree needs to be as reliable as possible, as some parts are used for a database (of messages and file state).

A (JDBC) connect string to connect to a specific Oracle instance of a Oracle RAC cluster. The connect string can have %h and %s and %i. The %h is replaced with the hostname of the Oracle instance, %s is replaced with the instance name and %i with the instance id. When this parameter is not set, it will try to connect using jdbc:oracle:thin:@%h:1521:%s.

• ${InstallDirectory}
• ${ProcessServer}
• ${HostName}
• ${SystemId}

Default on Microsoft Windows : ${InstallDirectory}\var\${SystemId}\${ProcessServer}

Default on UNIX : ${InstallDirectory}/var/${SystemId}/${ProcessServer}

Default on HP OpenVMS : ${InstallDirectory}[var.${SystemId}.${ProcessServer}]

Default on Java platforms : ${InstallDirectory}

The DataRootDirectory should point to a file system that is served by a local device driver. In other words, not a NFS or Microsoft Windows network share. The reason for this is that the file tree needs to be as reliable as possible, as some parts are used for a database (of messages and file state).

The value All is the default, automatic job description change is active for all job definitions. The value StandardOnly restricts the job description change only to built-in job definitions (job definitions with System_ prefix). The value None disables job description changes.

This parameter can be used to control how often to retry the retrieval of the output file(s) from the remote system. By default, three attempts will be made to retrieve an output file, and if all three fail, then the job is put into Error. Ignore Ignore any exception when retrieving the output, but put the job to the status according the PeopleSoft Job Retry [number of retries] (Default retry 2 times; must be 0 or greater) Retry the retrieval of output, with an optional number of retries. If the output is not retrieved within the number of retries the job is put into Error.

• ${InstallDirectory}
• ${ProcessServer}
• ${HostName}
• ${SystemId}

Default on Microsoft Windows : ${InstallDirectory}\var\${SystemId}\${ProcessServer}

Default on UNIX : ${InstallDirectory}/var/${SystemId}/${ProcessServer}

Default on HP OpenVMS : ${InstallDirectory}[var.${SystemId}.${ProcessServer}]

Default on Java platforms : ${InstallDirectory}

The DataRootDirectory should point to a file system that is served by a local device driver. In other words, not a NFS or Microsoft Windows network share. The reason for this is that the file tree needs to be as reliable as possible, as some parts are used for a database (of messages and file state).

For most services this indicates where the job will run, and indicates a server name or such as well as the lookup for credentials. For the PlatformAgentService this only defines a domain used to look up credentials, and this can be set to (for instance) a domain name or other group of servers sharing the same credentials.

When set to 'true', 'only' or 'fallback' the server will validate a getfile request and then ask the agent for a valid temporary URL that it then sends to jtool, which will then attempt a direct connection. If this succeeds the data is transferred without going through the central server; this saves resources on the central server and can be much quicker if the process server and jtool client have a faster network connection. Note that clients must be able to access the process server on the URL that is shown in SystemInformation item RemoteURI.

This parameter accepts the following values: Create - Try to create, fallback to the default if it cannot. CreateFail - Try to create, fail the job if it does not exist. NoCreateFail - Don't try to create, fail the job if it does not exist. Ignore - Ignore if it does not exist. On HP OpenVMS these values have no effect, default is ignore.

A LowVolume ProcessServer requires a license item that specifies the threshold for the number of jobs the ProcessServer can run per day.

When this process server parameter is set to true or a hostname, clients (browsers) will retrieve the job files residing on this process server directly from the process server without the file be routed through the central server; this is useful when the process server and central server do not reside in the same geographical location or subnet. Note that clients must be able to access the process server on the URL that is shown in SystemInformation item RemoteURI. If the system-derived RemoteURI is not satisfactory you can overrule the hostname by setting it as the value for RedirectJobFiles and the portnumber by setting the value for RemotePort.

You set this to the version of your platform agents if the version of your platform agent is lower than that of the central server and you do not wish to auto-update the agent. For example: 9.0.22.5 Multiple versions can be specified comma-separated. For example: 9.0.22.1,9.0.22.2,9.0.22.3 The asterisk wildcard is allowed. For example: 9.0.22.*

• ${InstallDirectory}
• ${ProcessServer}
• ${HostName}
• ${SystemId}

• ${TraceDirectory}
• ${InstallDirectory}
• ${DataRootDirectory}
• ${ProcessType}
• ${ProcessName}
• ${ProcessId}
• ${ProcessServer}
• ${Timestamp}
• ${FileSeparator}

• ${User}
• ${Command}

• ${InstallDirectory}
• ${DataRootDirectory}

Default on Microsoft Windows : ${InstallDirectory}\var\${SystemId}\${ProcessServer}

Default on UNIX : ${InstallDirectory}/var/${SystemId}/${ProcessServer}

Default on HP OpenVMS : ${InstallDirectory}[var.${SystemId}.${ProcessServer}]

Default on Java platforms : ${InstallDirectory}

Default value on most UNIX platforms : /usr/sbin/fuser "${Filename}"

Default value on macOS : /usr/bin/fuser "${Filename}"

Default value on Linux : builtin

Default value on Microsoft Windows : ${JobFilesDirectory}

Default value on UNIX : ${JobFilesDirectory}

Default value on HP OpenVMS : ${JobFilesDirectory}

Default value on UNIX : PATH,LANG,LC_*,NATIVEJAVA_CLASSPATH,TZ

Default value on UNIX : sudo -S -u ${User} ${Command}

Default value on Microsoft Windows : ${InstallDirectory}

Default value on UNIX : ${InstallDirectory}

Default value on HP OpenVMS : ${InstallDirectory}

The DataRootDirectory should point to a file system that is served by a local device driver. In other words, not a NFS or Microsoft Windows network share. The reason for this is that the file tree needs to be as reliable as possible, as some parts are used for a database (of messages and file state).

The value All is the default, automatic job description change is active for all job definitions. The value StandardOnly restricts the job description change only to built-in job definitions (job definitions with SAP_ prefix). The value None disables job description changes.

• ${InstallDirectory}
• ${ProcessServer}
• ${HostName}
• ${SystemId}

• ${ProcessServer}
• ${HostName}
• ${SystemId}
• ${JobId}
• ${FileSeparator}
• ${JobOwner}
• ${DateTime}
• ${JobDefinitionOwner}
• ${JobDefinition}
• ${JobDefinitionPartition}
• ${ProcessServer}
• ${ProcessServerPartition}
• ${Queue}
• ${QueuePartition}
• ${JobApplication}
• ${JobApplicationPartition}
• ${JobFileName}
• ${JobFileOrder}

• ${ProcessServer}
• ${HostName}
• ${SystemId}
• ${JobId}
• ${FileSeparator}
• ${JobOwner}
• ${DateTime}
• ${JobDefinitionOwner}
• ${JobDefinition}
• ${JobDefinitionPartition}
• ${ProcessServer}
• ${ProcessServerPartition}
• ${Queue}
• ${QueuePartition}
• ${JobApplication}
• ${JobApplicationPartition}
• ${JobFileName}
• ${FormatExtension}

• ${ProcessServer}
• ${HostName}
• ${SystemId}
• ${JobId}
• ${FileSeparator}
• ${JobOwner}
• ${DateTime}
• ${JobDefinitionOwner}
• ${JobDefinition}
• ${JobDefinitionPartition}
• ${ProcessServer}
• ${ProcessServerPartition}
• ${Queue}
• ${QueuePartition}
• ${JobApplication}
• ${JobApplicationPartition}
• ${JobFileName}
• ${JobFileOrder}

• ${ProcessServer}
• ${HostName}
• ${SystemId}
• ${JobId}
• ${FileSeparator}
• ${JobOwner}
• ${DateTime}
• ${JobDefinitionOwner}
• ${JobDefinition}
• ${JobDefinitionPartition}
• ${ProcessServer}
• ${ProcessServerPartition}
• ${Queue}
• ${QueuePartition}
• ${JobApplication}
• ${JobApplicationPartition}
• ${JobFileName}
• ${JobFileOrder}
• ${FormatExtension}

Default on Microsoft Windows : ${InstallDirectory}\var\${SystemId}\${ProcessServer}

Default on UNIX : ${InstallDirectory}/var/${SystemId}/${ProcessServer}

Default on HP OpenVMS : ${InstallDirectory}[var.${SystemId}.${ProcessServer}]

Default on Java platforms : ${InstallDirectory}

The DataRootDirectory should point to a file system that is served by a local device driver. In other words, not a NFS or Microsoft Windows network share. The reason for this is that the file tree needs to be as reliable as possible, as some parts are used for a database (of messages and file state).

• ${InstallDirectory}
• ${ProcessServer}
• ${HostName}
• ${SystemId}

• ${ProcessServer}
• ${HostName}
• ${SystemId}
• ${JobId}
• ${FileSeparator}
• ${JobOwner}
• ${DateTime}
• ${JobDefinitionOwner}
• ${JobDefinition}
• ${JobDefinitionPartition}
• ${ProcessServer}
• ${ProcessServerPartition}
• ${Queue}
• ${QueuePartition}
• ${JobApplication}
• ${JobApplicationPartition}
• ${JobFileName}
• ${JobFileOrder}

• ${ProcessServer}
• ${HostName}
• ${SystemId}
• ${JobId}
• ${FileSeparator}
• ${JobOwner}
• ${DateTime}
• ${JobDefinitionOwner}
• ${JobDefinition}
• ${JobDefinitionPartition}
• ${ProcessServer}
• ${ProcessServerPartition}
• ${Queue}
• ${QueuePartition}
• ${JobApplication}
• ${JobApplicationPartition}
• ${JobFileName}
• ${FormatExtension}

• ${ProcessServer}
• ${HostName}
• ${SystemId}
• ${JobId}
• ${FileSeparator}
• ${JobOwner}
• ${DateTime}
• ${JobDefinitionOwner}
• ${JobDefinition}
• ${JobDefinitionPartition}
• ${ProcessServer}
• ${ProcessServerPartition}
• ${Queue}
• ${QueuePartition}
• ${JobApplication}
• ${JobApplicationPartition}
• ${JobFileName}
• ${JobFileOrder}

• ${ProcessServer}
• ${HostName}
• ${SystemId}
• ${JobId}
• ${FileSeparator}
• ${JobOwner}
• ${DateTime}
• ${JobDefinitionOwner}
• ${JobDefinition}
• ${JobDefinitionPartition}
• ${ProcessServer}
• ${ProcessServerPartition}
• ${Queue}
• ${QueuePartition}
• ${JobApplication}
• ${JobApplicationPartition}
• ${JobFileName}
• ${JobFileOrder}
• ${FormatExtension}

Default on Microsoft Windows : ${InstallDirectory}\var\${SystemId}\${ProcessServer}

Default on UNIX : ${InstallDirectory}/var/${SystemId}/${ProcessServer}

Default on HP OpenVMS : ${InstallDirectory}[var.${SystemId}.${ProcessServer}]

Default on Java platforms : ${InstallDirectory}

The DataRootDirectory should point to a file system that is served by a local device driver. In other words, not a NFS or Microsoft Windows network share. The reason for this is that the file tree needs to be as reliable as possible, as some parts are used for a database (of messages and file state).

The value All is the default, automatic job description change is active for all job definitions. The value StandardOnly restricts the job description change only to built-in job definitions (job definitions with SAP_ prefix). The value None disables job description changes.

This parameter is used in conjunction with the settings on the Job Control Rules tab of SAP system definitions. If you enable spool file retrieval on the Job Control Rules tab, the value of this process server parameter has precedence. You can overrule the settings on the SAP system for big spool files, for example. Remember that setting this parameter to -1 disables spool file retrieval, regardless of what you configure on the SAP system definition.

• ${InstallDirectory}
• ${ProcessServer}
• ${HostName}
• ${SystemId}

• ${ProcessServer}
• ${HostName}
• ${SystemId}
• ${JobId}
• ${FileSeparator}
• ${JobOwner}
• ${DateTime}
• ${JobDefinitionOwner}
• ${JobDefinition}
• ${JobDefinitionPartition}
• ${ProcessServer}
• ${ProcessServerPartition}
• ${Queue}
• ${QueuePartition}
• ${JobApplication}
• ${JobApplicationPartition}
• ${JobFileName}
• ${JobFileOrder}

• ${ProcessServer}
• ${HostName}
• ${SystemId}
• ${JobId}
• ${FileSeparator}
• ${JobOwner}
• ${DateTime}
• ${JobDefinitionOwner}
• ${JobDefinition}
• ${JobDefinitionPartition}
• ${ProcessServer}
• ${ProcessServerPartition}
• ${Queue}
• ${QueuePartition}
• ${JobApplication}
• ${JobApplicationPartition}
• ${JobFileName}
• ${FormatExtension}

• ${ProcessServer}
• ${HostName}
• ${SystemId}
• ${JobId}
• ${FileSeparator}
• ${JobOwner}
• ${DateTime}
• ${JobDefinitionOwner}
• ${JobDefinition}
• ${JobDefinitionPartition}
• ${ProcessServer}
• ${ProcessServerPartition}
• ${Queue}
• ${QueuePartition}
• ${JobApplication}
• ${JobApplicationPartition}
• ${JobFileName}
• ${JobFileOrder}

• ${ProcessServer}
• ${HostName}
• ${SystemId}
• ${JobId}
• ${FileSeparator}
• ${JobOwner}
• ${DateTime}
• ${JobDefinitionOwner}
• ${JobDefinition}
• ${JobDefinitionPartition}
• ${ProcessServer}
• ${ProcessServerPartition}
• ${Queue}
• ${QueuePartition}
• ${JobApplication}
• ${JobApplicationPartition}
• ${JobFileName}
• ${JobFileOrder}
• ${FormatExtension}

Default on Microsoft Windows : ${InstallDirectory}\var\${SystemId}\${ProcessServer}

Default on UNIX : ${InstallDirectory}/var/${SystemId}/${ProcessServer}

Default on HP OpenVMS : ${InstallDirectory}[var.${SystemId}.${ProcessServer}]

Default on Java platforms : ${InstallDirectory}

The DataRootDirectory should point to a file system that is served by a local device driver. In other words, not a NFS or Microsoft Windows network share. The reason for this is that the file tree needs to be as reliable as possible, as some parts are used for a database (of messages and file state).

You set this to the version of your platform agents if the version of your platform agent is lower than that of the central server and you do not wish to auto-update the agent. For example: 9.0.22.5 Multiple versions can be specified comma-separated. For example: 9.0.22.1,9.0.22.2,9.0.22.3 The asterisk wildcard is allowed. For example: 9.0.22.*

• ${InstallDirectory}
• ${ProcessServer}
• ${HostName}
• ${SystemId}

• ${ProcessServer}
• ${HostName}
• ${SystemId}
• ${JobId}
• ${FileSeparator}
• ${JobOwner}
• ${DateTime}
• ${JobDefinitionOwner}
• ${JobDefinition}
• ${JobDefinitionPartition}
• ${ProcessServer}
• ${ProcessServerPartition}
• ${Queue}
• ${QueuePartition}
• ${JobApplication}
• ${JobApplicationPartition}
• ${JobFileName}
• ${JobFileOrder}

• ${ProcessServer}
• ${HostName}
• ${SystemId}
• ${JobId}
• ${FileSeparator}
• ${JobOwner}
• ${DateTime}
• ${JobDefinitionOwner}
• ${JobDefinition}
• ${JobDefinitionPartition}
• ${ProcessServer}
• ${ProcessServerPartition}
• ${Queue}
• ${QueuePartition}
• ${JobApplication}
• ${JobApplicationPartition}
• ${JobFileName}
• ${FormatExtension}

• ${ProcessServer}
• ${HostName}
• ${SystemId}
• ${JobId}
• ${FileSeparator}
• ${JobOwner}
• ${DateTime}
• ${JobDefinitionOwner}
• ${JobDefinition}
• ${JobDefinitionPartition}
• ${ProcessServer}
• ${ProcessServerPartition}
• ${Queue}
• ${QueuePartition}
• ${JobApplication}
• ${JobApplicationPartition}
• ${JobFileName}
• ${JobFileOrder}

• ${ProcessServer}
• ${HostName}
• ${SystemId}
• ${JobId}
• ${FileSeparator}
• ${JobOwner}
• ${DateTime}
• ${JobDefinitionOwner}
• ${JobDefinition}
• ${JobDefinitionPartition}
• ${ProcessServer}
• ${ProcessServerPartition}
• ${Queue}
• ${QueuePartition}
• ${JobApplication}
• ${JobApplicationPartition}
• ${JobFileName}
• ${JobFileOrder}
• ${FormatExtension}

Default on Microsoft Windows : ${InstallDirectory}\var\${SystemId}\${ProcessServer}

Default on UNIX : ${InstallDirectory}/var/${SystemId}/${ProcessServer}

Default on HP OpenVMS : ${InstallDirectory}[var.${SystemId}.${ProcessServer}]

Default on Java platforms : ${InstallDirectory}

The DataRootDirectory should point to a file system that is served by a local device driver. In other words, not a NFS or Microsoft Windows network share. The reason for this is that the file tree needs to be as reliable as possible, as some parts are used for a database (of messages and file state).

• ${InstallDirectory}
• ${ProcessServer}
• ${HostName}
• ${SystemId}

• ${ProcessServer}
• ${HostName}
• ${SystemId}
• ${JobId}
• ${FileSeparator}
• ${JobOwner}
• ${DateTime}
• ${JobDefinitionOwner}
• ${JobDefinition}
• ${JobDefinitionPartition}
• ${ProcessServer}
• ${ProcessServerPartition}
• ${Queue}
• ${QueuePartition}
• ${JobApplication}
• ${JobApplicationPartition}
• ${JobFileName}
• ${JobFileOrder}

• ${ProcessServer}
• ${HostName}
• ${SystemId}
• ${JobId}
• ${FileSeparator}
• ${JobOwner}
• ${DateTime}
• ${JobDefinitionOwner}
• ${JobDefinition}
• ${JobDefinitionPartition}
• ${ProcessServer}
• ${ProcessServerPartition}
• ${Queue}
• ${QueuePartition}
• ${JobApplication}
• ${JobApplicationPartition}
• ${JobFileName}
• ${FormatExtension}

• ${ProcessServer}
• ${HostName}
• ${SystemId}
• ${JobId}
• ${FileSeparator}
• ${JobOwner}
• ${DateTime}
• ${JobDefinitionOwner}
• ${JobDefinition}
• ${JobDefinitionPartition}
• ${ProcessServer}
• ${ProcessServerPartition}
• ${Queue}
• ${QueuePartition}
• ${JobApplication}
• ${JobApplicationPartition}
• ${JobFileName}
• ${JobFileOrder}

• ${ProcessServer}
• ${HostName}
• ${SystemId}
• ${JobId}
• ${FileSeparator}
• ${JobOwner}
• ${DateTime}
• ${JobDefinitionOwner}
• ${JobDefinition}
• ${JobDefinitionPartition}
• ${ProcessServer}
• ${ProcessServerPartition}
• ${Queue}
• ${QueuePartition}
• ${JobApplication}
• ${JobApplicationPartition}
• ${JobFileName}
• ${JobFileOrder}
• ${FormatExtension}

Default on Microsoft Windows : ${InstallDirectory}\var\${SystemId}\${ProcessServer}

Default on UNIX : ${InstallDirectory}/var/${SystemId}/${ProcessServer}

Default on HP OpenVMS : ${InstallDirectory}[var.${SystemId}.${ProcessServer}]

Default on Java platforms : ${InstallDirectory}