This topic explains how to extend the SOAtest and Virtualize interfaces and extend SOAtest's interface and operations to cover message formats not supported by default.

...

Once a custom message format has been added,SOAtest and Virtualize will SOAtest will automatically make a newclient or responder available newclient available for for configuring and sending request or response messages using that format. You can add instances of the new client/responder to your test scenarios or responder suites.

SeeCustom Client and Custom Message Responder for details about how to use them. The new message format will also appear in the XML Converter tool, which is described in XML Converter.

...

After setting up your environment (see General Procedure of Adding an Extension for instructions in Virtualize or General Procedure of Adding an Extension for SOAtest), implement the following interfaces (described in the Extensibility API documentation):

...

After you have implemented the necessary classes, define parasoft-extension.xml (introduced inGeneral Procedure of Adding an Extension in SOAtest and General Procedure of Adding an Extension in Virtualize) using the following schema:

...

• <client>: Optional element that holds some basic information for the custom SOAtest client generated for your custom message format.
  • icon - An optional attribute that specifies an icon to display in the GUI for the custom SOAtest client. This is a relative path to an icon that is contained within a jar file or Java project on the SOAtest classpath. If not provided, SOAtest will use its default tool icon for the custom SOAtest client.
  • defaultTransport - An optional attribute; the default SOAtest transport to be used in the client. Possible values are:
    • HTTP 1.0 (default)
    • HTTP 1.1
    • JMS
    • SonicMQ
    • WebSphere MQ
    • RMI
    • SMTP
    • TIBCO
    • .NET WCF HTTP
    • .NET WCF TCP

• <responder>: Optional element that holds basic information for the custom Virtualize responder generated for your custom message format.
  • icon - An optional attribute that specifies an icon to display in the GUI for the custom Virtualize responder. This is a relative path to an icon that is contained within a jar file or Java project on the Virtualize classpath. If not provided, Virtualize will use its default tool icon for the custom Virtualize responder.

Verifying the New Verifying the New Message Format

1. Build the project (seesee General Procedure of Adding an Extension in Virtualize or seeGeneral Procedure of Adding an Extension in SOAtest) and restartSOAtest or Virtualize.Virtualize.

2. Verify that a new client/responder that contains the name of your message format is available to add to a .tst or .pva file by choosing Add New> Test or Responder.

...