KB-2283 How to run the Sizing Script

Maggie Deppe-Walker — Mon, 18 Dec 2023 23:45:57 GMT

Current Revision posted to Appian Knowledge Base by Maggie Deppe-Walker on 12/18/2023 11:45:57 PM

Purpose

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.

Instructions

1. Identify port usage

Windows

Open up command prompt (cmd.exe) with the appropriate privileges for your Appian installation.
Navigate to the logs directory:
cd <APPIAN_HOME>/logs
Run the following command to identify the port used by each execution engine gateway:
findstr /I /c:"opened gateway" service_manager.log | findstr "execution"
1. Note: The numbers shown in the bottom lines of the output of the command correspond to the engine gateways (the number of lines varies based on the number of execution engines in your environment)
Add 1 to each port number to identify the port used by each process execution engine database

Linux

Run the following command from a Linux terminal:
ps aux | grep "/[a]db pe" | awk '{printf("%-1s %-1s\n","Execution Engine: "$22," | Port: "$16) }'
Analyze the output for the corresponding engine-port pairs.

2. Run the Sizing Script

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

When the Sizing Script is run on a port belonging to a non-execution engine, the generated report will be an empty CSV file. It will not throw any errors.
When the script is run on the port corresponding to an engine gateway instead of the engine itself, it will throw the following message:
```
An error occurred:
close
Run "sizing.sh help" to view help file.
```

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: December 2023

Tags: How To, engines, how-to, scripts

KB-2283 How to run the Sizing Script

pauline.delacruz — Mon, 18 Dec 2023 17:35:46 GMT

Revision 70 posted to Appian Knowledge Base by pauline.delacruz on 12/18/2023 5:35:46 PM

Purpose

Instructions

1. Identify port usage

Windows

Open up command prompt (cmd.exe) with the appropriate privileges for your Appian installation.
Navigate to the logs directory:
cd <APPIAN_HOME>/logs
Run the following command to identify the port used by each execution engine gateway:
findstr /I /c:"opened gateway" service_manager.log | findstr "execution"
1. Note: numbers shown in the bottom 3 lines (or however many lines correspond to the number of execution engines on your environment) of the output of the command
Add 1 to each port number to identify the port used by each process execution engine database

Linux

Run the following command from a Linux terminal:
ps aux | grep "/[a]db pe" | awk '{printf("%-1s %-1s\n","Execution Engine: "$22," | Port: "$16) }'
Analyze the output for the corresponding engine-port pairs.

2. Run the Sizing Script

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

<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.

Points to consider

When the Sizing Script is run on a port belonging to a non-execution engine, the generated report will be an empty CSV file. It will not throw any errors.
When the script is run on the port corresponding to an engine gateway instead of the engine itself, it will throw the following message:
```
An error occurred:
close
Run "sizing.sh help" to view help file.
```

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: December 2023

Tags: How To, engines, how-to, scripts

[DRAFT SP-9343] KB-XXXX A guide to running the Sizing Script

pauline.delacruz — Mon, 18 Dec 2023 17:08:25 GMT

Revision 69 posted to Appian Knowledge Base by pauline.delacruz on 12/18/2023 5:08:25 PM

Purpose

Instructions

1. Identify port usage

Windows

Open up command prompt (cmd.exe) with the appropriate privileges for your Appian installation.
Navigate to the logs directory:
cd <APPIAN_HOME>/logs
Run the following command to identify the port used by each execution engine gateway:
findstr /I /c:"opened gateway" service_manager.log | findstr "execution"
1. Note: numbers shown in the bottom 3 lines (or however many lines correspond to the number of execution engines on your environment) of the output of the command
Add 1 to each port number to identify the port used by each process execution engine database

Linux

Run the following command from a Linux terminal:
ps aux | grep "/[a]db pe" | awk '{printf("%-1s %-1s\n","Execution Engine: "$22," | Port: "$16) }'
Analyze the output for the corresponding engine-port pairs.

2. Run the Sizing Script

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

<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.

Points to consider

When the Sizing Script is run on a port belonging to a non-execution engine, the generated report will be an empty CSV file. It will not throw any errors.
When the script is run on the port corresponding to an engine gateway instead of the engine itself, it will throw the following message:
```
An error occurred:
close
Run "sizing.sh help" to view help file.
```

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: December 2023

Tags: How To, engines, how-to, scripts

[DRAFT SP-9343] KB-XXXX A guide to running the Sizing Script

pauline.delacruz — Wed, 06 Dec 2023 15:18:24 GMT

Revision 68 posted to Appian Knowledge Base by pauline.delacruz on 12/6/2023 3:18:24 PM

Purpose

Instructions

1. Identify port usage

Windows

