Pinned topic RPT Usage for Fidessa
Amarjeet Mahajan 270003XJNJ5 Posts
PaulLiskay 06000284J3587 Posts
Amarjeet Mahajan 270003XJNJ5 PostsACCEPTED ANSWER
Re: RPT Usage for Fidessa2013-12-17T06:09:48Z in response to PaulLiskay
Fidessa is providing multi-asset trading and investment infrastructure, their market data and analysis, and their decision making and workflow technology. its desktop / Thick client application developed in VB,C++ and may be python.
PaulLiskay 06000284J3587 PostsACCEPTED ANSWER
Re: RPT Usage for Fidessa2013-12-17T12:53:16Z in response to SystemAdmin
The only hope for capturing traffic would be to add Fidessa as either a managed Application or unmanaged application at recording time. This is the same dialog where it prompts which browser to use.
If it's added as a managed application and RPT doesn't capture the traffic then it's unsupported in RPT. RPT can't predict or be aware of how every client application will communicate with it's server.
The alternative is to try it as an unmanaged application, but the prerequisite is that the LAN settings for the client application must be configurable on the fly to point to the port the RPT Proxy recorder is using.
An example of how to do this with Chrome can be found here: http://www-01.ibm.com/support/docview.wss?uid=swg21653933
If the LAN settings for the Fidessa application can't be configured manually and dynamically at record time then it can't e recorded as an unmanaged application.
If traffic is captured as either a managed or unmanaged application and the protocol isn't HTTP, then it'll be socket protocol, which is OK but it's almost impossible to deal with (data correlation, datapools, etc) and is very sensitive to error conditions (response data might be set to exact number of bytes for example)
Worth experimenting. You can try Firefox or IE as both an unmanaged and managed application to understand how RPT handles such applications