ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » WMBT --> XML Mapping

Post new topic  Reply to topic
 WMBT --> XML Mapping « View previous topic :: View next topic » 
Author Message
Seb
PostPosted: Thu Jul 16, 2009 6:38 am    Post subject: WMBT --> XML Mapping Reply with quote

Apprentice

Joined: 27 Mar 2009
Posts: 41

Hi,

I am using the XML Mapping editor from the WMBT to create my XSL Stylesheets for the the XSL Transform Nodes.

Are there any best practices / documentations on this tool?

Actually, I am looking for an explanation on how to create xsl:choose elements with this tool.

Thanks in advance!

Seb
Back to top
View user's profile Send private message Send e-mail
mqjeff
PostPosted: Thu Jul 16, 2009 8:58 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

Why use XSLT at all?
Back to top
View user's profile Send private message
Seb
PostPosted: Thu Jul 16, 2009 9:59 am    Post subject: Reply with quote

Apprentice

Joined: 27 Mar 2009
Posts: 41

Hi Jeff,

because it makes it easier for the customer to create its own mappings, even if they don't have that much WMB background.

But back to my original question ... Has nobody ever used this tool, esp. people from IBM?
Back to top
View user's profile Send private message Send e-mail
Vitor
PostPosted: Thu Jul 16, 2009 11:45 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

Seb wrote:
because it makes it easier for the customer to create its own mappings, even if they don't have that much WMB background.


Will you tell your customer they're using the least efficient of the WMB mapping methods?

Seb wrote:
But back to my original question ... Has nobody ever used this tool, esp. people from IBM?


It's possible that no-one has. The use of XSLT within WMB is principally intended for the use of existing XSLT by people migrating onto WMB from an XSLT based method. WMB can use the XSLT, allowing immediate use, while new material is generated into ESQL within WMB.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
Seb
PostPosted: Thu Jul 16, 2009 12:23 pm    Post subject: Reply with quote

Apprentice

Joined: 27 Mar 2009
Posts: 41

Well I asked my customer how many messages they are going to send over that mapping flow. The answer was 200,000 p.a. (max. 5kb p.msg.)

I guess the XSL Transform node is more than sufficient for this kind of XML messages. So why use ESQL, which nobody can read after I have left the project?

Furthermore, I told my customer that XSLT is a product-independent standard esp. for XML message transformation. So if they are going to send more messages they might think about buying Datapower or use WESB or whatever. As far as I know, these products do not support ESQL and the specialists for these products have mostly no idea of what ESQL is. So why use ESQL for mappings, as there is already a standard?
Back to top
View user's profile Send private message Send e-mail
Vitor
PostPosted: Thu Jul 16, 2009 10:47 pm    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

Seb wrote:
I guess the XSL Transform node is more than sufficient for this kind of XML messages.


If the volumes are really that low then yes. But with volumes that low I wonder at the decision to purchase WMB, a fairly expensive item. Perhaps the customer intends this situation to change?

Seb wrote:
So why use ESQL, which nobody can read after I have left the project?


Aside from every person who's worked on WMB in the last 10 years. ESQL also has more features & flexibility (aside from the performance) than XSLT

Seb wrote:
Furthermore, I told my customer that XSLT is a product-independent standard esp. for XML message transformation.


True

Seb wrote:
So if they are going to send more messages they might think about buying Datapower or use WESB or whatever.


Why would they buy more product when they're hardly using this one? Datapower is intended for high speed wire transformation in high volume situtation (1000s of messages a minute). You're a long way from that.

Seb wrote:
As far as I know, these products do not support ESQL and the specialists for these products have mostly no idea of what ESQL is. So why use ESQL for mappings, as there is already a standard?


Not what I understood, but my experince of Datapower is limited to the sales pitch and some presentations, so I'll defer to your greater knowledge.

Though if this is the case, you have to wonder why WMBv6 makes so little use of XSLT and continues with ESQL as the principle transformation language.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
ovasquez
PostPosted: Fri Jul 17, 2009 7:19 am    Post subject: Reply with quote

Centurion

Joined: 09 Dec 2005
Posts: 141
Location: Lima, Peru

Seb wrote:

I guess the XSL Transform node is more than sufficient for this kind of XML messages. So why use ESQL, which nobody can read after I have left the project?

Depend...This is IBM Performance Report from WMB 6.1...example(In z/OS):
MQInput->XSLT->MQOuput
Msg Size ---Rate (Msgs/sec) %---- CPU Busy ----CPU ms/msg
4K---289.12--- 69.28--- 4.79
16K---101.84--- 66.15--- 12.99
64K---27.09--- 60.06--- 44.34
256K---6.68--- 61.37--- 183.82

MQInput->ESQL->MQOuput
Msg Size ---Rate (Msgs/sec) %---- CPU Busy ----CPU ms/msg
4K---302.60--- 64.10--- 4.24
16K---82.21--- 57.01--- 13.87
64K---19.71--- 54.88--- 55.68
256K---4.10--- 53.45--- 260.73

Seb wrote:

Furthermore, I told my customer that XSLT is a product-independent standard esp. for XML message transformation. So if they are going to send more messages they might think about buying Datapower or use WESB or whatever. As far as I know, these products do not support ESQL and the specialists for these products have mostly no idea of what ESQL is. So why use ESQL for mappings, as there is already a standard?

Sure? for example
XML-->MQInput-->(Transformation)--->MQOutput
You can use DataPower before MQInput....But in Flow is not posibled
_________________
Oscar Vásquez Flores


Last edited by ovasquez on Fri Jul 17, 2009 7:36 am; edited 1 time in total
Back to top
View user's profile Send private message Send e-mail
ovasquez
PostPosted: Fri Jul 17, 2009 7:27 am    Post subject: Reply with quote

Centurion

Joined: 09 Dec 2005
Posts: 141
Location: Lima, Peru

Seb wrote:
Hi Jeff,

because it makes it easier for the customer to create its own mappings, even if they don't have that much WMB background.

But back to my original question ... Has nobody ever used this tool, esp. people from IBM?


But use "Node Mapping" is very easy too, and not requiered background in ESQL. and is posibled export Node Mapping->ESQL, view suppport pack ia9y_1.0.0-WMB Toolkit Map to ESQL PlugIn
_________________
Oscar Vásquez Flores
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » WMBT --> XML Mapping
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.