Starting IBM Web Services Validation Tool for WSDL and SOAP

  1. Create a directory
  2. Uncompress the package
  3. Start the tool.

    If you get Java heap exhaustion due to large files, please use -vmargs -Xmx option to increase Java Heap.
    For example, wsvt -vmargs -Xmx512m will allocate 512 MB of Java heap to the tool environment

    The tool requires Java Runtime Environment 6.0 or higher.If your default Java Runtime Environment is not 6.0, please use -vm option to allow the tool to find Java Runtime Environment version 6.

    For example, wsvt -vm c:\java6\bin\java.exe

    IBM Java SE version 6 contains XML decryption libraries. No other software is required for IBM Java SE version 6.

    Sun Microsystems Java SE 6 does not include XML decryption API. The Apache XML Security libraries (http://santuario.apache.org/) are required for processing encrypted SOAP messages with Sun Microsystems Java SE 6.

    NOTE : If you have IBM Java 6, you don't need to install anything else. Everything you need is included in IBM Java 6. If you have Java 6 from Sun Microsystems, you need to let the tool know the location of the Apache XML Security version 1.4.3 in order to decrypt encrypted SOAP messages.

    For example, the following will start the tool with Sun Java 6 with the Apache XML Security library version 1.4.3 which is in the directory C:\xml-security-1_4_3\libs:

    wsvt -vm c:\SUNjava6\bin\java.exe -vmargs -DAXS=C:\xml-security-1_4_3\libs

    The following is the screenshot of the tool

    Initial screen

  4. Right mouse click on Projects, select New -> Project

    File open

  5. Select General - Project and press Next button

    File open

  6. Enter Project name and press Finish button

    File open

  7. Right mouse click on the project, select Import

    File open

  8. Select General - File System and press Next button

    File open

  9. Select a WSDL file and a SOAP message with XML file extension and press Finish button

    Open trace

  10. Import is completed. Double click sample WSDL file to review XML source of WSDL file.

    Open trace

  11. Press design tab to review WSDL file in design mode

    Open trace

  12. Double click sample SOAP file to review XML source of SOAP message.

    Open trace

  13. Press design tab to review SOAP message in design mode

    Open trace

  14. Right mouse click on the sample SOAP xml file, select Validate.

    Open trace

  15. If there's any digital signature in the SOAP xml file, you can click on "SOAP Message Digital Signature Verification" menu to verify digital signature. If digital signature is verified, the following message will be shown:

    Open trace

  16. If SOAP message is decrypted, you need to select keystore file to decrypt SOAP message. Location of keystore file, keystore type and password are required:

    Keystore selection

  17. Please select a key and password to decrypt SOAP message:

    Key selection

  18. If decryption is successful, decrypted SOAP message is created with "_decrypted" suffix. If decryption is tried more than once, decrypted SOAP messages are created with "_decrypted_N" suffix. N is a sequence number starting from 0.

    Key selection

  19. You can send SOAP messages to Web Services servers with the menu : Transmit SOAP Request and Receive SOAP response:

    Transmission

  20. Add required information to send SOAP messages to Web Services servers

    Transmission

  21. If a SOAP message is received successfully, response SOAP message is created with "_response" suffix. If response is received more than once, response SOAP messages are created with "_decrypted_N" suffix. N is a sequence number starting from 0.

    Transmission

  22. Line 5 is marked with red error icon and Problems view has detailed information

    Open trace

  23. If you move mouse cursor to the icon, you can see error message from the editor view

    Open trace

  24. According to the message, we need out instead of in. Correct the problem

    Open trace

  25. Save the change and validate the SOAP message again. We don't see the error anymore.

    Open trace

  26. If you don't want to manually revalidate, let's make it automatic. Bring up Properties menu of the project

    Open trace

  27. Check Add Validation Builder to project and press OK button

    Open trace

  28. From now on, the project is automatically revalidated after any change is saved

    Open trace