11-16-2009 09:23 AM
Does anyone has idea of how to deal body binary generated by LR. Is there options for LR to decode the body binary of the flex_web_request
i need to correlate some of the value inside the body binary, and body binary is in hex, its very hard to understand it and correlation is even harder, does hp has support and tutorial on performance test for flex apps?
11-17-2009 07:11 AM
If the LR is unable to parse the request by default, it generates the flex_web_request's.
Currently, LoadRunner supports only LCDS & BlazeDS Flex Servers. Other server may work.
You may ask your developers for the parser details. You can find the jar files in the Flex server.
Hope it clarifies.
11-17-2009 09:28 AM
im using LiveCycle which sit on top of JBoss.
im in the recording options->flex->code generation
there are 2 flex code generation options:
- Encode externalizable object with LR parser
- Encode AMF3 using external parser
do you mean the 3rd options? where there is no checkbox, and it says Flex server/application JAR files location
is thats the case, then I just need to enter a value which is a path to a folder to the server-libraries?
11-17-2009 10:03 PM
First copy the Jar files to the Vugen machine. You may need to copy the Jar files to all Load Generator machine to the same location during load test or you may need to use relative path.
11-18-2009 09:13 AM
I did what you guys suggest, but just like what Madhu suggested, "LoadRunner supports only LCDS & BlazeDS Flex Servers" other may work but it turns out it does not parse the binary for LiveCycle JBoss
11-21-2009 04:45 PM
A way to find out what classes are missing and need to be added during recording (in .jar format), is by enabling extra logging. Follow these steps to enable extra logs for tracking the missing classes:
1) Right click on My PC -> Properties -> Advanced -> Environment Variables
2) Choose either User Variables or System Variables and click New
3) For Variable Name type HP_FLEX_JAVA_LOG_FILE.
4) For Variable Value, specify a path and filename on which the log will be created (e.g. C:Flex.log)
Everytime a Flex script is generated using a external parser, the log file will be created. If it exists, it will be overwritten.