Advanced Search

Journal Navigation

Journal Home

Subscriptions

Archive

Contact Us

Table of Contents

Click here to sign up for SAGE Journal Email Alerts today!

Sign In to gain access to subscriptions and/or personal tools.
Concurrent Engineering
This Article
Right arrow Full Text (PDF)
Right arrow References
Right arrow Alert me when this article is cited
Right arrow Alert me if a correction is posted
Services
Right arrow Email this article to a friend
Right arrow Similar articles in this journal
Right arrow Alert me to new issues of the journal
Right arrow Add to Saved Citations
Right arrow Download to citation manager
Right arrowRequest Permissions
Right arrow Request Reprints
Right arrow Add to My Marked Citations
Citing Articles
Right arrow Citing Articles via Google Scholar
Right arrow Citing Articles via Scopus
Google Scholar
Right arrow Articles by Lapinski, M.
Right arrow Articles by Sobolewski, M.
Right arrow Search for Related Content
Social Bookmarking
Add to CiteULike   Add to Complore   Add to Connotea   Add to Del.icio.us   Add to Digg   Add to Reddit   Add to Technorati   Add to Twitter  
What's this?

Managing Notifications in a Federated S2S Environment

Michael Lapinski

GE Global Research, One Research Circle, Niskayuna, NY 12309, USA

Michael Sobolewski

Computer Science, Texas Tech University, Box 43104, Lubbock, TX 79409-3104, USA

The goal of the Federated Intelligent Product Environment (FIPER) is to form a federation of distributed services that provide engineering data, applications and tools on a network. A highly flexible software architecture has been developed, in which engineering tools like computer-aided design (CAD), computer-aided engineering (CAE), product data management (PDM), optimization, cost modeling, etc., act as distributed service providers and service requestors. Service providers can enter the federation by registering with a service registry and publish the services through a process of discovery and join. An environment like this requires a mechanism for interprocess message passing from services to clients, services to services, and even clients to clients. The design issues of such a system and its implementation in the FIPER environment are described.

Key Words: distributed systems • network centric computing • notifications • Peer-to-Peer (P2P) • Service-to-Service (S2S) • JINI • Java • RMI • Servlets • disconnected clients • web-based applications • federated services • concurrent engineering • and generic service framework

Concurrent Engineering, Vol. 11, No. 1, 17-25 (2003)
DOI: 10.1177/1063293X03011001002
Add to CiteULike CiteULike   Add to Complore Complore   Add to Connotea Connotea   Add to Del.icio.us Del.icio.us   Add to Digg Digg   Add to Reddit Reddit   Add to Technorati Technorati   Add to Twitter Twitter    What's this?