If you record a script against a Remedy application and there are a lot of TCP/IP functions recorded rather than high-level Remedy functions then it is possible that you are recording the Remedy fat client rather than the Web client. For example, the following portion of a recorded script indicates that the Remedy fat client client is being recorded: WebTcpipConnect(hWeb0, "100.11.12.13" , 7639 ); WebTcpipSendBin(hWeb0, "\h80" ); // ?? WebTcpipRecvExact(hWeb0, NULL, 36 ); WebTcpipShutdown(hWeb0); WebTcpipConnect(hWeb0, "100.11.12.13" , 7639 ); WebTcpipSendBin(hWeb0, "\h80" ); // ?? WebTcpipRecvExact(hWeb0, NULL, 192 ); WebTcpipSendBin(hWeb0, "\h80" ); // ?? WebTcpipRecvExact(hWeb0, NULL, 320 ); WebTcpipSendBin(hWeb0, "\h80" ); // ?? WebTcpipRecvExact(hWeb0, NULL, 740 ); This can be confirmed by reviewing the recorded log. The following entry indicates that the Remedy fat client is being recorded rather than the Web client: Start recording WinSock traffic of application: C:\Program Files\AR System\User\aruser.exe For details on SilkPerformer"s support for Remedy applications please refer to the release notes and the resolution, " Does SilkPerformer support Remedy ARS systems? ?".
↧