| Author |
Message
|
| Yang Yu |
 Posted: Mon Mar 15, 2004 12:41 pm Post subject: Does standard WBIMB V5.0 support NEON message format? |
 |
|
Novice
Joined: 04 Nov 2002
Posts: 12
|
Currently, our environment is WMQI 2.1 and we have many message flows which start with a NEON formatted IDOC message from our Sybase SAP R/3 Adapter. These use a NEON format in a NEON domain to parse the IDOC message. We do not use any NEON nodes. We will migrate our envirnoment to WBIMB V5.0 soon. We would like to find out whether standard WBI Message Broker 5.0 supports NEON message format, or we need to migrate to WBI Message Broker with Rules & Formatter Extension.
Any help on this would be appreciated! |
|
| Back to top |
|
 |
| Michael Dag |
| Posted: Mon Mar 15, 2004 1:39 pm Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
I don't get it (please explain further if I misunderstood...),
the Sybase (formerly NEON) SAP R/3 adapter produces a NEON formatter export file,
which you then need to import into your NEON formatter database, then using a NEON node you can use it in WMQI 2.1
You say you don't use a NEON node, what does your flow look like and what nodes ARE you using to interpret the NEON domain IDOC?
_________________
Michael
MQSystems Facebook page |
|
| Back to top |
|
|
| vmcgloin |
| Posted: Tue Mar 16, 2004 1:23 am Post subject: |
|
|
Knight
Joined: 04 Apr 2002
Posts: 560
Location: Scotland
|
| I believe that you will need the V5 product with Rules & Formatter Extension to be able to parse the NEON message even if you do it in a compue node instead of a NEON/NNSY node. I would not expect the non-R&F product to contain either the NEON parsers or the nodes or rules engine etc. |
|
| Back to top |
|
|
| Yang Yu |
| Posted: Tue Mar 16, 2004 2:09 pm Post subject: |
|
|
Novice
Joined: 04 Nov 2002
Posts: 12
|
Michael,
Thank you for your reply. Within WMQI 2.1 we use the message domain 'NEONMSG' which parses the IDOC messages and gives us a tree similar to an XML message. We usually set this domain on the MQInput node attributes and the compute node will get the Parsed NEONMSG tree.
Internally WMQI 2.1 reads the IDOC format stored in the NEON database and takes the Message from the queue and parses it to a tree using the format. |
|
| Back to top |
|
|
| Yang Yu |
| Posted: Tue Mar 16, 2004 2:19 pm Post subject: |
|
|
Novice
Joined: 04 Nov 2002
Posts: 12
|
vmcgloin,
Appreciate your help!!! |
|
| Back to top |
|
|
| Michael Dag |
| Posted: Wed Mar 17, 2004 8:12 am Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
Yang,
thanks for further explaining the way you work.
Basically by setting the domain on the Input Node to NEONMSG you are telling WMQI to parse the message according to the description in the NEON Formatter database.
The same effect can be achieved by using an Input node without NEONMSG, and then later when you have determined the incoming message is a NEON message, use the NEONFormatter node to interpret the message.
So you are using the NEON parts (underneath) without having a NEON node in your flow...
When you upgrade to WBIMB V5 and don't want to make changes you need to buy the NEON R&F Extensions.
I hope this helps you explaining the additional need for R&F Extensions.
_________________
Michael
MQSystems Facebook page |
|
| Back to top |
|
|
|
|
