RuleWizard ships with standalone test execution and code analysis tools, such as SOAtest and C/C++test DesktopProfessional, but it is also available as a standalone application from the Parasoft Marketplace.the Parasoft customer portal.

Requirements

• RuleWizard support the same systems as the Parasoft tools they are packaged with. For example, the RuleWizard distribution packaged with SOAtest for macOS will run on macOS.
• The standalone RuleWizard application is only supported on Windows and Linux. 

RuleWizard Packaged with Parasoft Tools

If you are using the instance shipped with your Parasoft product, you can launch RuleWizard from the Parasoft menu.  

Adding a License

A RuleWizrd license with the RuleWizard feature enabled is required. Refer to the documentation for your Parasoft tool for instructions on how to add a license.

...

If the RuleWizard feature is not enabled, contact your Parasoft representative for information on how to add RuleWizard to your license.

Image Added

Standalone RuleWizard Application

1. Extract the contents of the ParasoftRuleWizard-<version>.zip archive.
2. Run the .sh or .bat script to launch RuleWizard.

On some instances of Linux and Mac OS, you may need to set the temporary directory variable. Open the .sh script and specify the variable, e.g.:

Adding a License

When you launch RuleWizard for the first time, you will be prompted to enter a license. You can add a local or network license to the standalone version.

Anchor
local_license local_license

Local License

Enable the Use node-locked license option and enter the license password you received from Parasoft.

Image Added

Anchor
network_license network_license

Network License

Enable the Use license server option and specify from where RuleWizard should request a license. Parasoft tools can request licenses from either the License Server integrated with DTP or a standalone instance of License Server.

• Specify the Base URL of the License Server.

If the DTP that the License Server is integrated with is deployed to a location other than the root of the host server, the URL should include a context path (a relative path from the host name; for example: https://mydtp.mycompany.com:8443/contextPath). This may be the case if your organization uses a reverse proxy. Refer to the DTP documentation for additional information about reverse proxy server configuration and context path configuration.

The context pathis not supported for a standalone License Server.

• Specify the Username and Password, if needed.

Image Added
You can click Test Connection to verify the settings.