Search: "support object"

Support objects - Introduction

Key concepts == This microlearning focuses on support objects. With support objects, we mean: Component that help the functional components do the work they are supposed to do == 3.

To register such a list, you can add a support object called a Composite file list filter. [[image:Main.Images.Microlearning.WebHome@crashcourse-platform-create-support-objects-introduction--composite-file-list-filter-selection.png]] Opening the support object will give you the following pop-up.

Key takeaways == * Support objects help other functional components in executing their functional * Support objects can help in various categories * Each support object has a specific task and uses a case == 5.

This release, we have done several improvements for our Failover functionality and added two configuration options for our SMB session factory support objects. We have also updated our password policy, so from now on you are required to have a password with a minimum length of 14 characters!

Minor changes Create - Flow Designer: We have added two additional configuration options to the SMB session factory support object. Connect as guest: We have added the option to toggle whether the session factory should attempt to connect as a guest if the login attempt with the provided username and password is rejected.

Manage - Error messages: The status of error messages can now be reset to empty. (#965) Bug fixes Create - Flow Designer: If a component misses a support object, an alert is now shown in the Flow Designer, displaying which support object is missing. (#1305) Create - Flow Designer: The XML to flat file and flat file to XML transformers have been restyled, such that they are similar to all other components. (#1153) Create - Flow Designer: We fixed an issue where the browser page would get frozen when editing a flow component.

This release, we have done several improvements for our Failover functionality and added two configuration options for our SMB session factory support objects. We have also updated our password policy, so from now on you are required to have a password with a minimum length of 14 characters!

====Minor changes==== * Create - Flow Designer: We have added two additional configuration options to the SMB session factory support object. ** Connect as guest: We have added the option to toggle whether the session factory should attempt to connect as a guest if the login attempt with the provided username and password is rejected. ** Force SMB version 2: We have added the option to enforce the usage of SMB version 2.

Besides that, you will also see this shown in the pending changes list when you apply your changes to the environment. * Manage - Error messages: The status of error messages can now be reset to empty. (#965) ====Bug fixes==== * Create - Flow Designer: If a component misses a support object, an alert is now shown in the Flow Designer, displaying which support object is missing. (#1305) * Create - Flow Designer: The XML to flat file and flat file to XML transformers have been restyled, such that they are similar to all other components. (#1153) * Create - Flow Designer: We fixed an issue where the browser page would get frozen when editing a flow component. * Deploy - Releases: The version number of releases that have been activated, cannot be reused anymore for new releases.

Minor Changes Create - Flow Designer: The view button that can be found by navigating to the right panel of the Flow Designer and choosing the Support Objects tab opens a pop-up that shows a list of all support objects that can be added. This button is accessible only in the view mode of the Flow Designer. (#870) Bug fixes Create - Flow Creation: When creating the corresponding infra and entry flows belonging to a system that will host a SOAP endpoint, we fixed a bug causing two support objects to break upon creation. (#1517) Manage - Dashboard: The manage phase dashboard no longer breaks when an error occurs in a component with an id that does not follow the convention, or when that value is longer than expected. (#1566)

.** ====Minor Changes==== * Create - Flow Designer: The view button that can be found by navigating to the right panel of the Flow Designer and choosing the Support Objects tab opens a pop-up that shows a list of all support objects that can be added. This button is accessible only in the view mode of the Flow Designer. (#870) ====Bug fixes==== * Create - Flow Creation: When creating the corresponding infra and entry flows belonging to a system that will host a SOAP endpoint, we fixed a bug causing two support objects to break upon creation. (#1517) * Manage - Dashboard: The manage phase dashboard no longer breaks when an error occurs in a component with an id that does not follow the {{code}}[id].

In this microlearning, we’ll focus on the right-hand panel of the flow editor, where you’ll find key features like alerts, resources, support objects, and properties that help you fine-tune your integration.

[[image:Main.Images.Microlearning.WebHome@crashcourse-platform-create-flow-editor-basics--right-panel-add-model-resource.png]] === 3.3 Support objects === In the tab with the support objects, the current support objects in the flow can be seen. [[image:Main.Images.Microlearning.WebHome@crashcourse-platform-create-flow-editor-basics--right-panel-support-objects.png]] For more information on support objects and how to configure them please check out this [[microlearning>>Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-create-support-objects-introduction||target="blank"]]. === 3.4 Properties === In the properties tab, it can be viewed which properties are being used in the flow.

These support objects are: - Merlin crypto - WSS4J security interceptor In the merlin crypto support object, you need to reference the Keystore you need to authenticate yourself with the external party.

The support object you need to link to the entry is: * Merlin crypto In the merlin crypto support object, you need to reference the truststore where you store the public certificate against which the external needs to authenticate themselves. [[image:Main.Images.Microlearning.WebHome@expert-webservice-security-ws-security--ws-security-merlin-crypto-entry.png]] Next to adding the support object, you must open the message dispatcher support object.

Removed obsolete support object 'Management'. Removed obsolete "SOAP over JMS" functionality, i.e., the 'JMS listener container' and 'Web service message listener' support objects. Added many new (advanced) settings to the support object 'Apache ActiveMQ Artemis server'. See the build number 59 release notes for details.

. ** Removed obsolete support object 'Management'. ** Removed obsolete "SOAP over JMS" functionality, i.e., the 'JMS listener container' and 'Web service message listener' support objects. ** Added many new (advanced) settings to the support object 'Apache ActiveMQ Artemis server'.

. === 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.

To tell this to the flow component you will need some support objects. If you have defined your default message format correctly (i.e. set it to JSON) eMagiz will auto-generate the relevant support objects for you.

However, to also support the transformation from JSON to XML you need an additional support object called Result to string transformer [[image:Main.Images.Microlearning.WebHome@novice-create-your-transformations-json-to-xml--result-to-string-transformer.png]] Don't forget to properly link the support objects to the correct flow components for them to work.

Key takeaways == * eMagiz natively supports the transformation of JSON to XML with the help of: * Default message format * Data models in Design * Message mapping in Design * Create transformation in Create * Support Objects * Ensure that you link the support objects correctly * Don't forget to define the message format == 5.

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."

To tell this to the flow component you will need some support objects. If you have defined your default message format correctly (i.e. set it to JSON) eMagiz will auto-generate the relevant support objects for you.

In the offramp, you need to link the support objects to the transformation. In the exit, you need to link the JSON result factory to the validation.

Key takeaways == * eMagiz natively supports the transformation of XML to JSON with the help of: * Default message format * Data models in Design * Message mapping in Design * Create transformation in Create * Support Objects * Ensure that you link the support objects correctly * Don't forget to define the message format == 5.