I discovered one transaction signature using CEM transaction discovery (is not possible to use recording session ).
This transaction originates from web services SOAP request, so contains a POST parameter with the SOAP envelope in the parameter body (see the attached picture).
As you can see, the URL path is always the same but the method invoked is contained into the XML body.
So that, I want to promote this transaction signature to different Business Transactions specializing them based on a specific XML tag.
Anyone know how can I do this when use transaction discovery?
You mentioned that you are unable to use recording session (aka advanced recorder) . From my experience that is the recording mechanism that gives the greatest flexibility with xml. I wonder if using a plugin to parse the XML information may give you the most possibilities
I think the XML parsing capabilities in a transaction definition are limited using Transaction Discovery.
So if I understand, you say that using transaction discovery, the native CEM XML parsing is limited so in this case the solution is to use a custom plugin to parse the XML.
it is correct?
That is my understanding. There is an XML Plugin that global delivery supports that may help. CoreyCohen created it so including him
I don't think the old XML Plugin is in the Community Documents so I uploaded a copy I have here
Slightly later version with readme & screenshots below (thanks Guenter_Grossberger)
This version will show the XML request payload (not response)