Author |
Message
|
Rahul999 |
Posted: Thu Feb 11, 2010 7:38 pm Post subject: TCPIP nodes with Length Encoding |
|
|
 Centurion
Joined: 14 Mar 2007 Posts: 134
|
Hi All,
I need to send data to a TCPIP server socket, the requirement is to encode the length of the message and append it at the beginning of the message. I am using TCPIPClientOutputNode in Message Broker V6.1.
It was simple in case of Broker V6.0 as we had the support pack IA98, where in the node Advance properties you can specify "Tcpip length type", but there is no such option in V6.1 built in TCPIP nodes. Only option available for Records is "Record is unmodified Data", Record is Fixed Lenght Data" and "Record is delimited data", but there is no option to specify the "Encoding Size" and "Encoding Type"
Please suggest how to do it in Message Broker V6.1
Regards _________________ "For all your days be prepared, and meet them ever alike.
When you are the anvil, bear - when you are the hammer, strike."
- Edwin Markham |
|
Back to top |
|
 |
Rahul999 |
Posted: Fri Feb 12, 2010 12:46 am Post subject: |
|
|
 Centurion
Joined: 14 Mar 2007 Posts: 134
|
Hi All,
Can anyone please suggest anything, as I am unable to work out on any solution and it is very URGENT.
Thanks _________________ "For all your days be prepared, and meet them ever alike.
When you are the anvil, bear - when you are the hammer, strike."
- Edwin Markham |
|
Back to top |
|
 |
jareeve |
Posted: Fri Feb 12, 2010 2:22 am Post subject: length encoding on TCPIPClient |
|
|
Newbie
Joined: 15 Dec 2008 Posts: 2
|
Hi,
The built in TCPIP nodes rely on the MRM parser for any more complex record types than fixed size or delimited.
To do length encoded on the node you need to make a message set in the mrm that defines how the length encoding is done and used "unmodified" on the node.
I can send you a sample if it would help.
(For your interest: I wrote both the support pac and the built in function).
Regards, John. |
|
Back to top |
|
 |
Rahul999 |
Posted: Mon Feb 15, 2010 6:48 pm Post subject: |
|
|
 Centurion
Joined: 14 Mar 2007 Posts: 134
|
Hi John,
I have PMed you my email address, please send me the sample code.
Thanks _________________ "For all your days be prepared, and meet them ever alike.
When you are the anvil, bear - when you are the hammer, strike."
- Edwin Markham |
|
Back to top |
|
 |
vanshul |
Posted: Thu Feb 25, 2010 3:48 am Post subject: |
|
|
Novice
Joined: 06 Jun 2008 Posts: 13
|
You can create a MRM parser with CWF message.
Your CWF message will have the element as length encoded string instead of fixed string so that on Receive node you can set that stuff.
Mail me on vanshul.chawla@standardbank.co.za in case you need more information |
|
Back to top |
|
 |
goffinf |
Posted: Sun Mar 28, 2010 12:10 pm Post subject: Re: length encoding on TCPIPClient |
|
|
Chevalier
Joined: 05 Nov 2005 Posts: 401
|
jareeve wrote: |
Hi,
The built in TCPIP nodes rely on the MRM parser for any more complex record types than fixed size or delimited.
To do length encoded on the node you need to make a message set in the mrm that defines how the length encoding is done and used "unmodified" on the node.
I can send you a sample if it would help.
(For your interest: I wrote both the support pac and the built in function).
Regards, John. |
Hi John,
I too am facing some similar issue with regard to detecting the end of the input stream using the TCPIPServerInput node. I have tried using 'End of Stream' but this just hangs around until Broker times out. Whilst I can get an example using a custom or DOS/Unix delimeter to work, it appears that the *actual* client that is sending messages to my flow doesn't do either of these. I *believe* though that the message *does* include the length of the data stream in a set position at the start. The messages are primarily (but not exclusively) XML and naturally of all manner of shapes and sizes.
So .... perhaps I need to create a message-set that models the known and fixed part of the message stream as per your suggestion to the OP above. What do you think ??
... and if so, and if you have it handy, an example flow and message would be fabulous - (email: see PM)
Many thanks
Fraser.
Last edited by goffinf on Sun Mar 28, 2010 2:23 pm; edited 1 time in total |
|
Back to top |
|
 |
WMBDEV1 |
Posted: Sun Mar 28, 2010 1:41 pm Post subject: Re: length encoding on TCPIPClient |
|
|
Sentinel
Joined: 05 Mar 2009 Posts: 888 Location: UK
|
Hey Fraser, hows it going? Hope its going well, i'd be interesting in hearing about what you guys have been up to, whats worked well and what hasnt, but for now, just a quick none technical tip.... i'd recommend re-editing your post above to remove your email address to stop getting loads of spam mail. Its probably best to put it in a PM message to the intended recipient rather than on the public board
All the best. |
|
Back to top |
|
 |
goffinf |
Posted: Sun Mar 28, 2010 2:42 pm Post subject: |
|
|
Chevalier
Joined: 05 Nov 2005 Posts: 401
|
Thanks mate.
I hadn't noticed the PM and didn't know what it was for until now. Thanks for the tip.
Please feel free to contact me away from this list for a catch-up. Part of this post (as you may have realised) is related to the unit test framework for Broker that I was/am developing. In particular I am considering removing the AF specific parts to make it usable by anyone using Broker. |
|
Back to top |
|
 |
sangminli |
Posted: Tue Aug 31, 2010 3:56 pm Post subject: |
|
|
 Voyager
Joined: 26 Aug 2008 Posts: 75 Location: Hangzhou, China
|
Hi all, I have a related quesion here: i am using tcpip client node to receive tcp/ip packet from a monitoring system. and the msg starts with 68(hex)(first byte), and the second byte specifies the length of this packet. but how could decide the end of one packet when the tcpipinput node is receving hence it can decide it is going to receive another packet? |
|
Back to top |
|
 |
mqjeff |
Posted: Tue Aug 31, 2010 4:30 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
sangminli wrote: |
Hi all, I have a related quesion here: i am using tcpip client node to receive tcp/ip packet from a monitoring system. and the msg starts with 68(hex)(first byte), and the second byte specifies the length of this packet. but how could decide the end of one packet when the tcpipinput node is receving hence it can decide it is going to receive another packet? |
You decide this with a properly formatted message model.
If you want more help, open a new thread for your new issue, and point back to this one. |
|
Back to top |
|
 |
|