| Author |
Message
|
| chris boehnke |
 Posted: Sat May 12, 2007 1:27 pm Post subject: Do we need to create 2 msgsets for XML and Cobol Copybook |
 |
|
Partisan
Joined: 25 Jul 2006
Posts: 369
|
Hi,
We are getting messages from the source in XML as well as Cobol Copybook(mainframe app) to the same message flow.
In the message flow we need to convert the incoming XML format to another XML format by using XSLT
and
Mainframe message(Cobol copybook) to XML format.
Do we need to create two message set projects and add these to the flow in the bar file and deploy on to the broker? or else do you recommend any other solution?.
I heard somewhere that we can use the same message set but we need to create 2 message definition files(1 for XML and 1 for Cobol Copybook)?. Is it going to work out?. If so what precautions we need to take to avoid the collision between XML and Cobol Copybook messages?.
Thanks.
Chris |
|
| Back to top |
|
 |
| jbanoop |
| Posted: Sat May 12, 2007 5:35 pm Post subject: |
|
|
Chevalier
Joined: 17 Sep 2005
Posts: 401
Location: SC
|
I believe that if it is the same message structure you are receiving in both the XML as well as the copybook, then it is ok to have one messageset modelled with two physical wire format(s).
the decision on which one to use to parse the incoming message should be made from within the flow.
Hope it helps
Regards,
Anoop |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Sat May 12, 2007 7:19 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Really, you can have more than one logical message structure defined in the same message set.
So what it comes down to is - how many of the data elements are really the same between the two messages, even if the order is different. If you're having to do a lot of transformation or augmentation of the input message to create the output message, then probably two different message sets.
Otherwise, one might be fine.
On the other hand, you should consider if one will be changing more often than the other - if so, separate the message sets so you don't have to redeploy the unchanged one all the time.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| chris boehnke |
| Posted: Sun May 13, 2007 6:08 pm Post subject: How to connect the 2 message definition files in a msgset |
|
|
Partisan
Joined: 25 Jul 2006
Posts: 369
|
Hi,
If we create a single msgset for Cobol copybook and a XML incoming messages and creating two message definition files(Cobol copybook and XML Schema files), do we need to connect these 2 message definition files somehow in the messageset?. If so how do we need to connect them with one another?.
Thanks.
Chris |
|
| Back to top |
|
|
| jbanoop |
| Posted: Sun May 13, 2007 7:11 pm Post subject: |
|
|
Chevalier
Joined: 17 Sep 2005
Posts: 401
Location: SC
|
as i understand it .. u will have only 1 mxsd.. basically what we are trying to say by adding two wireformats to the same messageset is indicating that the structure of the message expected will remain the same but that it can come in either of the two formats .. XML or Copybook..
All the message set does is define how MB should try to parse the message .. so it will contain ony the structure of the message expected which in both cases remain the same.
So in case you are creating a message set as mentioned above, you would need to do only either of modelling it based on the xsd or importing the cobol copybook.
Once this is done .. go and add another physical format to the created message set (CWF or XML respectively)..
Hope this helps
Anoop |
|
| Back to top |
|
|
|
|
