Requirements

Refer to the SOAtest and Virtualize Compatibility with CTP section for version cross-compatibility.

Integrating Virtualize Server with CTP

 Connecting Virtualize to CTP is required for:

• Making Virtualize service virtualization assets (including virtual assets, proxies, data groups, and performance pro­files, and provisioning actions) available in CTP.
• Allowing these assets to be provisioned from CTP.
• Creating and managing service virtualization assets from CTP.
• Viewing Virtualize Server events in CTP.

A Service Enabled license is required to connect to CTP.

To connect a Virtualize Server to CTP:

1. In your Virtualize Server, go to Parasoft > Preferences > Continuous Testing Platform.
2. Enter the name and connection URL for your server. The protocol, machine name, and port are required. In addition, you need to enter any path parameters preceding /em. For example, if the CTP Server is located at http://mymachine.mycompany.com:8080/some/path/em, the Server URL field should contain http://mymachine.mycompany.com:8080/some/path (without the /em suffix).
   
3. Enable Notify CTP of virtual asset deployment.
4. If your CTP administrator has configured security for your CTP installation, you also need to enter a valid username and password (preferably with an admin role).
5. Click Test Connection to verify correct settings.
6. Click OK to save.
7. If the Virtualize Server is not already running, start it now.
8. Open CTP in a browser, then open the Service Virtualization module.
9. Confirm that the Virtualize Server listed in the tree without an Offline or Error status. 

You can now manage the Virtualize Server with CTP. Whenever you deploy a new virtual asset, re-deploy an existing one, or modify a message proxy, Virtualize will update CTP.

Integrating SOAtest Server with CTP

Connecting SOAtest to CTP is required for:

• Making SOAtest test assets (including test scenarios, data groups, variables, and so on) available in CTP.
• Allowing SOAtest test assets to be executed during CTP provisioning or run for health checks.
• Creating and managing test assets from CTP.
• Creating and executing test jobs from CTP.

A SOAtest "Server API Enabled" license is required to connect to CTP.

To connect a SOAtest Server to CTP:

1. In your SOAtest Server, go to Parasoft > Preferences > Continuous Testing Platform.
2. Enter the name and connection URL for your server. The protocol, machine name, and port are required. In addition, you need any path parameters preceding /em. For example, if the CTP Server is located at http://mymachine.mycompany.com:8080/some/path/em, the Server URL field should contain http://mymachine.mycompany.com:8080/some/path (without the /em suffix). 
   
3. If your CTP administrator has configured security for your CTP installation, you also need to enter a valid username and password (preferably with an admin role).
4. Click Test Connection to verify correct settings.
5. Click OK to save.
6. Start the server:
   • From the cli: Run soatestcli -startServer
   • From the UI: Click the Start Server button in the SOAtest Server view.
     
     If the Start Server button is grayed out and the red Stop Server button is enabled, this means that the server is running.
     
7. Open CTP in a browser, then open the API Testing module.
8. Confirm that the SOAtest Server listed in the tree without an Offline or Error status.

Before you can access the .tst files on this server from CTP, you need to add them to the TestAssets folder as follows (test assets must be in this specific folder in order for CTP to access them):

1. On the SOAtest Server that you just connected to CTP, create a project named TestAssets (if it does not already exist).
2. Copy (or drag and drop) any test assets that are associated with the test scenarios you want to launch from CTP. This can include .tst files, data sources, keystores, and so on. The .tst files should have already been configured so that test assets are referenced via relative paths.
3. To confirm that .tst files are accessible from CTP, open CTP and go to the API Testing module. You should see the test assets from your TestAssets folder.