Why Can\'t I Use Auto Config Script To Record?
This one stumped me.
I'm using RPT 7.0.1 on Windows.
I am trying to record a webapp that uses secure https in our internal network. I tried various LAN settings to get rid of the IWAT3040E error that RPT spits out when it doesn't like the recorder settings.
Basicially, when I do a dry-run of the test case, it works fine. Our company browsers have a default configuration script that points to a proxy (pac) file. I realized that if this is not checked, the application I'm trying to record does not work with RPT.
Automaticially Detect settings itself won't work. When I plug in the proxy settings (HTTP and Secure) for the connection, that doesn't work as well.
Can anyone help with this or know the limitations of RPT proxy/secure recording?
Re: Why Can\'t I Use Auto Config Script To Record?
Figured it out.
It was a proxy setting on my IE. RPT doesn't support autoconfig scripts.
I set my internet connection options as:
Check: Automaticially configure settings.
Proxy Server, Advance: I set my HTTP and Secure proxy to the SAME server/port configurations.
Through IBM, I found out that RPT records traffic through the same (one) server. Before I put in two separate servers when I only needed the main enterprise server listed twice.
Once I did this and recorded the script, I had to install the certificate DURING the record and continue until session end. Through IBM, I found that this is necessary to store the session information.
Now, I can record my SSL with no problem!