Appian Technical Support may request a report generated by the Sizing Script to investigate issues with the Process Execution engines. This guide provides steps to enable users to generate reports with meaningful data.
Windows
cd <APPIAN_HOME>/logs
findstr /I /c:"opened gateway" service_manager.log | findstr "execution"
Linux
ps aux | grep "/[a]db pe" | awk '{printf("%-1s %-1s\n","Execution Engine: "$22," | Port: "$16) }'
To run the Sizing Script, follow the steps in the Appian documentation. Below are three example use cases for generating a sizing report.
Generating a summary report for a single execution engine
This report provides an overview of the size of process data in a given execution engine. This is useful for quickly determining whether an engine is encountering problems due to excessive process sizing.
<APPIAN_HOME>/server/_scripts/tools/sizing.sh(.bat) summary -path "<Path to report>" -host <Engine hostname from appian-topology.xml> -port <Port from Step 1>
Generating a process model breakdown
This report summarizes the size of each process model in a given execution engine. This is useful for determining specific process models that are causing engine contention.
<APPIAN_HOME>/server/_scripts/tools/sizing.sh(.bat) processmodel -all -path "<Path to report>" -host <Engine hostname from appian-topology.xml> -port <Port from Step 1>
Generating a process size summary for instances of a given process model
This report is useful for isolating excessively large process instances after identifying process models of concern with the processmodel report.
<APPIAN_HOME>/server/_scripts/tools/sizing.sh(.bat) process -path "<Path to report>" -host <Engine hostname from appian-topology.xml> -port <Port from Step 1> -uuid <UUID(s) of large process model(s)>
Points to consider
An error occurred:closeRun "sizing.sh help" to view help file.
This article applies to all versions of Appian.
Last Reviewed: December 2023