Creating a SOAP Request

1. Select Design mode

   Click on the button.

2. Create a new virtual user

   Right-click on the Virtual User profiles node and select New Virtual User. Enter "VirtualUser", then click "OK".

3. Add a new SOAP request

   Right-click on the virtual user just created and select "Insert into", then "SOAP request".

4. Create the request from a WSDL definition

   Check the Generate request using a WSDL file option and enter the URL of that file. In our example the URL is: http://ws.strikeiron.com/textdisguise/CaptchaService?WSDL. NeoLoad analyzes the WSDL and extracts the methods that can be called.

   

   Click Next.

5. Select the method to call

   Based on the WSDL's definition, NeoLoad lists the methods that you can choose from. Here, we'll select the CaptchaServiceSoap.GetNewWord method.

   

   Click Next.

6. Define a request name

   NeoLoad provides a default request name which it usually derives from the method name defined in the WSDL. Most of the time you won't need to change this name. You might want to change it if you use this call several times with different parameter and configuration values.

   

   Click Next.

7. Define the service end point

   This steps lets you define the address for invoking the specified service. The WSDL includes this URL and most of the time you won't need to change this address. You might want to change the endpoint to switch from a test environment to a production one.

   

   Click Finish.

8. Check the main configuration elements

   At this point, the SOAP request is added to the virtual user.

   

   NeoLoad's right panel displays the main configuration elements of the SOAP request. This includes the end point URL which is defined by both the Server and Path elements. These elements, as mentioned earlier, have been extracted from the WSDL but can be changed to custom values. As with HTTP requests, the Path element can been defined using NeoLoad variables.

   The WSDL element can equally be changed or reloaded. Reloading is particularly useful when the SOAP request and it's associated WSDL are out of sync.

   	Warning
   	Reloading WSDL will re-initialize all previous configuration elements. All previously defined parameters will be lost.

9. Check the HTTP headers

   Most SOAP request require at least two HTTP header elements when SOAP is tunneled through HTTP. Always make sure that these elements are correctly set. They are available in the Advanced parameters dialog and are accessed by selecting the button:

   

   In our example these elements are ContentType and SOAPAction. If your web service framework requires additional HTTP header elements you can set them in the Advanced parameters dialog.

Configuring the SOAP request

Before actually testing the SOAP request, additional elements including parameter values and encoding types must be configured. Select the button to access the SOAP configuration dialog.

1. Define the main parameters of the SOAP body

   The Parameters tab let's you define the structure of the SOAP body. The tree structure in the left most panel of the SOAP Parameters dialog displays the structure and content of the SOAP body.

   As mentioned earlier, the GetNewWord method expects no parameters or an empty so the tree only has one root element called GetNewWord (an empty element as defined in the WSDL). Had there been several elements or several possible elements, NeoLoad would have displayed them in the tree. In our example no further configuration for the body is necessary.

   

2. Define the SOAP header

   Select the Headers tab to define and configure elements related to the SOAP header. The SOAP header elements are presented in exactly the same way as the SOAP body elements are. The left most panel contains an XML tree displaying the structure and contents of the header of the SOAP envelope. Adding and removing elements is achieved using the and, buttons. Moving elements around is achieved using the and buttons

   The structure contains either container elements, such as UnregisteredUser in our case, or leaf elements such as EmailAddress. Container elements are meant to contain other elements. Right clicking on them will pop up a menu from which you can choose to move the selected element or add and remove child elements. NeoLoad will only suggest child elements that are consistent with the WSDL definition.

   Leaf elements on the other hand cannot contain other elements but have an associated value. In our example you must enter a valid email address for the EmailAddress element.

   

   For both container and leaf elements, you can define attribute names and attribute values. Again attributes must be consistent with WSDL definition. Encoding allows special characters such as '>', '<' or '&' to be encoded.

3. Configure advanced settings

   The Advanced Settings panel let's you configure the binding styles of the SOAP request and the format of attachments. This information has been extracted from the WSDL and you should definitely be familiar with the types of bindings if you decide to change this setting.

   

