Changes for page Handling Webservice Timeouts
Last modified by Danniar Firdausy on 2024/09/18 21:36
From version 1.1
edited by eMagiz
on 2022/06/10 13:16
on 2022/06/10 13:16
Change comment:
There is no comment for this version
To version 9.8
edited by Danniar Firdausy
on 2024/09/13 09:06
on 2024/09/13 09:06
Change comment:
There is no comment for this version
Summary
-
Page properties (4 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - intermediate-soap-webservice-connectivity-handling-webservice-timeouts1 +Handling Webservice Timeouts - Parent
-
... ... @@ -1,1 +1,1 @@ 1 -Main.WebHome 1 +Main.eMagiz Academy.Microlearnings.Intermediate Level.SOAP Web service Connectivity.WebHome - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. eMagiz1 +XWiki.dfirdausy - Content
-
... ... @@ -1,18 +1,12 @@ 1 1 {{container}} 2 2 {{container layoutStyle="columns"}} 3 3 ((( 4 +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. In our previous [[course>>doc:Main.eMagiz Academy.Microlearnings.Novice.SOAP Web service Connectivity.WebHome]], we learned how to call a SOAP web service and how you can ensure that detailed faults are returned to the user. In this microlearning, we will build on this knowledge by learning what you can do when confronted with webservice timeouts from an external party. 4 4 5 -# Handling web service Timeouts 6 - 7 -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. In our previous [course](novice-soap-webservice-connectivity-index.md), we learned how to call a SOAP web service and how you can ensure that detailed faults are returned to the user. In this microlearning, we will build on this knowledge by learning what you can do when confronted with webservice timeouts from an external party. 6 +Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]]. 8 8 9 -Should you have any questions, please get in touch with academy@emagiz.com. 10 - 11 -- Last update: April 7th, 2022 12 -- Required reading time: 5 minutes 13 - 14 14 == 1. Prerequisites == 15 - -Basic knowledge of the eMagiz platform9 +* Basic knowledge of the eMagiz platform 16 16 17 17 == 2. Key concepts == 18 18 This microlearning centers around handling web service timeouts on SOAP Webservice calls. ... ... @@ -19,11 +19,11 @@ 19 19 20 20 With SOAP, we mean A messaging protocol specification for exchanging structured information in implementing web services in computer networks. 21 21 22 - -To manipulate the standard timeout on a SOAP web service in eMagiz, you need an HTTP Components message sender (support object)16 +* To manipulate the standard timeout on a SOAP web service in eMagiz, you need an HTTP Components message sender (support object) 23 23 24 24 == 3. Calling a SOAP Webservice == 25 25 26 -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. In our previous [course ](novice-soap-webservice-connectivity-index.md), we learned how to call a SOAP web service and how you can ensure that detailed faults are returned to the user. In this microlearning, we will build on this knowledge by learning what you can do when confronted with webservice timeouts from an external party.20 +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. In our previous [[course>>doc:Main.eMagiz Academy.Microlearnings.Novice.SOAP Web service Connectivity.WebHome]], we learned how to call a SOAP web service and how you can ensure that detailed faults are returned to the user. In this microlearning, we will build on this knowledge by learning what you can do when confronted with webservice timeouts from an external party. 27 27 28 28 By default, eMagiz will wait a maximum of 60 seconds to receive a response before throwing a timeout. However, sometimes we see that external parties need more time (for whatever reason) before they can respond to the request we send to the external party. At first, you should discuss alongside the external party whether the response can be delivered quicker to eMagiz to stay within the default timeout of 60 seconds. 29 29 ... ... @@ -41,29 +41,26 @@ 41 41 42 42 [[image:Main.Images.Microlearning.WebHome@intermediate-soap-webservice-connectivity-handling-webservice-timeouts--http-components-message-sender-linked.png]] 43 43 44 -== 4. Assignment ==38 +== 4. Key takeaways == 45 45 46 -Build a flow within your project in which you manipulate the default timeouts on a web service call. 47 -This assignment can be completed with the help of the (Academy) project that you have created/used in the previous assignment. 40 +* To manipulate the default timeout, use the HTTP Components message sender 41 +* Note that the values need to be supplied in milliseconds 42 +* Don't forget to link the support object to the functional component 43 +* Don't fill in a crazily high number for the timeout, as that could lead to slower processing of messages 48 48 49 -== 5. Keytakeaways ==45 +== 5. Suggested Additional Readings == 50 50 51 -- To manipulate the default timeout, use the HTTP Components message sender 52 -- Note that the values need to be supplied in milliseconds 53 -- Don't forget to link the support object to the functional component 54 -- Don't fill in a crazily high number for the timeout, as that could lead to slower processing of messages 47 +If you are interested in this topic and want more information, please read the help text provided by eMagiz and check out these links: 55 55 49 +* [[RCA Knowledge Base (Menu)>>doc:Main.eMagiz Support.RCA Knowledge Base.WebHome||target="blank"]] 50 +** [[Configuration Issues (Navigation)>>doc:Main.eMagiz Support.RCA Knowledge Base.rca-knowledgebase-configuration-issues.WebHome||target="blank"]] 51 +*** [[Timeout occurred on a web service call (Explanation)>>doc:Main.eMagiz Support.RCA Knowledge Base.Configuration Issues.rca-knowledgebase-timeout-occurred-on-webservice-call||target="blank"]] 52 +* [[Novice Level (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Novice.WebHome||target="blank"]] 53 +** [[SOAP Web service Connectivity (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Novice.SOAP Web service Connectivity.WebHome||target="blank"]] 54 +* [[Expert Level (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.WebHome||target="blank"]] 55 +** [[Webservice Security (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Webservice Security.WebHome||target="blank"]] 56 +*** [[WS-Addressing (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Webservice Security.expert-webservice-security-ws-addressing]] 57 +*** [[WS-Security (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Webservice Security.expert-webservice-security-ws-security]] 58 +* [[Webservice Timeout (Search Results)>>url:https://docs.emagiz.com/bin/view/Main/Search?sort=score&sortOrder=desc&highlight=true&facet=true&r=1&f_space_facet=0%2FMain.&l_space_facet=10&f_type=DOCUMENT&f_locale=en&f_locale=&f_locale=en&text=%22webservice+timeout%22||target="blank"]] 59 +)))((({{toc/}}))){{/container}}{{/container}} 56 56 57 -== 6. Suggested Additional Readings == 58 - 59 -If you are interested in this topic and want more information, please read the help text provided by eMagiz. 60 - 61 -== 7. Silent demonstration video == 62 - 63 -<iframe width="1280" height="720" src="../../vid/microlearning/" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe> 64 - 65 -{{video attachment="intermediate-soap-webservice-connectivity-handling-webservice-timeouts.mp4" reference="Main.Videos.Microlearning.WebHome"/}} 66 - 67 - 68 -((({{toc/}}))){{/container}}{{/container}} 69 -