Hi, thanks for your responses.
We’re using webMethods to integrate publisher and subscriber systems. The publisher and subscriber teams each provide us with an XSD, and perform a direct mapping which indicates which publisher field gets mapped to which subscriber field, as well as any transformation logic to be performed in ESB.
Once we have this information we create a proxy document, which is nothing more than an XSD where all of the fields are optional strings, and then directly map the publisher XML to the proxy input and the proxy output to the subscriber input with the requested transformation logic (i.e. transform Y to Yes or N to No).
What I would like to be able to do is to have a consolidated pipeline which contains all the above mentioned mapping logic. Using “View as HTML” is almost exactly what I was looking for, except for a couple of things:
- It only shows the mappings for that particular flow service
- It only says the names of the fields, not the path to them from the XSD
- i.e. if the publisher field PubRoot/PATH1/pField is mapped to the subscriber field SubRoot/PATH/sField, the output from “View as HTML” shows that the source is pField and the destionation is sfield, but I need the paths to pField and sField since that same field name could be present in multiplaces within the XSD.
Do you know if there is any way to change the settings for “View as HTML” to print out the full path to the fields as opposed to just the field names, and if there is a way to view all of the code as HTML on one screen?
Thank you again,