4. View XML

   The last tab of the SOAP Parameters dialog displays the actual XML content that will be sent. NeoLoad generates its content on the fly using the XML elements and attributes you have defined. Right clicking on the XML and selecting the Format as Pretty XML item will display a neatly indented XML.

   

   	Tip
   	You can search the generated XML for a particular expression by right clicking on the XML and selecting the Search ... item (or using the CONTROL + F shortcut keys).

Testing the SOAP request

By creating a temporary virtual user, NeoLoad provides an easy and quick method to check your SOAP request. Select the button to open the Check Virtual User dialog.

1. Start checking

   If you have already tested Virtual Users using NeoLoad you will be familiar with the following dialog. By selecting the Start checking button, NeoLoad will generate the SOAP request and send it to the specified end point. NeoLoad displays the associated response code and the number of failed assertions for the sent request. When the line associated to the request is selected the dialog displays further details in the lower part of the dialog. You can choose to display the SOAP request that was sent or the XML response.

   

   	Tip
   	You can search the SOAP request or the XML response for a particular expression by right clicking on the XML and selecting the Search ... item (or using the CONTROL + F shortcut keys).

   	Tip
   	You can neatly format SOAP request or the XML response by right clicking on the XML and selecting the Format as pretty XML item.

   If you are following our example and testing it, the first time you'll send the request the response will look like the following (the HTTP header has been omitted):

   <?xml version="1.0" encoding="utf-8"?>
   <soap:Envelope 
        xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" 
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
        xmlns:xsd="http://www.w3.org/2001/XMLSchema">
     <soap:Header/>
     <soap:Body>
       <soap:Fault>
         <faultcode>soap:Client</faultcode>
         <faultstring>
           Thank you for your attempt to try this Web service. Before the 
           free trial can occur, 
           you must first validate your email address. 
           Simply click on the link in the email that was just sent to you, 
           and you will then be able to invoke every Web service 
           within the StrikeIron Web Services Marketplace, including this one.
         </faultstring>
         <faultactor/>
       </soap:Fault>
     </soap:Body>
   </soap:Envelope>

   As indicated in the faultstring element, all you need to do to use the service a limited amount of times is to validate the email address you sent by following the link that StrikeIron has sent to you. Once your address is validated invoking the service should get you a response such as the one that follows (the HTML header has been omitted):

   <?xml version="1.0" encoding="utf-8"?>
   <soap:Envelope 
       xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" 
       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
       xmlns:xsd="http://www.w3.org/2001/XMLSchema">
     <Header xmlns="http://schemas.xmlsoap.org/soap/envelope/">
       <SubscriptionInfo xmlns="http://ws.strikeiron.com">
         <LicenseStatusCode>1</LicenseStatusCode>
         <LicenseStatus>Valid key</LicenseStatus>
         <LicenseActionCode>0</LicenseActionCode>
         <LicenseAction>Decremented hit count</LicenseAction>
         <RemainingHits>4</RemainingHits>
         <Amount>0</Amount>
       </SubscriptionInfo>
     </Header>
     <soap:Body>
       <GetNewWordResponse 
           xmlns="http://www.textdisguise.com/TextDisguise/CaptchaService/">
         <GetNewWordResult>
           <CaptchaImageGuid>
             82e16912-14c1-4253-bbcb-699585e3ba63
           </CaptchaImageGuid>
           <Url>
             http://www.textdisguise.com/TextDisguise/CaptchaService/
             CaptchaImage.aspx?
             guid=82e16912-14c1-4253-bbcb-699585e3ba63
           </Url>
         </GetNewWordResult>
       </GetNewWordResponse>
     </soap:Body>
   </soap:Envelope>
   

   From this point on you can use the link defined by the URL element in an HTML page. As detailed in the following section you can then use the ValidateImageWord method and the CaptchaImageGuid to validate a text entered by the user.

Manually creating a SOAP Request

1. Select Design mode

   Click on the button.

2. Create a new virtual user

   Right-click on the Virtual User profiles node and select New Virtual User. Enter "VirtualUser", then click "OK".

3. Add a new SOAP request

   Right-click on the virtual user just created and select "Insert into", then "SOAP request".

4. Specify a manually-generated request

   Check the Generate request manually option.

   

   Click Next.

