Hello.

Has anyone looked at the new probe in New UI that came in firmware 10.5.0.6 LTS (or 10.5.1 CD)? We switched to this version on DataPower Virtual Edition and have a lot of different problems with it:

1. Input message (XML) displayed incorrectly, showing just the XML declaration "<?xml version="1.0" encoding="UTF-8"?>"
2. No option to "View as XML" above input, just as Binary and as Plaintext
3. Execution trace of dp:url-open displayed in a wrong Transform action
4. Display of long message content that messes up page formatting

Old probe is displaying everything correctly with the same input messages, moreover it was more intuitive and clear in our opinion.

Do You have similar problems or any thoughts about it? Can't really call it like "Changed the new UI to full support".

Additionally, about two months ago, we posted an Idea for DataPower Gateway (DPGWY-I-427) to add a column with timestamp to probe and execution trace that would simplify and clarify the process of debugging incoming messages. If anyone is interested in upgrading the probe view, feel free to check that idea.

P.S. We just switched to the new firmware 10.5.0.7 and there's no change.

I, too, have reservations about calling the old UI fully deprecated.  They'll need time.  The new UI is sleek and modern, but I find myself scrolling more than previously.  Certainly the new UI is way better, IMHO, than the BluePrint console they built and discarded.  However,  I keep telling my old dog self to learn a new trick.

WRT to probes, KumbaSoft's DPAA probe view displays many things DataPower does not.  For example the time of transaction.  Is also displays the global transaction ID, which is extremely useful when you are aggregating probes from multiple services and even possibly multiple domains at one time!  Yes, you heard that right.  It can even aggregate probes from different service types.   It also lets you aggregate the probe data across multiple appliances, offers automatic refresh, and automates enable/disable of probes.   DPAA takes details of probes a bit further by showing, for example, the XSLT or GWS (if it isn't dynamically determined), the time of each action down to the millisecond, and at least attempts to display the output context of an action, rather than just the input context of the next action.

But, let me warn you.  If you ever start using DPAA, you will *never* want to go back!!!

The new probe (available only in the new UI) is still going through refinement to have full parity with the traditional probe (available only in the WebGUI). In the 10.5.0.7 fix pack shipped yesterday, is to the final probe. Therefore, stay tuned for future release of the 10.5.x CD stream where problems will be fixed in the 10.5.0.x LTS stream. The key functional difference is that the new probe is able to capture and view transaction data for debugging across self-balanced services (peer mode) but can still be defined in standalone mode for any service (not self-balanced). To exploit the new probe, you discovered the need of a gateway-peering instance. I know that this area is problematic to set up, but this is part of the improvements that are in the pipeline.

I'm forwarded your IDEA to the development team, so we'll see what happens with that enhancement.

For the layout of the new UI vs the WebGUI, all is to be compliant to Carbon Design. The WebGUI is deprecated, so is going away in the future. The new UI is now fully supported (no longer a technology preview). However, as discovered, there's visual and UX differences, so utilities that are not available, and some additions that are incompatible (e.g., the probe).

Michal,

To your points 2-4, we are aware of those issues and expect those to be resolved in a future fixpack.

As far as point 1, we need a bit more context to understand. May need you to open a PMR, so we can look into the specifics of the recreate. Are you referring to the initial input into the transaction or an input into a specific action?

Hello Chris,

Our input message is an XML without declaration, for example <test>data</test>. In the new probe we can see:

xml Content of Context 'INPUT':
<?xml version="1.0" encoding="UTF-8"?>

and is not treated as XML (View as JSON and View as XML is grayed out).

In the old probe we can see:

Content of context 'INPUT':

    <test>data</test>