Search: "support object"

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.

To do so you need the following: * A SQL resource that defines the table structure * The support object called JDBC H2 Connection Pool * The support object called JDBC initialize database A simple SQL statement that defines a table that holds the access token could look something like this.

[[image:Main.Images.Microlearning.WebHome@expert-solution-architecture-h2-database-for-other-applications--jdbc-h2-component-filled.png]] The third and final step to set up the table within the H2 database is to add the support object called JDBC initialize database. [[image:Main.Images.Microlearning.WebHome@expert-solution-architecture-h2-database-for-other-applications--jdbc-h2-initialize-empty.png]] There are two things we need to do to configure the component correctly. First, we need to link this component to the support object we have just created. Second, we need to refer to the SQL script that we have uploaded to our flow.

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

. ==== 3.4.1 Format File Name Generator ==== The first option is the format file name generator. This is a support object in eMagiz [[image:Main.Images.Microlearning.WebHome@crashcourse-messaging-drop-files--drop-file-format-file-name-generator.png]] This component has several tokens available that can be replaced with values.

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

Alternatively you can determine the namespace prefix and the namespace itself, just as you can in the support object called Xpath expression. [[image:Main.Images.Microlearning.WebHome@intermediate-create-your-transformations-FlatFileTransformation-xml2flat-Step4.png]] **Filling in the correct xpath expression per column** For each column you have just generated you now have to define the xpath expression.

The support objects are needed for setting up the connectivity with the database and for other purposes (such as the creation of a H2 database). When we zoom in on the support objects, we see six different support objects. Of those six there is one support object, the JDBC BoneCP data source object, that you should use if you want to set up a connection with an external database.

Secondly, we need a support object that will set up the connection between the eMagiz flow and the eMagiz Event Streaming cluster that hosts the topic.

If you have done all of this it should look like this: [[image:Main.Images.Microlearning.WebHome@intermediate-event-streaming-connectors-emagiz-as-consumer--create-phase-kafka-listener-basic-filled-in.png]] Now that we have filled in the basics for the support object we can fill in the details for our Kafka message-driven channel adapter.

[[image:Main.Images.Microlearning.WebHome@intermediate-event-streaming-connectors-emagiz-as-consumer--create-phase-kafka-flow-messaging-ssl-resources.png]] Now that we have these resources added to the flow we can navigate back to the support object and open the SSL tab and fill it in accordingly.

Secondly, we need a support object that will set up the connection between the eMagiz flow and the eMagiz Event Streaming cluster that hosts the topic.

Here you select the output channel and link the support object to this component. Furthermore, you define the topic to which you want to produce the data.

[[image:Main.Images.Microlearning.WebHome@intermediate-event-streaming-connectors-emagiz-as-producer--create-phase-kafka-flow-messaging-ssl-resources.png]] Now that we have these resources added to the flow we can navigate back to the support object, open the SSL tab and fill it in accordingly.

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.