5. Enter a name for the request

   Enter a name for the manually-defined request.

   In our example we'll name the request ValidateImageWord.

   

   Click Next.

6. Define the end-point of the request

   This is the URL where the service is located. You can also change this later on. In our example the service end point is http://ws.strikeiron.com:80/textdisguise/CaptchaService.

   

   Click Finish.

7. Check main configuration elements

   At this stage the SOAP request is added to the virtual user. You can rename this node to your convenience. In our example a ValidateImageWord node has been added at the end of the existing SOAP requests.

   

   NeoLoad's right panel displays the main configuration elements of the SOAP request. This includes the end point URL which is defined by both the Server and Path elements. These elements can be changed to custom values. As with HTTP requests, the Path element can been defined using NeoLoad variables.

8. Check the HTTP headers

   Most SOAP request require at least two HTTP header elements when SOAP is tunneled through HTTP. Always make sure that these elements are correctly set. They are available in the Advanced parameters dialog and are accessed by selecting the button:

   

   In our example these elements are ContentType and SOAPAction.

Configuring the XML content

To configure the XML content, select the Edit XML Content button.

At this stage you must define the XML request either by copying and pasting a request you have tested or by manually defining each element and attribute of the request. We will be using the first method in our example.

Copying and pasting an existing XML request using the Flat XML panel is the easiest way to define the XML content of the request. In our example we have copied and pasted the XML containing the call to the ValidateImageWord method:

You could also use the XML Tree panel to manually define or to edit the XML using elements and attributes. NeoLoad automatically constructs one view from the other (the XML tree view from the flat view and vice versa). Selecting the XML Tree tab would look like the following:

At this stage the request is completely defined and configured, you can immediately start testing it.

Testing the SOAP request

By creating a temporary virtual user, NeoLoad provides an easy and quick method to check your SOAP request. Select the button to open the Check Virtual User dialog.

1. Start checking

   If you have already tested Virtual Users using NeoLoad you will be familiar with the following dialog. By selecting the Start checking button, NeoLoad will send the SOAP request to the specified end point. NeoLoad displays the associated response code and the number of failed assertions for the sent request. When the line associated to the request is selected the dialog displays further details in the lower part of the dialog. You can choose to display the SOAP request that was sent or the XML response.

   

   	Tip
   	You can search the SOAP request or the XML response for a particular expression by right clicking on the XML and selecting the Search ... item (or using the CONTROL + F shortcut keys).

   	Tip
   	You can neatly format SOAP request or the XML response by right clicking on the XML and selecting the Format as pretty XML item.

Extracting the image identifier CaptchaImageGuid from GetNewWord's response

1. Go to Design Mode by selecting the button

2. Select the Virtual users tab

3. Unfold the appropriate virtual user node

4. Select the GetNewWord request from which the image identifier value will be extracted:

   

5. Go to the Variable extractors tab

   1. Open the Advanced settings dialog by selecting the button.

   2. Select the Variable extractors tab:

      

6. Define a new variable

   Select the button to add a new variable. This opens a Variables Extractor dialog. In our example we will define the captchaImageGuid variable . The way the value is identified and extracted is quite straightforward since the XML response is simple. We want to extract anything appearing between the starting <captchaImageGuid> and ending </captchaImageGuid> XML tags. The following screen shot reflects these decisions:

   

   At this stage the extraction part of the process is complete. Each time the GetNewWord is invoked NeoLoad will extract the value of the image identifier and set the captchaImageGuid variable with it.

   For more details on extracting variables refer to the section called “Creating a Variable Extractor” and to the reference guide.

Re-injecting the value into the ValidateImageWord request using a variable

1. Select the ValidateImageWord request in which the image identifier value will be injected.

2. Select the Edit XML Content button to configure the XML content.

3. Select the XML Tree tab

4. Select the captchaImageGuid element in the XML panel

5. Select the Variable Picker dialog using the ... button. You can also start typing something like ${c and NeoLoad will suggest variable name completions.

6. Choose the captchaImageGuid variable

   The XML Content dialog should look like the following:

   

   With such a configuration NeoLoad will extract the image identifier from the GetNewWord response and inject it in the ValidateImageWord request. This sequence can be replayed multiple times.