Open up command prompt (cmd.exe) with the appropriate privileges for your Appian installation
Navigate to the logs directory:
cd <APPIAN_HOME>/logs
Run the following command to identify the port used by each execution engine gateway:
findstr /I /c:"opened gateway" service_manager.log | findstr "execution"
Note the port numbers shown in the bottom 3 lines (or however many lines correspond to the number of execution engines on your environment) of the output of the command
Add 1 to each port number to identify the port used by each process execution engine database

Linux

Run the following command from a Linux terminal:
ps aux | grep "/[a]db pe" | awk '{printf("%-1s %-1s\n","Execution Engine: "$22," | Port: "$16) }'
Analyze the output for the corresponding engine-port pairs.

2. Run the Sizing Script

To run the Sizing Script, follow the steps in the Appian documentation. Below are 3 example use cases for generating a sizing report.

Generating a summary report for a single execution engine

<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.

Points to consider

When the Sizing Script is run on a port belonging to a non-execution engine, the generated report will be an empty CSV file. It will not throw any errors.
When the script is run on the port corresponding to an engine gateway instead of the engine itself, it will throw the following message:
```
An error occurred:
close
Run "sizing.sh help" to view help file.
```

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: December 2023

Tags: How To, engines, how-to, scripts

[DRAFT SP-9343] KB-XXXX A guide to running the Sizing Script

Adam Walker — Wed, 06 Dec 2023 07:12:14 GMT

Revision 67 posted to Appian Knowledge Base by Adam Walker on 12/6/2023 7:12:14 AM

Purpose

Instructions

1. Identify port usage

Windows

Open up command prompt (cmd.exe) with the appropriate privileges for your Appian installation
Navigate to the logs directory:
cd <APPIAN_HOME>/logs
Run the following command to identify the port used by each execution engine gateway:
findstr /I /c:"opened gateway" service_manager.log | findstr "execution"
Note the port numbers shown in the bottom 3 lines (or however many lines correspond to the number of execution engines on your environment) of the output of the command
Add 1 to each port number to identify the port used by each process execution engine database

Linux

Run the following command from a Linux terminal:
ps aux | grep "/[a]db pe" | awk '{printf("%-1s %-1s\n","Execution Engine: "$22," | Port: "$16) }'
Analyse the output for the corresponding engine-port pairs.

2. Run the Sizing Script

To run the Sizing Script, follow the steps in the Appian documentation. Below are 3 example use cases for generating a sizing report.

Generating a summary report for a single execution engine

<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 summarises 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.

Points to consider

When the Sizing Script is run on a port belonging to a non-execution engine, the generated report will be an empty CSV file. It will not throw any errors.
When the script is run on the port corresponding to an engine gateway instead of the engine itself, it will throw the following message:
```
An error occurred:
close
Run "sizing.sh help" to view help file.
```

Affected Versions

This article applies to all versions of Appian.

Tags: How To, engines, how-to, scripts

[DRAFT SP-9343] KB-XXXX A guide to running the Sizing Script

Adam Walker — Wed, 06 Dec 2023 07:11:19 GMT

Revision 66 posted to Appian Knowledge Base by Adam Walker on 12/6/2023 7:11:19 AM

Purpose

Instructions

1. Identify port usage

Windows

Open up command prompt (cmd.exe) with the appropriate privileges for your Appian installation
Navigate to the logs directory:
cd <APPIAN_HOME>/logs
Run the following command to identify the port used by each execution engine gateway:
findstr /I /c:"opened gateway" service_manager.log | findstr "execution"
Note the port numbers shown in the bottom 3 lines (or however many lines correspond to the number of execution engines on your environment) of the output of the command
Add 1 to each port number to identify the port used by each process execution engine database

Linux

Run the following command from a Linux terminal:
ps aux | grep "/[a]db pe" | awk '{printf("%-1s %-1s\n","Execution Engine: "$22," | Port: "$16) }'
Analyse the output for the corresponding engine-port pairs.

2. Run the Sizing Script

To run the Sizing Script, follow the steps in the Appian documentation. Below are 3 example use cases for generating a sizing report.

Generating a summary report for a single execution engine

<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 summarises 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 individual process instances that are excessively large after identifying process models of concern with the processmodel report.

Points to consider

When the Sizing Script is run on a port belonging to a non-execution engine, the generated report will be an empty CSV file. It will not throw any errors.
When the script is run on the port corresponding to an engine gateway instead of the engine itself, it will throw the following message:
```
An error occurred:
close
Run "sizing.sh help" to view help file.
```

Affected Versions

This article applies to all versions of Appian.

Tags: How To, engines, how-to, scripts

[DRAFT SP-9343] KB-XXXX A guide to running the Sizing Script

Adam Walker — Wed, 06 Dec 2023 07:10:18 GMT

Revision 65 posted to Appian Knowledge Base by Adam Walker on 12/6/2023 7:10:18 AM

Purpose

Instructions

1. Identify port usage

Windows

