• serviceintel sa pripoji na demona emcommd, ktory prijme balicky (1)
• emcommd ich ?ulozi? do /opt/emtest/emcommd (aj ked ako temp adresar pouziva /tmp/emcommd/) (bindat.xml sa ulozi ako control.xml), dalej spusti nasledujuce skripty (spustenim emmaps skriptu sa spustaju startovacie skripty v /opt/emtest/etc/rc.d - poradie spustania vid podla obrazku hore):

//volanie skriptov v aplikacii emcommd
e_system ("/etc/init.d/emapps", "emapps", "stop");
e_system("opt/emtest/etc/init.d/flashmessage","flashmessage","start");
...
system("runapp /tmp/emcommd/ tgz_26985.img > /dev/null 2>&1");//takto to v skutocnosti nie je to je len priklad ako si to moze vyskladat
...
e_system("opt/emtest/etc/init.d/flashmessage","flashmessage","stop");
e_system ("/etc/init.d/emapps", "emapps", "start");

• skript /usr/sbin/runapp - skopiruje balicek z cesty /tmp/emcommd/ do /mnt/tmpfs/images zabezpeci vybratie postinstall.sh a install.sh z balicka - nasledne ich pusti

//cast skriptu runapp
cat "./1.data" | tar xz postinstall.sh 2> /dev/null
cat "./1.data" | tar xz install.sh 2> /dev/null
 
...
. ./install.sh
 
if [ -f ./postinstall.sh ]; then
       . ./postinstall.sh
fi

• install.sh rozbaluje balicek: tar xzvf /mnt/tmpfs/images/1.data ktory je v ceste /mnt/tmpfs/images do adresara /opt/emtest/
• aplikacia dataservice data rozbali do adresara, ktory je urceny podla polozky path v subore /opt/emtest/emcommd/control.xml (standardne je to cesta: opt/emtest/var/spool/incoming/)