Skip to Content

Changes for page Interpret Statistics

Last modified by Erik Bakker on 2024/02/20 09:09
From version 35.1
edited by Erik Bakker
on 2023/01/20 12:11
Change comment: There is no comment for this version
To version 39.1
edited by Erik Bakker
on 2023/01/20 12:15
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -13,11 +13,14 @@
13 13  
14 14  Now that we have a running solution we should be able to see logging and runtime statistics in Manage. So as a first exercise please check the logging and runtime statistics of your deployed solution.
15 15  
16 -Once you have confirmed that you see the logging and the runtime statistics it becomes time to send some data through the system so we can analyze whether that went as expected and data arrives at the end system. For this to work you need to save the following example file locally
16 +Once you have confirmed that you see the logging and the runtime statistics it becomes time to send some data through the system so we can analyze whether that went as expected and data arrives at the end system. For this to work you need to save the following example file locally as an XML file and place it in the input directory you have defined in your properties.
17 17  
18 -
19 19  * [[Example Message (Multiple Orders CAPE)>>attach:Main.Images.Exercises Crash Course.WebHome@multi-order-cape.xml||target="blank"]]
20 20  
20 +Assuming you configured everything correctly eMagiz will retrieve your file and will output two files on the basis of this. We can track the message(s) with the help of our queue statistics functionality.
21 +
22 +{{info}}Note, that when you do not see the expected behavior you should check the "Error Messages Dashboard" and the "Logging".{{/info}}
23 +
21 21  == 3. Solution ==
22 22  
23 23  In this short movie, you will find the workout of this exercise. Take a moment to review this one and compare it to your solution.