DevTest Portal v10.1.0, using Inspection View to check incoming transactions to a VS. When a TX is matched, I seem to be able to view only a truncated excerpt of the request message, on the Listener's "Step Response" event. Is there a VSE configuration which controls how much of the request message is captured, here? Thank you.
Can you post a couple of screenshots of the behavior you are seeing?
- 2 people found this helpful
I believe you are looking for the testexec.lite.longMsgLen property. testexec.lite.longMsgLen allows viewing the full text of long responses. Set this property to the length of your longest response in the local.properties file. Run a test, capture what you need, verify that the correct response is indeed being sent back, and then comment out the added line in the local.properties file to revert to the default length which is 1,024 bytes.
The reason one does not want to leave this on all the time is that it can negatively affect the performance of the VSE.
As an alternative, try looking in the vse, vse_matches, or VS_serviceName log files for the full incoming request. I have also used the built-in _logger inside scripts to dump requests into the vse log.
- 2 people found this helpful
The request what comes to VS is available in a property "lisa.vse.http.current.transaction.body". If it is not a big request, you should see it in the property "lisa.vse.http.current.transaction.body".
As Joel said, setting the property -Dtestexec.lite.longMsgLen with some big number in VSE vmoptions should help you with the truncation.
The response usually in a Transient form and you can't see it in the inspection view. If you want to see the response in inspection view, then the VSE response should be stored in a property before the Responder step deletes it.
Thank you very much for the prompt feedback! We will take a look at the logs and other options per suggestions from Prema and Joel.
- 1 person found this helpful
Still another way of viewing the complete request is to use tcpmonitor which is in the bin folder (tcpmonitor.bat). Use the following steps (example): 1. Create a test. Set the test endpoint url to point to a host on port 16000. 2. run tcpmonitor on the VSE's registry server. Listen on Port 16000. Set the Host to localhost, set the Port to the port number of the virtual service you want to monitor. tcpmonitor will pass the request to the virtual service after monitoring. 3. That's it. In the TCPMontor display you will see the complete request. -no need to look into any log files. no need to do any data "mining". Simple.
The request what comes to VS is available in a property "lisa.vse.http.current.transaction.body". If it is not a big request, you should see it in the property "lisa.vse.http.current.transaction.body".
As Joel said, setting the property -Dtestexec.lite.longMsgLen with some big number in VSE vmoptions should help you with the truncation.
The response usually in a Transient form and you can't see it in the inspection view. If you want to see the response in inspection view, then the VSE response should be stored in a property before the Responder step deletes it.