Search: "support object"

. ** Don't forget the HTTP Components Message Sender support object ** Don't forget to link the support object to the functional component == 3.

In cases where this is not possible, you could use a support object called HTTP Components message sender to influence when eMagiz throws a timeout.

Now that we have saved the component, the last step is to link the support object to the web service outbound gateway to ensure that your changed setting will be applied to the web service call. Then, open the web service outbound gateway and select your support object as the message sender. [[image:Main.Images.Microlearning.WebHome@intermediate-soap-webservice-connectivity-handling-webservice-timeouts--http-components-message-sender-linked.png]] == 4.

We will build upon that knowledge in this microlearning and apply our expertise to the world of REST web services. We need a support object to ensure that the proper certificates are sent along with the call to the REST web service. Support objects are components in eMagiz that support the working of other elements.

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

. === 3.2 Calling an external SOAP Webservice that requires WS-Addressing === To ensure that eMagiz creates the required SOAP headers on top of your SOAP message, you must add one support object to the flow where you want to call the external web service (predominantly the exit). This support object is: - WS-Addressing action callback Within this component, you can set the following headers as well as choose the version of WS-Addressing that is required: - Action (required) - To - From - Reply To - Fault To [[image:Main.Images.Microlearning.WebHome@expert-webservice-security-ws-addressing--ws-addressing-basic.png]] [[image:Main.Images.Microlearning.WebHome@expert-webservice-security-ws-addressing--ws-addressing-advanced.png]] When you are satisfied with your configuration, you can link this support object to the web service outbound gateway as follows: [[image:Main.Images.Microlearning.WebHome@expert-webservice-security-ws-addressing--ws-addressing-callback.png]] After doing all this, you can test the flow to verify that the WS-Addressing is correctly configured, allowing you to call the external web service. == 4.

* The endpoint consists of the following elements: ** Starts with https:// or http:// ** The second part is the host (i.e., where the endpoint is running) ** The third part is the port on which the incoming traffic is accepted ** These three things combined make up the first part of our endpoint, which will vary per environment ** Following that, we have a static remainder of the endpoint that is built up as follows: /{soap WS name}/{Id}/ ** If you want to get to the WSDL, add the name of the WSDL (which is defined by the ID given to the "Dynamic WSDL" support object) and the .wsdl extension to the endpoint when viewing it in the browser As you can see, the endpoint can be divided into two parts.

The infra flow has a support object of the type "Dynamic WSDL". Here, you see the default location of the hosted SOAP endpoint, which is http://localhost:${entry.connector.ws.port}/ws/{soap WS name}/.

An example URI, in that case, would be {{code}}https://soap-test-cloud0000.emagizcloud.com/ws/soapgn3-connector/soapgn3-connector.wsdl{{/code}}{{/info}} [[image:Main.Images.Microlearning.WebHome@novice-soap-webservice-connectivity-validate-incoming-messages-gen3--dynamic-wsdl-support-object-infra.png]] == 4. Key takeaways == * The endpoint consists of the following elements: ** Starts with https:// or http:// ** The second part is the host (i.e., where the endpoint is running) ** The third part is the port on which the incoming traffic is accepted ** These three things combined make up the first part of our endpoint, which will vary per environment ** Following that, we have a static remainder of the endpoint that is built up as follows: /{soap WS name}/{Id}/ ** If you want to get to the WSDL, add the name of the WSDL (which is defined by the ID given to the "Dynamic WSDL" support object) and the .wsdl extension to the endpoint when viewing it in the browser * The relevant information can be derived from the "Dynamic WSDL" support object and by determining where the endpoint is hosted == 5.

To ensure that a certain authorization is added to this HTTP outbound component we need to add the [[support object>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-create-support-objects-introduction||target="blank"]] called REST Template to the flow: [[image:Main.Images.Microlearning.WebHome@intermediate-rest-webservice-connectivity-authorization-oauth-client-credentials--rest-template-search.png]] After you have added the support object to the canvas and given it a name you can open it by double clicking on the component. eMagiz will show you the following pop-up: [[image:Main.Images.Microlearning.WebHome@intermediate-rest-webservice-connectivity-authorization-oauth-client-credentials--rest-template-empty.png]] As you can see here you can select various authentication schemes.

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

Suggested Additional Readings == If you are interested in this topic and want more information, please read the help text provided by eMagiz and read the following links: * [[Crash Course (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.WebHome||target="blank"]] ** [[Crash Course Platform (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.WebHome||target="blank"]] *** [[Support objects - Introduction (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-create-support-objects-introduction||target="blank"]] * [[Intermediate Level (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.WebHome||target="blank"]] ** [[REST Connectivity (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.REST Connectivity.WebHome||target="blank"]] *** [[Call a REST Webservice (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.REST Connectivity.intermediate-rest-webservice-connectivity-call-a-rest-webservice||target="blank"]] * [[OAuth 2.0 (Search Results)>>url:https://docs.emagiz.com/bin/view/Main/Search?

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-platform-create-flow-editor-basics--service-activator-components.png]] === 3.8 Support === In eMagiz, support objects can be linked to a functional component to aid the working of that component.

[[image:Main.Images.Microlearning.WebHome@crashcourse-platform-create-flow-editor-basics--annotation-components.png]] === 3.11 The Combination === Combining this all together results in a flow with at least an input and output component helped by several support objects. An example of what a working flow looks like is: [[image:Main.Images.Microlearning.WebHome@crashcourse-platform-create-flow-editor-basics--working-flow.png]] == 4.

* If no best practice has yet emerged only the known components are generated * A flow needs to have at least an input and output component paired with the default support objects * Every component has a specific function and there are a lot of them == 5.

On top of that configuration there is a support object in eMagiz that will help you with the analysis of your problems when calling the SOAP web service.

This support object is named "Detailed SOAP Fault Message Resolver". To link the support object to your web service outbound gateway you open the web service outbound gateway, navigate to the Advanced tab, and select the Fault message resolver.

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 Component for Data Enrichment === Once you have configured the storage mechanism, now you can start with setting up the component to retrieve the stored state data for the enrichment operation.

{{info}} Note that these persisted states can only be retrieved by eMagiz flows running in the same runtime where the support objects are deployed. Thus, we suggest placing these support objects in the infra flow so the stored state data can be retrieved by other flows.