| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| XML Mapping Editor in v8 |
« View previous topic :: View next topic » |
| Author |
Message
|
| goffinf |
 Posted: Thu Dec 29, 2011 8:50 am Post subject: XML Mapping Editor in v8 |
 |
|
Chevalier
Joined: 05 Nov 2005
Posts: 401
|
version: 8
I notice that the info centre for v8 appears to have no mention of the XML Mapping Editor (there was quite a lot in previous versions) ??
I *can* invoke this editor but when I add a schema as an input or output source/target nothing appears in the mapping pane.
Has something changed in v8 that would cause this behaviour ?
Fraser. |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Sat Dec 31, 2011 8:22 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Version 8 has an entirely new mapper, that should be fully functional for XML.
I assume you're actually talking about some kind of non-Broker specific XML mapper, that was likely part of the RAD components of the Broker Toolkit, that would let you create an XSLT rather than a Broker Mapping node map.
I suspect they don't include that component of RAD with Broker Toolkit v8, since Broker Toolkit v8 is not designed or intended to be a general purpose development enviornment, but rather a specific development environment for BROKER.
The XML Transformation node has always been better used to allow you to reuse existing XSLTs until you can convert them to Broker transformations. Because if you're paying for Broker and only using it as an XLST engine, you're wasting a lot of money.
Import your XML Schemas as message sets, create a real Broker map using the Mapping Editor instead of writing an XSLT. |
|
| Back to top |
|
|
| goffinf |
| Posted: Sun Jan 01, 2012 11:00 am Post subject: |
|
|
Chevalier
Joined: 05 Nov 2005
Posts: 401
|
Yes your are entirely correct, we were/are using the XML Mapper to generate a specification for turning application specific data models to the canonical model we use for our ESB (Broker). The users of this tooling are our data analysts rather than Broker Devs and it provides a nice link between the two teams especially since it doesn't require our data analysts to know anything about Message Broker, but still allows them to create artefacts that are useful to a Broker Dev. That isn't the case for mapping nodes and message sets.
The XML Mapping Editor *does* appear to be installed as part of the toolkit (this is an absolutely fresh install with nothing else on it other than Broker), but I had observed it didn't appear to work correctly and the was nothing in the InfoCentre about it any longer, which is different to previous versions.
Whilst we do sometimes generate XSLT and run it within Broker, we also parse the .map file into ESQL. I appreciate that Broker is not tuned as an XSLT engine but as I'm sure you understand (and have seen you comment in this forum), it often about using the right tools for the job in hand and sometimes the choices have many facets beyond purely technical considerations (availability of skills for example). Interestingly we have not used the XSL Transformation node provided with Broker ever. When we do use XSLT we use our own custom node which supports XSLT 2 (and beyond) which we find more useful particularly in respect of functionality. As far as wasting our money, well, we use Broker for an awful lot more than just transformation, and indeed one design principle that we try hard for is transformation avoidance, so no not really.
We have tended to stay away from Using Message Sets except in circumstances which really demand it. By and large we use ESQL for almost all transformation logic in Broker.
Anyway, As you rightly point out mapping has move on some in v8, so I should spend some time evaluating this further.
I was really only commenting that something that previously worked quite satisfactorily does not now appear to do so. I appreciate that this is not necessarily a Broker issue and you appear to have confirm that this is the case.
It's likely that others use the XML Mapping Editor, so this was as much a *heads up* for them as for my own reasons.
Thanks for your response
Fraser. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