Open up command prompt (cmd.exe) with the appropriate privileges for your Appian installation
Navigate to the logs directory:
cd <APPIAN_HOME>/logs
Run the following command to identify the port used by each execution engine gateway:
findstr /I /c:"opened gateway" service_manager.log | findstr "execution"
Note the port numbers shown in the bottom 3 lines (or however many lines correspond to the number of execution engines on your environment) of the output of the command
Add 1 to each port number to identify the port used by each process execution engine database

Linux

Run the following command from a Linux terminal:
ps aux | grep "/[a]db pe" | awk '{printf("%-1s %-1s\n","Execution Engine: "$22," | Port: "$16) }'
Analyse the output for the corresponding engine-port pairs.

2. Run the Sizing Script

To run the Sizing Script, follow the steps in the Appian documentation. Below are 2 common use cases for generating a sizing report.

Generating a summary report for a single execution engine

<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 summarises 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 individual process instances that are excessively large after identifying process models of concern with the processmodel report.

Points to consider

When the Sizing Script is run on a port belonging to a non-execution engine, the generated report will be an empty CSV file. It will not throw any errors.
When the script is run on the port corresponding to an engine gateway instead of the engine itself, it will throw the following message:
```
An error occurred:
close
Run "sizing.sh help" to view help file.
```

Affected Versions

This article applies to all versions of Appian.

Tags: How To, engines, how-to, scripts

[DRAFT SP-9343] KB-XXXX A guide to running the Sizing Script

Adam Walker — Wed, 06 Dec 2023 07:09:47 GMT

Revision 64 posted to Appian Knowledge Base by Adam Walker on 12/6/2023 7:09:47 AM

Purpose

Instructions

1. Identify port usage

Windows

Open up command prompt (cmd.exe) with the appropriate privileges for your Appian installation
Navigate to the logs directory:
cd <APPIAN_HOME>/logs
Run the following command to identify the port used by each execution engine gateway:
findstr /I /c:"opened gateway" service_manager.log | findstr "execution"
Note the port numbers shown in the bottom 3 lines (or however many lines correspond to the number of execution engines on your environment) of the output of the command
Add 1 to each port number to identify the port used by each process execution engine database

Linux

Run the following command from a Linux terminal:
ps aux | grep "/[a]db pe" | awk '{printf("%-1s %-1s\n","Execution Engine: "$22," | Port: "$16) }'
Analyse the output for the corresponding engine-port pairs.

2. Run the Sizing Script

To run the Sizing Script, follow the steps in the Appian documentation. Below are 2 common use cases for generating a sizing report.

Generating a summary report for a single execution engine

<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 summarises 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 individual process instances that are excessively large after identifying process models of concern with the processmodel report.

Points to consider

When the Sizing Script is run on a port belonging to a non-execution engine, the generated report will be an empty CSV file. It will not throw any errors.
When script is run on the port corresponding to an engine gateway instead of the engine itself, it will throw the following message:
```
An error occurred:
close
Run "sizing.sh help" to view help file.
```

Affected Versions

This article applies to all versions of Appian.

Tags: How To, engines, how-to, scripts

[DRAFT SP-9343] KB-XXXX A guide to running the Sizing Script

Adam Walker — Wed, 06 Dec 2023 07:07:31 GMT

Revision 63 posted to Appian Knowledge Base by Adam Walker on 12/6/2023 7:07:31 AM

Purpose

Instructions

1. Identify port usage

Windows

Open up command prompt (cmd.exe) with the appropriate privileges for your Appian installation
Navigate to the logs directory:
cd <APPIAN_HOME>/logs
Run the following command to identify the port used by each execution engine gateway:
findstr /I /c:"opened gateway" service_manager.log | findstr "execution"
Note the port numbers shown in the bottom 3 lines (or however many lines correspond to the number of execution engines on your environment) of the output of the command
Add 1 to each port number to identify the port used by each process execution engine database

Linux

Run the following command from a Linux terminal:
ps aux | grep "/[a]db pe" | awk '{printf("%-1s %-1s\n","Execution Engine: "$22," | Port: "$16) }'
Analyse the output for the corresponding engine-port pairs.

2. Run the Sizing Script

To run the Sizing Script, follow the steps in the Appian documentation. Below are 2 common use cases for generating a sizing report.

Generating a summary report for a single execution engine

<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 summarises 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 specified process model

This report is useful for isolating individual process instances that are excessively large after identifying process models of concern with the processmodel report.

Points to consider

When the Sizing Script is run on a port belonging to a non-execution engine, the generated report will be an empty CSV file. It will not throw any errors.
When script is run on the port corresponding to an engine gateway instead of the engine itself, it will throw the following message:
```
An error occurred:
close
Run "sizing.sh help" to view help file.
```

Affected Versions

This article applies to all versions of Appian.

Tags: How To, engines, how-to, scripts

[DRAFT SP-9343] KB-XXXX A guide to running the Sizing Script

Adam Walker — Wed, 06 Dec 2023 07:06:41 GMT

