| Author |
Message
|
| foxman |
 Posted: Sun Oct 05, 2008 12:16 pm Post subject: Splitting a BLOB stream with variable length records |
 |
|
Newbie
Joined: 04 Oct 2008
Posts: 3
|
| I have a message flow that inputs a large data stream that contains multiple variable length records via a tcpipclientreceive node. I created an MRM message definition that defines each record. I've verified that the MRM is correct, however, the output from the tcpip node is only one record after the connection closes. I was hoping that it would create multiple records as the data arrived at the node. Any suggests on how I might be able to do that. I modified the MRM to declare the group as repeating, but that creates a large message that contains multiple parsed records, and is sent to the output terminal only after the connection is closed. |
|
| Back to top |
|
 |
| kimbert |
| Posted: Mon Oct 06, 2008 12:51 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
|
| Back to top |
|
|
| foxman |
| Posted: Mon Oct 06, 2008 7:51 am Post subject: Splitting a BLOB stream with variable length records |
|
|
Newbie
Joined: 04 Oct 2008
Posts: 3
|
| I did read the InfoCenter, and according to the information about the TCPIPClientReceive node if I specify a Record detection option of Parsed Record Sequence the node will propagate each recognized record as a separate message. The problem is that it only propagates one record. Is there some other option I need to set? |
|
| Back to top |
|
|
| kimbert |
| Posted: Mon Oct 06, 2008 10:49 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
OK - you didn't say that you were using Parsed Record Sequence. That's definitely the correct approach.
Can you give a little more info about your message. Which format ( CWF / TDS / XML )? What setting did you choose for 'Parsed Record Sequence'? |
|
| Back to top |
|
|
| foxman |
| Posted: Mon Oct 06, 2008 4:00 pm Post subject: Splitting a BLOB stream with variable length records |
|
|
Newbie
Joined: 04 Oct 2008
Posts: 3
|
The format was CWF. I created from the message definition from scratch. It basically looks like the following:
Action_Msg
timestamp string[16]
data_type int
sequence_number int
compressed_size int
decompressed_size int
compressed_data hexBinary (size is reference length)
I didn't set any other values on the Records and Elements properties for the Input Node. |
|
| Back to top |
|
|
|
|
