Help !!! - Webservices not accessible in target systems after transport

[Former Member]

Hi

We have a ECC 5.0 box ( WAS 640 ) and have created Webservice definitions and released it to SOAP runtime. We were able to make calls to the this Webservice from external SOAP clients and looks ok. We had this webservice definition ( and its associated objects like - virtual interface,server proxy implementation etc ) moved to our QA system. In the QA system - we had to release the WS for runtime using t.code WSCONFIG and the service shows up in SICF transaction under /default_host/sap/bc/srt/xip/sap/ as active . But we are unable to access the service in our QA system http://xxxxxx:8625/sap/bc/srt/xip/sap/SVCNAME?sap-client=080&wsdl=1.1 ?

We checked the icm monitor from SMICM and everything looks ok in QA and the very same as in development. Can anybody out there help me with this ? Any pointers/similar experiences /known problems with transport webservices- and how you resolved it would be extremely helpful and appreciated.

This is the first time we are trying out this mode and we are under time-pressure to get this working. Please help !!!

[athavanraja]

http://xxxxxx:8625/sap/bc/srt/xip/sap/SVCNAME?sap-client=080&wsdl=1.1 ?

ICF requires you to use Fully qualified domain name.

xxxx.domain.com:port

amy be this is an issue

[Former Member]

Hi

We seem to have nailed the issue. Its basically a firewall setting wherein certain http ports on some of the R3 boxes are not open to access in our environment. Thanks for the suggestion anyway.

[Former Member]

Your descriptions seems to me to be an ITS scenario.

Therfore you have to

- set the system parameters

- to publish the services (SE80)

- and to start the services within SICF

Did you publish your services in SE80?

You also have to publish the Service SYSTEM with SE80