Revision 62 posted to Appian Knowledge Base by Adam Walker on 12/6/2023 7:06:41 AM

Purpose

Instructions

1. Identify port usage

Windows

Open up command prompt (cmd.exe) with the appropriate privileges for your Appian installation
Navigate to the logs directory:
cd <APPIAN_HOME>/logs
Run the following command to identify the port used by each execution engine gateway:
findstr /I /c:"opened gateway" service_manager.log | findstr "execution"
Note the port numbers shown in the bottom 3 lines (or however many lines correspond to the number of execution engines on your environment) of the output of the command
Add 1 to each port number to identify the port used by each process execution engine database

Linux

Run the following command from a Linux terminal:
ps aux | grep "/[a]db pe" | awk '{printf("%-1s %-1s\n","Execution Engine: "$22," | Port: "$16) }'
Analyse the output for the corresponding engine-port pairs.

2. Run the Sizing Script

To run the Sizing Script, follow the steps in the Appian documentation. Below are 2 common use cases for generating a sizing report.

Generating a summary report for a single execution engine

<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 summarises 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 specified process model

This report is useful for isolating individual process instances that are excessively large after identifying process models of concern with the processmodel report.

Points to consider

When the Sizing Script is run on a port belonging to a non-execution engine, the generated report will be an empty CSV file. It will not throw any errors.
When script is run on the port corresponding to an engine gateway instead of the engine itself, it will throw the following message:
```
An error occurred:
close
Run "sizing.sh help" to view help file.
```
Pay close attention to your syntax when using this script. Extra hyphens or misspellings may cause a kdb+ error to appear when running sizing.sh (.bat). ffff

Affected Versions

This article applies to all versions of Appian.

Tags: How To, engines, how-to, scripts

[DRAFT SP-9343] KB-XXXX A guide to running the Sizing Script

Adam Walker — Wed, 06 Dec 2023 07:05:47 GMT

Revision 61 posted to Appian Knowledge Base by Adam Walker on 12/6/2023 7:05:47 AM

Purpose

Instructions

1. Identify port usage

Windows

Open up command prompt (cmd.exe) with the appropriate privileges for your Appian installation
Navigate to the logs directory:
cd <APPIAN_HOME>/logs
Run the following command to identify the port used by each execution engine gateway:
findstr /I /c:"opened gateway" service_manager.log | findstr "execution"
Note the port numbers shown in the bottom 3 lines (or however many lines correspond to the number of execution engines on your environment) of the output of the command
Add 1 to each port number to identify the port used by each process execution engine database

Linux

Run the following command from a Linux terminal:
ps aux | grep "/[a]db pe" | awk '{printf("%-1s %-1s\n","Execution Engine: "$22," | Port: "$16) }'
Analyse the output for the corresponding engine-port pairs.

2. Run the Sizing Script

To run the Sizing Script, follow the steps in the Appian documentation. Below are 2 common use cases for generating a sizing report.

Generating a summary report for a single execution engine

<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 summarises 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 specified process model

This report is useful for isolating individual process instances that are excessively large after identifying process models of concern with the processmodel report.

Points to consider

When the Sizing Script is run on a port belonging to a non-execution engine, the generated report will be an empty CSV file. It will not throw any errors.
When script is run on the port corresponding to an engine gateway instead of the engine itself, it will throw the following message:
```
An error occurred:
close
Run "sizing.sh help" to view help file.
```
Pay close attention to your syntax when using this script. Extra hyphens or misspellings may cause a kdb+ error to appear when running sizing.sh (.bat). ffff

Affected Versions

This article applies to all versions of Appian.

Tags: How To, engines, how-to, scripts

[DRAFT SP-9343] KB-XXXX A guide to running the Sizing Script

Adam Walker — Wed, 06 Dec 2023 07:05:16 GMT

Revision 60 posted to Appian Knowledge Base by Adam Walker on 12/6/2023 7:05:16 AM

Purpose

Instructions

Purpose
Instructions
- 1. Identify port usage
- 2. Run the Sizing Script
Affected Versions

1. Identify port usage

Windows

Open up command prompt (cmd.exe) with the appropriate privileges for your Appian installation
Navigate to the logs directory:
cd <APPIAN_HOME>/logs
Run the following command to identify the port used by each execution engine gateway:
findstr /I /c:"opened gateway" service_manager.log | findstr "execution"
Note the port numbers shown in the bottom 3 lines (or however many lines correspond to the number of execution engines on your environment) of the output of the command
Add 1 to each port number to identify the port used by each process execution engine database

Linux

Run the following command from a Linux terminal:
ps aux | grep "/[a]db pe" | awk '{printf("%-1s %-1s\n","Execution Engine: "$22," | Port: "$16) }'
Analyse the output for the corresponding engine-port pairs.

2. Run the Sizing Script

