1 / 14

Notespace IOC Initial Operational Capability

Notespace IOC Initial Operational Capability. Rachel Hunt Viet Nguyen Griff Hazen Erich Smick Friday, March 6, 2003. Software and Hardware Preparation. System Requirements x86 CPU PostgreSQL 7.2.1 installed Tomcat4 installed

duke
Download Presentation

Notespace IOC Initial Operational Capability

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Notespace IOCInitial Operational Capability Rachel Hunt Viet Nguyen Griff Hazen Erich Smick Friday, March 6, 2003

  2. Software and Hardware Preparation • System Requirements • x86 CPU • PostgreSQL 7.2.1 installed • Tomcat4 installed • A signed SSL certificate installed on Tomcat4 (When SSL enabled) • Port 443 (SSL) configured on tomcat. • J2SE installed

  3. Software and Hardware Preparation (Servlet) • The servlet stores information about users and their notes using a PostgreSQL database • A simple database must be set up with two tables described on the following slides • Documentation about PostgreSQL can be found here: http://cubist.cs.washington.edu/doc/postgresql7/

  4. Current Servlet Status • Servlet is operational and installed on the deployment site. • Servlet administrators are on call and ready to support deployment.

  5. web.xml file: Configure the Servlet • Parameters to be defined by an administrator • Database URL (one of the following forms) • jdbc:postgresql:database • jdbc:postgresql://host/database • jdbc:postgresql://host:port/database • Database username • Database password • Minimum and Maximum username length • Minimum and Maximum password length • Minimum and Maximum note title length • Maximum note text length • Maximum email and name (not username) length • SMTPServer (for outgoing email) • Administrator Email

  6. Tables for the Database Users Notes name VARCHAR(x1) title VARCHAR(x5) username VARCHAR(x2) create_date TIMESTAMP password VARCHAR(x3) rec_mod_date TIMESTAMP email VARCHAR(x4) rec_view_date TIMESTAMP userid SERIAL PRIMARY KEY note_text VARCHAR(x6) ownerid SMALLINT noteid SERIAL PRIMARY KEY x1 = the maximum name length defined in web.xml file x2 = the maximum username length defined in web.xml file x3 = the maximum password length defined in web.xml file x4 = the maximum length of an email address defined in web.xml file x5 = the maximum length of a note title defined in web.xml file x6 = the maximum length of note_text defined in web.xml file *SERIAL is an auto-incrementing type

  7. Testing (Servlet) • The servlet database and interface have been extensively tested, and expose no known problems. • Primary testing tool: a web-based test container found at http://cubist.cs.washington.edu/~griff/ • This test container allows easy testing of database functions, error handling, and application interface.

  8. People Preparation (Servlet) • Griff Hazen and Erich Smick working together should be able to support the servlet • To make operations smoother a hired Tomcat4 expert would be helpful

  9. Software Preparation (Applet) • All specified functionality completed • No support software of its own • Readiness testing complete • Used human testing (since largely a GUI component) • In all cases of error, applet displays message and allows user the option of fixing the problem

  10. Site Preparation (Applet) • Anyone with correct drivers for java applets of the v1.4.1 variety should do fine • Applet has been tested in both of the major browsing environments: IE and Netscape • Must be able to use SSL connections • Should accept the security certificate of our servlet (or the applet won’t work)

  11. People Preparation (Applet) • Someone who’s familiar with our applet should be prepared to deal with users’ problems • Need not be overly familiar with the architecture, although reading the specs would be expected • Should also be familiar with other two parts, in case of interoperability issues

  12. Software Preparation (Midlet) • System Requirements: • Internet-capable, J2ME-enabled device - such as cell phone, cell phone emulator, or PDA • The two Notespace midlet files are 22 KB in size, with any internal storage requiring much less than 1 KB in size • The midlet has been exhaustively hand-tested by multiple users as well as tested through automated test cases

  13. Site Preparation (Midlet) • In order to run the Notespace midlet, the location of the servlet must be noted on the ns_midlet.jad file first. After that, the midlet files (ns_midlet.jad and ns_midlet.jar) may be installed on any J2ME-enabled device that has Internet capability.

  14. People Preparation (Midlet) • Notespace users can range from children to experienced engineers – Notespace has been designed to be user-friendly, simple to use, and easy to understand. • The primary requirement for further support will be handling problems the users may encounter, and creating further versions of the Notespace midlet if necessary. Further versions would be created, after feedback from the user group, by the original architect of the midlet.

More Related