| Author |
Message
|
| Lucky |
 Posted: Fri Jul 31, 2009 4:02 am Post subject: TCPIPServerInput node properties - Dymanic delimeter value |
 |
|
Apprentice
Joined: 06 Feb 2007
Posts: 35
|
Hi,
We have a message flow using TCPIPServerInput node. One type of delimeter was coming in message from clinet and we had set the Record detection property of node as "delimited" and given its hex value.
Now we have a requirement that we get 2 msgs -One handshake & 2. Application msg with different delimeters in End of Msg.
We use fixed length msg and length of Handshake & application msg differs.
Is there a way to configure TCPIPServerInput node to get message with diff delimeters.Please help!!! |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Fri Jul 31, 2009 4:21 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
As the TCPipServer node is the start of the flow, AFAIK, then the only way to solve your problem without trying to do the impossible and make the flow second guess the type of data that is arriving is to:-
Use TWO TCPipServer Input Nodes listeneing on different ports. These can have the different termination characters configured.
Is there any reason why one of the sources can't be changed to use a different Termination String?
Using one termination string in an enterprise is IMHO a good idea.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| Lucky |
| Posted: Mon Aug 03, 2009 1:34 am Post subject: |
|
|
Apprentice
Joined: 06 Feb 2007
Posts: 35
|
We get both the msgs from same port. So, there was no chance left to use 2 ServerInput nodes.
Client is not ready to send same Termination String for both of these messages that leading to this post. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Mon Aug 03, 2009 3:09 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Hmmmm I think you are going to be out of luck here if you really, really have to use the same port.
As I said in my previous reply, you are wanting the InputNode to sort of second guess where the data is coming from and look for the right set of termination characters. I don't think this is possible but there again, I might be wrong.
The definitive answer would be to raise a PMR with IBM on the subject. if you do then please post the answer here.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| kimbert |
| Posted: Mon Aug 03, 2009 3:11 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
You could try this:
- set 'Record Detection' to 'Parsed Record Sequence'
- create a message set with a TDS physical format
- use the MRM parser to split up the input bit stream for you |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Aug 03, 2009 4:14 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| kimbert wrote: |
You could try this:
- set 'Record Detection' to 'Parsed Record Sequence'
- create a message set with a TDS physical format
- use the MRM parser to split up the input bit stream for you |
With a Tagged-Delimited choice that TDS will be able to resolve for you.
Provided the two messages start with something that can be used as a tag. |
|
| Back to top |
|
|
|
|
