Changes for page Endpoint Check

Last modified by Danniar Firdausy on 2024/09/04 10:26

From 35.2 to 35.1 From 36.2 to 36.1

From version 36.1

edited by Erik Bakker
on 2022/06/12 09:36

Change comment: There is no comment for this version

To version 35.2

edited by Erik Bakker
on 2022/06/12 09:35

Change comment: Update document after refactoring.

Raw
Rendered

Summary

Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Title

@@ -1,1 +1,1 @@
--Validate Incoming Messages
++novice-soap-webservice-connectivity-validate-incoming-messages

Content

@@ -1,113 +1,100 @@
--{{container}}{{container layoutStyle="columns"}}(((
--When setting up a point at which your customers can talk to you eMagiz offers various methods of creating such a point. One of those options is by hosting a SOAP Webservice in eMagiz that handles XML messages asynchronously or synchronously. In this microlearning, we will zoom in on the part that validation of the messages plays when offering such a SOAP web service.
++{{container}}{{container layoutStyle="columns"}}(((
++When talking to external parties via a SOAP web service you need to define in eMagiz that you want to call a SOAP web service so eMagiz will form a correct SOAP message. On top of the call there is a support object in eMagiz that will help you with the analysis of your problems when calling the SOAP web service. In this microlearning, we will learn how to call a SOAP web service from eMagiz.
  Should you have any questions, please contact academy@emagiz.com.
--* Last update: June 10th, 2021
--* Required reading time: 7 minutes
++* Last update: April 1st, 2022
++* Required reading time: 5 minutes
  == 1. Prerequisites ==
  * Basic knowledge of the eMagiz platform
  == 2. Key concepts ==
--This microlearning centers around configuring your SOAP web service.
++This microlearning centers around calling a SOAP Webservice.
--By configuring, we mean: Designing and determining the characteristics of the SOAP web service
++With SOAP, we mean:  A messaging protocol specification for exchanging structured information in the implementation of web services in computer networks.
--Crucial parts in the configuration are:
--* Operation Name
--* SOAP Webservice Namespace
--* Validation
--* Authentication
--
--Of these four points, we will zoom in on the validation part of our SOAP Webservice in this microlearning.
++* To call a REST Webservice you need either:
++    ** A Web Service Outbound Gateway
++* Critical information when configuring this component:
++    ** URL
++    ** Retry Advice
++    ** Error Handling
++    ** Authentication
--== 3. Validate Incoming Messages ==
++== 3. Calling a SOAP Webservice ==
--When setting up a point at which your customers can talk to you eMagiz offers various methods of creating such a point. One of those options is by hosting a SOAP Webservice in eMagiz that handles XML messages asynchronously or synchronously. In this microlearning, we will zoom in on the part that validation of the messages plays when offering such a SOAP web service.
++When talking to external parties via a SOAP web service you need to define in eMagiz that you want to call a SOAP web service so eMagiz will form a correct SOAP message. On top of the call there is a support object in eMagiz that will help you with the analysis of your problems when calling the SOAP web service. In this microlearning, we will learn how to call a SOAP web service from eMagiz.
--Crucial parts in the configuration are:
--* Operation Name
--* SOAP Webservice Namespace
--* Validation
++Calling a SOAP Webservice within eMagiz can be done with the help of a Web Service Outbound Gateway. To correctly configure this component you need to consider the following elements:
++
++* URL
++* Retry Advice
++* Error Handling
  * Authentication
--Of these four points, we will zoom in on the validation part of our SOAP Webservice in this microlearning. The SOAP Webservice serves as a point of entry where people with the rights credentials (security) and the right answers (validation) are allowed to enter and perform their actions. In the next microlearning, we will talk about the security part. In this microlearning, we talk about the validation part.
++We will discuss the first three items in this list in this microlearning. In the microlearnings that will follow this microlearning, we will delve deeper into various authentication possibilities.
--As you have learned from the crash course you can validate an XML message with the help of an XSD. This XSD describes dataTypes, order, associations, and length of attributes. You can use such an XSD for the validation of what your clients send you. eMagiz will automatically define a WSDL based on the XSD that you provide that stores metainformation and stores the XSD for validation purposes. This way you can communicate the WSDL (location) to external parties as a reference document upon which they can build their solution. If you keep the eMagiz defaults you can access the WSDL via http://host:port/ws/ws-name/ws-name.wsdl. Note that you need to all values (except for the ws and .wsdl part) with actual values.
++Before we delve into the configuration of the component let us first move to Create and open an exit flow in which we want to call the SOAP Webservice. When you open the exit flow it will look similar to this:
--What eMagiz does need from you is the correct XSD for validation. As a starting point you should download the XSD that eMagiz has generated based on the system message(s) you have defined in the Design phase. Once you have that you can structure the XSD correctly. A valid XSD start with a schema segment. In this segment you need to define your SOAP WS namespace:
++[[image:Main.Images.Microlearning.WebHome@novice-soap-webservice-connectivity-calling-a-soap-webservice--exit-flow-starting-point.png]]
--<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
--<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
--    xmlns="http://www.academy.emagiz.com/ns/mlacade-bus/spwbsrv-connector/1.0/"
--    attributeFormDefault="unqualified" elementFormDefault="unqualified"
--    targetNamespace="http://www.academy.emagiz.com/ns/mlacade-bus/spwbsrv-connector/1.0/">
++Now that we have opened the flow and are in "Start Editing" mode we need to add the web service outbound gateway to start with.
--Once you have that you need to copy all complex and simple types from the XSD that you downloaded and paste them below the lines you have created:
++[[image:Main.Images.Microlearning.WebHome@novice-soap-webservice-connectivity-calling-a-soap-webservice--web-service-outbound-component.png]]
--<xs:complexType name="Input">
--        <xs:sequence>
--            <xs:element name="String" type="nonEmptyString"/>
--            <xs:element minOccurs="0" name="Decimal" type="xs:decimal"/>
--            <xs:element name="Enum" type="Enum"/>
--            <xs:element name="Integer" type="xs:long"/>
--            <xs:element name="Boolean" type="xs:boolean"/>
--            <xs:element minOccurs="0" name="DateTime" type="xs:dateTime"/>
--        </xs:sequence>
--    </xs:complexType>
--    <xs:simpleType name="nonEmptyString">
--        <xs:restriction base="xs:string">
--            <xs:minLength value="1"/>
--        </xs:restriction>
--    </xs:simpleType>
--    <xs:simpleType name="Enum">
--        <xs:restriction base="xs:string">
--            <xs:enumeration value="URGENT"/>
--            <xs:enumeration value="HIGH"/>
--            <xs:enumeration value="MEDIUM"/>
--            <xs:enumeration value="LOW"/>
--            <xs:enumeration value="PLANNING"/>
--        </xs:restriction>
--    </xs:simpleType>
++=== 3.1 URL ===
--To wrap things up you need to define your Request and Response element and close the schema:
++Now that we have added the correct component to the canvas it has become time to configure the component correctly. The first thing to configure when calling a SOAP Webservice is determining and registering the endpoint (URL) eMagiz should call to deliver the message too. As always in scenarios where an information element can change between environments, you should use a property reference and determine the correct value on a per-environment basis.
--<xs:element name="SendNptRequest">
--        <xs:complexType>
--            <xs:sequence>
--                <xs:element name="Input" type="Input"/>
--            </xs:sequence>
--        </xs:complexType>
--    </xs:element>
--    <xs:element name="SendNptResponse">
--        <xs:complexType/>
--    </xs:element>
--    </xs:schema>
++[[image:Main.Images.Microlearning.WebHome@novice-soap-webservice-connectivity-calling-a-soap-webservice--web-service-outbound-component-url.png]]
--Combining this will result in a valid XSD for my example. In your case, you will need to enter other values. When you are done with the creation of the XSD save it with a name such as spwbsrv-connector.xsd and upload it to the flow. After you have uploaded the XSD link it to the connector-xsd support object in your entry.
++=== 3.2 Retry Advice ===
--[[image:Main.Images.Microlearning.WebHome@novice-soap-webservice-connectivity-validate-incoming-messages--uploaded-file.png]]
++The second setting we need to configure is the retry advice. With retry advice, you can guard your solution against temporary connection losses between eMagiz and the external party. As this can happen from time to time the best practice is to configure such a Retry Advice on every Web Service Outbound component. To add the Retry Advice move to the Advanced tab and move down to the Request handler advice chain segment. Within this segment, you will see a button called Retry Advice.
--[[image:Main.Images.Microlearning.WebHome@novice-soap-webservice-connectivity-validate-incoming-messages--file-linked-to-xsd-component.png]]
++[[image:Main.Images.Microlearning.WebHome@novice-soap-webservice-connectivity-calling-a-soap-webservice--web-service-outbound-component-retry-advice-button.png]]
--With this done you have successfully added validation to your SOAP web service.
++When you click on the Retry Advice button you will be prompted with a pop-up. In here you need to configure the exact settings
++[[image:Main.Images.Microlearning.WebHome@novice-soap-webservice-connectivity-calling-a-soap-webservice--web-service-outbound-component-retry-advice-pop-up-empty.png]]
++
++The best practice for this configuration is as follows for asynchronous solutions:
++* Select the option called Simple Retry Policy
++* Set the max attempts at 6
++* Select the Fixed back off policy
++* Set the backoff period at 5000 (ms)
++
++When you have done so the configuration should look as follows. The only thing left is to press Save to save your Retry Advice configuration
++
++[[image:Main.Images.Microlearning.WebHome@novice-soap-webservice-connectivity-calling-a-soap-webservice--web-service-outbound-component-retry-advice-pop-up-filled-in.png]]
++
++=== 3.3 Error Handling ===
++
++When calling a SOAP Web service with the configuration we have defined up till here you could suffer from cryptic error response you get back when the SOAP web service call fails. To improve the error handling to make your life easier when analyzing the problem you need to add a support object to the canvas and link it to the web service outbound gateway. 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. Afterward press Save to save the link between the components.
++
++[[image:Main.Images.Microlearning.WebHome@novice-soap-webservice-connectivity-calling-a-soap-webservice--web-service-outbound-component-fault-message-resolver.png]]
++
++Now that we have configured the HTTP Outbound component to our liking we can press Save on the component level to store our changes. As a result the flow will look as follows:
++
++[[image:Main.Images.Microlearning.WebHome@microlearning/novice-soap-webservice-connectivity-calling-a-soap-webservice--flow-result.png]]
++
  == 4. Assignment ==
--Add validation to the SOAP Webservice we have been configuring.
++Build a flow within your project in which you do a call to an external party that hosts a SOAP web service.
  This assignment can be completed with the help of the (Academy) project that you have created/used in the previous assignment.
  == 5. Key takeaways ==
--* Crucial parts in the configuration are:
--    ** Operation Name
--    ** SOAP Webservice Namespace
--    ** Validation
++* eMagiz will create a valid SOAP message when using this component
++* eMagiz provides a support object for better error handling of SOAP faults
++* There are four key configuration elements:
++    ** URL
++    ** Retry Advice
++    ** Error Handling
      ** Authentication
--* Validation is done with the help of an XSD
--* The WSDL is used for external documentation
--* Use the XSD generated by eMagiz based on the system message as a starting point
  == 6. Suggested Additional Readings ==
@@ -115,6 +115,6 @@
  == 7. Silent demonstration video ==
--{{video attachment="novice-soap-webservice-connectivity-validate-incoming-messages.mp4" reference="Main.Videos.Microlearning.WebHome"/}}
++{{video attachment="novice-soap-webservice-connectivity-calling-a-soap-webservice.mp4" reference="Main.Videos.Microlearning.WebHome"/}}
  )))((({{toc/}}))){{/container}}{{/container}}

Changes for page Endpoint Check

Summary

Details

Navigation