AppScan cannot import manually generated explore data files (exd)
上一篇 /
下一篇 2010-08-11 14:15:54
/ 个人分类：IBM Appscan Security Scan
| |
| Problem(Abstract) |
| AppScan cannot import manually generated explore data files(exd file - formally known as Business Process file).If the file has been manually modified, you will encounter this error message:"Import Explore Data Failed".AppScanSys.log will write the following error "System : Failed to load data from business process file." |
| | |
|
|
| Resolving the problem |
The reason for AppScan's inability to import this explore data file is likely due to the following reasons :
a) The exd file was generated manually. (The exd file should not be edited as it indicates in the file itself.)
and
b) The offending exd file contained characters from the high ascii range.
Usually, when AppScan creates .exd files through the AppScan UI (that is, it is not generated manually), it converts high ascii characters, and only then writes them to the exd file.
When they are generated manually there is a possibility that some of the high ascii characters were left un-encoded, therefore preventing the exd file from being imported into AppScan.
First, open the offending exd in IE. It will load the file until it reaches such a character, and it will show you the line that contains it.
Go to the line and see if the parameter value contains a character from the high ascii range.
Use the AppScan "encode/decode" power tool to encode that value.
We also add a direction in the exd to treat the value as encoded.
Therefore, the line would look like this:
<parameter encodeValue="True" name="someparametername" value="encoded parameter value=" type="BODY" linkParamType="hidden" />
(You can do the same for parameter names � add encodeName="True" and encode the parameter name with the encode/decode too)
This will allow you to import the explore data file (exd) successfully.
|
收藏
举报
TAG:
