2017-10-04 17:20:29 +02:00
|
|
|
---
|
|
|
|
|
layout: pattern
|
|
|
|
|
title: EIP Wire Tap
|
|
|
|
|
folder: eip-wire-tap
|
|
|
|
|
permalink: /patterns/eip-wire-tap/
|
2017-12-25 11:30:24 +02:00
|
|
|
categories: Integration
|
2017-10-04 17:20:29 +02:00
|
|
|
tags:
|
2019-12-13 21:09:28 +02:00
|
|
|
- Enterprise Integration Pattern
|
2017-10-04 17:20:29 +02:00
|
|
|
---
|
|
|
|
|
|
|
|
|
|
## Intent
|
|
|
|
|
In most integration cases there is a need to monitor the messages flowing through the system. It is usually achieved
|
|
|
|
|
by intercepting the message and redirecting it to a different location like console, filesystem or the database.
|
|
|
|
|
It is important that such functionality should not modify the original message and influence the processing path.
|
|
|
|
|
|
2019-12-07 20:01:13 +02:00
|
|
|
## Diagram
|
2017-10-04 17:20:29 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
## Applicability
|
|
|
|
|
Use the Wire Tap pattern when
|
|
|
|
|
|
|
|
|
|
* You need to monitor messages flowing through the system
|
|
|
|
|
* You need to redirect the same, unchanged message to two different endpoints/paths
|
|
|
|
|
|
|
|
|
|
## Credits
|
|
|
|
|
|
|
|
|
|
* [Gregor Hohpe, Bobby Woolf - Enterprise Integration Patterns](http://www.enterpriseintegrationpatterns.com/patterns/messaging/WireTap.html)
|
|
|
|
|
* [Apache Camel - Documentation](http://camel.apache.org/wire-tap.html)
|
