Skip to main content

We have a web service written using Extend 9.1.1,running on a local server, with several methods.  We can access the methods locally using SoapUI with no problem, using the convention:

servername/.../method.srf


We have forwarded port 80 on our router to the server inside the network,and we can access a web page resident on that server, from outside the network through the internet.


However, we are unable to access any methods of the web service, using either:

publicurl/.../method.srf or

publicurl/.../method.srf

The latter seems the one we should use; and SoapUI does take longer to return an error. 

Is there another port we need forwarded through the router, or is there a different naming convention we need to use?

Or might this be related to the security?  the BIS server is set up as "Run as the interactive user"; I was not able to get BIS working using the "Run using this account" option.

Thanks

Tony

We have a web service written using Extend 9.1.1,running on a local server, with several methods.  We can access the methods locally using SoapUI with no problem, using the convention:

servername/.../method.srf


We have forwarded port 80 on our router to the server inside the network,and we can access a web page resident on that server, from outside the network through the internet.


However, we are unable to access any methods of the web service, using either:

publicurl/.../method.srf or

publicurl/.../method.srf

The latter seems the one we should use; and SoapUI does take longer to return an error. 

Is there another port we need forwarded through the router, or is there a different naming convention we need to use?

Or might this be related to the security?  the BIS server is set up as "Run as the interactive user"; I was not able to get BIS working using the "Run using this account" option.

Thanks

Tony

Hi Tony, There is also a license difference when using BIS in a WAN. If you'd like you could email me your runtime license and I could verify that is is set up for BIS WAN Stephen.hjerpe@microfocus.com