To run the Sizing Script, follow the steps in the Appian documentation. Below are 2 common use cases for generating a sizing report.

Generating a summary report for a single execution engine

<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 summarises 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 specified process model

This report is useful for isolating individual process instances that are excessively large after identifying process models of concern with the processmodel report.

Points to consider

When the Sizing Script is run on a port belonging to a non-execution engine, the generated report will be an empty CSV file. It will not throw any errors.
When script is run on the port corresponding to an engine gateway instead of the engine itself, it will throw the following message:
```
An error occurred:
close
Run "sizing.sh help" to view help file.
```
Pay close attention to your syntax when using this script. Extra hyphens or misspellings may cause a kdb+ error to appear when running sizing.sh (.bat). ffff

Affected Versions

This article applies to all versions of Appian.

Tags: How To, engines, how-to, scripts

[DRAFT SP-9343] KB-XXXX A guide to running the Sizing Script

Adam Walker — Wed, 06 Dec 2023 06:52:57 GMT

Revision 59 posted to Appian Knowledge Base by Adam Walker on 12/6/2023 6:52:57 AM

Purpose

Instructions

1. Identify port usage

Windows

Open up command prompt (cmd.exe) with the appropriate privileges for your Appian installation
Navigate to the logs directory:
cd <APPIAN_HOME>/logs
Run the following command to identify the port used by each execution engine gateway:
findstr /I /c:"opened gateway" service_manager.log | findstr "execution"
Note the port numbers shown in the bottom 3 lines (or however many lines correspond to the number of execution engines on your environment) of the output of the command
Add 1 to each port number to identify the port used by each process execution engine database

Linux

Run the following command from a Linux terminal:
ps aux | grep "/[a]db pe" | awk '{printf("%-1s %-1s\n","Execution Engine: "$22," | Port: "$16) }'
Analyse the output for the corresponding engine-port pairs.

2. Run the Sizing Script

To run the Sizing Script, follow the steps in the Appian documentation. Below are 2 common use cases for generating a sizing report.

Generating a summary report for a single execution engine

<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 summarises 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 specified process model

This report is useful for isolating individual process instances that are excessively large after identifying process models of concern with the processmodel report.

Points to consider

When the Sizing Script is run on a port belonging to a non-execution engine, the generated report will be an empty CSV file. It will not throw any errors.
When script is run on the port corresponding to an engine gateway instead of the engine itself, it will throw the following message:
```
An error occurred:
close
Run "sizing.sh help" to view help file.
```
Pay close attention to your syntax when using this script. Extra hyphens or misspellings may cause a kdb+ error to appear when running sizing.sh (.bat). ffff

Affected Versions

This article applies to all versions of Appian.

Tags: How To, engines, how-to, scripts

[DRAFT SP-9343] KB-XXXX A guide to running the Sizing Script

Adam Walker — Wed, 06 Dec 2023 06:42:47 GMT

Revision 58 posted to Appian Knowledge Base by Adam Walker on 12/6/2023 6:42:47 AM

Purpose

Instructions

1. Identify port usage

Windows

Open up command prompt (cmd.exe) with the appropriate privileges for your Appian installation
Navigate to the logs directory:
cd <APPIAN_HOME>/logs
Run the following command to identify the port used by each execution engine gateway:
findstr /I /c:"opened gateway" service_manager.log | findstr "execution"
Note the port numbers shown in the bottom 3 lines (or however many lines correspond to the number of execution engines on your environment) of the output of the command
Add 1 to each port number to identify the port used by each process execution engine database

Linux

Run the following command from a Linux terminal:
ps aux | grep "/[a]db pe" | awk '{printf("%-1s %-1s\n","Execution Engine: "$22," | Port: "$16) }'
Analyse the output for the corresponding engine-port pairs.

2. Run the Sizing Script

To run the Sizing Script, follow the steps in the Appian documentation. Below are 2 common use cases for generating a sizing report.

Generating a summary report for a single execution engine

<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 summarises 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 specified process model

This report is useful for isolating individual process instances that are excessively large after identifying process models of concern with the processmodel report.

Points to consider

When the Sizing Script is run on a port belonging to a non-execution engine, the generated report will be an empty CSV file. It will not throw any errors.
When script is run on the port corresponding to an engine gateway instead of the engine itself, it will throw the following message:
```
An error occured: 
close
Run "sizing.sh help" to view help file.  
```
Pay close attention to your syntax when using this script. Extra hyphens or misspellings may cause a kdb+ error to appear when running sizing.sh (.bat).

Affected Versions

This article applies to all versions of Appian.

Tags: How To, engines, how-to, scripts

[DRAFT SP-9343] KB-XXXX A guide to running the Sizing Script

Adam Walker — Wed, 06 Dec 2023 06:41:58 GMT

Revision 57 posted to Appian Knowledge Base by Adam Walker on 12/6/2023 6:41:58 AM

Purpose

Instructions

