| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQSI OR WMQI PARSER QUESTION |
« View previous topic :: View next topic » |
| Author |
Message
|
| itechnologist |
 Posted: Mon Oct 06, 2003 10:22 pm Post subject: MQSI OR WMQI PARSER QUESTION |
 |
|
Novice
Joined: 06 Oct 2003
Posts: 10
|
hi:
does mqsi v2.x series or wmqi 2.x series have ansi x12 hipaa parser.
if so what is the name of parser that i should set in the node.
Lets say for instance, i dont want to parse the entire message tree inot child nodes. i only want to pass the x12 message straight through into the C++ plug in node that i developed as a text stream and invoke my own limited C++ X12 HIPAA parser code within the node to extract few key information from message text stream. Is this possible? How would i do it?
If i set the parser to NULL in my own C++ plug in node property, can i input the message as a text stream into the node? Or if the parser is not set to one of the standard values like XML, MRM< NEON the message will be input as BLOB and the contents of the message will be opaque inside the node?
can someone throw some light on how to pass messge inside the node as text stream without parsing it into child nodes as straight through message.
thanks |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Tue Oct 07, 2003 5:21 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
My understanding of writing custom nodes is this.
If you are writing an input node, then you are responsible for creating a bitstream from some kind of datasource, and presenting that bitstream to the system for parsing.
If you are writing a plug-in node, you are responsible for working with the message tree, through the various methods for accessing Elements.
If you are writing a parser, you are responsible for taking individual pieces of a bitstream, which is presented to you through the parser API, and creating elements that get put into the message tree.
If you do not assign a parser to the primitive MQInput node AND the input message does not have an MQRFH2 header that specifies a valid WMQI parser, then the parser that is assigned will be the BLOB parser - which makes the raw bitstream available as a BLOB field at Root.BLOB.BLOB. This raw bitstream is then available through both ESQL and the various methods in the plug-in API at that point in the message tree.
So an example - you could write a plug-node that would read the bitstream from InputRoot.BLOB.BLOB and extra the specific fields you are interested in, and populate fields in Environment that you could then query outside your plug-in to make routing and transformation decisions.
Or you could create a custom parser that would work with the raw bitstream and create new elements in Root.<YourParserName> and then use other ESQL to access those fields.
Or you could use MRM to model your message data to the level of detail you're interested in, rather than creating any custom plug-ins or parsers.
I believe there is an IBM solution for working with HIPAA transactions. But I don't think it's free with WMQI.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| itechnologist |
| Posted: Tue Oct 07, 2003 12:32 pm Post subject: Which is the best option |
|
|
Novice
Joined: 06 Oct 2003
Posts: 10
|
hi:
i have ansi x12 hipaa record. use mqsi 2.1
have to extract few fields from the record.
dont need to parse the entire record and
create message tree from root to child to
siblings all way down. not required and
performance overhead.
i am not sure if ibm has parser for this ansi x12
hipaa.
which is the best way to do this?
use MRM , custom node, custom parser or ibm primitives?
which is the best way to do this?
thanks |
|
| 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
|
|
|
|
