1. One Stop Mail Service Bhattacharya, Tonmoy, Bhattacharya, Tonmoy, ttb3@buffalo.edu Hariharan, Rama Krishnan, rkh2@buffalo.edu MS in Engineering Science, University at Buffalo

2. Objectives  Implement an e-mail client service which unifies service provided by different email services.  Allow the user to provide the list of email accounts that needs to be managed.  Provide an interface for the user to access his accounts and view the mails in each account.  Provide basic authentication for user login.  Maintain a relational database service to maintain information pertaining to different users.

3. Project Explanation  Mash-up SOA application that unifies the user’s mail accounts from several online mail providers  Makes email management it easy for users of multiple email accounts.  Project undertaken to cater to online e-mail providers’ clients with multiple e-mail accounts across different services.  Project will ensure user operate on their accounts in a more organized, efficient and speedy manner – from a single application.  Project does so by storing the users log-in information to various email accounts using which the One Stop Mail Service logs into those email accounts.

4. Enterprise Design

5. Architectural Design

6. Technology Used  Java EE 5  Glassfish 9.1  Eclipse IDE

7. Design Choices  Used Java Web Services to create the service and client. Java annotations were used to map java methods to WSDL and conversely call service functions from them.  Java EE 5 technology was used throughout to enable the development of the project.  Web services deployed in Glassfish Application server.  Eclipse IDE was used for development of the project.  JSP was used in creation of the client web pages.

8. Implementation Details (Yahoo!)  Register the application with Yahoo - Provide URL of the application & get an application id.  Browser based user authentication (BBA) - One Stop Mail application redirects user to Yahoo login page for getting user’s login details. On authorizing, Yahoo! returns a token to the application using which the user’s mails can be retrieved.  Need for an external static ID. - Application registration and BBA made an external static IP necessary. Yahoo mail was not implemented as part of the One Stop Mail service because of this reason. - Application registration and BBA made an external static IP necessary. Yahoo mail was not implemented as part of the One Stop Mail service because of this reason.

9. Implementation Details (Gmail)  Google provides only Atom feeds for Gmail.  Made use of Google Data APIs to retrieve the Gmail atom feeds.  A new web service for accessing Gmail was created using this API.  One Stop Mail Service takes the user inputs for two mail accounts and invokes this Web Service twice to retrieve the mails of both ids.  Gmail allows only feed reading and so other operations like deleting, composing, moving a mail, etc is not possible.

10. DEMO

11. Why This is an SOA  Client invokes one stop mail service which invokes Gmail Web Services thus making the application an SOA.  The resolution of static external IP issue for and inclusion of yahoo mail checking facility will make One Stop Mail a full-fledged process enabled SOA.

12. Results  User’s Multiple Accounts Accessible from One Stop Mail  User Account Login Dynamically acquired.  Application is designed to enable easy future improvements.

13. Thank You