Meeting Scheduling System Capstone Project - Team#5 Fall2007

Dr. Kwok-Bun Yue (Instructor) Mr. DIlhar De Silva (Project Mentor) Team Members:  Waleed Alsaglab (Team Lead)  Srikanth Tasupalli  Manoj Kumar  Rohit Rangera

 Project Abstract  Specification  Design  Interface  Solution  Conclusion Waleed Srikanth Rohit Manoj

RoboComm project is a meeting scheduling system that uses a Rules-based engine for implementing the rules of a successful meeting. Project main goal is to minimize the human interaction during the meeting scheduling.

 Meeting initiator: ◦ Suggest meeting times ◦ Invite attendees  Attendees: ◦ Accept ◦ Decline (and suggest new meeting time) 1/3 2/3

1/3 2/3

 Meeting initiator: ◦ Review meeting times suitability ◦ Confirm a meeting time 3/3

AJAX Tool kit Web Browser Apple Evolution Zimbra Sync Plug In Zimbra Client Outlook Zimbra MAPI Plug In Perl Script SMTP XML(JSON) HTTP/S XML HTTP/S XML HTTP/S Zimbra Server Tom cat My SQL Open LDAP Zimbra Architecture

o AJAX stands for Asynchronous Java Script and XML. o Ajax leverages Web 1.0 technologies to build rich user interactive interfaces. o Ajax is used to leverage the additional technologies of Zimbra Server o Zimbra Client is using JavaScript to build dynamic interface. o Zimbra Clients have secured remote access.

o Ajax is a web standard o Zimbra Clients applications have rich interactive user interface, look and feel of the web and integration with other web content.

o The Zimbra Server ties together OpenDAP, MySQL and Perl Script to build an integrated platform forming a mix of protocols, libraries and file formats. o Validates XML requests from the client. o The Zimbra Server is a mail-box server o All invocations to various internet services are made through Zimbra Server. o Concurrency in processing inputs and outputs. o Graphical search builder

o Zimbra has a relational database for managing mail-box data. o MySQL is compatible with open source licensing and distribution o MySQL has efficient caching for frequent updates. o The database creation is transparent to server.

o Open Source directory server o User identification and authentication.

o Sending and receiving mails.

 How does it work  Difference from if then statement

 Weekend Rule  Late and Early (must be within office hours)

 External  Internal

 VIP  Minimum percentage

 Collaboration Suite ◦ Server (Exchange server compatible) ◦ Web Client ◦ Calendar

First window when we put our URL

 Better AJAX Components  Better User Interface

 Separate Business logic From Process  Easier for Developer to Develop, Deploy, Modify, and Manage

 Based on Previously Existing Technologies (HTML and Java Script)  Better and Faster Interface

 Huge Project to Understand (ZIMBRA)  Primarily Developed For Unix  Understanding Jboss Rules

 Zimbra Succesfully Installed on All the Machines  Decided upon what changes we have to make on Current Version of Zimbra  Worked on Jboss Rules (Small Applications)

 Add Photo and Time Zone on Contact Info Page  Change the Create Meeting page and Add more Rules  Reply form with Choices of Time and Date for Invitees if they deny the meeting Request

 Zimbra  OpenLDAP  Mysql  Tomcat  Drools (JBossRules)