Hexadecimal Correlation

Hexadecimal Correlation

Some times in our scripts the dynamic values which return from the server return with several variations, some values will return with a Hexadecimal sum of the value and some without. Hnadling these values or dynamic values using correlation:

§  RB/BIN= should be used when Hexadecimal value is used in the boundary.

§  Hexadecimal value is returned from the server as \x07site_idt\x00, meaning with one back slash.

§  Additional back slash will need to be added to the correlated boundary as following \\x07site_idt\\x00.

§  The script should be tested with full log, by searching for the string StreamCorruptedException you may understand the error location and issue.

§  Also add global verification: web_global_verification("Text=java.io.StreamCorruptedException",    "Fail=Found", "ID=JavaStream", LAST);

Below you can find suggested way to correlate above statements:

■         Without Hexadecimal sum:

Value to be correlated: //\\x07site_idt\x00  000006929t

Suggested correlation:

web_reg_save_param("site_id",

 "LB/BIN=\\x07site_idt\\x00          ",

 "RB=t",

 "ORD=1"

,LAST);

■         With Hexadecimal sum of the value:

The best way to correlate is to catch the Hexadecimal value as well.

In order to remove the value SaveOffset should be added to the web_reg_save_param function:

Value to be correlated: //\\x05objidt\\x00\\x059426t\\x00\\x06et

Suggested correlation:

web_reg_save_param("objid",

 "LB/BIN=\\x05objidt\\x00",

"RB/BIN=t\\x00\\x06et",

"ORD=1",

 "SaveOffset=1

",LAST);

           

As mentioned before The value which will be removed is \\x05