We are facing below error in MFT SOAP api - getBWSession and...

[Manoj Chaurasia]

We are facing below error in MFT SOAP api - getBWSession and other MFT admin related call.

SOAP Envelope is invalid at com.tibco.plugin.share.soap.errors.DefaultSoapErrorHandler.throwEngineException(Unknown Source) at com.tibco.plugin.share.soap.errors.DefaultSoapErrorHandler.throwEngineException(Unknown Source) at com.tibco.plugin.share.soap.processors.SoapLogger.a(Unknown Source) at com.tibco.plugin.share.soap.processors.SoapLogger.throwEnvelopeError(Unknown Source) at com.tibco.plugin.soap.SOAPSendReceiveActivity.postEval(Unknown Source) at com.tibco.pe.core.TaskImpl.eval(Unknown Source) at com.tibco.pe.core.Job.a(Unknown Source) at com.tibco.pe.core.Job.k(Unknown Source) at com.tibco.pe.core.JobDispatcher$JobCourier.a(Unknown Source) at com.tibco.pe.core.JobDispatcher$JobCourier.run(Unknown Source)

This call were working for few weeks and we started getting this error. There was no change in MFT Command center of IS level. Do note that BW code that make this call works ok in one environment, but not in another. Same code works is able to call MFT SOAP API in QA but failing in DEV and PROD. MFT Version is same across al environments - 7.2.2

 

Anyone faced this issue with MFT SOAP API call

[Andy-dont-use Pritchard]

Ranjeet, My initial thought is an encoding issue.

The first thing to check is what Encoding value you have defined in the domain definitions. And what encoding you have defined for the MFT command centre's JVM.

Other than that can you try to prove if this is a BW or MFT issue. I'd get the QA BW to try calling the DEV MFT, if that works the problem is at the BW end. If it fails, then the problem is at the MFT end.

Are you able to capture the SOAP messages via a network analyser and compare the two payloads

Andy

[Manoj Chaurasia]

thanks Andy, Let me try out your suggestions.

[Dylan Ma 3]

Hi,

 

We faced a similar error and found that re-importing the WSDL worked for us.