| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Error: Failed to setup SOAP transport for node SOAP Input. |
« View previous topic :: View next topic » |
| Author |
Message
|
| salberto |
 Posted: Thu Oct 13, 2016 2:23 pm Post subject: Error: Failed to setup SOAP transport for node SOAP Input. |
 |
|
Novice
Joined: 08 Aug 2016
Posts: 14
|
Hi all
Im creating a SOAP webserice, I already have all the message flow created, I have created my WSDLfor my soap input node. everything looks fine, I do not have errors but when I try to deploy it I get the following error:
| Quote: |
BIP3726E: Failed to setup SOAP transport for node SOAP Input.
The SOAP nodes rely on the configuration of the SOAP transport layer within the integration node, and this has not been initialised correctly. The node will not be operational until the problems have been corrected.
Determine the cause of the error and correct it. Subsequent error messages may contain more information.
BIP3732E: The specified WSDL binding dbAltaClientes_msjSETSOAP_HTTP_Binding could not be found in the supplied WSDL file dbAltaClientes_msjSET/com/ibm/www/dbAltaClientes_msjSETService.wsdl.
The WSDL binding dbAltaClientes_msjSETSOAP_HTTP_Binding from the target namespace www.ibm.com associated with message set was not found in the WSDL file dbAltaClientes_msjSET/com/ibm/www/dbAltaClientes_msjSETService.wsdl. This could be because the WSDL file is missing, invalid or corrupt.
|
I have validated my WSDL and the Binding information is correct, also I have created a new message set and a new WSDL from my xml schema and generated a new WSDL but the error is the same.
I found this topic about my issue:
But I already have the version 10.0.0.6 .
also I have checked similar issues but I did not find a solution.
Any clue about how to fix it?
Thanks |
|
| Back to top |
|
 |
| salberto |
| Posted: Fri Oct 14, 2016 12:29 pm Post subject: |
|
|
Novice
Joined: 08 Aug 2016
Posts: 14
|
HI all
I have fixed the problem.
I dont know the root cause of the problem but the the MF is working as expected with my workaround.
if I drop the WSDL into de MF to generate the SOAP nodes automatically the MF is not working due to the error that I sent.
If I create all SOAP nodes manually and I select the WSDL manually, the MF is working fine.
Thanks |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Fri Oct 14, 2016 9:30 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
If what you tried and failed is repeatable then it might be worth raising a PMR.
FWIW, on an old project (4+ years) I used a template subflow for this rather than generating the nodes automatically just because of a bug in the Broker version (6.1).
Later versions (6.1.0.6 onwards) resolved the issue and I've not had it since. However some of my colleagues got it to work on the buggy version. Perhaps it was the way that I was doing the drop of the WSDL but we will never know now.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
