Troubleshooting Remedy applications which use a Security Token Property
This advice applies to Silk Performer 15.0 (with no additional hotfixes applied) and earlier. This has been resolved in SilkPerformer 15.5 With Hotfix 2 (SP155_HF2.zip).
Silk Performer supports a range of Remedy application versions, all of which are documented within the Silk Performer online help, under the heading, 'Remedy', SILK PERFORMER | HELP | CONTENTS.
Remedy versions which are currently not supported by Silk Performer include 7.6.04 SP5, 8.1.00 SP1. For these versions of Remedy, the Mid-tier configuration property will come with a security token property, arsystem.securitytoken_enable=true, and when this is true, the back channel will include an "sToken" value:
"sToken" := "07D2-1JZP-JJPU-M2MS-0EAT-HDPT-MGYP-MBIY";
When testing these Remedy versions with Silk Performer, the sToken value will not be appended to the back channel request, as the Remedy.bdh file, does not include the functionality to achieve this, which will lead to subsequent Replay errors - "WebRemedyBackChannelUrl(WebEngine: 72 - Data verification, "Network protocol/data error" appeared 1 times - verification (<1) failed)".
To determine if the sToken is used, refer to the dclform section for the back channel request and there should be a field called "- sToken".
To ensure that the sToken is appended to the request, the following changes will need to be made to the Remedy.bdh file which can be found in the Silk Performer project folder.
Within the Remedy.bdh file, a function entitled WebRemedyBackChannelUrl() is included; replace the contents of the this function with the following and save the changes:
function WebRemedyBackChannelUrl(sUrl : string;
sTimer : string optional;
formUrl : form optional) : boolean <API_FUNCTION>
sXmlData : string(100000);
WebFormValueGet(formUrl, sXmlData, sizeof(sXmlData), "param");
WebFormValueSet(formUrl, "param", RemedyBackChannelData(sXmlData));
WebRemedyBackChannelUrl := WebPageUrl(sUrl, sTimer, formUrl);
If the errors persist after the changes have been made, it is possible that Token itself will need to be customized.
To confirm, carry out two identical recordings against the application and verify whether the Token changes in content. If dynamic, you will need to search through the TrueLog to determine where the Token comes in and proceed to customize accordingly, i.e:
Please note that full support for the more recent versions of Remedy is planned in the first update of Silk Performer 15.0 and the remedy .bdh file will be updated with the additional logic by default.
If this does not help, also see the following article in regard to a Recording Rule which may help with this: