| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Defining message sets |
« View previous topic :: View next topic » |
| Author |
Message
|
| slimshady |
 Posted: Mon Aug 22, 2005 10:50 pm Post subject: Defining message sets |
 |
|
Newbie
Joined: 21 Aug 2005
Posts: 4
|
Hello all
It takes a lot of effort to define a simple message set using WBIMB tool kit. Is there a way to write utility programs to create message sets.. I mean any API available which can be used to create message sets.
Any ideas? |
|
| Back to top |
|
 |
| kimbert |
| Posted: Tue Aug 23, 2005 2:55 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
The short answer is 'no', although you're not the first person to ask for this. One reason is that the message model has a very simple core set of facilities (which is probably all you need) but some quite complex additional features. Any API would have to deal with most of the complex features.
The other reason is that there is a pretty good set of importers available, and most people find that they can write a COBOL copybook or an XML Schema and then import it ( although physical properties will still need to be set manually ) |
|
| Back to top |
|
|
| elvis_gn |
| Posted: Tue Aug 23, 2005 4:11 am Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
The closest you can perhaps get is if you have a sample message and have some software like Altova XMLSpy....
In this case u can use the message to create a DTD or XML Schema and then Import as kimbert specified. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Aug 23, 2005 4:15 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
In my opinion, the message modelling tool is actually the least friendly and most complicated piece of the broker Toolkit now.
As Kimbert says, the imports do not set physical properties, like field length, even in some cases where the length is known in the import file (Import a copybook into a TDS message set, for example).
And then tooling gives you no good way to go through and quickly set all field lengths. You have to go to each field, and set it's length.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| martinrydman |
| Posted: Wed Aug 24, 2005 11:47 am Post subject: |
|
|
Centurion
Joined: 30 Jan 2004
Posts: 139
Location: Gothenburg, Sweden
|
This is just a pointer. Often, I find myself defining long simple flatfile structures with tedious names and properties like data type and field length. I've developed a simple tool (in Excel/VBA) that generates the local elements in the actual XML format of the mxsd file. I then model the compound types, add a placeholder element, open the mxsd file in some texteditor, paste the autogenerated xml-snippet, save and refresh the project. Works like a charm.
The basis for this is often some kind of documentation where names, types and lengths of the fileds are electronically available. It is mostly a trivial task to cut and paste into an excel-sheet and edit to fit my macro.
It's a hack, but it saves me lots of time
/Martin |
|
| 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
|
|
|
|
