Ilan,
I'm a little confused -- do you want to have flume data sent to your application where it can be processed or do you want your application to generate data and send it to a flume node elsewhere?
If you want to embed flume into your application and use it to send data there is roughly 3 ways to do it.
1) embed a sink. instantiate a rpcSink and create events and append the events to the sink. no heartbeats (thus no central config, no direct e2e), and in the same thread as your app.
2) embed a logical node. you'd have a custom source. There is no heartbeat.
3) embed a physical node. This would include the heartbeating mechanism, and allow the node to be centrally configed and work with e2e mode.
I'd suggest option 1 since it is the simplest. It could be used to feed a "normal" flume node on the same machine.
Jon