Reasons for Change FEC 4/03The proposal seeks to make the objectives more detailed (and also - perforce! - split into the various domains :-). The name of the unit and the content for the handbook entry have also been changed to make the emphasis of the unit clearer to prospective students. None of these changes will make any significant difference to how the unit is actually taught.The prerequisites have been modifed to include a Java programming unit, since students without any previous Java programming experience were finding it hard to understand the necessary code.Reasons for IntroductionThis unit has been taught for several years as an elective in the Bachelor of Computing at Gippsland. This proposal is to add an alternative prerequisite to make the unit available to students in the Graduate Diploma of Computing at Gippsland, through the web-based enrolment system.

UGPSC 5/06: The prerequisites of this unit have been updated to ensure that students will understand and learn the contents better when they have a more advanced level of programming experiences.

ASCED Discipline Group classification: 020103 Programming

Distributed database systems: clients, servers, application servers, database servers, clusters of servers.

Distributed database architectures: single-tier, two-tier, multi-tier.

Implementation issues: performance, security, transactions.

Enterprise application server capabilities: hot deployment, clean shutdown, clustering, farming, load balancing, automatic fail-over.

Enterprise application coding: DBMS access, distributed components, messaging services, authentication, authorization, encryption, transactions, fat clients, thin (web) clients.

Exterprise application software development tools (both GUI and command-line).

Access to the University's computer systems through an Internet service provider is compulsory for off-campus students.

Distributed database systems: clients, servers, application servers, database servers, clusters of servers. Distributed database architectures: single-tier, two-tier, multi-tier. Implementation issues: performance, security, transactions. Enterprise application server capabilities: hot deployment, clean shutdown, clustering, farming, load balancing, automatic fail-over. Enterprise application coding: DBMS access, distributed components, messaging services, authentication, authorization, encryption, transactions. Exterprise application software development tools. Access to the University's computer systems through an Internet service provider is compulsory for off-campus students.

Roman, Sriganesh and Brose, Mastering Enterprise JavaBeans, Third Edition, Wiley, 2004, ISBN 0764576828 (textbook). ?Note: Hope to use the Fourth Edition if it is published in time for 2007.?

Monson-Haefel, Burke and Labourey, Enterprise JavaBeans, Fourth Edition, O'Reilly, 2004, ISBN 059600530X.

Sierra and Bates, Head First EJB (Brain-Friendly Study Guides; Enterprise JavaBeans), O'Reilly, 2003, ISBN 0596005717.

Boone, Applied Enterprise JavaBeans Technology, Prentice Hall, 2002, ISBN 0130449156.

Wutka, Special Edition Using Java 2 Enterprise Edition, Que, 2001, ISBN 0789725037.

Marinescu, EJB Design Patterns, Wiley, 2002, ISBN 0471208310.

Alur, Malks and Crupi, Core J2EE Patterns: Best Practices and Design Strategies, Second Edition, Prentice Hall, 2003, ISBN 0131422464.

JBoss AS 4.0 or later (http://www.jboss.org/products/jbossas)

JBoss-IDE 1.4.0 or later (http://www.jboss.org/products/jbosside)

J2SE 1.5.0 or later (http://java.sun.com/j2se/index.jsp)

Required by: Start of week 1

Tester: Douglas Thomson

Licensing: Freely distributable

(Note: Some kind of virtual PC environment may be required depending on how JBoss is installed.)

FIT1007 or GCO1812 or equivalent