Using PowerShell Scripts

The Configuration Tool CLI creates and downloads PowerShell scripts for the core ScanCentral DAST containers. These scripts offer the following options:

Use one script to pull images of the DAST API, DAST Global Service, and DAST Utility Service, and then start the containers.
Use two scripts: one to pull the images, and then another to start the containers.

You use the script or scripts on the host where you want to run the DAST API, DAST Global Service, and DAST Utility Service containers.

For information on how to use the PowerShell scripts to pull a Windows version of the Fortify WebInspect on Docker image and start the container as a DAST sensor, see the Micro Focus Fortify WebInspect and OAST on Docker User Guide.

Using One Script

Use the following process to use a single PowerShell script to pull images and start the containers.

Stage Description

Stage	Description
1.	Copy the following files to the host where you want to run the DAST API, DAST Global Service, and DAST Utility Service containers: `DAST-api.pfx` (Required only if generated by the Configuration Tool CLI) `DAST-utilityservice.pfx` (Required only if generated by the Configuration Tool CLI) `pull-and-start-containers.ps1`
2.	On this same host, start Windows PowerShell ISE as Administrator. For more information about using PowerShell, refer to your Windows PowerShell documentation.
3.	To avoid errors regarding non-digitally signed scripts, run the contents of the `pull-and-start-containers.ps1` script as follows: Copy the contents from the `pull-and-start-containers.ps1` script. Paste the contents in the PowerShell ISE script pane. Click the Run Selection icon. Note: Alternatively, you can set the execution policy to allow all scripts, and then run the script as follows: `& "<drive>:<path_to_script>\pull-and-start-containers.ps1"` For more information about setting the execution policy, refer to your Windows PowerShell documentation. The DAST API, DAST Global Service, and DAST Utility Service images are pulled and the containers are started.

Copy the following files to the host where you want to run the DAST API, DAST Global Service, and DAST Utility Service containers:

DAST-api.pfx (Required only if generated by the Configuration Tool CLI)
DAST-utilityservice.pfx (Required only if generated by the Configuration Tool CLI)
pull-and-start-containers.ps1

2. On this same host, start Windows PowerShell ISE as Administrator. For more information about using PowerShell, refer to your Windows PowerShell documentation.

To avoid errors regarding non-digitally signed scripts, run the contents of the pull-and-start-containers.ps1 script as follows:

Copy the contents from the pull-and-start-containers.ps1 script.
Paste the contents in the PowerShell ISE script pane.
Click the Run Selection icon.

Note: Alternatively, you can set the execution policy to allow all scripts, and then run the script as follows:

& "<drive>:<path_to_script>\pull-and-start-containers.ps1"

For more information about setting the execution policy, refer to your Windows PowerShell documentation.

The DAST API, DAST Global Service, and DAST Utility Service images are pulled and the containers are started.

Using Two Scripts

Use the following process to use separate pull and start PowerShell scripts.

Stage	Description
1.	Copy the following files to the host where you want to run the DAST API, DAST Global Service, and DAST Utility Service containers: `DAST-api.pfx` (Required only if generated by the Configuration Tool CLI) `DAST-utilityservice.pfx` (Required only if generated by the Configuration Tool CLI) `pull-images.ps1` `start-containers.ps1`
2.	On this same host, start Windows PowerShell ISE as Administrator. For more information about using PowerShell, refer to your Windows PowerShell documentation.
3.	Pull the images. To avoid errors regarding non-digitally signed scripts, run the contents of the `pull-images.ps1` script as follows: Copy the contents from the `pull-images.ps1` script. Paste the contents in the PowerShell ISE script pane. Click the Run Selection icon. Note: Alternatively, you can set the execution policy to allow all scripts, and then run the script as follows: `& "<drive>:<path_to_script>\pull-images.ps1"` For more information about setting the execution policy, refer to your Windows PowerShell documentation. The DAST API, DAST Global Service, and DAST Utility Service images are pulled.
4.	Start the containers. To avoid errors regarding non-digitally signed scripts, run the contents of the `start-containers.ps1` script as follows: Copy the contents from the `start-containers.ps1` script. Paste the contents in the PowerShell ISE script pane. Click the Run Selection icon. Note: Alternatively, if you set the execution policy to allow all scripts as described in Stage 3, you can run the script as follows: `& "<drive>:<path_to_script>\start-containers.ps1"` The DAST API, DAST Global Service, and DAST Utility Service containers are started.