Configuring and Sizing Platform Agent Hosts
This topic discusses sizing requirements for Platform Agents of various types. These requirements are in addition to a computer's normal specs.
The numbers in this topic are based on normal behavior (for example, no tracing) and a load that is spread over the period described. If the load is focused on a smaller time frame, the specs should be scoped to accommodate this fact.
If different roles are combined on a single Platform Agent, the specs should be combined. Redwood does not recommend combining higher-load Platform Agents on one machine.
Tip: It is a Redwood best practice to use a dedicated Spool Host Platform Agent and two Secure Gateway Platform Agents (so there is always a backup) in production.
Warning: Every RunMyJobs instance and customer environment is different, so the guidelines in this document are not definitive, and no guarantee is given that the hardware specifications herein will deliver an optimum environment.
Internet Connection
Every Platform Agent in an SaaS RunMyJobs instance requires an Internet connection, but data volume per process is usually below 25KB, and in most cases, only a Secure Gateway will need more than that. For example, a million process executions require 25GB of Internet traffic. This is well above the average Redwood sees, but it is a safe number to calculate with. Be sure to take peak moments into consideration.
Note: These numbers exclude file transfer usage, in case there is no direct agent-to-agent connection and data is streamed.
Warning: The proxy or firewall should not block file downloads from runmyjobs.cloud.
Regular Platform Agent
A regular Platform Agent simply enables process automation on a computer. Disk requirements depend primarily on process logs, so consider both the number of executions and log file retention rules. A clean installation requires only 100MB of disk space. The following table shows the minimum requirements for regular Platform Agents that perform a given number of executions per day.
| Executions per Day | Minimum Specs |
|---|---|
| 1 – 5.000 | 1 core / 1GB RAM / 20GB Disk |
| 1001 – 50000 | 2 Core / 2GB RAM / 200GB Disk |
| 50001 – 150000 | 3 Core / 4GB RAM / 300GB Disk |
| > 150000 | 4 Core / 8GB RAM / 500GB Disk |
Platform Agent Running as Secure Gateway
For a Platform Agent running as a Secure Gateway, Redwood recommends Windows or Linux x86 (64-bit highly preferred).
| Non-agent executions per Day* | Minimum Specs |
|---|---|
| 1 – 100000 | 1 Core / 2GB RAM / 300MB Disk / 1 Mbit |
| 100001 – 750000 | 2 Core / 2GB RAM / 500MB Disk / 3 Mbit |
| > 750000 | 2 Core / 4GB RAM / 750MB Disk / 5 Mbit |
*A “non-agent execution” is a process that does not run on a Platform Agent. Rather, it runs on the RunMyJobs server, and connects to a target system (such as a database or an ERP tool). Such connections run through the Secure Gateway, so if you have a lot of them, you may need a more powerful Secure Gateway.
Platform Agent Running as Spool Host
For a Platform Agent running as a Spool Host, Redwood recommends Windows or Linux x86 (64-bit highly preferred).
A Spool Host serves only as a spool/data storage location, and executes no other processes. Disk requirements depend primarily on the size of the spool files hosted, so take into account both the average spool file size and spool file retention rules. You can create multiple Spool Hosts to handle large quantities of files. The following table shows the minimum requirements for regular Platform Agents that handle a given number of spool files per day.
| Spool Files per Day | Minimum Specs |
|---|---|
| 1 – 10.000 | 1 Core / 1 GB RAM / 5 GB Disk |
| 10.001 – 250.000 | 2 Core / 2 GB RAM / 150 GB Disk |
| > 250.000 | 2 Core / 4 GB RAM / 500 GB Disk |
JVM
The JVM Platform Agent can execute certain RunMyJobs processes and other Java-related processes. A JVM Agent should run on the same Java version as the RunMyJobs server (Java 11 or 17), Java runs best on Linux.
Note: If you are using parallel executions, the required size can be higher, because parallel executions greatly increase core and memory usage.
| Number of Executions per Day on this Platform Agent | Minimum specs |
|---|---|
| 1 – 5000 | 2 Core / 4GB RAM / 20GB Disk |
| 1001 – 50000 | 8 Core / 16GB RAM / 200GB Disk |
| 50001 – 100000 | 16 Core / 32GB RAM / 300GB Disk |
Process File Locations
The following table lists the process file storage locations for various process Definition Types.
| Process Definition Type | Storage Location |
|---|---|
AS400
|
Central server |
BASH
|
Platform Agent |
CMD
|
Platform Agent |
CSH
|
Platform Agent |
DCL
|
Platform Agent |
FTP
|
Platform Agent |
GROOVY
|
Platform Agent |
HTTP
|
Central server |
JAVA
|
Platform Agent |
JCL_FTP
|
Platform Agent |
JDBC
|
Central server |
JOB_CHAIN
|
Does not generate any files |
KSH
|
Platform Agent |
MAIL
|
Central server |
OBJECT_SEARCH
|
Central server |
OraApps
|
Spool host |
OracleJob
|
Central server |
OraOhi
|
Spool host |
OS_NATIVE
|
Platform Agent |
PeopleSoft
|
Spool host |
PERL
|
Platform Agent |
PERLUNICODE
|
Platform Agent |
PS1
|
Platform Agent |
PUBLISH
|
Central server |
PYTHON
|
Platform Agent |
R
|
Platform Agent |
RECONCILIATION
|
Central server |
REDWOOD_SCRIPT
|
Central server |
REPORT
|
Central server |
SOAP
|
Central server |
SAP_BOBJ
|
Spool host |
SAP_PI
|
Spool host |
SAP_R3
|
Spool host |
System
|
Central server |
UserMessage
|
The user message Definition Type does not generate any files, but attachments are stored on the central server |
Note: The output and log files for pre-running, on-change, and post-running actions are stored on the central RunMyJobs server, regardless of the Definition Type.
Note: The Get Support Files process stores its output files on the central RunMyJobs server by default. A Java Process Server runs the process and stores its output files.