Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
<strong>FIMS</strong> <strong>Media</strong> <strong>SOA</strong> <strong>Framework</strong> Phase1 (Preliminary)9.2 Asynchronous operations for long running process<strong>Media</strong> <strong>SOA</strong> workflows are often long running processes, sometimes active for hours, days, or even weeks. Thisplaces specific persistence requirements of the <strong>SOA</strong> BPM platform. Servers may be stopped or restarted whileprocesses are running, and the system needs to save state and be able to restart at the same point in theworkflow and process orchestration without loss or state or data.Many <strong>Media</strong> <strong>SOA</strong> service are external hardware or software based systems that operate in a loosely coupledasynchronous environment. Therefore if servers are stopped or started these services may continue running,and job process state must be recovered after the <strong>SOA</strong> system restarts.Asynchronous operation status updates may be implemented with either callbacks or polling depending on <strong>SOA</strong>platform architecture.The details of asynchronous communication are discussed in Section 8 <strong>Media</strong> Service Communication.Private committee documentWorking Draft for review by <strong>FIMS</strong> Rev v1, Nov-16-2010 Page 82 of 89
Change language