Search: "support object"

To make sure that your existing data pipeline will function in the same way, you should execute the following steps: * Add a support object called top level poller and configure it as follows [[image:Main.Images.Migrationpath.WebHome@migration-path-job-dashboard-cleanup--migration-path-job-dashboard-cleanup-top-level-poller-config.png]] * Add a channel called clean * Add a standard inbound channel adapter called clean.cron and configure it as follows (As you can see it cleans the job dashboard every day at five in the morning) [[image:Main.Images.Migrationpath.WebHome@migration-path-job-dashboard-cleanup--migration-path-job-dashboard-cleanup-clean-cron-config.png]] * Add a standard inbound channel adapter called startup.cron and configure it as follows (It cleans the job dashboard on startup) [[image:Main.Images.Migrationpath.WebHome@migration-path-job-dashboard-cleanup--migration-path-job-dashboard-cleanup-startup-cron-config.png]] * Add a JDBC outbound channel adapter to your flow * Use the clean channel as input * Link it to the h2 database that is in your flow * Enter the query that you can find below [[image:Main.Images.Migrationpath.WebHome@migration-path-aws-redshift-refresh--migration-path-job-dashboard-cleanup-result-part-one.png]] === 3.2 Query you need for cleanup === The following query is needed to cleanup all relevant parts of the job dashboard to ensure that only the last month's jobs are still visible.

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.

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

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

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.

After you have uploaded the XSD link it to the connector-xsd support object in your entry. [[image:Main.Images.Microlearning.WebHome@novice-soap-webservice-connectivity-validate-incoming-messages--uploaded-file.png]] [[image:Main.Images.Microlearning.WebHome@novice-soap-webservice-connectivity-validate-incoming-messages--file-linked-to-xsd-component.png]] With this done you have successfully added validation to your SOAP web service. == 4.

[[image:Main.Images.Microlearning.WebHome@expert-robotic-process-automation-call-a-robot--http-outbound-example.png]] {{info}}Note that you need a header mapper support object to send the correct headers towards dexi.

If you ever want to validate whether a support object is linked to your component, click on it once.

In the context of eMagiz, this means that every flow has its unique support object (that is generated by default) to support this functionality.