Have you tried to understand the message flows to diagnose a problem with a particular message? Usually, when you have a complex BizTalk application, the message passes through multiple artifacts creating different patterns. Messages that contain repetitive patterns can cause excessive memory use, causing the database to fill quickly. How do you handle such situations?
With BizTalk360, you can automatically identify all the messaging patterns existing in your BizTalk environment and record only the unique patterns. With the Messaging Patterns feature, you can trace the path of the message and understand how the artifacts are related to each other.

How is it different from Graphical Message Flow?

BizTalk360 Graphical Message Flow simply constructs the visualization of the message flow, while the messaging patterns records only the unique message patterns. View the transaction volume at each point in the flow (receive ports, orchestrations, and send ports).

biztalk360 features
biztalk360 product features

Viewing the Message Properties

With messaging patterns, you can get to know how many messages passed through a particular port, and the average time of execution for each message across a time period. To make things easier, we provide this information in a nice graph view. With the graph, you have the option of zoom and pan to get a detailed view of the plotted data.

Informative Legends

Legends makes the graph meaningful! The legends below the graph show the different ports in the system. We’ve kept user friendliness in mind! Simply click the legend to display/hide the information in the graph.

biztalk360 software features
features in biztalk360

Search & Rename Data Flows

The search tool is a great way to find exactly what you are looking for. Be it the pattern name, or the custom name of the message flow, you can easily search for the data flow of your choice.
Did we say, “Custom name of your message flow”? Yes, you read it right. You have the option of renaming your message flow id according at your convenience. After all, “SAP invoicing” name sounds better than “1e5d6b86-df10-4f22-91e7-9d6e289fcfc4”, doesn’t it?