Redwood Documentation

Product Documentation

 

›Process Servers

RunMyJobsProcess Servers and Queues

Process Servers

  • Using Process Servers
  • Creating a Process Server
  • Configuring a Process Server
  • Raising Events with Files
  • Creating a Monitoring Platform Agent
  • Monitoring External Systems with Platform Agents
  • Visualizing Process Server - Queue Relationships
  • Files
  • Values for Creating a Process Server
  • Process Server Parameters

Queues

  • Using Queues
  • Creating a Queue
  • Using Queues to Administer Process Execution
  • Using Resources to distribute the load
← Visualizing Process Server - Queue RelationshipsValues for Creating a Process Server →

Files

Processes generate output, usually at least one output file and when errors occurred there is also a log file. These files can be plain text files or of another format, like PDF, depending on the process. These files are stored on the process server, SAP and System output gets stored on the central Redwood Server; Remote agents store output of processes locally. Sufficient free space must be available on these file systems,

The default output file of processes is named stdout.log, which refers to the concept of the standard output stream of computer systems. The log file is named stderr.log which refers to the concept of standard error stream of computer systems. Additional output files have the name of the output, if for example in a KSH or CMD process definition you direct output to a file, the filename will be the name of the output.

In the following example, the file will have the name of the output, done.txt.

echo done > done.txt

The location of the output and log files is configured with the DataRootDirectory process server parameter, which can be set for all process servers. The DataRootDirectory also contains process server log files, as well as other data used by file event processes.

note

The process server parameter can have a trailing slash / or __, however, this is not required.

Under the DataRootDirectory a lis and log directory will be created, the first for the output, which by default will have a txt extension, and the latter for log files, which by default will have a log extension. The extension of the files depends on the output and log format.

SAP and System Process Servers

SAP and System process servers do not have the parameter in their parameters list and use the default value, which is java.io.tmpdir, and depends on the configuration of your JEE Application Server, where it can be changed centrally.

In Redwood Platform, the default java.io.tmpdir, is set to ${InstallDir}\j2ee\cluster\server1\temp.

The DataRootDirectory of the System process server can be set with the process definition System_SetSystemDataRootDirectory.

The DataRootDirectory of SAP process servers just needs to be set on the process server. Previous versions required the process server to have a System definition type, this is no longer the case.

Platform Agents

The default value of DataRootDirectory is set to <InstallDir>/var by default, this value should be changed to a directory on a large file system.

<InstalLDir> is the installation directory, on Windows the default is %ProgramFiles%\Redwood\Server on UNIX systems there is no default, it will default to the current working directory.

note

Previous releases had the DataRootDirectory set to <InstallDir>/<version>/var; Redwood highly recommends to set the DataRootDirectory process server parameter before upgrading if you had not set it previously. If you choose not to, file events can loose their state after the upgrade.

See Also

The Environment of Platform Processes

← Visualizing Process Server - Queue RelationshipsValues for Creating a Process Server →
  • SAP and System Process Servers
  • Platform Agents
  • See Also
Docs
Getting StartedInstallationFinance InstallationConcepts
TroubleshootingArchiving
Learn and Connect
Support Portal
BlogEventsResources
ISO/ IEC 27001 Information Security Management
Automate to be human

2023 All Rights Reserved |

Terms of Service | Policies | Cookies | Glossary | Third-party Software | Contact | Copyright | Impressum |