Team Members:

• Dawei Gu mailto:dwgu@cs.cmu.edu
• Maneesh Sharma mailto:maneeshs@andrew.cmu.edu
• Morgan Linton mailto:mlinton@andrew.cmu.edu
• Wei Zhang mailto:wzhang@cs.cmu.edu

Team Roles:

• Dawei Gu - Application, Performance Analysis, Reliability
• Maneesh Sharma - Application, CORBA Analysis
• Morgan Linton - Application, Documention, Database Connectivity
• Wei Zhang - Application, Web Services

Project Title: Unicommerce

Baseline Application Description:

Configuration:

• Middleware - CORBA
• Operating System - Windows XP
• Programming Language - Java

Third-party software, if any (databases):

• Database - MS SQL Server
  

Baseline Application Features:

• Allow users to post and read messages
• Categorize messages by type, sender, date, etc.
• Personalized account and purchase history
• Allow users to search for items and listings

Reliability Requirements:

• Transactions preserved under system failure
• User accounts saved under system failure
• All posts backed-up and restored should a system failure occur

Real-Time Requirements:

• User post appears on the system within one minute of sending post
• User can login to system and have all settings loaded in two seconds
• Server can start in ten seconds
• Search results are returned to user in two seconds

Performance Requirements:

• System can support profiles for 100 users
• System can support five simultaneous transactions
• Support for 100 transactions in one minute
• Database can support up to 1000 items

Architectural Diagram

Scenarios/Interactions

Interfaces [ View IDL Interface]

Downloads [Source Code Package]

Building & Running Procedure

• How to build the baseline application?

• How to run the baseline application?

Acceptance Test/Use Case

• Acceptance Test #1

CVS Setup Steps

Scenarios/Interactions

• Server replicas can be registered using different names
• Client catches CORBA exceptions indicating that primary replica died
• Client remembers failed operation
• Client switches over and binds to backup replica
• Client re-invokes failed operation
• Failed primary is re-started and brought back into service

Description of our Fault-Tolerance Architecture

Architecture Details

How to Build the Fault-Tolerant Baseline Application

Click Here for Step-By-Step Guide Setup Guide

How to Run the Fault-Tolerant Baseline Application

Click Here for Step-By-Step Guide Setup Guide

Tests

Test #2 - Client switches over and binds to backup replica when primary fails

Test #3 - Replication manager re-starts the failed primary

Current Status

• Completed

Downloads

All source files for this project may be downloaded from the src folder in the team's webpage directory. To access this directory, simply ftp (or telnet) into an ece machine and change directory to: /afs/ece.cmu.edu/class/ece841/public_html/team4/src

Data and Graphs

• Colocated Free

• Colocated Fault

• Distributed Free

• Distributed Fault

Load Manager

• View Diagram

Current Status

In Progress

Downloads

Scenarios/Interactions

Current Status

Downloads