1. Identify port usage

Windows

Open up command prompt (cmd.exe) with the appropriate privileges for your Appian installation
Navigate to the logs directory:
cd <APPIAN_HOME>/logs
Run the following command to identify the port used by each execution engine gateway:
findstr /I /c:"opened gateway" service_manager.log | findstr "execution"
Note the port numbers shown in the bottom 3 lines (or however many lines correspond to the number of execution engines on your environment) of the output of the command
Add 1 to each port number to identify the port used by each process execution engine database

Linux

Run the following command from a Linux terminal:
ps aux | grep "/[a]db pe" | awk '{printf("%-1s %-1s\n","Execution Engine: "$22," | Port: "$16) }'
Analyse the output for the corresponding engine-port pairs.

2. Run the Sizing Script

To run the Sizing Script, follow the steps in the Appian documentation. Below are 2 common use cases for generating a sizing report.

Generating a summary report for a single execution engine

<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 summarises 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 specified process model

This report is useful for isolating individual process instances that are excessively large after identifying process models of concern with the processmodel report.

Points to consider

When the Sizing Script is run on a port belonging to a non-execution engine, the generated report will be an empty CSV file. It will not throw any errors.
When script is run on the port corresponding to an engine gateway instead of the engine itself, it will throw the following message:
```
An error occured: 
close
Run "sizing.sh help" to view help file.  
```
Pay close attention to your syntax when using this script. Extra hyphens or misspellings may cause a kdb+ error to appear when running sizing.sh (.bat).

Affected Versions

This article applies to all versions of Appian.

Tags: How To, engines, how-to, scripts

[DRAFT SP-9343] KB-XXXX A guide to running the Sizing Script

Adam Walker — Wed, 06 Dec 2023 06:40:59 GMT

Revision 56 posted to Appian Knowledge Base by Adam Walker on 12/6/2023 6:40:59 AM

Purpose

Instructions

1. Identify port usage

Windows

Open up command prompt (cmd.exe) with the appropriate privileges for your Appian installation
Navigate to the logs directory:
cd <APPIAN_HOME>/logs
Run the following command to identify the port used by each execution engine gateway:
findstr /I /c:"opened gateway" service_manager.log | findstr "execution"
Note the port numbers shown in the bottom 3 lines (or however many lines correspond to the number of execution engines on your environment) of the output of the command
Add 1 to each port number to identify the port used by each process execution engine database

Linux

Run the following command from a Linux terminal:
ps aux | grep "/[a]db pe" | awk '{printf("%-1s %-1s\n","Execution Engine: "$22," | Port: "$16) }'
Analyse the output for the corresponding engine-port pairs.

2. Run the Sizing Script

To run the Sizing Script, follow the steps in the Appian documentation. Below are 2 common use cases for generating a sizing report.

Generating a summary report for a single execution engine

<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 summarises 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 specified process model

This report is useful for isolating individual process instances that are excessively large after identifying process models of concern with the processmodel report.

Points to consider

When the Sizing Script is run on a port belonging to a non-execution engine, the generated report will be an empty CSV file. It will not throw any errors.
When script is run on the port corresponding to an engine gateway instead of the engine itself, it will throw the following message:
```
An error occured: 
close
Run "sizing.sh help" to view help file.  
```
Pay close attention to your syntax when using this script. Extra hyphens or misspellings may cause a kdb+ error to appear when running sizing.sh (.bat). Always check that your syntax is correct before reaching out to Appian Support.

Affected Versions

This article applies to all versions of Appian.

Tags: How To, engines, how-to, scripts

[DRAFT SP-9343] KB-XXXX A guide to running the Sizing Script

Adam Walker — Wed, 06 Dec 2023 06:38:17 GMT

Revision 55 posted to Appian Knowledge Base by Adam Walker on 12/6/2023 6:38:17 AM

Purpose

Instructions

1. Identify port usage

Windows

Open up command prompt (cmd.exe) with the appropriate privileges for your Appian installation
Navigate to the logs directory:
cd <APPIAN_HOME>/logs
Run the following command to identify the port used by each execution engine gateway:
findstr /I /c:"opened gateway" service_manager.log | findstr "execution"
Note the port numbers shown in the bottom 3 lines (or however many lines correspond to the number of execution engines on your environment) of the output of the command
Add 1 to each port number to identify the port used by each process execution engine database

Linux

Run the following command from a Linux terminal:
ps aux | grep "/[a]db pe" | awk '{printf("%-1s %-1s\n","Execution Engine: "$22," | Port: "$16) }'
Analyse the output for the corresponding engine-port pairs.

2. Run the Sizing Script

To run the Sizing Script, follow the steps in the Appian documentation. Below are 2 common use cases for generating a sizing report.

Generating a summary report for a single execution engine

<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 summarises 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 specified process model

This report is useful for isolating individual process instances that are excessively large after identifying process models of concern with the processmodel report.

