In some data integration scenarios, it can be common for us to receive multiple inbound messages from different business partners or from different application systems. When that happens, these messages may have the same meaning, but follow different formats, depending on the external systems, their data content, and different preferences. The Normalizer data integration pattern is used to process messages that are semantically equivalent but can arrive in different formats.
The Normalizer pattern will utilize a Message Router to route the incoming message to the appropriate Message Translator. This implementation will require that the Message Router be able to detect the type of the inbound message. Many messaging applications will equip each message with a type indicator field in the Message Header to simplify this task.