<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns="http://purl.org/rss/1.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"><channel rdf:about="https://www.bibsonomy.org/user/cschie/service"><title>BibSonomy bookmarks for /user/cschie/service</title><link>https://www.bibsonomy.org/user/cschie/service</link><description>BibSonomy RSS Feed for /user/cschie/service</description><items><rdf:Seq><rdf:li rdf:resource="http://tibcoblogs.com/cep/2009/03/20/event-handling-boosted-in-bpmn-20/"/><rdf:li rdf:resource="http://architectguy.blogspot.com/2008/11/state-events-time-confusion-around-cep.html"/><rdf:li rdf:resource="http://elementallinks.typepad.com/bmichelson/2006/02/eventdriven_arc.html"/><rdf:li rdf:resource="http://geekswithblogs.net/cyoung/articles/118506.aspx"/><rdf:li rdf:resource="http://www.udidahan.com/2008/11/01/soa-eda-and-cep-a-winning-combo/"/><rdf:li rdf:resource="http://tibcoblogs.com/cep/2007/06/26/differences-between-a-bre-and-a-rule-driven-cep-engine-part-1/"/><rdf:li rdf:resource="http://www.dmreview.com/issues/2007_48/10001105-1.html"/></rdf:Seq></items></channel><item rdf:about="http://tibcoblogs.com/cep/2009/03/20/event-handling-boosted-in-bpmn-20/"><title>Complex Event Processing (CEP) Blog » Event handling boosted in BPMN 2.0</title><description>Bruce makes an interesting comment on business rules too: that “routing logic in process gateways” are not “business rules”. That doesn’t really make sense: for sure some gateways will be process-housekeeping decisions of little interest to the business user, but others will surely embed business-critical decisions. On the other hand, it has long been acknowledged that a best practice for BPM is to delegate such business decisions to a managed decision service - hence the explicit new business rule (aka decision) task in BPMN 2.0. And,in the CEP world, for tools like TIBCO BusinessEvents to invoke a decision managed by its Decision Manager tool.</description><link>http://tibcoblogs.com/cep/2009/03/20/event-handling-boosted-in-bpmn-20/</link><dc:creator>cschie</dc:creator><dc:date>2009-03-23T10:14:44+01:00</dc:date><dc:subject>TIBCO CEP event BPM service processing BPMN decision 2.0 rules business </dc:subject><content:encoded>&lt;span itemprop=&#034;description&#034;&gt;Bruce makes an interesting comment on business rules too: that “routing logic in process gateways” are not “business rules”. That doesn’t really make sense: for sure some gateways will be process-housekeeping decisions of little interest to the business user, but others will surely embed business-critical decisions. On the other hand, it has long been acknowledged that a best practice for BPM is to delegate such business decisions to a managed decision service - hence the explicit new business rule (aka decision) task in BPMN 2.0. And,in the CEP world, for tools like TIBCO BusinessEvents to invoke a decision managed by its Decision Manager tool.&lt;/span&gt;</content:encoded><taxo:topics><rdf:Bag><rdf:li rdf:resource="https://www.bibsonomy.org/tag/TIBCO"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/CEP"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/event"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/BPM"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/service"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/processing"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/BPMN"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/decision"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/2.0"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/rules"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/business"/></rdf:Bag></taxo:topics></item><item rdf:about="http://architectguy.blogspot.com/2008/11/state-events-time-confusion-around-cep.html"><title>A Software Architect&#039;s point of view: State, events, time - a view on the confusion around CEP</title><description>- leave anything related to transport, communication to other layers- use this revised CEP to express and execute event-relevant logic, the purpose of which is to translate the ambient events into relevant business events- have these business events trigger business processes (however lightweight you want to make them)- have these business processes invoke decision services implemented through decision management to decide what they should be doing at every step- have the business processes invoke action services to execute the actions decided by the decision services- all the while generating business events or ambient events- etc.</description><link>http://architectguy.blogspot.com/2008/11/state-events-time-confusion-around-cep.html</link><dc:creator>cschie</dc:creator><dc:date>2009-03-05T17:07:20+01:00</dc:date><dc:subject>CEP architecture complex confusion context decision event process processing rules service situation software state time view </dc:subject><content:encoded>&lt;span itemprop=&#034;description&#034;&gt;- leave anything related to transport, communication to other layers- use this revised CEP to express and execute event-relevant logic, the purpose of which is to translate the ambient events into relevant business events- have these business events trigger business processes (however lightweight you want to make them)- have these business processes invoke decision services implemented through decision management to decide what they should be doing at every step- have the business processes invoke action services to execute the actions decided by the decision services- all the while generating business events or ambient events- etc.&lt;/span&gt;</content:encoded><taxo:topics><rdf:Bag><rdf:li rdf:resource="https://www.bibsonomy.org/tag/CEP"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/architecture"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/complex"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/confusion"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/context"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/decision"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/event"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/process"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/processing"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/rules"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/service"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/situation"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/software"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/state"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/time"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/view"/></rdf:Bag></taxo:topics></item><item rdf:about="http://elementallinks.typepad.com/bmichelson/2006/02/eventdriven_arc.html"><title>Event-Driven Architecture Overview :elemental links</title><description>For those unfamiliar with business-driven architecture, I believe the most viable, agile architectures will be comprised of a blend of architecture strategies, including (but not limited to) service-oriented architecture, event-driven architecture, process-based architecture, federated information, enterprise integration and open source adoption.</description><link>http://elementallinks.typepad.com/bmichelson/2006/02/eventdriven_arc.html</link><dc:creator>cschie</dc:creator><dc:date>2009-03-05T16:43:05+01:00</dc:date><dc:subject>EDA SOA architecture driven event service </dc:subject><content:encoded>&lt;span itemprop=&#034;description&#034;&gt;For those unfamiliar with business-driven architecture, I believe the most viable, agile architectures will be comprised of a blend of architecture strategies, including (but not limited to) service-oriented architecture, event-driven architecture, process-based architecture, federated information, enterprise integration and open source adoption.&lt;/span&gt;</content:encoded><taxo:topics><rdf:Bag><rdf:li rdf:resource="https://www.bibsonomy.org/tag/EDA"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/SOA"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/architecture"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/driven"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/event"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/service"/></rdf:Bag></taxo:topics></item><item rdf:about="http://geekswithblogs.net/cyoung/articles/118506.aspx"><title>MS BRE: The Rules Engine Update (REU) Service and Policy Execution</title><description>The MS Rules Framework was a spirited attempt by MS to create a wide-ranging environment that could integrate rules held in different forms in different repositories, mange the deployment of rule sets out across an enterprise environment and even target a range of different rules engines.</description><link>http://geekswithblogs.net/cyoung/articles/118506.aspx</link><dc:creator>cschie</dc:creator><dc:date>2009-03-02T14:22:15+01:00</dc:date><dc:subject>engine enterprise environment framework ms policy repository rules service update </dc:subject><content:encoded>&lt;span itemprop=&#034;description&#034;&gt;The MS Rules Framework was a spirited attempt by MS to create a wide-ranging environment that could integrate rules held in different forms in different repositories, mange the deployment of rule sets out across an enterprise environment and even target a range of different rules engines.&lt;/span&gt;</content:encoded><taxo:topics><rdf:Bag><rdf:li rdf:resource="https://www.bibsonomy.org/tag/engine"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/enterprise"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/environment"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/framework"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/ms"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/policy"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/repository"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/rules"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/service"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/update"/></rdf:Bag></taxo:topics></item><item rdf:about="http://www.udidahan.com/2008/11/01/soa-eda-and-cep-a-winning-combo/"><title>SOA, EDA, and CEP a winning combo</title><description></description><link>http://www.udidahan.com/2008/11/01/soa-eda-and-cep-a-winning-combo/</link><dc:creator>cschie</dc:creator><dc:date>2009-02-27T12:59:26+01:00</dc:date><dc:subject>CEP EDA SOA architecture event service </dc:subject><content:encoded>&lt;a itemprop=&#034;url&#034; data-versiondate=&#034;2009-02-27T12:59:26+01:00&#034; href=&#034;http://www.udidahan.com/2008/11/01/soa-eda-and-cep-a-winning-combo/&#034; rel=&#034;nofollow&#034; class=&#034;description-link&#034;&gt;http://www.udidahan.com/2008/11/01/soa-eda-and-cep-a-winning-combo/&lt;/a&gt;</content:encoded><taxo:topics><rdf:Bag><rdf:li rdf:resource="https://www.bibsonomy.org/tag/CEP"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/EDA"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/SOA"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/architecture"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/event"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/service"/></rdf:Bag></taxo:topics></item><item rdf:about="http://tibcoblogs.com/cep/2007/06/26/differences-between-a-bre-and-a-rule-driven-cep-engine-part-1/"><title>Complex Event Processing (CEP) Blog » Differences between a BRE and a rule-driven CEP engine (Part 1)</title><description>Most BREs today are deployed as “decision services”, and are used in “stateless” transactions to make “decisions” as a part of a business process. A CEP application is instead processing multiple event streams and sources over time, which requires a “stateful” rule service optimized for long running. This is an important distinction, as a stateful BRE for long-running processes needs to have failover support - the ability to cache its working memory for application restarting or distribution. And of course long-running processes need to be very particular over issues like memory handling - no memory leaks allowed!</description><link>http://tibcoblogs.com/cep/2007/06/26/differences-between-a-bre-and-a-rule-driven-cep-engine-part-1/</link><dc:creator>cschie</dc:creator><dc:date>2009-02-27T10:41:49+01:00</dc:date><dc:subject>CEP EDA architecture business complex engine event processing rules service </dc:subject><content:encoded>&lt;span itemprop=&#034;description&#034;&gt;Most BREs today are deployed as “decision services”, and are used in “stateless” transactions to make “decisions” as a part of a business process. A CEP application is instead processing multiple event streams and sources over time, which requires a “stateful” rule service optimized for long running. This is an important distinction, as a stateful BRE for long-running processes needs to have failover support - the ability to cache its working memory for application restarting or distribution. And of course long-running processes need to be very particular over issues like memory handling - no memory leaks allowed!&lt;/span&gt;</content:encoded><taxo:topics><rdf:Bag><rdf:li rdf:resource="https://www.bibsonomy.org/tag/CEP"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/EDA"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/architecture"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/business"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/complex"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/engine"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/event"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/processing"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/rules"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/service"/></rdf:Bag></taxo:topics></item><item rdf:about="http://www.dmreview.com/issues/2007_48/10001105-1.html"><title>Maximize Business Value through Right-Time Information Using Data Services</title><description>Maximize Business Value through Right-Time Information Using Data Services</description><link>http://www.dmreview.com/issues/2007_48/10001105-1.html</link><dc:creator>cschie</dc:creator><dc:date>2008-10-15T14:49:37+02:00</dc:date><dc:subject>agility data latency real-time service </dc:subject><content:encoded>&lt;span itemprop=&#034;description&#034;&gt;Maximize Business Value through Right-Time Information Using Data Services&lt;/span&gt;</content:encoded><taxo:topics><rdf:Bag><rdf:li rdf:resource="https://www.bibsonomy.org/tag/agility"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/data"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/latency"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/real-time"/><rdf:li rdf:resource="https://www.bibsonomy.org/tag/service"/></rdf:Bag></taxo:topics></item></rdf:RDF>