Search: "messaging"

Messaging Asynchronous

Messaging Asynchronous == Asynchronous messaging is the pre-dominant option when you implement a messaging integration via eMagiz.

Key takeaways == * Asynchronous messaging is the pre-dominant option when you implement a messaging integration via eMagiz. * Key characteristics of asynchronous messaging are: ** Non-blocking.

Suggested Additional Readings == If you are interested in this topic and want more information on it please see the following links: * [[Intermediate Level (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.WebHome||target="blank"]] ** [[Key concepts eMagiz Messaging (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Key concepts eMagiz Messaging.WebHome||target="blank"]] *** [[Messaging Synchronous (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Key concepts eMagiz Messaging.intermediate-key-concepts-emagiz-messaging-messaging-synchronous.WebHome||target="blank"]] * [[Asynchronous Messaging (Search Results)>>url:https://docs.emagiz.com/bin/view/Main/Search?

crashcourse-messaging-messaging-asynchronous

Crash Course Messaging

Messaging - Introduction

crashcourse-messaging-introduction-pic1.png

crashcourse-messaging-introduction-pic2.png

Some of the required data might be outside the organization. The messaging integration pattern allows processing messages that contain data in a secure, reliable manner.

[[image:Main.Images.Microlearning.WebHome@crashcourse-messaging-introduction-pic1.png]] === 3.2 Support formats and protocols === The Messaging pattern of eMagiz can handle the most common formats and protocols.

[[image:Main.Images.Microlearning.WebHome@crashcourse-messaging-introduction-pic2.png]] == 4. Key takeaways == * eMagiz provides robust Messaging integration patterns designed to tackle complex integration challenges, accommodating diverse formats and protocols

crashcourse-messaging-introduction

Crash Course Messaging

eMagiz Messaging

Introducing Messaging == eMagiz Messaging is the pattern in which you can connect various parties via various connectivity mechanisms to the eMagiz messaging engine.

[[image:Main.Images.Fundamental.WebHome@fundamental-messaging-introduction--logical-view-landscape.png]] Any messaging integration in eMagiz consists of five layers.

Key takeaways == * Messaging uses five layers to transport data between systems * The CDM is a crucial component within messaging * To transport the messages, we use the queueing mechanism * Errors from the messaging flows show up in the manage dashboard * Messaging runtimes should be deployed as close to the system as possible == 5.

fundamental-messaging-introduction

crashcourse-messaging-filter--cdm-structure.png

crashcourse-messaging-filter--filter-options.png

crashcourse-messaging-filter--xpath-filter.png

crashcourse-messaging-filter

Crash Course Messaging

[[image:Main.Images.Microlearning.WebHome@crashcourse-messaging-filter--standard-filter-filled-in-example.png]] Or you use a Groovy script.

If the result is true the message may continue. If not it will be dropped. === 3.2 XPath Filter === The XPath filter can only be used to filter XML messages.

With the help of this filter, you can filter messages based on the evaluation of an XPath expression [[image:Main.Images.Microlearning.WebHome@crashcourse-messaging-filter--xpath-filter.png]] In this example, we want to validate that at least one Project is available in our CDM message [[image:Main.Images.Microlearning.WebHome@crashcourse-messaging-filter--cdm-structure.png]] To do so we need to fill in the correct XPath and place the component at the correct place within the flow.

Messaging Synchronous

Key concepts eMagiz Messaging

intermediate-key-concepts-emagiz-messaging-messaging-synchronous

{{/info}} == 3. Messaging Synchronous == Synchronous messaging is the less used, the less advised option when implementing a messaging integration via eMagiz.

The subsequent process (the onramp) will process the message and will put the message on the next queue (the synchronous routing). That process will route each message to the correct offramp. This process continues until the message eMagiz delivers to the external system.

Splitting messages

Key concepts == This microlearning focuses on splitting messages. With splitting messages we mean: Cutting up the input messages in multiple output messages with the same format == 3.

[[image:Main.Images.Microlearning.WebHome@crashcourse-platform-create-splitting-messages--splitter-system-message.png]] To do so we need to place an XPath splitter before validating the system message.

Determining the correct XPath to split my message to end up with a valid system message. To be able to determine the correct XPath we need to know: * The structure of the input message * Whether the input messages has a namespace * Always start at the root of the input message when writing an XPath outside of the transformation Let us first determine what the structure of the input message is.

Message redelivery

As the flow is already available in Create you don't want to loose your progress when you want to activate message redelivery. In those instances several manual steps are needed to configure the flow(s) correctly in Create to make the message redelivery functionality work for you.

As the flow is already available in Create you don't want to loose your progress when you want to activate message redelivery. In those instances several manual steps are needed to configure the flow(s) correctly in Create to make the message redelivery functionality work for you.

This will ensure that once the message is succesfully delivered to the eMagiz error process the message will be placed on the queue designed to handle failed messages within the message redelivery functionality.

Example Message

JSON === Below, the information for the example message, needed for the exercise, is provided. {{code language="json"}}{ "Type": "ALG", "Description": "Test Order API Gateway Training", "Value": 500, "OrderLine": [ { "Description": "Test Order API Gateway Training OrderLine", "Value": 300 }, { "Description": "Test Order API Gateway Training OrderLine", "Value": 200 } ] }{{/code}} )))((({{toc/}}))){{/container}}{{/container}}

Transforming messages

{{container}}{{container layoutStyle="columns"}}((( This exercise will guide you in practising with transforming a message with an API. Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]]. == 1.

crashcourse-messaging-asynchronous-routing--filter-configuration.png

crashcourse-messaging-asynchronous-routing--filter-construction.png

crashcourse-messaging-asynchronous-routing--new-value-mapping.png

crashcourse-messaging-asynchronous-routing

Crash Course Messaging

{{container}}{{container layoutStyle="columns"}}((( In this microlearning, we will dive into the essentials of asynchronous routing and its importance in managing message distribution within the five-layer messaging model.

Simply open the router component and select the button New Mapping [[image:Main.Images.Microlearning.WebHome@crashcourse-messaging-asynchronous-routing--new-value-mapping.png]] In here you fill in the correct unique combination of a target system and the message type and select the channel you want to route the message to.

When the value of the property is true the message can pass. If the value of the property is any other value the message will be halted.