How I can make test SOAP Request in JMeter version 3.2? In old version I had Soap/XML-RPC Data sampler while in version 3.2 I don't see this option. Please help.
Use HTTP Request sampler, in case you need to set some headers like Content-Type or SOAPAction you can use HTTP Header Manager
You can see Building a WebService Test Plan article for more information if required.
Related
I have a simple test script which I recorded using out of the box JMeter and the recording template. I recorded a simple page, which create a "recording controller" in the threadgroup, and below that the pages "http requests".
When I upload this to the Azure DevOps JMeter runner, I get the error:
At least one HTTP Request sampler should be present and enabled.
Is there any way to get round this?
I am not sure why the http request is not recognised as a sampler. I am using JMeter 5.3. I know azure only supports 3.x, but till now this has not been an issue.
Since 3.x to 5.3 there are could be many incompatible changes.
There are two bugs fixed in HTTP Samplers block in JMeter 5.3, Release Notes says.
And one of them marked as an Incompatible changes:
Default value of httpclient4.time_to_live has been modified from 2000
to 60000, this means HTTP connections will live longer than before.
This has impact on connection creation and SSL handshake, see Bug 64289
So, try to record your script in previous version of JMeter, the best choice is JMeter 3.x, if Azure supports only 3.x.
I'm working on an old project using Savon to connect to the SalesForce api. I'm getting this error:
UNSUPPORTED_CLIENT: TLS 1.0 has been disabled in this organization. Please use TLS 1.1 or higher when connecting to Salesforce using https
How do I get it to use TLS 1.2? Or is there a simple alternative to Savon that does use TLS 1.2?
Savon uses HTTPI as a common interface for Ruby's HTTP libraries
Configure Savon to use a specific library with:
HTTPI.adapter = :httpclient
HTTPI.adapter = :curb
...
it currently tries the libs in the following order:
[:httpclient, :curb, :em_http, :excon, :net_http, :net_http_persistent]
If you haven't installed httpclient, it will try curbnext and so on.
You should try setting an explicit lib and see if it works for you.
Just to help others in the future who may face the same problem. It seems the TLS level is not built in the savon gem but in the httpi adapter. By changing the adapter to httpclient (installed the gem, put require 'httpclient') the savon gem starts using it without further configuration. Just remove the ssl_level params and the latest and more modern cypher is used. Problem solved.
I create a client in Domino to consume a web service that works with SOAP 1.2 and has HTTPBinding.
The client generation tool for Domino Designer Web services an error is displayed when trying to generate reporting that the SOAP accepted version is 1.1.
I decided to create the client with CXF framework through tool wsdl2java. In an agent I used these classes to consume the web service, however the below error was displayed. I think it's because of the SOAP version, but I'm not sure.
com.sun.xml.internal.ws.protocol.soap.MUTube getMisUnderstoodHeaders
INFO: Element not understood={http://www.w3.org/2005/08/addressing}Action
Also generated a jar of classes generated by wsdltojava and imported to another agent, but the error below is displayed.
java.lang.UnsupportedClassVersionError: JVMCFRE003 bad major version; class=, offset=6
The question is, no way consume a web service with SOAP 1.2 in Domino only supports up to version 1.1?
Thanks a lot!
I don't believe that Domino's web service consumer supports SOAP 1.2 at this time. You might be able to do what you need with an agent though - here's one way: How can I call a SOAP 1.2 Web service from a LotusScript agent?
In fact there is no way to natively consume a web service with soap version 1.2. There are already several requests from IBM to upgrade the SOAP version. What I did, was to develop a new layer through a new web service with the version SOAP 1.1, which internally calls the web service with the SOAP version 1.2;
I wanted some clarification regarding SudzC for iPhone. Does SudzC support SOAP 1.2?
I tried using SudzC with the web service http://www.restfulwebservices.net/wcf/CurrencyService.svc?wsdl and it works fine but with my web service it doesn't. The only difference I can spot is that the above service uses SOAP1.1 while mine used 1.2.
Regards,
EC
You pretty much answered your own question. A service expecting a soap 1.2 message is not required to be backward compatible to soap 1.1 formatted messages. You can configure WCF to accept soap 1.1 messages by creating a custom binding as show here. Although that WCF config is for a client, you can also configure a service to use that custom binding. If the service needs to support soap 1.2 messages, you can just leave your existing endpoint configured as-is and create a new endpoint for the soap 1.1 custom binding.
Is there are any wsdl-validation profiles available to check the ws-i compliance of wsdl file with soap 1.2?
Or I need to switch to soap 1.1 to pass the WS-I compliance test?
I believe you can use the following tools to test your service. I guess they should also work for SOAP 1.2 (haven't tried it though).
You could try to use the tools by themselves but I think it would be easier to do it with SoapUI. If I'm not mistaken, the BSP Test Tools is what's used by default by SoapUI to test WS-Interoperability.
Good luck!