cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

This product reached the end of support date on March 31, 2021.

SOAP Methods not mapping in DCRUM 2017

jose_colella
Inactive

Hello everyone,

After upgrading from 12.3 to 2017, one of the software service changed from SOAP over HTTP to HTTP , which I understand, as both XML and SOAP were merged into HTTP protocol. But in the operations we are no only seeing the SOAP method calls only http calls. I also added 'application/soap+xml' to the content-type of the software service.

Any suggestions?

3 REPLIES 3

jean_louis_lorm
Dynatrace Pro
Dynatrace Pro

Look at this ticket about the impact of the XML decode migration.

I hope it will help you.

https://support.dynatrace.com/supportportal/browse...

In my case, the SAOP software service didn't decode correctly with the migrated configuration. I recreated all my SOAP software service with the recommanded configuration (as describe by the support) and after that the issue was fixed.

Regards,

JLL

jose_colella
Inactive

I have received feedback from @Adam P.. In 2017, SOAP methods are mapped to Miscellaneous Parameter 5. The operation will show the http uri called, with the Miscellaneous Parameter 5 showing the SOAP method invoked. Adding this dimension to the DMI should allow you to see the SOAP method.

Thanks @Adam P.

That's good to know. Thanks Jose for sharing this valuable information.