LoadRunner generates body binary with flex app (627 Views)
Reply
Occasional Visitor
jaepar
Posts: 3
Registered: ‎11-16-2009
Message 1 of 8 (627 Views)

LoadRunner generates body binary with flex app

Hi,

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?
HP Expert
KMadan
Posts: 1,079
Registered: ‎05-27-2009
Message 2 of 8 (627 Views)

Re: LoadRunner generates body binary with flex app

Please input the server parser Jar files to LoadRunner during recording/replay. Using that, LR can able to generate the readable code.

-Madhu

Madan
Occasional Visitor
Aravinthan
Posts: 1
Registered: ‎11-16-2009
Message 3 of 8 (627 Views)

Re: LoadRunner generates body binary with flex app

Hi madthrt,

What do you exactly mean by "server parser Jar files"?

We face the same problem.
HP Expert
KMadan
Posts: 1,079
Registered: ‎05-27-2009
Message 4 of 8 (627 Views)

Re: LoadRunner generates body binary with flex app

Generally the Flex responses are in encrypted format. By default, LoadRunner uses its own parser to parse the binary data. Most of the times it may fail because of different parsing mechanisms used by your Flex server. So, if you input the Parser jar files in the recording options, LR uses those files and decrypt the messages. Hence you will get a readable script with proper functions instead of flex_web_Request.

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.

-Madhu

Madan
Occasional Visitor
jaepar
Posts: 3
Registered: ‎11-16-2009
Message 5 of 8 (627 Views)

Re: LoadRunner generates body binary with flex app

Thanks for your reply madthrt

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?
HP Expert
KMadan
Posts: 1,079
Registered: ‎05-27-2009
Message 6 of 8 (627 Views)

Re: LoadRunner generates body binary with flex app

Yes, Select the option "Encode AMF3 using external parser". and provide jar files path at Flex Server JAR Files location.

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.

-Madhu

Madan
Occasional Visitor
jaepar
Posts: 3
Registered: ‎11-16-2009
Message 7 of 8 (627 Views)

Re: LoadRunner generates body binary with flex app

Hi,

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
HP Expert
KMadan
Posts: 1,079
Registered: ‎05-27-2009
Message 8 of 8 (627 Views)

Re: LoadRunner generates body binary with flex app

Did you input the correct parser jar files? You may try this.

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.

-Madhu

Madan
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.