Submitting local translation and remote scan requests
You can submit a project that OpenText SAST has already translated to your OpenText ScanCentral SAST sensors for remote scanning. To submit a scan request to perform only the scan phase, use the start command with either the --build_id (-b) or the ‑mbs option to identify the local translation or an existing mobile build session file together with the -scan option. The following is an example of a scan request to submit a remote scan:
scancentral -sscurl <ssc_url> -ssctoken <token> start -b <build_id> -scan
You can include supported OpenText SAST scan options in the scan request (see Options Accepted for -sargs (--scan-args)). You must include only the OpenText SAST analysis options after the –scan option. If the parameter for the option you specify includes a space, you must enclose it in quotes. For example:
-scan –build-label "Application 5.4 June 8, yyyy"
You can also perform a local translation and remote scan using the OpenText ScanCentral SASTpackage command and the PackageScanner tool. For more details and an example, see Using the PackageScanner tool.
If the scan request is successful, you will receive a job token. The OpenText ScanCentral SAST sensor pulls the scan request from the Controller, processes it, and publishes the results to the Controller.
By default, jobs submitted and scan results (FPR files) cannot be larger than 1 GB. Before you start large scans, review Optimizing Scan Performance.
See also