|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
MQ integrator v2.1 using Neon transform node |
« View previous topic :: View next topic » |
Author |
Message
|
sebastian |
Posted: Wed Feb 11, 2004 12:33 pm Post subject: MQ integrator v2.1 using Neon transform node |
|
|
 Centurion
Joined: 12 Nov 2003 Posts: 110 Location: Philadelphia
|
Dear MQSeries.net:
I am relatively new to MQSI and hoped you might have some advice on a few issues.
Our company began using the v1.1 integration tool and is now in the process of upgrading to MQSI v2.1.
Many of the current message flows in our v2.1 use the Neon transform node. We use this primarily for SAP idoc formats.
I have some questions for MQ veterans out there. Is it possible to create a message flow using esql instead of the Neon transform nodes? Is there anything neon can do that esql can not? If a company was starting from v2.1, would they consider using the Neon components or would they use some external adapter? I have been told that the neon node is easier and more efficient than esql but have not done an A-B comparison myself yet.
I am getting the impression that IBM may not support the neon pieces in the long term. Since we have created most of our interfaces with neon, I am concerned about the coding effort to upgrade.
Any feedback is greatly appreciated,
Sebastian _________________ sebastian signature |
|
Back to top |
|
 |
Michael Dag |
Posted: Wed Feb 11, 2004 2:14 pm Post subject: Re: MQ integrator v2.1 using Neon transform node |
|
|
 Jedi Knight
Joined: 13 Jun 2002 Posts: 2607 Location: The Netherlands (Amsterdam)
|
Quote: |
Dear MQSeries.net:
I am relatively new to MQSI and hoped you might have some advice on a few issues. |
let me try...
Quote: |
Our company began using the v1.1 integration tool and is now in the process of upgrading to MQSI v2.1. |
good! isn't 1.1 long out of support or are you on z/OS?
Quote: |
Many of the current message flows in our v2.1 use the Neon transform node. We use this primarily for SAP idoc formats. |
they can be a real pain...
Quote: |
I have some questions for MQ veterans out there. |
well your company started with 1.1, I would qualify that as 'veteran'...
Quote: |
Is it possible to create a message flow using esql instead of the Neon transform nodes? |
Yes, that's what most of us do...
Quote: |
Is there anything neon can do that esql can not? |
with 2.0 there was, like tagged data, tagged data support was introduced with 2.1, but only really working after CSD3...
Quote: |
If a company was starting from v2.1, would they consider using the Neon components or would they use some external adapter? |
I would not start with neon, nor would I advice any customer to invest in it unless they have some good skill in that area around and plan on keeping them...
Quote: |
I have been told that the neon node is easier and more efficient than esql but have not done an A-B comparison myself yet. |
easier I would seriously contest! have you looked at the formatter screen, with let's say 5 to 10 IDOC formats loaded?
more efficient exactly the same, in esql you can use proper code versus klunky combinations of simple check for if this, if that in the neon formatter...
the only part that neon is good at is performance!, but comes at a big price in coding and 'maintainability... kinda like assembler versus sql
Quote: |
I am getting the impression that IBM may not support the neon pieces in the long term. |
in the end IBM might drop support, however due to the change in pricing (the rules&formatter is an optional component as of V5) and packaging (the option, rather then standard included) they may not drop it after all
Quote: |
Since we have created most of our interfaces with neon, I am concerned about the coding effort to upgrade. |
and you should be! converting from NEON to MRM/TDS and Esql is a major task and practically forces you to completly 'understand' all mappings and do a comple 'rewrite'!
There is however a 'migration' service from IBM Dublin as they have a number of programs around that can convert NEON Formats to MRM/TDS formats,
I don't know which companies used those services from IBM, nor do I know the experiences those companies had, nor do I know the cost...
So anyone gone through this migration using IBM Services, please let us know...
Quote: |
Any feedback is greatly appreciated,
Sebastian |
I hope this helped...
Michael |
|
Back to top |
|
 |
wmqiguy |
Posted: Thu Feb 12, 2004 10:28 am Post subject: |
|
|
 Centurion
Joined: 09 Oct 2002 Posts: 145 Location: Florida
|
Sebastian:
Here is my two cents, having been on both sides of the fence. (I have worked at both NEON and IBM). I have a sentimental side that really loves the NEON Formatter since I know the team that created it. It has a lot of flexibility and has some nice functionality for parsing some bizarre message layouts and was a requirement for many WMQI solutions in the past.
The TDS layer actually has that same type of functionality now, so the MRM is much more powerful and gives the developer options beyond NEON. So the question is (as Michael referenced), what are you comfortable with? This is more of a subjective question than an objective one so I can't give you a simple answer. These are the variables as I would see them:
1. What is the NEON/IBM relationshsip? (Not sure anyone knows, so toss a coin.)
2. What is your skillset and how stable is it? (Skilled MRM developers are more plentiful.)
3. Do you want to maintain the infrastructure necessary for NEON? Keeping everything in MRM/XML simplifies the topology and administration.
4. Are you using the NEON adapter for SAP? Pretty easy to create formats that way....
5. And like everything....money. What are the licensing requirements?
Having said all that, you probably have a bigger decision than can be addressed in this forum.
Good Luck!  |
|
Back to top |
|
 |
sebastian |
Posted: Fri Feb 13, 2004 4:42 am Post subject: |
|
|
 Centurion
Joined: 12 Nov 2003 Posts: 110 Location: Philadelphia
|
Michael:
I appreciate your response. Could you possibly send me an example of ESQL code that either parses or formats an SAP IDOC? I am mostly concerned about the parent and child relationships typical to IDOCS. I know that segments are often repeating or optional. It would be great to see an example of this since my only experience with parsing IDOCS is using the NEON method.
Any feedback is greatly appreciated,
Sebastian _________________ sebastian signature |
|
Back to top |
|
 |
MVO |
Posted: Thu Feb 19, 2004 12:00 pm Post subject: |
|
|
 Centurion
Joined: 09 Sep 2001 Posts: 131
|
Michael,
My shop is using NEON intensively to parse. I would be interested in getting the IBM programs that convert NEON to MRM. Could you help please ?
Thanks
NEONlover !!! |
|
Back to top |
|
 |
Michael Dag |
Posted: Thu Feb 19, 2004 12:41 pm Post subject: |
|
|
 Jedi Knight
Joined: 13 Jun 2002 Posts: 2607 Location: The Netherlands (Amsterdam)
|
MVO,
the programs are owned by IBM and they offer them as a paid service only. (I have no experience with them)
contact: dubadapt@ie.ibm.com to find out the details, let us know the results and experiences!
Michael |
|
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
|
|
|
|