This issue manifests itself as customers not seeing SOAP operations they expect to see, instead the SOAP operations URLs show up as hits.
Enhancement request to support binary SOAP+msbin1 format in FxM(Foglight Experience Monitor)
Some applications are using proprietary binary SOAP messages.
These messages contain no XML tags.
There are several formats and these is no standardized non proprietary standards for this binary communication.
It may be possible to configure the application to force the use of SOAP-XML, if so that would resolve the issue, this would be a configuration change on the applications side.
This issue has been assigned Quest Tracking ID BR1733 for consideration in a future release.
The reason why you do not see these SOAP Operations in FxM is because they are not in standard XML format. These SOAP Operations are in SOAP+msbin1 ( a proprietary binary) format. In simple terms this is a non XML data format that both the client and the server need to understand to communicate. There are no TAGS in this format as you would find in other XML communication.
Currently there is no standard for this type of binary communication; there are several different formats that are not interoperable.
Currently FxM cannot support these formats as there is no standard, if an open standard appears Quest could consider adding this functionality to the product. But currently there are too many variations and they can change at any time without notice which would break any functioning monitoring.