C. Tomlinson, P. Attie, P. Cannata, G. Meridith, A. Sheth, M. Singh, D. Woelk. Workflow Support in Carnot. In Data Engineering Bulletin, June 1993.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....and the fuzzy nature of the queries. InfoSleuth will build on Carnot semantic modeling capabilities to enable deep descriptions of available information sources. InfoSleuth will deploy semantic agents (based on the Rosette scripting language and the Carnot Extensible Services Switch (ESS) TOML93] to carry out distributed, coordinated, self adapting search algorithms. InfoSleuth agents will collaborate with each other and can remain active in the network to monitor events or the addition of new information. 3. Database Applications on the World Wide Web A Carnot based application ....

Tomlinson, C., P. Attie, P. Cannata, A. Sheth, M. Singh, and D. Woelk, "Workflow Support in Carnot", Data Engineering Bulletin, Vol. 16, No. 2, June, 1993, pp. 33-36.

....Furthermore, error handling (system or logical) using the dependencies is limited. WFSL also supports more types of tasks and interfaces and a flexible data transfer specification. Other, albeit less relevant, specification and language efforts are the script based workflow specification in Carnot [29], and the extensions to MSQL to support some features of workflows [27] For transaction processing environments, the STDL language [3] supports several features we consider to be important, including, support for tasks that are transactions, RPC based tasks, and queued tasks, as well as ....

....from several predecessors with which it shares its objectives and functionality. These include, among others, DOL [26] and the interfaces that support executions of heterogeneous tasks against different processing entities (e.g. LAM in Narada [18] RSI in Interbase [12] and ESS in Carnot [29]) 7 Conclusions Reengineering and automation of enterprise applications can be supported using workflow management that support coordinated execution of heterogeneous tasks on heterogeneous processing systems. We have discussed a workflow model and languages for specifying the workflows to ....

C. Tomlinson et. al. Workflow Support in Carnot. In

....class of compensatable transactions. Unlike many of these models, we do not view the entire application or the activities in only transactional terms, since several tasks can be non transactional. Other specification and language efforts are the script based workflow specification in Carnot [36], and the extensions to MSQL to support some features of workflows [33] and the STDL language [3] The ideas behind TSL have been borrowed from several predecessors with which it shares its objectives and functionality. These include, among others, DOL [32] and the interfaces that support ....

....from several predecessors with which it shares its objectives and functionality. These include, among others, DOL [32] and the interfaces that support executions of heterogeneous tasks against different processing entities (e.g. LAM in Narada [25] RSI in Interbase [17] and ESS in Carnot [36]) There have also been other approaches for multimedia document flow management [24] that are non transactional in nature. 4. METEOR s Integrated Approach In this section, we discuss the model, and the basic design decisions behind two languages for specifying multi system workflow ....

C. Tomlinson et. al. Workflow Support in Carnot. In [15].

....class of compensatable transactions. Unlike many of these models, we do not view the entire application or the activities in only transactional terms, since several tasks can be non transactional. Other specification and language efforts are the script based workflow specification in Carnot [34], and the extensions to MSQL to support some features of workflows [31] For transaction processing environments, the STDL language [3] supports several features we consider to be important, including, support for tasks that are transactions, RPC based tasks, and queued tasks, as well as ....

....from several predecessors with which it shares its objectives and functionality. These include, among others, DOL [30] and the interfaces that support executions of heterogeneous tasks against different processing entities (e.g. LAM in Narada [23] RSI in Interbase [16] and ESS in Carnot [34]) There have also been other approaches for multimedia document flow management [22] that are non transactional in nature. 4 METEOR s Integrated Approach Any solution for workflow management requires a careful trade off between the flexibility of the system, the functionality it can provide, and ....

C. Tomlinson et. al. Workflow Support in Carnot. In [14].

.... in an environment consisting of transaction monitors and event monitoring synchronizing facilities (e.g. similar to those proposed in CORBA [47] The first approach is aligned to the work reported in [12] Variants of the second approach are used in the Narada [27] Interbase [15] and Carnot [49] projects. The facilities provided by these projects may be used to implement relaxed transaction and workflow capabilities. GTE s Distributed Object Management (DOM) project [22] seems to follow a combination of the first two approaches by distinguishing between native DOM objects and data ....

.... IPL, such as more sophisticated format translation and information exchange facilities and coordination of concurrent workflows (termed global applications in [15] Carnot goes further in developing support for distributed services and applications, including relaxed transactions and workflows [52, 49]. Its main component, called an Extensible Services Switch (ESS) uses a language called Rosette based on an Actor model. Rosette supports interpretive control of distributed applications, high concurrency, and ultra lightweight processes. Since control programs or scripts are interpreted, one ....

C. Tomlinson, P. Attie, P. Cannata, G. Meridith, A. Sheth, M. Singh, D. Woelk. Workflow Support in Carnot. In Data Engineering Bulletin, June 1993.

....services, the task of providing communication facilities to customers. This task is executed in a heterogeneous multidatabase environment. It is an example of workflow control, in that it provides control and data flows among transactions executing on multiple autonomous systems [Jin et al. 1993; Tomlinson et al. 1993] Service provisioning typically takes several weeks and requires coordination among many operation support systems and network elements. Configuring the operation support systems so that they can perform such a task often takes several months to complete. We investigated ways to improve the ....

Christine Tomlinson, Paul Attie, Philip Cannata, Greg Meredith, Amit Sheth, Munindar Singh, and Darrell Woelk, "Workflow Support in Carnot," IEEE Data Engineering, 1993.

....develop prototypes for a few applications. These other applications can be characterized by the requirement to dynamically discover the requirement for collaboration and then dynamically discover the pattern of collaboration that should be followed. 2. Implementation of Rosette Agents Rosette [8] is a high performance interpreter for the Actor model [9] which has been enhanced with object oriented mechanisms for inheritance and reflection. It has been under development at MCC since 1988. With Rosette, the object oriented programming model and the Actor concurrent execution model are ....

Tomlinson, C., P. Attie, P. Cannata, A. Sheth, M. Singh, and D. Woelk, "Workflow Support in Carnot", Data Engineering Bulletin, Vol. 16, No. 2, June, 1993, pp. 33-36.

....research staff is able to run practical experiments to determine the optimal conditions under which each type of agent should be deployed. We are also investigating hybrid agent implementations with optimal features based on the type of application. Rosette Agents (Procedurally Scripted) Rosette [7] is a high performance interpreter for the Actor model [8] which has been enhanced with object oriented mechanisms for inheritance and reflection. It has been under development at MCC since 1988. With Rosette, the objectoriented programming model and the Actor concurrent execution model are ....

Tomlinson, C., P. Attie, P. Cannata, A. Sheth, M. Singh, and D. Woelk, "Workflow Support in Carnot", Data Engineering Bulletin, Vol. 16, No. 2, June, 1993, pp. 33-36.

.... object oriented command language based on the Actor model that incorporates sophisticated support for the dynamic definition of foreign language storage structures and typechecked access to procedures generated by foreign language processors and linked dynamically into the runtime environment [TOML93]. These features make it possible to rapidly integrate new facilities into Rosette and to configure software based on Rosette at runtime in the field. Rosette actors executing on different systems communicate through the Rosette Tree Space. The Tree Space is an enhanced implementation of the Linda ....

Tomlinson, C., P. Attie, P. Cannata, A. Sheth, M. Singh, and D. Woelk, "Workflow Support in Carnot", Data Engineering Bulletin, Vol. 16, No. 2, June, 1993, pp. 33-36.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC