Posts tagged Sensor
Last night, the AMIS Mobile Special Interest Group convened. This session had as objective to explore the many different mobile agents and devices that we encounter, the types of signals, information and functions that are relevant with these various agents and the impact their inclusion in the mobile sphere of our customers has on the enterprise applications and architecture.
Our guest speaker – Rolf Hut of the Faculty of Civil Engineering and Geosciences – did an excellent job of introducing a new class of mobile agents with his presentation on hydro-meteorological stations. He even had us all build rain-sensors, from easily accessible and very cheap materials. 10 minutes of super-glueing, soldering and kindergarten-level handcrafting was all it took for 6 teams to create a sensor that could be connected to a laptop to register simple signals.
From this very practical example, it was not hard to envisage a wide network with hundreds or thousands of devices that report findings – to be processed by the backend infrastructure.
See Rolf presenting on YouTube: http://www.youtube.com/watch?v=Nh7GDD3Ssr8&feature=player_embedded#at=44.
Investigation into the true parallellism of the Oracle BPEL PM Flow activity in 11g (Technical Preview 4) – on flow, sequence, wait and (a)synchronous calls
The Flow activity is used to configure parallel activity in BPEL processes. In theory, activities contained in two or more branches (sequence containers) inside a Flow activity are executed in parallel. However, some sections in the BPEL PM documentation raise some doubt: "By default, Oracle BPEL Process Manager executes in a single thread, executing the branches sequentially instead of in parallel". I am not sure exactly what this means. But it certainly suggests that what I assumed to be pure parallel branches are in fact activity sequences that are both carried out, but sequentially! Time to investigate…
In this article, we will go through a number of steps to ascertain what exactly the parallellism for the Flow activity is. Note that I did this research in the 11g TP4 release of the SOA Suite. I will repeat the analysis in the 10g stack – as some findings seem erroneous and are perhaps due to the status of the Technical Preview. (more…)
When developing and/or debugging BPEL processes, the Oracle BPEL Console is your best friend. Every change to every variable, every activity that was executed, everything is right there for you to inspect, whether the instance is still in-flight or already completed. But although this sounds like the ultimate debugging tool, Iâ€™m sure youâ€™ve noticed like me that when your processes get really big (which they tend to do rather quickly), thereâ€™s two reasons why debugging can be difficult. The first is plain and simple â€œinformation overloadâ€. If your audit flow contains hundreds of activities and possibly thousands of variable data changes, finding an individual piece of information is not trivial. I find the second reason, however, to be of even more profound impact: the BPEL console will not show you the execution path through your process flow (which would indicate which parts of the code got executed, and which didnâ€™t), but rather it displays a long, sequential list of Activities that were executed. Especially if you have a lot of switch and/or pick statements, and if your code contains loops (in which case each iteration will add all executed Activities to the list), More >