If you’ve been on Performance Testing for a while, you should know that there are several ways of doing the same thing. Most examples were tested using LR 9.5 and Oracle 11i. I know that most tips can also be applied to LR 8.1, 9.1 and also Oracle 10.
Tip 1: How to correlate the Login?
Login is usually the tricky part of the Oracle Apps. The way I usually do is to use a multiple protocol script, HTTP and Oracle NCA. I know that the newer versions of LR have a specific protocol for Oracle Apps, but this has worked pretty well for me.
To make things easier, let’s record the steps from the web interface first. Don’t forget to add some comments, Each click on the web interface generates several requests and sometimes the same happens inside the application too.
All very simple so far. If you done the right things so far, LR should be capturing all events, both on the web interface and the Oracle interface. Once you’ve finished and LR generated the basic script, the tricky correlations come in.
On most cases, you will be using more than one application note. This means load balancing. In order to do this, the web front-end will send you a node name, port and domain.
To capture this information, use the following lines on the first request made when selected a form. Right before the “RF.jsp” call.
web_reg_save_param("serv_name", "LB=var xsname = \"", "RB=\"", LAST);
web_reg_save_param("port_num", "LB=var xsport = \"", "RB=\"", LAST);
web_reg_save_param("domain_name", "LB=var xdname = \"", "RB=\"", LAST);
This will capture the required information for the load balancing. Now let’s concatenate this and create a connection string. Add this right after the “RF.jsp” call.
lr_save_string(lr_eval_string("{serv_name}{domain_name}"), "serv_name");
Now that we have the connection string, we need to capture some variables needed for the connection, like the form to be launched, some profile information, etc.
Right after the command above, add the following lines:
web_reg_save_param("nca_connect_1", "LB=
Tip 1: How to correlate the Login?
Login is usually the tricky part of the Oracle Apps. The way I usually do is to use a multiple protocol script, HTTP and Oracle NCA. I know that the newer versions of LR have a specific protocol for Oracle Apps, but this has worked pretty well for me.
To make things easier, let’s record the steps from the web interface first. Don’t forget to add some comments, Each click on the web interface generates several requests and sometimes the same happens inside the application too.
All very simple so far. If you done the right things so far, LR should be capturing all events, both on the web interface and the Oracle interface. Once you’ve finished and LR generated the basic script, the tricky correlations come in.
On most cases, you will be using more than one application note. This means load balancing. In order to do this, the web front-end will send you a node name, port and domain.
To capture this information, use the following lines on the first request made when selected a form. Right before the “RF.jsp” call.
web_reg_save_param("serv_name", "LB=var xsname = \"", "RB=\"", LAST);
web_reg_save_param("port_num", "LB=var xsport = \"", "RB=\"", LAST);
web_reg_save_param("domain_name", "LB=var xdname = \"", "RB=\"", LAST);
This will capture the required information for the load balancing. Now let’s concatenate this and create a connection string. Add this right after the “RF.jsp” call.
lr_save_string(lr_eval_string("{serv_name}{domain_name}"), "serv_name");
Now that we have the connection string, we need to capture some variables needed for the connection, like the form to be launched, some profile information, etc.
Right after the command above, add the following lines:
web_reg_save_param("nca_connect_1", "LB=
No comments:
Post a Comment