Search: "support object"

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.

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.

You can define this by dragging a format file name generator (support object) to the canvas. [[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-archiving--file-name-generator.png]] After we have done this please add a file outbound channel adapter to the flow including an input channel.

We start with a composite file filter (support object). Within this filter, we at least define how old a file must be before it can be deleted (in milliseconds).

After you have done so, we first add the support object to our flow. In this case, we will use the Default SFTP caching session factory.

Now that we have configured the support object adding the SFTP outbound channel adapter to the flow has become time.

Furthermore, we need to link the support object we have just created and decide whether to auto-create the directory.

To send a mail, we need at least the support object called "Java mail sender" and the outbound channel adapter called "Mail outbound channel adapter" from the list below.

[[image:Main.Images.Microlearning.WebHome@advanced-mail-connectivity-using-mime-transform-xml-to-mime.png]] Note that before you can correctly configure your "XML to MIME transformer," you first need to define your "Java mail sender" support object. In here, you need to fill in, at the minimum, a reference to the host and the port of the mail server to whom you want to connect.

**Example** Flows containing a Jetty server (support object), primarily used to host REST and SOAP web services, require some special attention when deploying because not all combinations of build number 50 (and higher) and 48 (and lower) flows will work correctly: * After installing any build 50 (or higher) flow, build 48 (or lower) flows containing a Jetty server on the same runtime cannot be started anymore.

[[image:Main.Images.Microlearning.WebHome@crashcourse-messaging-pick-up-files--composite-file-list-filter-component.png]] In this filter, we use the following four criteria to filter our messages: * Regular files only * Size list filter (minimum 1 bytes, maximum 1048575) * Age file list filter (minimum 10000) * Simple pattern file list filter (${file.pickup.pattern}) The result of this configuration should be: [[image:Main.Images.Microlearning.WebHome@crashcourse-messaging-pick-up-files--composite-file-list-filter.png]] The next step would be to link this support object to the file inbound channel adapter (the starting point of our flow).

Here you need to select the correct filter to reference your support object. [[image:Main.Images.Microlearning.WebHome@crashcourse-messaging-pick-up-files--composite-file-list-filter-linked.png]] === 3.2 Frequency === Now that we have established the criteria that govern which messages can and which messages cannot pass the next thing we need to consider is with what frequency we are going to let eMagiz check for new files.

After dragging it onto the canvas, you need to give it a name and save the support object by double clicking on it without making any changes.

Or perhaps eMagiz has released a standardized template that will make your life easier (i.e. automatic generation of support objects for JSON transformations in messaging) and you want to benefit from those changes.

Besides the changed naming of the transformation, no JSON factory support objects are required in your flow in comparison with a JSON messaging format.