Workflow (via Internal/External Stored Procedures and Trigger-based Routing)

• Enterprise processes organize and group sets of related transactions
• Interorganizational process networks as "supply chains" or "demand chains"
• Enables the configuration of distributed, networked enterprises or enterprise components into a virtual enterprise.
• Example architecture for networked enterprise system component
• Process workflows enable
• Task guidance
• Just-in-time training
• Performance monitoring for process improvement
• Administrative or regulatory control
• Workflows as process instances
• Automated workflows bring work items (transactions, queries, data entry forms, documents, etc.) to the user
• Via message-based routing (e.g., Email)
• Via DBMS triggers
• Storing, retrieving and invoking computer-supported workflow actions (including application or query invocation) as stored procedures in DBMS vs. as separate Web server application programs ("servlets") 
• Example (Flash demo using Zope CMS)
• An ECommerce/EBusiness example of a Web-based business process for Acquisition/Procurement
• Uses DB to store: 
• relations for workflow precedence and decomposition 
• location (e.g., hyperlink URL) of large document types (e.g., proposal, budget, best practices, etc.) stored within an external repository 
• Supporting multi-tasking, multi-processing and other forms of concurrent coordinated enterprise work
• Version control applied to shared artifacts
• Tracking (status of ) problem or defect reports, or customer requests 
• cf. CRM
• Collaboration tools (e.g., distributed authoring/editing, fine-grain transaction locking)

Data Syndication and Information Logistics

• The practice of coordinating the aggregation, transport, delivery, and installation of large sets of data.
• The Information and Content Exchange (ICE) protocol is a proposed Web standard for data syndication. 
• Also see Content Distribution Systems (vs. CMS) for syndicating news wire feeds like Slashdot (or get your own open source CDS from Slashcode)
• Example application: network broadcast of  region-specific radio/TV commercials via local affiliates.

• Aggregation: Bringing together disparate sources of routinely produced data (e.g., daily news stories, comics, music videos) as content for an audience of interested consumers of that data.
• Uses Publish and Subscribe messaging infrastructure (cf. DBM System Architectures) across a virtual private network (a within firm Intranet, or across multiple firms Extranet).
• Oftens requires transformation of source materials into pre-defined delivery forms
• Using XML, XSL, XSLT
• Requires content licensing (copyright and property rights management), payment and billing services.
• Transport: Using bulk file transfer services and protocols that are reliable, though not necessarily fast. For example:
• specially-tuned version of FTP, the file transfer protocol) 
• Real-time streaming protocol (RTSP) used for video streaming services
• Internet caching services (e.g., Inktomi, Akamai, Digital Island) may be employed via contract to assist in bulk transport and delivery.
• Delivery: Browser, "set-top" players, and mobile devices that enable the consumers to access and view the content. These require some form of registration or remote recognition (e.g., via "cookies") to determine how to best format content for consumption
• Installation: A variation of delivery where content must be transferred and configured into the consumer's local repository.
• Can have nasty side-effects (e.g., searching for and breaking competitor offerings)