I need a little help in clearing up an issue:
We had a Windows server that was both a web server hosting our web applications as well as the host for our webMethods IS proxy server. We had a web application that instantiated a VB DLL that in turn called an internal webMethods service through our proxy server. The VB DLL code was generated using the “Generate Code” option on the webMethods service from the Developper tool. All we did was fill in the proxy server setttings and let the server settings default.
This worked great until we moved the web server applications to another host server. We now have two physical servers in our DMZ, a dedicated webMethods IS proxy server and a web server. The web application in question was simply moved to the new server along with the VB DLL. The DLL was registered and all that other stuff. The problem is that it is no longer connecting to the webMethods server. It instantiate the object but is unable to connect. (The wc.context is not executing the connect method.)
I believe the problem may reside in the way we have our proxy settings and our server settings set within our VB DLL code.
Can someone please confirm if the following assumption is correct:
1- Proxy server, port, user & password are what we have setup as our external proxy and should not change from one server to another.
2- Server, port, user & password should be for our external IS server located in the DMZ?
Please let me know if additional info is required.