This topic explains how to extend SOAtest's interface and operations to cover message formats not supported by default.This topic explains how to extend Virtualize's interface and operations to cover message formats not supported by default.This topic explains how to extend the SOAtest and Virtualize interfaces and operations to cover message formats not supported by default.Sections include:
...
SOAtest and Virtualize include a framework that allows you to extend their built-in message formats. The framework can support any message format that you are working with, for example, mainframe message formats, binary formats, or any other kind of proprietary custom message format. The message formats are defined by creating a conversion between the native format and XML. This conversion allows the user to construct and validate messages using the rich XML tooling that is available. This extension is done using Java.Once a custom message format has been added, SOAtest and Virtualize will automatically make a new client or responder available for for configuring and sending request or response messages using that format. You can add instances of the new Once a custom message format has been added, SOAtest will automatically make a new client available for for configuring and sending request or response messages using that format.Once a custom message format has been added, Virtualize will automatically make a new responder 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.See Custom Client and Custom Message Responder for for details about how to use them. The new See Custom Client and Custom Message Responder for details about how to use them.See 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.
...
Interfaces to Implement for Custom Message FormatsCustom Message Formats
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 setting up your environment (General Procedure of Adding an Extension), implement the following interfaces (described in the Extensibility API documentation):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):
...
| Anchor | ||||
|---|---|---|---|---|
|
After you have implemented the necessary classes, define parasoft-extension.xml (introduced in General Procedure of Adding an Extension in SOAtest and General Procedure of Adding an Extension in Virtualize) using the following schema:After you have implemented the necessary classes, define parasoft-extension.xml (introduced in General Procedure of Adding an Extension in SOAtest and ) using the following schema:After you have implemented the necessary classes, define parasoft-extension.xml (introduced in General Procedure of Adding an Extension in Virtualize) using the following schema:
...
Build the project (see General Procedure of Adding an Extension in Virtualize or General Procedure of Adding an Extension in SOAtest) and restart SOAtest or Virtualize.Build the project (see General Procedure of Adding an Extension) and restart SOAtest.Build the project (see General Procedure of Adding an Extension in Virtualize) and restart Virtualize.
- 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.
...