cancel
Showing results for 
Search instead for 
Did you mean: 

Scenario proxy to soap synchronous with external definitions

former_member217283
Participant
0 Kudos

Hi all,

I have a problem with my scenario.

In development environment all is working fine, but when I have transported to preproduction environment and we have executed my scenario I have the following error:

<SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server did not recognize the value of HTTP Header SOAPAction: http://geisiedes.endesa.es/WSRespuesta/WsRespuestaSIE.asmx/EnviarRespuestaNocturnaWF.</SAP:AdditionalText>

<SAP:Stack />

I attach the receiver communication channel configuration.(cc_config.jpg)

I changed the target URL in the receiver channel, with the preproduction machine, but I didn't change the sopa action because is define in the wsdl ( soap_action.jpg).


I have othe external definitions for preproduction environmet but its contect is different to external definitions in development change the reference to machine where geisiepre instead geiseides.

Whe I import this external definitions I lose the configuration in messages mappings.

How can I solve this problem? Is mandatory to have the same external definitions in the three environments??

Thanks and best regards

Mónica

Accepted Solutions (0)

Answers (2)

Answers (2)

iaki_vila
Active Contributor
0 Kudos

Hi Monica,

I normally use the all the tag content in the SOAPAction tag, but you can try with EnviarRespuestaNocturnaPC in the SOAP receiver communication channel.

Have you tried to test your wsdl endpoint with SOAPui?, you can get sometimes valuable information about how design/configure in PI and if the request is identical in PI and in SOAPui.

Regards.

Harish
Active Contributor
0 Kudos

Hi Monica,

did you tried to configure the correct soap action in preprod and test? AFAIK - it should be good if you have soap action set in receiver comm channel.

regards,

Harish