SOAtest and Virtualize
to work with
services deployed using HTTPS (HTTP via the SSL), you need to identify and register the certificate being used for the HTTPS connection from the server:
SOAtest and/or Virtualize
if it is currently open.
Copy the certificate to the following location:
This directory should contain a
cacerts file in which the trusted certificates are stored.
Execute a command of the following format:
keytool -import -alias <certificate_alias> -file <certificate_file> -keystore cacerts
For example, if your certificate file is named
test.cert, you would execute the following command from the
keytool -import -alias serverTrustCert -file test.cert -keystore cacerts
This will import the certificate into the cacerts file with the alias "s
To add the included Java binaries to your path, open a command line prompt and enter the following before referencing the keytool:
Note that <
yes. You will then see a message indicating that the certificate has been added to the keystore.
keytool -list -keystore cacerts
SOAtest or Virtualize
and try to access the service again.
If you experience issues working with services deployed over HTTS, verify the following:
If you cannot satisfy the above requirements (for example, if you don’t have necessary permissions):
will then try to access any WSDL you specify, regardless of any problems with the certificate. However,
will still try use the certificate while trying to send SOAP messages because it is required to do so.
You must add certificates to cacerts files on load test slave machines as well as on the master machine. Otherwise, SSL connections will not work when running a load test with slave machines.
If none of these procedures solve your problem, contact Parasoft in one of the ways described in Contacting Parasoft Technical Support.
SOAtest and Virtualize run
on a standard JVM. To show the SSL/TLS handshake details and help identify causes of SSL connection problems, enable JVM network and SSL debugging:
-J-Dssl.debug=true -J-Djavax.net.debug=all -consolelog
will start as usual, but whenever SSL connections are made, debugging output will be printed on the console. If you wish to save the trace output to a file (for example,
output.txt), you may append the following to the end of the command :
For more information about managing keys and certificates using the Java keytool, see the Oracle Java documentation. refer to: