Changes for page Endpoint Check

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

From 33.1 to 32.2 From 40.1 to 39.1

From version 39.1

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

Change comment: There is no comment for this version

To version 33.1

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

Change comment: There is no comment for this version

Raw
Rendered

Summary

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

Details

Page properties

Title

@@ -1,1 +1,1 @@
--Endpoint Check
++novice-soap-webservice-connectivity-configure-your-soap-webservice

Content

@@ -1,111 +1,67 @@
  {{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. One last check to perform before you can communicate with the external parties that the endpoint is available to receive messages and up and running. In this microlearning, we will learn how you can perform such a check.
++In some cases, the input you receive or the output that you need to send to an external party cannot handle all characters or the input or output is written with the help of a character set. In this microlearning, we will learn how you can define the character set for file-based connectivity to ensure that you can process and deliver files according to the specifications.
--Should you have any questions, please contact academy@emagiz.com.
++Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
--* Last update: June 11th, 2021
++* Last update: May 31th, 2021
  * Required reading time: 7 minutes
  == 1. Prerequisites ==
++
  * Basic knowledge of the eMagiz platform
  == 2. Key concepts ==
--This microlearning centers around the endpoint check.
--By endpoint check, we mean: determine whether the WSDL is accessible on the correct endpoint so we can forward the URL to the WSDL + the URL to call to our external parties
++This microlearning centers around learning how to define the character set to ensure that eMagiz processes the information correctly.
--The endpoint consists of the following elements:
--* Starts with https:// or http://
--* Second part is the host (i.e. where is the endpoint running)
--* Third part is the port on which the incoming traffic is accepted
--* These three things combined make up the first part of our endpoint that will vary per environment
--* Following that we have a static remainder of the endpoint that is build up as follows: /ws/{path-specific-servlet-mapping}/
--* If you want to get to the WSDL simply add the name of the WSDL and the .wsdl extension to the endpoint when viewing it in the browser
--
--== 3. Endpoint Check ==
++By character set, we mean: The composite number of different characters that are being used and supported by computer software and hardware. It consists of codes, bit patterns, or natural numbers used in defining some particular character.
--hen 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. One last check to perform before you can communicate with the external parties that the endpoint is available to receive messages and up and running. In this microlearning, we will learn how you can perform such a check.
++* Some external system talk in a different character set
++* eMagiz talks in default UTF-8 as a character set and assumes everyone else also does this
++* In cases of mismatch correct is at the point where you talk with the other system (i.e. entry or exit)
--The endpoint consists of the following elements:
--* Starts with https:// or http://
--* Second part is the host (i.e. where is the endpoint running)
--* Third part is the port on which the incoming traffic is accepted
--* These three things combined make up the first part of our endpoint that will vary per environment
--* Following that we have a static remainder of the endpoint that is build up as follows: /{context-path}/{path-specific-servlet-mapping}/
--* If you want to get to the WSDL simply add the name of the WSDL and the .wsdl extension to the endpoint when viewing it in the browser
++== 3. Character set ==
--As you can see the endpoint can be divided into two parts. One part is dynamic across environments and one part is static across environments. Let us first determine how we can find out the first part of our endpoint.
++In some cases, the input you receive or the output that you need to send to an external party cannot handle all characters or the input or output is written with the help of a character set. In this microlearning, we will learn how you can define the character set for file-based connectivity to ensure that you can process and deliver files according to the specifications.
--=== 3.1 HTTPS or HTTP ===
++Sometimes external systems only talk in a specific character set. To ensure that all the data is properly communicated between eMagiz and the other system we need to make sure that we define which character set that is so we can tell it to eMagiz via a component. That way eMagiz will deviate from its default (i.e. UTF-8) and will process the file according to that different character set. In practice, we mainly see windows-1252 as an alternative that pops up once in a while. In various components that deal with file handling, you can define the character set on which eMagiz should act. Examples of such components are:
--We start at the top with the determination of HTTPS or HTTP. A simple rule of thumb is that when running in the eMagiz Cloud the endpoint starts with https:// and when the endpoint is running locally (i.e. on-premise) the endpoint starts with http:// (unless you secure it yourself, more on that later).
++- File to string transformer
++- Flat file to XML transformer
++- File outbound channel adapter
--=== 3.2 Host ===
++In all these components you have the option to define the character set within the Advanced tab of the component. In this microlearning, we will use the File to string transformer to illustrate how that will look.
--The next part of the endpoint is the host. The host is effectively the (virtual) machine on which the endpoint is running. When hosting an endpoint in the eMagiz cloud the host part is the combination between the DNS left-most label on Route level and the cloudslot on which your environment is running. The first part of the equation can be found under Deploy -> Architecture. The second part can be found under Deploy -> Properties by looking for the {technicalnameproject}.amqp01.host. You need to combine the two elements via a dash (-). An example of this would then be spwbsrv-test-cloud0001.emagizcloud.com. In case of an on-premise installation, you should ask your customer what the IP address or DNS name is to connect to the machine on which your runtime is running. If the runtime is running locally on your laptop the host equals localhost.
++[[image:Main.Images.Microlearning.WebHome@novice-file-based-connectivity-characterset--characterset-configuration.png]]
--=== 3.3 Port ===
++In this field, you can define the character set of your choice. To make this work in eMagiz you need to navigate to the Create phase of eMagiz and open the entry flow in which you want to retrieve the file to a certain location. Within the context of this flow, we need to add functionality that will ensure that the correct character set is used. To do so first enter "Start Editing" mode on flow level. After that open, the File to string transformer, navigate to the Advanced tab, and fill in the correct character set. After you have defined the correct character set the only thing left to do is to Save the component. See the suggested additional readings section on the complete list of character sets that are supported by Java 8.
--Whether or not the port needs to be defined to get to the endpoint is once again determined by the location. If the endpoint is hosted in the eMagiz Cloud the port is *not* part of the endpoint. However, when you host your endpoint locally the endpoint becomes part of your endpoint. Note that to make this piece work in the eMagiz Cloud you should set up your Route properly. More on that in our Cloud Management courses. You can determine the port, for the endpoint or the route, in two steps. First, we navigate to the all entry we have created and open the Jetty component. The first segment of the Jetty Server talks about the server connector. In this part, the port is defined (either via a property or statically).
++Congratulations you have successfully learned how to specify the character set.
--[[image:Main.Images.Microlearning.WebHome@novice-soap-webservice-connectivity-endpoint-check--server-connector-settings.png]]
--
--If it is defined via a property you can search for the corresponding value under Deploy -> Properties by checking on the property name and filtering on runtime level to get to the port. If it is defined statically you can simply read it here. Note that the best practice is to use a property value as that allows you to use a different range for your port numbering between environments. In other words, it allows you to use the 9000 range for Test, the 8000 range for Acceptance, and the 9000 range for Production. This is also to safeguard against someone accidentally sending data to the wrong environment.
--
--=== 3.3 Context Path ===
--
--The first part of the static remainder of the endpoint is the context. By default, this is filled with /ws but you as a user can alter this. You can check the current value by opening the Jetty component again and looking at the context path that is filled in.
--
--[[image:Main.Images.Microlearning.WebHome@novice-soap-webservice-connectivity-endpoint-check--context-path.png]]
--
--=== 3.4 Path Specific Servlet Mapping ===
--
--The last part of our endpoint is determined by the path-specific servlet mapping. You can once again find the value (and change it if you want to) within the Jetty component. In this component, you can see the servlet mappings and see the path that belongs to that servlet. For SOAP Webservice the best practice is to have only one servlet-mapping and in 99% of the cases, the auto-generated value of eMagiz is more than fine.
--
--[[image:Main.Images.Microlearning.WebHome@novice-soap-webservice-connectivity-endpoint-check--path-specific-servlet-mapping.png]]
--
--Combining all of this, assuming we run in the eMagiz Cloud, will result in the following endpoint for our Test environment:
--* https://spwbsrv-test-cloud0001.emagizcloud.com/ws/spwbsrv-connector/
--
--Combining all of this, assuming we run locally on our laptop, will result in the following endpoint for our Test environment:
--* http://localhost:9091/ws/spwbsrv-connector/
--
--=== 3.5 Getting the WSDL name ===
--
--To get to the WSDL to verify if it is available to be shared with external parties the last thing you need is the WSDL name. You can find this one, surprisingly enough, in the Jetty component. To get to the WSDL name double click on the servlet that is defined under the heading Servlets and navigate to the Advanced tab. Here you will see the name of the WSDL. If you have adhered to the default of eMagiz the name will mimic the name of your path-specific servlet mapping.
--
--[[image:Main.Images.Microlearning.WebHome@novice-soap-webservice-connectivity-endpoint-check--wsdl-name.png]]
--
--With this information we could reach the WSDL via the following endpoint, assuming we run in the eMagiz Cloud:
--* https://spwbsrv-test-cloud0001.emagizcloud.com/ws/spwbsrv-connector/spwbsrv-connector.wsdl
--
--With this information we could reach the WSDL via the following endpoint, assuming we run locally on our laptop:
--* http://localhost:9091/ws/spwbsrv-connector/spwbsrv-connector.wsdl
--
--With this information, you should be able to access the WSDL and communicate both the endpoint as well as the WSDL to your external parties.
--
  == 4. Assignment ==
--Determine the endpoint of your SOAP Webservice and retrieve the WSDL.
++Configure an entry in which you define the component and configuration needed to process a file on a per-line basis.
  This assignment can be completed with the help of the (Academy) project that you have created/used in the previous assignment.
  == 5. Key takeaways ==
--* The endpoint consists of the following elements:
--    ** Starts with https:// or http://
--    ** Second part is the host (i.e. where is the endpoint running)
--    ** Third part is the port on which the incoming traffic is accepted
--    ** These three things combined make up the first part of our endpoint that will vary per environment
--    ** Following that we have a static remainder of the endpoint that is build up as follows: /{context-path}/{path-specific-servlet-mapping}/
--    ** If you want to get to the WSDL simply add the name of the WSDL and the .wsdl extension to the endpoint when viewing it in the browser
--* The relevant information can be derived from the Jetty component and by determining where the endpoint is hosted
++* Some external system talk in a different character set
++* eMagiz talks in default UTF-8 as a character set and assumes everyone else also does this
++* In cases of mismatch correct is at the point where you talk with the other system (i.e. entry or exit)
++* eMagiz provides several components within which you can define the character set
  == 6. Suggested Additional Readings ==
--If you are interested in this topic and want more information on it please read the help text provided by eMagiz.
++If you are interested in this topic and want more information on it please read the help text provided by eMagiz and read the following links:
++* https://docs.oracle.com/javase/8/docs/technotes/guides/intl/encoding.doc.html
++* https://www.techopedia.com/definition/941/character-set
++* https://www.smashingmagazine.com/2012/06/all-about-unicode-utf8-character-sets/
++
  == 7. Silent demonstration video ==
--{{video attachment="novice-soap-webservice-connectivity-endpoint-check.mp4" reference="Main.Videos.Microlearning.WebHome"/}}
++This video demonstrates how you could have handled the assignment and gives you some context on what you have just learned.
++{{video attachment="novice-file-based-connectivity-characterset.mp4" reference="Main.Videos.Microlearning.WebHome"/}}
++
  )))((({{toc/}}))){{/container}}{{/container}}

Changes for page Endpoint Check

Summary

Details

Navigation