| Author |
Message
|
| praveenmq |
 Posted: Mon May 07, 2012 5:02 am Post subject: WSDL file is corrupted |
 |
|
Voyager
Joined: 28 Mar 2009
Posts: 96
|
Hi all when i do a mqsi list it displays a error saying that WSDL file is missing.
As shown below,
mqsilist BROKER02 -e default
BIP2087E: Broker BROKER02 was unable to process the internal configuration message.
The entire internal configuration message failed to be processed successfully.
Use the messages following this message to determine the reasons for the failure. If the problem cannot be resolved after reviewing these messages, contact your IBM Support center. Enabling service trace may help determine the cause of the failure.
BIP4041E: Execution group 'default' received an invalid configuration message. See the following messages for details of the error.
The message broker received an invalid configuration message and has not updated its configuration. This can arise as a result of errors in the specification of either message flows or message sets which the configuration manager was unable to detect. It can also result from a message flow requiring a type of node that is not supported by the broker installation, from the broker having become out of step with the configuration database or from other applications sending extraneous messages to the broker's configuration queues (SYSTEM.BROKER.ADMIN.QUEUE & SYSTEM.BROKER.EXECUTIONGROUP.QUEUE).
Check the relevant message flow and message set definitions, check that all necessary user-defined extensions are installed, perform a complete redeploy of the broker's configuration and ensure that no applications are writing to the broker's configuration queues.
BIP3726E: Failed to setup SOAP transport for node SOAP Input.
The SOAP nodes rely on the configuration of the SOAP transport layer within the broker, 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 UserInfoExternalSvcSOAP could not be found in the supplied WSDL file /var/mqsi/components/BROKER02/c56c3184-2601-0000-0080-fdfc1dcf033b/config/XSD/MS_CUSTOM_MEDIATION_SERVICE/qa/gov/igov/service/userinfosvc/UserInfoExternalSvc.wsdl.
The WSDL binding UserInfoExternalSvcSOAP from the target namespace urn:igov.gov.qa/service/UserInfoSvc associated with message set MS_CUSTOM_MEDIATION_SERVICE was not found in the WSDL file /var/mqsi/components/BROKER02/c56c3184-2601-0000-0080-fdfc1dcf033b/config/XSD/MS_CUSTOM_MEDIATION_SERVICE/qa/gov/igov/service/userinfosvc/UserInfoExternalSvc.wsdl. This could be because the WSDL file is missing, invalid or corrupt.
Determine the cause of the error and correct it. Ensure that the WSDL file is valid and that it validates correctly.
BIP8071I: Successful command completion.
Could you please let me know where to find the WSDL file and also check whether the file is not corrupted?
Thanks,
Praveen. |
|
| Back to top |
|
 |
| praveenmq |
| Posted: Mon May 07, 2012 5:07 am Post subject: |
|
|
Voyager
Joined: 28 Mar 2009
Posts: 96
|
Recently i changed the password for BROKER using mqsichangebroker
So could that be a issue for the WSDL filein Message flow to be corrupted |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon May 07, 2012 5:32 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| praveenmq wrote: |
| So could that be a issue for the WSDL filein Message flow to be corrupted |
No.
You'll find (or should find) the WSDL file's message set deployed to the execution group that uses it. Unlike other referenced message sets WMB won't accept the deploy of a flow containing SOAP without the WSDL in place & I imagine (though I've never tried it) would consider the flow deployment invalid if the WSDL was later removed / renamed.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| praveenmq |
| Posted: Mon May 07, 2012 7:08 am Post subject: |
|
|
Voyager
Joined: 28 Mar 2009
Posts: 96
|
| Where can we find the wsdl file? |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon May 07, 2012 7:18 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| praveenmq wrote: |
| Where can we find the wsdl file? |
| Vitor wrote: |
| You'll find (or should find) the WSDL file's message set deployed to the execution group that uses it |
Why ask questions if you're not going to read all of the answers?  
If you mean "where do we find the original WSDL", it's whereever you left it. I'd start with your source code control system.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Mon May 07, 2012 7:22 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| praveenmq wrote: |
| Where can we find the wsdl file? |
If the Webservice is an external (outside your company) then that company will supply the WSDL (and often the xsd to go with it) for you.
The external site (http) may well have a like to a page where the .wsdl etc is available for download. Companies like Experian do it this way.
Others may make the wsdl available via the ?wsdl estension to the site URL.
Using "?wsdl" as a search request to google may well prove enlightening in your quest to understand and eventually become the SOAP Guru you have always desired 
{Other search engines are available but may not return relevant information}
_________________
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 |
|
|
|
|
