Search: "support object"

The first step is to add a support object called the H2 connection pool to the flow.

This is where another support object of eMagiz comes in. It is called JDBC initialize database.

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

Here we can add a support object called HTTP Components message sender.

[[image:Main.Images.Microlearning.WebHome@novice-soap-webservice-connectivity-authorization-calling-a-soap-webservice--http-components-message-sender-filled-in.png]] After you have done so you can link the support object to the functional component by double-clicking on the functional component, navigate to the Advanced tab and select the correct message sender.

Key takeaways == * Main form used is a username/password combination (i.e. basic authentication) * Other standard eMagiz options are: ** Mendix authentication ** Metacom authentication ** Zimbra authentication * Make sure to link the support object to the functional component == 5. Suggested Additional Readings == * [[Crash Course (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.WebHome||target="blank"]] ** [[Crash Course API Gateway (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course API Gateway.WebHome||target="blank"]] *** [[Setting up Exit gate (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course API Gateway.crashcourse-api-gateway-setting-up-exit-gate||target="blank"]] * [[Novice (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Novice.WebHome||target="blank"]] ** [[SOAP Web service Connectivity (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Novice.SOAP Web service Connectivity.WebHome||target="blank"]] *** [[Configure your SOAP web service (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Novice.SOAP Web service Connectivity.novice-soap-webservice-connectivity-configure-your-soap-webservice-gen3.WebHome||target="blank"]] *** [[Securing your SOAP Webservice (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Novice.SOAP Web service Connectivity.novice-soap-webservice-connectivity-securing-your-soap-webservice||target="blank"]] *** [[Validate Incoming Messages (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Novice.SOAP Web service Connectivity.novice-soap-webservice-connectivity-validate-incoming-messages-gen3.WebHome||target="blank"]] *** [[Endpoint Check (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Novice.SOAP Web service Connectivity.novice-soap-webservice-connectivity-endpoint-check-gen3.WebHome||target="blank"]] *** [[SOAP Headers (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Novice.SOAP Web service Connectivity.novice-soap-webservice-connectivity-soap-headers||target="blank"]] *** [[Calling a SOAP Web service (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Novice.SOAP Web service Connectivity.novice-soap-webservice-connectivity-calling-a-soap-webservice||target="blank"]] * [[Intermediate (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.WebHome||target="blank"]] ** [[SOAP Web service Connectivity (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.SOAP Web service Connectivity.WebHome||target="blank"]] * [[Expert (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.WebHome||target="blank"]] ** [[Webservice Security (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Webservice Security.WebHome||target="blank"]] * [[Authentication (Search Result)>>url:https://docs.emagiz.com/bin/view/Main/Search?

The functional components that you might need are called: * SMB inbound Channel adapter * SMB outbound Channel adapter On top of that, you need the following support object. * SMB session factory In this microlearning, we will use the SMB inbound channel adapter combined with the SMB session factory to illustrate the configuration.

Now that we have configured the support object,we can add the SMB inbound channel adapter to the flow.

Furthermore, we need to link the support object we have just created and define a poller.

Important in this expression is that we correctly reference the complete name of the SMB Session Factory support object in the flow and that once the host is set, the actual message is passed along.

[[image:Main.Images.Microlearning.WebHome@advanced-file-connectivity-dynamically-manipulate-smb-settings--standard-service-activator-filled-in.png]] === 3.2 Dynamic Share and Directory === If you have a "multi-level" path that eMagiz needs to create automatically, you must dynamically set the Share and Directory settings on the SMB Session Factory support object. To do so, we need to add a component to the flow that will override the host setting.

Important in this expression is that we correctly reference the complete name of the SMB Session Factory support object in the flow and that once the host is set, the actual message is passed along.

[[image:Main.Images.Microlearning.WebHome@novice-soap-webservice-connectivity-validate-incoming-messages-gen3--root-entity-for-wsdl.png]] === 3.2 Effect in Create === In the infra flow, eMagiz automatically adds a support object of the "Dynamic WSDL" type. In this support object, the link is made between the system message definitions and the WSDL that will be created based on this. [[image:Main.Images.Microlearning.WebHome@novice-soap-webservice-connectivity-validate-incoming-messages-gen3--dynamic-wsdl-support-object-infra.png]] {{warning}}Note that when you make changes to the system message after the integration is already in Create, or when you add a new integration to Create, you need to create a new version of your infra flow to be able to deploy the changes to your WSDL.

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.

[[image:Main.Images.Microlearning.WebHome@intermediate-solution-architecture-function-of-h2-database--auto-generation-entry-h2-components.png]] The support objects ensure that the H2 database is created and that the data in it is encrypted.

All of this is nothing you as a user should worry about. Those support objects are created with the best possible settings.

Furthermore, this message bridge is linked to a support object (transaction manager). This configuration allows the poller action to be part of the transaction and therefore gives the ability to perform a rollback in case of error.

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.

This means you need to execute the following steps at a minimum: * Draw a line in Capture towards an (existing) system * Add Integration to Create * Open the exit flow to build the flow in such a way that you can send out emails ** Don't forget the XML to MIME transformation ** Don't forget the Mail sender support object == 3. Solution == In this short movie, you will find the solution for how to configure the flow in Create.

Note that when there is no bus-connection-plain support object available within the context of your flow, copy + paste this component from another flow in which it is available.

Key takeaways == * A JMS message-driven channel adapter within your flow that listens for data on the 'custom' queue * The fully qualified name of the 'custom' queue on which to listen * When the support object named bus-connection-plain is missing, please add it via a copy+paste action == 5.