Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

In several enterprise integration scenarios, a single message event will trigger a sequence of processing steps, with each one performing a specific process or action. For example, assume a new customer order arrives in our enterprise in the form of a message. To process this message, we may need to implement several requirements:

  • All messages will be encrypted

  • Ensure that orders are placed only by trusted customers, each message will contain authentication information in the form of a digital certificate

  • Eliminate duplicate messages before subsequent order processing steps are initiated.

To meet these requirements, we need to transform a stream of possibly duplicated, encrypted messages containing extra authentication data into a stream of unique, simple plain-text order messages without the extraneous data fields.

  • No labels