I would like to use Compuware to simulate webservice calls
First i would save the webservice request header data (picture)
Question:
Is it possible to replay this data, can we change the frequence of the replay, can we change values in the requests?
Thx
Answer by Andreas G. ·
Hi Steven
You can basically capture ANY data you want. Whether it is Request Parameters or Method Arguments. This data will show up in the PurePath Details on the individula PurePath nodes. In order to query the data through REST you would need to create a Business Transaction that splits on these values, e.g: Method Argument. You can then query the result of that BT through REST - or - even consider the Real Time Business Transactions Feed which allows you to receive this data via PUSH instead of pulling it out
Answer by Steven L. ·
Hello Andres,
I have created a sensor,
2 questions:
Compuware creates a splittong on Xml?, strange because there are no splittings definedi
like to have for each web call a line with the xml value
Is it normal that Compuware does not capture the complete argument value (in my case the xml value)
If so, can i set a parameter to trace the complete argument, i hope so otherwise i cannot reply data
Thx,
Answer by Steven L. ·
Hello Andres,
This is the soap envelop out of JMeter,
This info comes from the Compuware documentation,
My settings for a agent group
These are the resilt, but i cannot find the soap xm?
Thx
Hi. The SOAP XML is part of the HTTP POST Body which IS NOT captured by dynaTrace in its entirety. dynaTrace can capture HTTP PArameters that come in via POST but is not capturing the full POST Body. That could be megabytes per request.
If you need individual values from the SOAP Body you need to capture them from some methods in your code that retrieve them as parameters. For that you simply define custom sensors. Best is to talk with engineering or use the Class Browser and search for methods that get these values as parameters.
Andi
Answer by Steven L. ·
Thx Andreas,
Tomorrow i have a meeting with the boss,
to be sure i do not make any missasumptions, i do not need create a sensor correct?
out of the box i can trace a soap request, a REST request and i can retrieve this data by using compu REST API
(without making any business transaction), then it is my resposability to replay (example JMETER) Correct?
Thx
Out of the box i can, by changing
If HTTP Parameters, Cookies, ... is all you need for your JMEter script then you are correcct. Just change the Sensor Properties as highlighted in your screenshot and dynaTrace will capture all this data.
ONE REMINDER THOUGH: with putting an * on all these entries it means dynaTrace will capture ALL this data for EVERY Request. Why am I mentioning this? Because it may put some additional overhead on your application because our code needs to capture all this data. If you are going to use this for JMeter you are probably good with just the Parameters - correct? No need for Server Variables, Session Entries, Cookies or Headers. This would keep overhead low if you just focus on Parameters
Andi
Answer by Steven L. ·
Summary of what my boss wants
We have a field test environment with let say 100 customers wish are creating load.
We want continuously capture load and replay it on our test environment with a release candidate.
--> If i compare to new relic I'am glad that Compuware has the option to capture web request data, it is the starting point for me.
Nice to have Question? Can we capture anything we want? For example a sensor on Method(int Value), can Value be captured into Compuware database
One's we have the request we can:
Just replay all the request on same frequency
Replay with higher frequency (example peak load test)
Duplicate requests, what will hapen if we have 10 new customers within one month,
The release candidate has new features, what is impact (need we more memory, more cpu, ... for the release candidate)
The Idea was to use jmeter to replay data, but to be sure i was wondering what Compuware could do out of the box
Answer by Andrew P. ·
Hi Steven,
Unfortunately simply replaying a request that you receive is not really within the scope of dynaTrace's functionality, though not all is lost...
You could potentially do this with a combination of dynaTrace and Gomez, but the information in the replayed requests would be fairly static. It would be a matter of capturing the data, creating a script that mimics the request, then playing it back either manually (with the script recorder) or on a regular interval using the Gomez portal. You could manually change the values that are sent in the request, or even choose randomly from a databank (though you would need to create this yourself - an array in a custom action is probably the simplest example).
Perhaps I'm misunderstanding, can you give a bit more information about the context of the question and what you are trying to achieve?
JANUARY 15, 3:00 PM GMT / 10:00 AM ET