Welcome Guest! Log in


The forum is in read only mode.
Stambia versions 2.x, 3.x, S17, S18, S19 and S20 are reaching End of Support January, 15th, 2024. Please consider upgrading to the supported Semarchy xDI versions. See Global Policy Support and the Semarchy Documentation.

The Stambia User Community is moving to Semarchy! All the applicable resources have already been moved or are currently being moved to their new location. Read more…

Topic-icon Question Can we schedule a delivery on an event in Web Analytics

16 Jan 2015 17:05 #1 by Virginie_Samson
Can we schedule a delivery on an event in Web Analytics ?
Event like :
** File arrived
** something written in a table
** etc.

16 Jan 2015 18:08 #2 by Thomas BLETON
This has to be done in the Process development. Not in Analytics.

For example you can make a process with a FileWait action which will watch a specified directory every 10 seconds, indefinitely.
Have a look the attached process.
This attachment is hidden for guests.
Please log in or register to see it.

FileWait watches the "datafiles" directory and executes the "TreatFile" action for each file named "*.go". The idea is to bind an "ExecuteDelivery" action.

The SqlOperation action also has this kind of feature : use the parameters "Wait Nb Rows", "Wait Count Select", "Wait Poll Interval"...

If you don't want a permanent running process, you can set the timeout to some positive value, and schedule this process at your preferred periodicity.

This message has an attachment file.
Please log in or register to see it.

16 Jan 2015 18:23 #3 by Virginie_Samson
Replied by Virginie_Samson on topic Can we schedule a delivery on an event in Web Analytics
How many waiting process could we manage in the same time ?
Won't it use son server's memory ?
13 Feb 2015 15:55 - 13 Feb 2015 16:31 #4 by Thomas BLETON
This kind of process can be very small, if it is dedicated to "watching", and then launching a delivery as an Execute Delivery.
Here is a screenshot of "jvisualvm" (available in most JDKs), showing the memory used when lauching 1, 3, or 15 instances of the fileWaitForever process.
As you can see, there is no much difference : the peeks vary from about 25Mb to 30Mb. :)

Edit : this measure has been done without "input data", just to show the small impact on memory of those waiting action. In real life, if many FileWait actions receive many files at the same time, it is important to carry out some load testing and memory analysis.
Last edit: 13 Feb 2015 16:31 by Thomas BLETON.