| Author |
Message
|
| drajib |
 Posted: Tue Aug 19, 2003 7:25 am Post subject: NEONMESSAGESET Problem |
 |
|
Apprentice
Joined: 25 Mar 2003
Posts: 42
Location: India
|
Hi!
Working with a NNSY message definition (output structure) obtained from a third party. It has a number of segments. Output, when it reaches the queue, is getting truncated before a particular Optional & Repeating segment. Though traces before the output node & even after the out terminal, show that all the segments are properly populated.
No Exceptions are thrown and in the absence of a trace, We're at a loss!
Waiting for your esteemed views.
Regards,
rajib. |
|
| Back to top |
|
 |
| EddieA |
| Posted: Tue Aug 19, 2003 11:48 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
Do you have the following set correctly for the repeating fields:
NNSY-XML-repeating="true"
Without it, repeats do not.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| drajib |
| Posted: Tue Aug 19, 2003 11:00 pm Post subject: |
|
|
Apprentice
Joined: 25 Mar 2003
Posts: 42
Location: India
|
Thanks Eddie for your prompt reply. However that's there and not the cause.
Any other suggestions!
Regards. |
|
| Back to top |
|
|
| eaisp |
| Posted: Wed Aug 20, 2003 9:09 pm Post subject: NEON problem |
|
|
Newbie
Joined: 18 Aug 2003
Posts: 3
|
Hi,
I am working in WebSphere MQSeries Integrator v 2.1. In that I am using NEON parser for parse swift message. I tested in the Neon visual tester its working fine.
In my message flow I am using NEON Formatter node, because I didn't use NEON Rules. So in that I gave Target format name and domain name. In my MQInput node I gave my Input format & domain name. After deployment it is not working. What was the reason I couldn't get that.
Pls give some input for this problem, how can I solve this.
Regards
EAISP |
|
| Back to top |
|
|
| drajib |
| Posted: Mon Aug 25, 2003 3:47 am Post subject: |
|
|
Apprentice
Joined: 25 Mar 2003
Posts: 42
Location: India
|
In between I was involved in some other ventures and could not get back!
Eddie you happened to be correct.
We had something like this -:
| Code: |
MyMsg
- Segment1
- Segment2 {Repeating)
- Segment3
- Segment4
- Segment5
- Segment6 {Repeating)
- Segment7 |
The output used to have fields till start of Segment6 for which we had NNSY-XML-repeating="true". However the same was not mentioned for Segment2 as it was known that there would always be a single occurence of it. It was referered by Index, as - Segment2[1]. It turned out that, NNSY-XML-repeating="true" also has to be mentioned for Segment2.
The result now is coming out as expected, though I'm still a bit confused as to why beforehand the generated output included segments upto Segment6?
Best regards, |
|
| Back to top |
|
|
| EddieA |
| Posted: Mon Aug 25, 2003 4:19 pm Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
Without digging a lot deeper, I can't really answer why it worked before, but not now. A CSD update, perhaps.
But glad to see that it now does work.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
|
|
