I am trying to write a data handler for tcp request.
This tcp request(s) is generated by triggering a SOAP request in the front end.
The format of the tcp Requests is:
4ByteHeader(which specifies the length of data payload) followed by DataPayload
The way the 2 part Request comes in is:
1st part (Request): 4ByteHeader
2nd part (a new Request): Followed by the data payload.
In the vs that I have created, in the first tcp listen step which contains the header, I do nothing and trigger the tcp Respond step. This particular action generates an error response (in the original SOAP request which is the front end request that generates the entire tcp requests that I am trying to write a handler for). I also observe that, the subsequent tcp request that contains the data payload comes in next, and it is processed successfully with the proper response, but this response becomes completely mute in the original SOAP transacation, since it already generated the error response resulting from the handling of the first part 4byteheader tcp portion.
Any tips and/or help will be appreciated on how to process/handle the first tcp header part which can be totally ignored and move straight to processing the 2nd tcp data payload part.
Have you written a custom TCP Delimiter along with your DPH? The TCP Delimiter is what helps DevTest to identify the start/end of a payload. If you have a 4 byte header which should be ignored, you could create your delimiter to remove/ignore the first four bytes of the message. If you create a custom delimiter, it should appear in the list of TCP delimiters for you to choose from. I can send you a sample TCP Delimiter if you are not familiar with them.