Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE

How can I indentify if my Abode Flex Application under test is using non supported Externalizable Traits?

How can I indentify if my Abode Flex Application under test is using non supported Externalizable Traits?

A good indicator as to whether the application you have recorded against contains "Externalizable Traits" is if the SilkPerformer AMF3 Recorder generates a BDF script which captures the AMF3 data as binary data instead of transforming it to XML. So instead of seeing the AMF transformed to XML, like this:

WebPagePost("http://localhost/graniteamf/amf", "\r\n"
"\r\n"
" \r\n"
" \r\n"
" \r\n"..

You see the data recorded as binary data, like this:

WebPagePost("",
"\h00030000000100046E756C6C00022F34" // ????????????????????????null??????/4 00000000
"\h000001560A00000001110A81134F666C" // ?????????V???????????????????????????Ofl 00000010
"\h65782E6D6573736167696E672E6D6573" // ex.messaging.mes 00000020
"\h73616765732E52656D6F74696E674D65" // sages.RemotingMe 00000030
"\h73736167650D736F75726365136F7065" // ssage???source???ope 00000040
"\h726174696F6E0F686561646572731374" // ration???headers???t 00000050
"\h696D657374616D7011636C69656E7449" // imestamp???clientI 00000060
"\h6409626F64791764657374696E617469" // d???body???destinati 00000070
"\h6F6E136D65737361676549641574696D" // on???messageId???tim 00000080
"\h65546F4C69766501060D627573636172" // eToLive?????????buscar 00000090
"\h0A0B01154453456E64706F696E74061B" // ????????????DSEndpoint?????? 000000A0
"\h6D792D6772616E697465616D66010400" // my-graniteamf????????? 000000B0
"\h010903010A0729656E746974792E5365" // ??????????????????)entity.Se 000000C0
"\h61726368436F6E7465787401040004FF" // archContext??????????????? 000000D0

You can verify if you have encountered externalizable traits by searching for the binary values "0A 07" and sometimes "0A 0F" within the binary data contained in the SilkPerformer BDF script (as shown in bold above). Typically these values are followed by usually a single byte that contains length information for the upcoming classname or the classname itself. Additionally another indicator is if you see an error message similar to the following in the corresponding Record.log file

Error: TransformDll: Transformation for "FLASH_REMOTING": TransformBegin: at binary offset dec 658 (hex 292), unexpected end of data, while parsing a data type tag..

Currently SilkPerformer has limited support for certain externalizable traits; if you have verified the above steps then your application is not suitable for testing using SilkPerformer. For further information on externalizable traits please view the following resolution:

What are AMF3 Externalizable Traits and does SilkPerformer support them?

DISCLAIMER:

Some content on Community Tips & Information pages is not officially supported by Micro Focus. Please refer to our Terms of Use for more detail.
Top Contributors
Version history
Revision #:
1 of 1
Last update:
‎2013-02-15 19:08
Updated by:
 
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.