| Author |
Message
|
| giorginus80 |
 Posted: Mon Nov 17, 2008 5:30 am Post subject: AggregateNode and simple variable in each Request |
 |
|
Centurion
Joined: 08 Jul 2008
Posts: 124
Location: Rome, Italy
|
Hi,
I'm using the aggregation. The aggregation works great, but I have problems, when I recollect the request. I just need to put in every request a variable, and then to recall it in the rebuild of message. I tried to put this variable in every message
| Code: |
| SET OutputRoot.XMLNSC.ns:credit.mykey = aKey; |
but I can't see the field mykey in the reaggregation because isn't defined in the MessageSet, and for some reason I can't define it in the mxsd so I need to put the mykey variable in other place. How Can I do It? |
|
| Back to top |
|
 |
| kimbert |
| Posted: Mon Nov 17, 2008 6:01 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
Hi,
Not sure what this means:
| Quote: |
| for some reason I can't define it in the mxsd so I need to put the mykey variable in other place. |
What is stopping you from defining it in the mxsd? Can you explain in more detail please. |
|
| Back to top |
|
|
| giorginus80 |
| Posted: Mon Nov 17, 2008 6:06 am Post subject: |
|
|
Centurion
Joined: 08 Jul 2008
Posts: 124
Location: Rome, Italy
|
| I can't modify the mxsd because is shared in the project, I tried to add a local element, but it crash the previous flow, that parse a flat fixed length file to an MRM. I think because it can't find the element in the flat file so it crashes. (sorry for me I'm not an expert of WMB) |
|
| Back to top |
|
|
| kimbert |
| Posted: Mon Nov 17, 2008 6:57 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
It sounds as if you need two message definitions in your message set:
1. The message definition which describes the flat file input
2. The message definition which you propagate to the rest of the flow. This one has an extra field.
I would be interested to know what the extra field 'mykey' is for. Is it a correlator for the request messages? |
|
| Back to top |
|
|
| giorginus80 |
| Posted: Mon Nov 17, 2008 7:30 am Post subject: |
|
|
Centurion
Joined: 08 Jul 2008
Posts: 124
Location: Rome, Italy
|
Thanks Kimbert, I build another message in the mxsd it was a good idea. I need that field because it's a Oracle DB Sequence and I need to keep it in my flow, but I can't put in the original message because the original message have to be the same of Flat Fixed length file!
Thanks |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Nov 17, 2008 7:45 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| giorginus80 wrote: |
Thanks Kimbert, I build another message in the mxsd it was a good idea. I need that field because it's a Oracle DB Sequence and I need to keep it in my flow, but I can't put in the original message because the original message have to be the same of Flat Fixed length file!
Thanks |
Bad design. If you need an Oracle Sequence for the insert this should happen in a stored procedure or something and not be held in the broker.
If you need it as primary key for retrieval, it should be part of the message. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
