Tips and Tricks for - Oracle JDE (enterprise one) performance scripting using LoadRunner:

4 May 2019.

There are not much information available as to how you can create vugen script for JDE packaged application. Recently I completed a JDE performance test and below are my recommendations.

1) The following values need correlation (there may be others depending on the scenario flow but these are the key ones):

     a) E1MAINMENU_<dynamic number>
     b) RID
     c) jfasxxxcacheUID (sorry can't remember the name correctly)
     d) dummyparam (this one is optional as I have seen it works sometimes without correlating this
 
2) Most of the time you will see that some of your next transaction may have requests from the previous transaction. Put comments and manually move requests to correct it. I still don't know why it's happening. (Let me know if you know a better approach :) !!!

3) The most annoying issue for me was when I placed launch/login and logout into init and end sections it always failed in 2nd iteration. The solution for this is:

       a) Create a parameter for iteration number.
       b) Replace the value 1 in following cases with the parameter:
            - stackId", "Value=1"
            - &stackId=1&
            -

Comments

Popular posts from this blog

CI CD Continuous Performance Test Framework with LoadRunner/Jenkins/Bitbucket

LoadRunner integration with HP QC/ALM

Android native app scripting with LoadRunner