See also the other content about jMeter with Web Dynpro Java

Browser check

In case you only get a 200 response, but nothing is transmitted back from the server, welcome to Web Dynpro.

/wp-content/uploads/2013/08/jmeterprobs1_262500.jpg

Check the NWA Log Viewer.

/wp-content/uploads/2013/08/jmeterprobs2_262501.jpg

Caused by:

com.sap.tc.webdynpro.services.cal.core.exceptions.WDClientException: Found no client: clientNameReqParam=null, clientNameAppParam=null, useragent=Java/1.7.0_21


This may happen specifically when creating a HTTP request manually. You have to send the right HTTP headers:

/wp-content/uploads/2013/08/jmeterprobs3_262508.jpg

Add to ever HTTP sampler an HTTP Header Manager.

Unable to POST file to WDJ

Executing a previous recorded test plan where a file is submitted to the server using POST won’t work. This is given to the fact how jMeter is working. The file in question is recorded with a location relative to the jMeter execution path. Therefore, the file needs to exist in the same directory where jmeter.bat was called from.

/wp-content/uploads/2013/08/jmeterprobs4_262509.jpg

Create the file to be uploaded in the directory <path/to>/jmeter/bin and POSTing the file will work.

Secure ID sent does not match error

When executing a test plan you get HTTP 500 or 400 errors. This may even be more strange as the same test works fine in NetWeaver 7.1, but not anymore in 7.3.

/wp-content/uploads/2013/08/jmeterprobs5_262510.jpg

SAP changed the token for identifying the secure session id. In earlier releases, I was able to get the identifier by using the regexp name=”sap-wd-secure-id” value=”(.+?)”. In 7.3, this regexp returns:

/wp-content/uploads/2013/08/jmeterprobs6_262511.jpg

The session identifier returned is: VYT_ZknQSpUHbVgFpHw_Hg== While this looks cryptic enough to match someone’s expectations, it is the wrong identifier. This parameter is once passed as parameter in the URL and appears inside the HTML response body as such:

  • sap-wd-norefresh=X&amp;sap-wd-secure-id=DrT_3I8VO2P8nBaRUiJ4JQ%3D%3D&amp;sap-sessioncmd

and once in a variable:

  • lsdata=”{0:‘sap-wd-secure-id’,2:’DrT_3I8VO2P8nBaRUiJ4JQ==‘}

The first one is escaped, the second one not, showing the difference in the last 2 characters used: ==. Therefore, the regexp changes for getting the secure id changes to:

{0:’sap-wd-secure-id’,2:'(.+?)’}

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply