It's possible to configure Rumba to send its traffic to the Silk Performer SOCKS proxy using the configuration below. Rumba cannot be configured to use the HTTP proxy unless Rumba Security Server (RSS) is also installed on the machine. The first step is to determine which port the Silk Performer SOCKS proxy is using. This can be found in Settings | System | Recorder | Proxies. By default, port 19180 is used. Once you know the port, open Rumba, go to Connection | Configure and choose which interface you are going to use, for example TN3270. This will enable the TN3270 Advanced tab as below: Click the 'Security' button to enable the 'Mainframe Security Properties' screen and then choose the 'Proxy' tab. Now you need to choose 'SOCKS v4 proxy' from the drop down list and enter the server and port where the Silk Performer recorder will be running. If Rumba and Silk Performer are on the same machine localhost will work. It's essential to also check the 'Proxy' checkbox at the bottom of the screen. If this is not checked Rumba will not know to use the proxy. Once Rumba has been configured, start the Silk Performer recorder via the Record | Recorder method. Restart Rumba and connect to your Mainframe server. If the configuration is correct, the Silk Performer recorder should start to see the traffic and script WebTelnet* type functions after the connection.
↧