Message based asynchronous integration framework for in- and outbound messages

Overview

Through simple data management entities the framework handles message based asynchronous integration. A message consists of:

A unique identifier
A message type
Eventual message receiver, message sender and message queue, used for routing the message.

The message body as json, xml or csv.

Monitoring

From received to released, the message can be followed from a central workspace, offering overview of messages in each state and allowing the uses work with staging data. Access to data can be limited by specifying applicable user roles for each message type.

Integration flow

These are the states a message can go through:

Received. The message data has been received, through the data entity, but not otherwise processed yet.
Deserialized. The message body has be successfully deserialized in the related staging tables.
Deserialized failed. The message body could not the deserialized. Related error messages are recorded and available from the message.
Released. The message has been successfully released to the application, e.g. a sales order is created.
Released failed. The message body could not the deserialized. Related error messages are recorded and available from the message.
Cancelled manually. A user has cancelled the message.
Cancelled automatically. Business logic, for example from the release process, has cancelled the message.
Without. A user has put the message on without. Further attempts to process the message will not happen before the status is changed back from Withhold.

Staging data

Administrators can easily design what fields to show from staging tables, the order of fields, access policy and add custom translations for fields. All directly from the Staging table designer form.

Message processing

Messages are processed though a job where you decide which message to proces and which states to process. When running in batch, you can setup the messages to be processed in several parallel batch tasks for optimal performance.

Business events

Business events can be sent when the state of a message changes. This allows for external services to follow up on the state of messages sent to Dynamics, and to know about messages created in Dynamics for external consumption.

Extensibility

To add a new message type, all you need to add is:

A class to deserialize/serialize the message.
Staging tables.
A class to release to message.

SCALES Integration Hub

by SCALES A/S