Points to consider

When the Sizing Script is run on a port belonging to a non-execution engine, the generated report will be an empty CSV file. It will not throw any errors.
When sizing is run on the port corresponding to an engine gateway instead of the engine itself, it will throw the following message:
```
An error occured: 
close
Run "sizing.sh help" to view help file.  
```

Affected Versions

This article applies to all versions of Appian.

Tags: How To, engines, how-to, scripts

[DRAFT SP-9343] KB-XXXX A guide to running the Sizing Script

Adam Walker — Wed, 06 Dec 2023 06:37:13 GMT

Revision 54 posted to Appian Knowledge Base by Adam Walker on 12/6/2023 6:37:13 AM

Purpose

Instructions

1. Identify port usage

Windows

Open up command prompt (cmd.exe) with the appropriate privileges for your Appian installation
Navigate to the logs directory:
cd <APPIAN_HOME>/logs
Run the following command to identify the port used by each execution engine gateway:
findstr /I /c:"opened gateway" service_manager.log | findstr "execution"
Note the port numbers shown in the bottom 3 lines (or however many lines correspond to the number of execution engines on your environment) of the output of the command
Add 1 to each port number to identify the port used by each process execution engine database

Linux

Run the following command from a Linux terminal:
ps aux | grep "/[a]db pe" | awk '{printf("%-1s %-1s\n","Execution Engine: "$22," | Port: "$16) }'
Analyse the output for the corresponding engine-port pairs.

2. Run the Sizing Script

To run the Sizing Script, follow the steps in the Appian documentation. Below are 2 common use cases for generating a sizing report.

Generating a summary report for a single execution engine

<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 summarises 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 specified process model

This report is useful for isolating individual process instances that are excessively large after identifying process models of concern with the processmodel report.

3. Points to consider

When the Sizing Script is run on a port belonging to a non-execution engine, the generated report will be an empty CSV file. It will not throw any errors.
When sizing is run on the port corresponding to an engine gateway instead of the engine itself, it will throw the following message:
```
An error occured: 
close
Run "sizing.sh help" to view help file.  
```

Affected Versions

This article applies to all versions of Appian.

Tags: How To, engines, how-to, scripts

[DRAFT SP-9343] KB-XXXX A guide to running the Sizing Script

Adam Walker — Wed, 06 Dec 2023 06:35:52 GMT

Revision 53 posted to Appian Knowledge Base by Adam Walker on 12/6/2023 6:35:52 AM

Purpose

Instructions

1. Identify port usage

Windows

Open up command prompt (cmd.exe) with the appropriate privileges for your Appian installation
Navigate to the logs directory:
cd <APPIAN_HOME>/logs
Run the following command to identify the port used by each execution engine gateway:
findstr /I /c:"opened gateway" service_manager.log | findstr "execution"
Note the port numbers shown in the bottom 3 lines (or however many lines correspond to the number of execution engines on your environment) of the output of the command
Add 1 to each port number to identify the port used by each process execution engine database

Linux

Run the following command from a Linux terminal:
ps aux | grep "/[a]db pe" | awk '{printf("%-1s %-1s\n","Execution Engine: "$22," | Port: "$16) }'
Analyse the output for the corresponding engine-port pairs.

2. Run the Sizing Script

To run the Sizing Script, follow the steps in the Appian documentation. Below are 2 common use cases for generating a sizing report.

Generating a summary report for a single execution engine

<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 summarises 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 specified process model

This report is useful for isolating individual process instances that are excessively large after identifying process models of concern with the processmodel report.

3. Points to consider

When the Sizing Script is run on a port belonging to a non-execution engine, the generated report will be an empty CSV file. It will not throw any errors.
When sizing is run on the port corresponding to an engine gateway instead of the engine itself, it will throw the following message:
```
An error occured: 
close
Run "sizing.sh help" to view help file.  
```

Affected Versions

This article applies to all versions of Appian.

Tags: How To, engines, how-to, scripts

[DRAFT SP-9343] KB-XXXX A guide to running the Sizing Script

Adam Walker — Wed, 06 Dec 2023 06:35:24 GMT

Revision 52 posted to Appian Knowledge Base by Adam Walker on 12/6/2023 6:35:24 AM

Purpose

Instructions

1. Identify port usage

Windows

Open up command prompt (cmd.exe) with the appropriate privileges for your Appian installation
Navigate to the logs directory:
cd <APPIAN_HOME>/logs
Run the following command to identify the port used by each execution engine gateway:
findstr /I /c:"opened gateway" service_manager.log | findstr "execution"
Note the port numbers shown in the bottom 3 lines (or however many lines correspond to the number of execution engines on your environment) of the output of the command
Add 1 to each port number to identify the port used by each process execution engine database

Linux

