| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MRM, XML elements limit |
« View previous topic :: View next topic » |
| Author |
Message
|
| yaakovd_new |
 Posted: Wed Feb 11, 2004 8:03 am Post subject: MRM, XML elements limit |
 |
|
Apprentice
Joined: 03 Feb 2004
Posts: 25
Location: Israel
|
Hi,
The questions are relevant for WMQI 2.1 and WBI 5 as well.
I'm working with XML parser using MRM.
I have single XMLRoot element for all parts of the system. Under I XMLRoot I have XMLHeader, which also same for everithing.
But each application has unique DataMsg. So my XML looks as folowing:
XMLRoot
....XMLHeader
........Hfield1
........Hfield2
........Hfield3
....DataMsg
........App1field1
........App1field1
........App2field1
........App2field1
........App3field1
...
I prefer to created single message set (single DTD) for all.
All elements (around 1000 elem) under DataMsg will be optional and each application will receive/create only the relevant data (5-10 elements).
And here the questions:
If exists any limitation on number of elements in MRM or DTD?
What is an impact on performance in case of big DTD ?
Thanks ahead for your help.
_________________
_________________
Best regards.
Yaakov Dolgov
E-Business Solutions Consultant
IBM Global Services, Israel
preiger.yaakov@il.ibm.com |
|
| Back to top |
|
 |
| kirani |
| Posted: Wed Feb 11, 2004 1:17 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
| yaakovd_new wrote: |
If exists any limitation on number of elements in MRM or DTD?
|
I don't think so.
| yaakovd_new wrote: |
What is an impact on performance in case of big DTD ?
|
Your cleint machine (where Control Center application runs) will perform slower. You need to increase the JVM heap size for the Control Center application so that you don't get "Out of Memory" error when working with this message set. Large message sets will take more space in the momory during execution time.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| yaakovd_new |
| Posted: Thu Feb 12, 2004 12:00 am Post subject: |
|
|
Apprentice
Joined: 03 Feb 2004
Posts: 25
Location: Israel
|
Thanks Kiran,
But, actually I asked about broker (RunTime) performance.
Input message will contain 5-10 fields, but MRM has big number of choices and optional elements.
_________________
_________________
Best regards.
Yaakov Dolgov
E-Business Solutions Consultant
IBM Global Services, Israel
preiger.yaakov@il.ibm.com |
|
| Back to top |
|
|
| kimbert |
| Posted: Thu Feb 12, 2004 1:52 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
I imagine it will perform a little slower than a fixed-format message, because of the large number of choices.
You do not need to use choices/optional elements for this. Just create global elements for all the different fields under DataMsg. Set the Type Content of DataMsg's compound type to 'Open Defined'. This will make your message model simpler, and it may even produce a small performance improvement. |
|
| 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
|
|
|
|
