This topic provides a general guide on how to add projects, .pva (Parasoft Virtual Asset) files and Responder suites using Virtualize’s various wizards. This section includes:
Creating Action Suites and .pvn files
The process for creating action suites and .pvn files for provisioning actions is very similar to the process for creating Responder suites and .pvas. For details on functionality specific to action suites, see Defining Provisioning Actions.
Wizard Descriptions
For a description of the various wizards available for adding projects, .pva files, and Responder suites, see Overview of Wizards in Virtualize.
Projects, .pva files, and Responder Suites
A project (an entity created by Eclipse) can contain any number of Virtualize-specific .pva files. Projects can also contain source files you want to use with Virtualize, and any other resources that make sense for your environment.
Each .pva (virtual asset) file can include any number of Responder suites.
A Responder suite is a collection of virtual assets and related items (such as data source files).
Any .pvas and responder suites that are created in the VirtualAssets project will be automatically deployed to the local server.
Creating an Empty Project
You can create an empty project as follows:
- Open the pull-down menu for the New toolbar button (top left) then choose Project.
- Choose Virtualize> Empty Project, then click Next.
- Enter a name for the project, change the destination if needed, then click Finish.
Adding a New .pva File to an Existing Project
To add a new .pva file to an existing project:
- Do one of the following:
- Right click the project node, and select Add New> .pva File from the shortcut menu.
- Choose File > New > .pva File.
- In the New .pva File wizard that opens, select the project that you want to contain the .pva file, enter a name for the .pva file, then click Next.
You can then complete the wizard to specify how you want to create virtual assets. For help selecting and completing the available wizards, see Overview of Wizards in Virtualize.
Migrating a SOAtest .tst file to a Virtualize .pva File
If you have an existing SOAtest .tst files with emulated services, you can convert it to a .pva file by changing the extension from .tst to .pva, then importing it into Virtualize (e.g., you could create a project using the Virtualize> Migration for Existing Users> Create Project From Existing Responder Suites wizard).
Adding a Responder Suite
To create a new Responder suite:
- Do one of the following:
- Select the Virtual Asset Explorer node where you want to add the new Responder suite, then click the Add Responder suite button:
- Right-click the Virtual Asset Explorer node where you want to add the new Responder suite, then choose Add New> Responder suite from the shortcut menu.
- Select the Virtual Asset Explorer node where you want to add the new Responder suite, then click the Add Responder suite button:
For help selecting and completing the available wizards, see Overview of Wizards in Virtualize.
Using Eclipse Java Projects in Virtualize
Creating a New Virtualize Java Project
To create a new Virtualize Java project:
- Choose File> New> Project.
- Select Virtualize> Custom Development> Virtualize Java Project, then click Next.
- Complete this wizard, which has the same options as Eclipse’s Java Project wizard.
- Click Finish.
Your new Java project will be shown in the Package Explorer view in the Eclipse Java development perspective. The project's build path will automatically have the jar files needed in order to use Virtualize 's Extensibility API. Any Java classes added to your project can be accessed by Extension tools in your Virtualize Responder suite.
Using an Existing Java Project
To use an existing Java project from your workspace, you must first add that Java project to Virtualize 's classpath as follows:
- Choose Parasoft> Preferences.
- Open the Parasoft> System Properties page.
- Click the Add Java Project button and choose the appropriate project.
The selected Java Project's build output folder and build path entries will be added to the classpath table.
If the Automatically reload classes option is enabled, then Virtualize will attempt to reload classes from your Eclipse project after being modified or recompiled. The Reload button can also be used to force Virtualize to reload classes from the classpath entries.
