| Author |
Message
|
| Vijji |
 Posted: Sat Mar 25, 2006 11:21 am Post subject: TDS to XML |
 |
|
Voyager
Joined: 30 Aug 2005
Posts: 83
|
Hi every body,
Is there any way to convert TDS format to XML format with out using message sets. |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Sat Mar 25, 2006 11:22 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
What's wrong with using message sets?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Vijji |
| Posted: Sat Mar 25, 2006 11:50 am Post subject: |
|
|
Voyager
Joined: 30 Aug 2005
Posts: 83
|
No jeff..actually i just want to play with various formats..So can u tel me the way if there is any.Here I want to take my TDS input where my parser is BLOB.But after accepting it into Compute node i am getting the message as BLOB.So can u suggest me any way to do this..or ..Am i wasting time ? ..
Cheers,
Vijji. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Sat Mar 25, 2006 12:00 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
If you want to learn the product, then learn to use message sets.
The difference between data in the BLOB domain and data in the MRM domain (which includes TDS data) is that data in the BLOB domain is not modelled at all, and data in the MRM domain is modelled using message sets.
So, technically, it doesn't make sense to say "TDS data in the BLOB domain".
If you wish to use WMB as a completely dumb programming environment, it is entirely possible to write ESQL that will hand parse fields out of BLOB based on byte count or based on the appearance of tags or delimiters by making heavy use of the SUBSTRING and POSITION functions on BLOB data.
But this is like using WebSphere Application Server to print "Hello World". Yes, it can be done - but there are a lot easier and cheaper ways to do it, and you're not using any of the real features of the product that presumably are why you paid for the product in the first place.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Vijji |
| Posted: Sat Mar 25, 2006 12:08 pm Post subject: |
|
|
Voyager
Joined: 30 Aug 2005
Posts: 83
|
Thnx Jeff,
For u r info I am using message sets from past one year..I am doing this scenario for R&D sake only..Anyway thanx for the clarification.
Vijji. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Sat Mar 25, 2006 12:19 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I guess I still don't understand your question.
If you have an MQInput node that defaults to using BLOB, and you do not specify an MQRFH2 header on the messages, then your data will be received as BLOB data.
Then you can change the properties of the message to indicate that it is MRM data and should be processed by a TDS physical layer from a particular message set. This is done either with an RCD node or with ESQL directly. Then you can cause the data to be reparsed as MRM data. This can be done with Create Field... Parse or by accessing your message fields.
Or you can use SUBSTRING, POSITION and other string manipulation fields to extract chunks of the BLOB data and convert them to elements in a logical message tree.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
