Forum Discussion
Sachin_Sawe__Pr
15 years agoContributor
Robert,
See here is what I feel but you can correct me if I am wrong. soap ui suggests that user point to localhost:8081 when 8081 tunnel is running as soapui monitor. This can perhaps work if you point to localhost:8081 and keeping rest of url for webservice same only if you do this from within soapui. I have tried this from one soapui to another soapui instance and that works too.
In this case what I doing is invoking tomcat localhost call to an ip:port/monitorServiceInSoapUI. Do you think this would work? Essentially can we invoke a call to soapui monitor running as tunnel and that call is invoked from external tomcat?
Attached is the snapshot of my tunnel setup.
Thanks,
Sachin
See here is what I feel but you can correct me if I am wrong. soap ui suggests that user point to localhost:8081 when 8081 tunnel is running as soapui monitor. This can perhaps work if you point to localhost:8081 and keeping rest of url for webservice same only if you do this from within soapui. I have tried this from one soapui to another soapui instance and that works too.
In this case what I doing is invoking tomcat localhost call to an ip:port/monitorServiceInSoapUI. Do you think this would work? Essentially can we invoke a call to soapui monitor running as tunnel and that call is invoked from external tomcat?
Attached is the snapshot of my tunnel setup.
Thanks,
Sachin
Related Content
- 5 years agopaulvinders
- 5 years agormnrdi
- 9 years agogiovanni