Skip to Content
Last modified by Danniar Firdausy on 2024/09/18 21:36
From version 9.9
edited by Danniar Firdausy
on 2024/09/13 09:06
Change comment: There is no comment for this version
To version 9.10
edited by Danniar Firdausy
on 2024/09/18 21:36
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,7 +1,7 @@
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 +In our previous [[module>>doc:Main.eMagiz Academy.Microlearnings.Novice.SOAP Web service Connectivity.WebHome]], we explored how to call a SOAP web service and manage detailed faults. Building on that foundation, this microlearning will focus on addressing web service timeouts from external parties. We’ll cover how to adjust the default timeout settings in eMagiz using the HTTP Components message sender to ensure smoother communication with external services.
5 5  
6 6  Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]].
7 7  
... ... @@ -10,9 +10,7 @@
10 10  
11 11  == 2. Key concepts ==
12 12  This microlearning centers around handling web service timeouts on SOAP Webservice calls.
13 -
14 -With SOAP, we mean A messaging protocol specification for exchanging structured information in implementing web services in computer networks.
15 -
13 +* With SOAP, we mean A messaging protocol specification for exchanging structured information in implementing web services in computer networks.
16 16  * To manipulate the standard timeout on a SOAP web service in eMagiz, you need an HTTP Components message sender (support object)
17 17  
18 18  == 3. Calling a SOAP Webservice ==
... ... @@ -37,10 +37,10 @@
37 37  
38 38  == 4. Key takeaways ==
39 39  
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
38 +* Use the HTTP Components message sender to customize the default timeout settings for SOAP web service calls.
39 +* Enter timeout values in milliseconds. For example, a 120-second timeout should be set as 120000 milliseconds.
40 +* Ensure you connect the HTTP Components message sender to the web service outbound gateway for the settings to take effect.
41 +* Setting an excessively high timeout could delay the processing of other messages, as eMagiz processes one message at a time by default.
44 44  
45 45  == 5. Suggested Additional Readings ==
46 46