Distributed Object Management and Transaction Processing Systems COMP 4101

Overview Introductions Course –Communication –Logistics –Process –Deliverables –Objective –Outline

Introduction Tony White, Associate Professor –Office: Herzberg 5354 –Tel: x2208 –Fax: – –Web: –Course:

Communication All course-related to have a subject line that contains the text “COMP 4101” All requests must be documented via , a verbal agreement is insufficient. Requests for extensions to an assignment or project deadline, changes in student lecture schedule must occur more than 24 hours prior to the deadline or lecture time. Failure to do this will result in the student being considered in default of the deadline. Notes for illness: I do require them.

Logistics Lectures: –Tuesday and Thursday 1:00pm-3:00pm, TB 236 Rescheduled classes: –None yet … Office Hours: –Tuesday and Thursday 11:30am-1:00pm –By arrangement, with confirmation of professor’s availability. Assignments: –Due by 11:55pm on date posted. –Late assignments will be not be accepted unless a deferral is granted. –Submission is using Raven system

Course Expectations Final: 20% –Will consist of multi-choice, definitions, and programming Project: 35% –Objective: build a distributed application using course techniques –Teams of 3/4 –Involves: Presentation (to class) Written report, demonstration and group oral (with professor) Midterm: 20% –Will consist of multi-choice, definitions, and programming Assignments: 25% –3 (or 4) assignments, submitted in teams of 2 –Poor testing or inadequate documentation will be heavily penalized –25% of assignment marks for testing and documentation Notes: –Assignments delivered using Raven system –JacORB Object Request Broker (ORB), JBoss, Eclipse available on epsilonXX

I provide: Lecture notes, study guides Assignments Assignment solutions Course news At: Link on or At

Software and Books Course Book (useful): –Engineering Distributed Objects Useful: –Enterprise Integration Patterns, Hohpe –Fundamentals of Distributed Object Systems, Bukres ORBs –JacORB: Application Servers –Lots of sites on JBoss!

Plagiarism Plagiarism n 1.A piece of writing that has been copied from someone else and is presented as being your own work 2.The act of plagiarizing; taking someone's words or ideas as if they were your own SourceSource: WordNet ® 1.6, © 1997 Princeton University

Results of Plagiarism If suspected, an oral examination will occur. For a first offence: –If confirmed, student will be given zero marks for the piece of work and the incident will be reported to the Director. On a second offence: –If confirmed, the student will be given an “F” grade for the course and asked to withdraw. The Director will be informed.

Objectives Design and programming of distributed object systems –Management of heterogeneity –CORBA Services: Naming, Location, Transaction etc Management –Enterprise Integration Patterns Communications, coordination –Service Oriented Architectures Important architectural components BPEL, Patterns, Management issues –New paradigms (as time permits) P2P: JXTA

Course of Study I What is a distributed system? Designing distributed objects Middleware for distributed objects CORBA, COM and Java/RMI Resolving Heterogeneity Dynamic Object Requests

Course of Study II Advanced Communication between D.O’s. Locating Distributed Objects Life cycle of Distributed Objects Persistence in Distributed Objects Distributed Object Transactions Security Patterns for Communication

Course of Study III Service Oriented Architectures –Concepts: service, registry, repository –Patterns Communication Design Lifecycle –Choreography Service composition

Course of Study IV P2P Computing –JXTA Concepts Patterns Applications Web Services –Principles –Technology