on 07-19-2012 10:06 PM
Hi Guys,
I have been surfind the internet looking for a solution to this issue that I'm having with the WSDL generated by a web services that it was created based on an RFC. This is the scenario:
1. I create a function group with 2 function modules (add and sub)
2. Go to Utilities > More Utilities > Create Web Services > Function Group
3. I select all the basic configuration (Transport: No Authentication and No Transport Guarantee, local object) and click on finish.
4. The web services was created on ECC and I execute SOAMANAGER to create the endpoint.
5. Here I leave all the default configuration and create the binding
6. Once that I finished the following happens:
- If I press in the 1st link (Open Design Time WSDL document) it opens the WSDL but binding and service tags are missing. (Check attachment)
- If I press in the 2nd link (Open WSDL document for selected binding or service) after 60 seconds I get a Time Out with the following error:
500 Connection timed out
--------------------------------------------------------------------------------
Error: -5
Version: 7200
Component: ICM
Date/Time: Thu Jul 19 20:36:16 2012
Module: icxxthr_mt.c
Line: 4295
Server: scdecc_ECC_00
Error Tag: {-}
Detail: Connection to partner timed out after 60s
In addition, because of the lack of Binding and Service tags in the WSDL I can't use SOAP UI to generate testing scenarios because it gives me an error due to the missing tags.
I would really appreciate it any kind of help, I had been checking SDN for discussions like this but the ones that I found didn't have the answer or didn't apply.
Thanks in advance!
Best regards,
Diego Dora.
Hi Diego,
Once you create the endpoints in SOAMANAGER of ECC, there service will get published in the Service Registry. (automatically, depends on the publishing rules).
A) Check if you can locate the service in the Services Registry.
B) You must be getting these options in SOAMANAGER after selecting the service.
try options 3 & 4.
Regards,
Anish
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Anish,
Thanks for you answer! On friday night I got to the bottom of it, I'm going to explain it here so we can keep the solution for the community:
- Basically, the option Open WSDL document for selected binding or service was timing out.
- It seems that the reason why was Timing Out (with a 60 seconds Time Out) is that the standard code that generates the WSDL with the corresponding binding was being compiled on the background.
- After extending the time out to 3600 from the transaction SMICM (ICM Monitor) it took a couple of minutes and the WSDL was generated.
- Now, it only takes a couple of seconds to generate the WSDL with the binding.
For more details, here is the step by step:
Check the System Time Out
After this, press the link for the corresponding service in the SOA Manager : Open WSDL document for selected binding or service.
I hope this help other fellow colleagues!
Best,
Diego Dora.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.