In the testing scenarios, we are dealing with multiple systems. One frustration for me is, I need to simulate those systems but (to my knowledge) only way to generate the ACK is to use the accelerator pipeline with parties.To use the standard accelerator pipeline component is not an easy thing, the schemas have to be developed, deployed, parties need to be configured, lots of headache.

I then come up with the idea of developing this passthrough yet able to generate the ACK pipeline component. The concept is to develop a custom disassembler component, return the original message as well as reading and replacing a ACK message from a template. Below are some notes with this component:

1. I removed most of the properties of the incoming message since I do not want it to be route back to the request port
2. I created the MSA message on the fly using a template file (could be more fancy using configurable properties) I then stamp this message with bunch of necessary properties for supporting bi-directional routing
1. EpmRRCorrelationToken
2. RouteDirectToTP
3. CorrelationToken
4. ReqRespTransmitPipelineID
5. ReceivePipelineResponseConfig
3. En-queue the above messages and return one by one in the GetNext method

After configure it in a request-response receive location as a receive pipeline component, got the behavior to pass through the incoming request yet able to generate acknowledgement. This will ease my testing, hopefully..