Run the following command from a Linux terminal:
ps aux | grep "/[a]db pe" | awk '{printf("%-1s %-1s\n","Execution Engine: "$22," | Port: "$16) }'
Analyse the output for the corresponding engine-port pairs.

2. Run the Sizing Script

To run the Sizing Script, follow the steps in the Appian documentation. Below are 2 common use cases for generating a sizing report.

Generating a summary report for a single execution engine

<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 summarises 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 specified process model

This report is useful for isolating individual process instances that are excessively large after identifying process models of concern with the processmodel report.

Points to consider

When the Sizing Script is run on a port belonging to a non-execution engine, the generated report will be an empty CSV file. It will not throw any errors.
When sizing is run on the port corresponding to an engine gateway instead of the engine itself, it will throw the following message:
```
An error occured: 
close
Run "sizing.sh help" to view help file.  
```

Affected Versions

This article applies to all versions of Appian.

Tags: How To, engines, how-to, scripts

[DRAFT SP-9343] KB-XXXX A guide to running the Sizing Script

Adam Walker — Wed, 06 Dec 2023 06:34:49 GMT

Revision 51 posted to Appian Knowledge Base by Adam Walker on 12/6/2023 6:34:49 AM

Purpose

Instructions

1. Identify port usage

Windows

Open up command prompt (cmd.exe) with the appropriate privileges for your Appian installation
Navigate to the logs directory:
cd <APPIAN_HOME>/logs
Run the following command to identify the port used by each execution engine gateway:
findstr /I /c:"opened gateway" service_manager.log | findstr "execution"
Note the port numbers shown in the bottom 3 lines (or however many lines correspond to the number of execution engines on your environment) of the output of the command
Add 1 to each port number to identify the port used by each process execution engine database

Linux

Run the following command from a Linux terminal:
ps aux | grep "/[a]db pe" | awk '{printf("%-1s %-1s\n","Execution Engine: "$22," | Port: "$16) }'
Analyse the output for the corresponding engine-port pairs.

2. Run the Sizing Script

To run the Sizing Script, follow the steps in the Appian documentation. Below are 2 common use cases for generating a sizing report.

Generating a summary report for a single execution engine

<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 summarises 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 specified process model

This report is useful for isolating individual process instances that are excessively large after identifying process models of concern with the processmodel report.

3. Points to consider

When the Sizing Script is run on a port belonging to a non-execution engine, the generated report will be an empty CSV file. It will not throw any errors.
When sizing is run on the port corresponding to an engine gateway instead of the engine itself, it will throw the following message:
```
An error occured: 
close
Run "sizing.sh help" to view help file.  
```

Affected Versions

This article applies to all versions of Appian.

Tags: How To, engines, how-to, scripts

KB-2283 How to run the Sizing Script

KB-2283 How to run the Sizing Script

Purpose

Instructions

1. Identify port usage

2. Run the Sizing Script

Affected Versions

KB-2283 How to run the Sizing Script

Purpose

Instructions

1. Identify port usage

2. Run the Sizing Script

Affected Versions

[DRAFT SP-9343] KB-XXXX A guide to running the Sizing Script

Purpose

Instructions

1. Identify port usage

2. Run the Sizing Script

Affected Versions

[DRAFT SP-9343] KB-XXXX A guide to running the Sizing Script

Purpose

Instructions

1. Identify port usage

2. Run the Sizing Script

Affected Versions

[DRAFT SP-9343] KB-XXXX A guide to running the Sizing Script

Purpose

Instructions

1. Identify port usage

2. Run the Sizing Script

Affected Versions

[DRAFT SP-9343] KB-XXXX A guide to running the Sizing Script

Purpose

Instructions

1. Identify port usage

2. Run the Sizing Script

Affected Versions

[DRAFT SP-9343] KB-XXXX A guide to running the Sizing Script

Purpose

Instructions

1. Identify port usage

2. Run the Sizing Script

Affected Versions

[DRAFT SP-9343] KB-XXXX A guide to running the Sizing Script

Purpose

Instructions

1. Identify port usage

2. Run the Sizing Script

Affected Versions

[DRAFT SP-9343] KB-XXXX A guide to running the Sizing Script

Purpose

Instructions

1. Identify port usage

2. Run the Sizing Script

Affected Versions

[DRAFT SP-9343] KB-XXXX A guide to running the Sizing Script

Purpose

Instructions

1. Identify port usage

2. Run the Sizing Script

Affected Versions

[DRAFT SP-9343] KB-XXXX A guide to running the Sizing Script

Purpose

Instructions

1. Identify port usage

2. Run the Sizing Script

Affected Versions

[DRAFT SP-9343] KB-XXXX A guide to running the Sizing Script

Purpose

Instructions

Table of Contents

1. Identify port usage

2. Run the Sizing Script

Affected Versions

[DRAFT SP-9343] KB-XXXX A guide to running the Sizing Script

Purpose

Instructions

1. Identify port usage

2. Run the Sizing Script

Affected Versions