Search: "support object"
Last modified by Erik Bakker on 2026/01/02 13:53
Refine your search
Select a category and activate filters on the current results
Last modification date
Configuration REST web service
Located in
- Raw document content
To ensure that the HTTP security in the new 3rd generation runtime works as before, you need to add a support object of the type "HTTP Security." In this "HTTP Security" support object, you only need to define "Disabled" in the Security drop-down.
Using eMagiz as producer
Located in
- Raw document content
Secondly, we need a support object that will establish the connection between the eMagiz flow and the eMagiz Event Streaming cluster, which hosts the topic.
…[[image:Main.Images.Microlearning.WebHome@intermediate-event-streaming-connectors-emagiz-as-producer--create-phase-dsh-template.png]] === 3.3 Configure the support object === In this section, we will discuss all configuration options for the necessary support object.
…Here, we need to link the template we just created as a support object to the outbound component and define the topic to which we want to produce it.
Using eMagiz as a consumer
Located in
- Raw document content
Secondly, we need a support object that will establish the connection between the eMagiz flow and the eMagiz Event Streaming cluster, which hosts the topic.
…[[image:Main.Images.Microlearning.WebHome@intermediate-event-streaming-connectors-emagiz-as-consumer--create-phase-kafka-listener.png]] === 3.3 Configure the support object === In this section, we will discuss all configuration options for the necessary support object.
…* ${emagiz.dsh.keystore.certificate} * ${emagiz.dsh.keystore.key} * ${emagiz.dsh.keystore.password} * ${emagiz.dsh.truststore.certificate} [[image:Main.Images.Microlearning.WebHome@intermediate-event-streaming-connectors-emagiz-as-consumer--create-phase-kafka-listener-basic-filled-in.png]] === 3.4 Configure the outbound component === Now that we have the support object configured, we can fill in the details for our Kafka message-driven channel adapter.
Defining a message format
Located in
- Raw document content
By selecting this option in Design you notify eMagiz that you want to process EDI messages and eMagiz will as a result add the relevant support objects to your flow. {{warning}}This functionality for EDI messages only works in the new runtime architecture.
Aggregation
Located in
- Raw document content
To manage this storage, you have the option to select a Message Store support object if you have created one before, or leave it empty, which will default to an in-memory store that may result in data loss upon runtime shutdowns or restarts.
…Therefore, you will need to set up these support objects as well if you have not done so already: * Infinispan cache manager * Infinispan message store Once you have done so, you can set the "Simple cache" option in your message store to "no" and then set the "Persistent" option to "yes". For more information on configuring these support objects and understanding their settings, please refer to this [[State Persistence>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.State Generation.intermediate-state-persistence||target="blank"]] microlearning. == 4.
Grouping - Configuration
Located in
- Raw document content
You can add this support object in the [[standard manner>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-create-support-objects-introduction||target="blank"]] by searching for "infinispan cache manager."
…You can add this support object in the [[standard manner>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-create-support-objects-introduction||target="blank"]] by searching for "lock registry."
…You can add this support object in the [[standard manner>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-create-support-objects-introduction||target="blank"]] by searching for "leader."
Duplicate Detection
Located in
- Raw document content
. === 3.1 Detecting Duplicates === First of all, you can start with setting up the component that is responsible for detecting duplicating messages and then either mark these messages as duplicates or discard them. eMagiz provides a support object that can do this, namely, the Duplicate Detector that you can add into your flow via the [[standard manner>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-create-support-objects-introduction||target="blank"]] by searching for "Duplicate detector".
…Afterwards, you can either select a metadata store support object you have created if you require state persistence, or leave it empty, which will default to an in-memory store that may result in data loss during runtime shutdowns or restarts.
…To do this, go to the Advanced tab of the Duplicate Detector support object, where you will find the Discard Channel configuration.
Change Detection
Located in
- Raw document content
For such a purpose, eMagiz provides two support objects to set up this storage mechanism and one flow component to store the states into it: * Infinispan cache manager * Infinispan metadata store * Metadata outbound channel adapter Please refer to this [[State Persistence>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.State Generation.intermediate-state-persistence||target="blank"]] microlearning to learn on how to configure these support objects and flow component. === 3.2 Stateful Configuration to Detect Changes === Once you have configured the storage mechanism, now you can start with setting up the component to retrieve the past states to detect changes in incoming messages by comparing them to past states.
Enrichment
Located in
- Raw document content
For such a purpose, eMagiz provides two support objects to set up this storage mechanism and one flow component to store the states into it: * Infinispan cache manager * Infinispan metadata store * Metadata outbound channel adapter Please refer to this [[State Persistence>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.State Generation.intermediate-state-persistence||target="blank"]] microlearning to learn on how to configure these support objects and flow component. === 3.2 Stateful Component for Data Enrichment === Once you have configured the storage mechanism, now you can start with setting up the component to retrieve the stored state data for the enrichment operation.
…{{info}} Note that these persisted states can only be retrieved by eMagiz flows running in the same runtime where the support objects are deployed. Thus, we suggest placing these support objects in the infra flow so the stored state data can be retrieved by other flows.
State Persistence
Located in
- Raw document content
You can add this support object in the [[standard manner>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-create-support-objects-introduction||target="blank"]] by searching for "infinispan cache manager".
…You can add this support object in the [[standard manner>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-create-support-objects-introduction||target="blank"]] by searching for "infinispan metadata store". This support object acts as the storage that stores your state data in the form of {"key":"value"} pairs.