Overview
Using this plug-in JMeter provides an easy way record and replay Appian processes.
JMeter for Appian accomplishes this by hooking into JMeter's Test Script Recorder mechanism. It alters the behavior of most HTTP requests so that additional logic runs when the test is recorded. This logic extracts the standard dynamic values that are passed back and forth when a user interacts with Appian.
Key Features & Functionality
This JMeter plug-in will add post processing to Appian requests/responses to:
The plug-in does not attempt to parameterize end user entered data. This could however be added to the generated test script.
Hi!!
Im having problems when trying to execute a recording that has startProcess, Is there any way to solve it?
Thanks!
Most likely you need to:
(1) in jmeter.properties, set CookieManager.save.cookies=true
(2) in the login POST to suite/auth, populate X-APPIAN-CSRF-TOKEN with ${COOKIE___appianCsrfToken}.
We are having problems with the Appian authentication in JMeter because is not working. Is there any guidance how to do it?
Thanks, that works!
Now i have a problem with a post request, a saveInto variable, could you help me?
Hi!
I have a problem with Jmeter for Appian.
First, I can solve a problem with login by using X-APPIAN-CSRF-TOKEN and JSESSIONID as cookies in HTTP COOKIE MANAGER.
Then I’d like to make a search (search a project) in our Appian cloud, but Jmeter returns me an error “Response code 401” when I do a POST resquest.
I have 2 variables in my body data request, “saveInto” and “context value”. Context value is ok but the problem is in saveInto.
Before the request I have a Json extractor, automatically created by “AppianJsonParser-20.3.0-SNAPSHOT”
Json extractor gets the variable with “\ /” and response data hasn´t this character. How can I do for solve it?
My request body:
"<<jA0EAwMCd7VWJIKW7uMB0qEB4gr03ece1fNv\/y4Pg0ICDVpb2JTjXqQKFFbbTFyDBsBUX1Ig641O\r\nEIvj9abXOz0cMHc+45Ts9GjWWy+Fmc07WVsuxzoD+u1DSGLN26EM0sa1Ke4++9ugE7lZNuB4hVh2\r\nr3lwggg7P84gys5KDCLkcY6LZ1I05\/zcSpkTmqAPwUb8m1NjVswMcRYF6KbPmoGN+QHdTDW+8Q26\r\nb7MTqs0TEA==\r\n>>"
Response body data:
"<<jA0EAwMCd7VWJIKW7uMB0qEB4gr03ece1fNv/y4Pg0ICDVpb2JTjXqQKFFbbTFyDBsBUX1Ig641O\r\nEIvj9abXOz0cMHc+45Ts9GjWWy+Fmc07WVsuxzoD+u1DSGLN26EM0sa1Ke4++9ugE7lZNuB4hVh2\r\nr3lwggg7P84gys5KDCLkcY6LZ1I05/zcSpkTmqAPwUb8m1NjVswMcRYF6KbPmoGN+QHdTDW+8Q26\r\nb7MTqs0TEA==\r\n>>"
Thanks
It may be an issue with your jmeter.properties. Try setting
CookieManager.allow_variable_cookies=trueCookieManager.save.cookies=true
You can use a regex extractor like __appianCsrfToken:\s+(.+) on the headers, but I believe that value updates between the initial get and the login, which is why I like to use the cookie variable instead.
Does this plug-in work in Appian 21 version?
Hi, we have tried this plug-in in Appian 21 version and we can´t login to our Appian cloud.
We have followed step by step the Jmeter for Appian documentation and we have made a simple navigation in our cloud. Using Jmeter version 5.4.1 or 5.3, we get the same errors. When we stop recording, we can see our tree results all in green. But if we run the test again, we find problems in our login item, specifically in X-APPIAN-CSRF-TOKEN.
We have tried to pass ${COOKIE___appianCsrfToken} but we don’t know exactly the way to use that. If we will need a regular expresion extractor to pass this, could you help us with the steps to use that please?
No, it doesn't work with 5.3 as well, already tried it! It's probably due to how 20.4 version of appian works in conjuction with browser.
The ApacheJMeter_http.jar that was altered to hook in the Appian logic was built against Jmeter 5.3, I would recommend using that version. Not sure that is the root cause of you issue, but it could be.