figures - Rochester Institute of Technology
Contents
1. Boana 7 Figure 19 Viewing the defect s contents San H Aung Page 15 of 21 Web based Distributed EJB BugsTracker 3 5 PROJECT ADMINISTRATION CATEGORY 3 http localhost 8080 bugweb prjAdmin do Microsoft Internet Explorer File Edit View Favorites Tools Help Back Y gt Q A A Gsearch Favorites meda Sl Ar 3 a RHO YD Address http ocalhost 8080 bugweb prjAdmin do EJB Login as sanl 3 BugTracker l l JavaHelp Main Page Bugs Tracking ProjectAdmin JUserA dmin Log Off All Available Projects a in Project Name Description Created E El Kodak El dl Xerox Project LastModified 12 0413 05 11 17 48 44 Pees 21 Kack Pate Dw 05 11 2003 05 11 2003 17 48 56 Ed E Done pe a Local intranet a Figure 20 Project Administration main page The primary purpose of the Project Administration Figure 20 as the name implies is for managing the following tasks 1 To create a new project the system administrator must click at new project icon E depicted in Figure 20 where leads to the creation of new project page depicted in Figure 21 2 To edit existing project the project manager must click on the edit icon E depicted from Figure 20 where leads to the edit page for the defect depicted in Figure 22 3 To delete existing project 1f that is permitted by the administrator project manager must click on the delete icon D that results in casca2. 9 Appending notes for audit trail San H Aung Page 12 of 21 Web based Distributed EJB BugsTracker EJB BugsTracker Microsoft Internet Explorer File Edit View Favorites Tools Help Back gt A A QSearch Favorites Meda SB Ary 3 aaa YM Address http ocalhost 5080 bugweb bugTrackEditBug do BugId 1 EJB Login as admin BugsTracker ae Home Project List Project Admin User Admin Log Off iak Project uist user Admin Log of Edit defects no 1 Summary Kodak s defect reported by tester Status Open y Assigned to devKodak y Severity Enhancement y Enter by tester Component PC y Version 1 7 Description Steps to Reproduce detail steps to reproduce the defect El Audit Trail Updated by Defect history Updated On i tester New Bug Created 07 29 2003 14 42 12 2 admin Assigned to changes devKodak to admin 07 29 2003 14 46 09 3 admin 07 29 2003 15 54 39 4 admin Severity changes Minor to Critical 07 29 2003 15 56 50 Severity has been changed to Critical by Admin user 5 admin Assigned to changes admin to devKodak 07 29 2003 16 46 18 6 devKodak 07 29 2003 16 52 24 Appending of defect s note to the audit trail could be as long as size of the Java data type String at the memory space however the backend database has its own limit As a result the storage sizes for the Java String will depend on the type of the database server 7 admin Assigned to
3. Project List Page Summary of available projects 2 1 Reporting a new defect on a specific project 2 2 Listing all defects from authorized project 2 2 1 Editing defects with its audit trail 2 2 2 Viewing defects with its audit trail 3 Project administration Page normally accessible to project manager 3 1 Creating new project by administrator 3 2 Editing existing projects by the project manager 3 2 1 Defining new versions for a specific project by the project manager 3 2 2 Defining new components for a project by the project manager 3 3 Deleting existing project by project manager Cascade Deletion 4 User administration Page normally accessible to administrator 4 1 Creating new users by administrator 4 2 Editing a user profile and its permission for a specific project 4 3 Deleting existing users by the administrator 5 Logoff Filter defects status PA I A fA l L SN 1 Home 2 Project List 3 Project Admin 4 UserAdmin 5 Logoff N j SN N ho 4 3 Delete User 1 1 Edit Defects 4 1 NewUser 4 2 EditUser S Exclusivel 2 1 Report new defect XCIUSIVEIY 3 1 New Project Permitted to Super Users 3 2 1 New Versions 3 2 2 New Components 2 2 List defects for each project 3 3 Delete prj 3 2 Edit Project 2 2 1 Edit defect 2 2 2 View defect Figure 11 All access paths for each screen San H Aung Page 10 of 21 Web based Distributed EJB BugsTracker 3 USER M
4. table for the first super user admin admin c rr 9 Figure 11 All access paths for each screen EEE EEE 10 Figure 12 login DATE AAA A e a a e ai Il Figure 13 Welcome page right after user login POeeeeeeeeee eer err eer ere ee rere eer ere eer ee ree eer rere eer errr rere err ee reer ee rer eee eee reer Il Figure 14 Currently login user K Home page E E E E E E E E E 12 Figure 15 Editing defects rr E E T 13 Figure 16 Project 5 SUIMMGALY DAG meee ene NIST AON TIE REAM e coto 14 Figure 17 Reporting new defect rr ereereere ere ere ree eee re sree reer rere ere reer ere erie 14 Figure 18 listing of all defects associated with the given project Kodak 11 rrr 15 Figure 19 Viewing the defect R616 7112111 ee cece 15 Figure 20 Project Administration main E O ee 16 Figure 2I Creating new project by system OVINA KYA A016 A 16 Figure 22 Editing of existing project rr a rere rire reer eee eee 17 Figure 23 User administration main page where list all available users to the system tr 18 Figure 24 Creating a new user by the administrator e ecrterrrerrrrrnrnrnnnonn roca non n nn nro nro n non ron c non nro nano nnroncranncnnnnno 18 Figure 25 Editing user permissions and its profiles A a T 19 San H Aung Page 3 of 21 Web based Distributed EJB BugsTracker 1 PROJECT INSTALLATION 1 1 INSTALLING J2SDK If you have J2SDK installed on your system please skip this section For those who do not have J2SKD on the system you will need to download
5. EJBs and Web Components Q conf 0 logs 61 03 server 03 shared 2 temp E H O webapps 4 work gt E 24 TS Disk free space 32 4 MB 1 1 02 MB ar My Computer aA Figure 3 Directories structure of JBoss is on the left and the deployment files are on the right 1 3 RUNNING INTEGRATED SERVER TOMCAT JBOSS AND HSQL DB Depicted in Figure 4 change the current directory under JBOSS_HOME bin directory and launch the run script that matches the OS e For Unix run sh e For Windows E jboss 3 0 7 J tomcat 4 1 24 bin gt run Shortcut 35 to JbossConsole rosoft Windows 2000 version 5 00 2195 te F Copyry ight 1985 2000 ee alee Corp a tomcat 4 1 241b1n run lE 4Jboss 3 0 7_Jakar Figure 4 Run JBoss server in Windows 2000 If everything is setup correctly administrator should see the following text at the end of the run script e Server JBoss MX MicroKernel 3 0 7 CVSTag JBoss_3_0_7 Da te 200304081816 Started in 0m 13s 439ms If you get to this point with no error messages HSQL database server Tomcat Web Server and JBoss Application Servers are up and running San H Aung Page 5 of 21 Web based Distributed EJB BugsTracker 14 DEPLOYMENT OF EJBS AND WEB SERVER COMPONENTS Application deployment process in JBoss is straightforward In each configuration a specific directory is constantly scanned for changes by JBoss The default location is JBOSS_HOME server default deploy This directory is inform
6. INF c 055 3 _jakarta tomcat 4 1 24 tomcat 4 1 s work Maingngine TOCE INF c asses O Engine a o paper Deploy JAR WEB INF 1ib strut OF cat 24Ntomcat 4 1 work MainEngine local Lear Contex ctConfigl bugweb Added certificates gt reques EmbeddedCatalinaService41 Using Java parent classloader de Engine _StandardManager bugweb Seeding random number gene ecureRandom lengine oe anew e a e a Seeding of random number g completed Engine Standardwrapper bugweb default Loading container Engine Standardwrapper bugweb invoker Loading container MessageResour ces 5 Initializing config org apache s dul l true 3 geResc es config org sSageResou peek Initializing config Applicationr 59 er Deploy yed package file E jboss 3 0 7_jakarta tomcat 4 1 24 server ni bugweb war San H Aung Page 6 of 21 Web based Distributed EJB BugsTracker Figure 5 Completion of EJBs and Web components deployment 1 6 RUNNING HSQL DATBASE MANAGER Get another DOS command prompt and run the HSQL database manager by typing the following commands as show in Figure 6 java cp server default lib hsqldb jat org hsqldb util DatabaseManager le Shorteut 3 to IbosstConsole Mi croseft windows 2000 version 0 Copyright 1985 2000 Mi a Corp ta tomeat 4 1 24 binejava cp ser ver fdefault lib hsaldb jl ata He as eManager Figure 6 Running HSQL Database Manager Default The default server port
7. for the database server is being setup at 1476 To connect to the database from Database Manager type the full address of URL dbc hsqldb hsql localhost 1476 as in Figure 7 and press OK Connect x Type HSQL Database Engine Server Driver forg hsqldb jdbeDriver Password FO Ok J Cancel java sql SQLException Connection is broken Connection refused connect Figure 7 HSQL Database manager connection San H Aung Page 7 of 21 Web based Distributed EJB BugsTracker 1 7 INITIALIZING THE NEW DATABASE Before doing anything Database administrator must first initialize the new database by copying the following SIX SQLs to the Database Manager and click at the execute button as shown in the Figure 6 These SQL entries are critical since the Container Management Bean is totally dependent upon the table name IDS so that it can generate independent primary keys regardless of any database servers INSERT INTO IDS tablename nextid VALUES AS 1 INSERT INTO IDS tablename nextid VALUES Bug 0 INSERT INTO IDS tablename nextid VALUES o 0 INSERT INTO IDS tablename nextid VALUES Permission 0 INSERT INTO IDS tablename nextid VALUES istoryBuas 0 INSERT INTO IDS tablename nextid VALUES Version 0 INSERT INTO IDS tablename nextid VALUES Penrenenel Or INSERT INTO USER 1D LOGIN SUPER USER VALUES 0 UnAssign TRUE INSERT INTO USER 1D LOGIN PASSWORD SUP
8. is to manage the users profile and the permission features on projects and its related defects The administrator is in charge of following three options in this category 1 To create a new user the system administrator must click on new icon H that leads to the create new user page depicted in Figure 24 2 To edit or update an existing user s profile the administrator must click on edit icon EI to get the edit user s permission page depicted in Figure 25 3 To delete an existing user the administrator must click on the delete icon o which gets to back to the user administration main page depicted in Figure 25 57 http localhost 8080 bugweb user AdminNewUser jsp Microsoft Internet Explorer maxi File Edit View Favorites Tools Help EBack v gt A A Asearch Favorites meda S Br 3 a ag 2 Address http localhost 8080 bugweb userAdminNewlUser jsp v Go EJB Login as sanl 3 BugTracker Taho Main Page BugsTracking ProjectAdmin UserAdmin Log Off Login Password First Namel Last Namel Email Super User e Yes cNo Submit El A TE sacan xy Figure 24 Creating a new user by the administrator San H Aung Page 18 of 21 Web based Distributed EJB BugsTracker EIB BugsTracker Microsoft Internet Explorer File Edit View Favorites Tools Help Back gt A A Gsearch GaFavorites iedia 4 Er 3 a agy Address http ocalhost 5
9. user will NOT be listed on this home page The filter options at the upper right hand corner of the page helps the user to categorize and manage his or her defects according to the defect s status EIB BugsTracker Microsoft Internet Explorer i lol x File Edit View Favorites Tools Help Back gt 2 A Asearch GFavorites BPmeda 4 B 3 a agy 2 Address E http focalhost 8080 bugwebmainMenu do v Go EJB Login as admin AO AP EuosTracker Joule ject List Project Admin User Admin Log Off admin Home Page Filter Defect s Status AI y All defects for admin Defect summary Project name Severity Status Last Modified Kodak s defect reported by tester Kodak Critical 07 29 2003 15 56 50 Xerox s defect reported by tester Xerox Major 07 29 2003 15 57 03 RIT s defect reported by tester RIT Minor 07 29 2003 15 56 10 Local intranet Figure 14 Currently logged in user s Home page Continue moving forward from home page Figure 14 the only available option to the user is either the edit or the view defects Click at the edit icon El next to the defect summary leads to the edit page Figure 15 where the users can micro manage the following modifiable contents of the defect 1 Defects summary 2 Defect s status 3 Defect s assigned to 4 Defect s severity 5 Defect s component 6 Defect s version 7 Defect s description 8 Defect s steps to reproduce
10. 3 Developer 2 1 Relatively different for the manager the developers are NOT allowed to edit the content of the project The only tasks for the developers and the testers are managing the defects San H Aung Page 20 of 21 4 5 Web based Distributed EJB BugsTracker 2 Asa result 1t is recommended that the developers must be able to report edit and assign defects however it is optional for the developers to be able to close the defects The testers responsibilities are reporting new defects verifying the finished fixes and closing the defects Tester 3 1 Relatively different from the developet s role the tester must be able to verify the defects and set all the verified defects to the final state close defects Client 4 1 Only has limited privileges to view and report new defects 3 8 DEFINITION OF THE DEFECT S STATUS San H Aung OPEN Open signifies a defect that has been opened and is ready for either a code change or cancellation This is the initial state for all defects Defects in the open state can either be verified corrections were made or canceled meaning that the defects were not reproduce ot duplicate VERIFY After a defect has been corrected the defect is put into the verify state usually by the developer This signifies that the problem specified by the defect is ready to be verified for correctness Defects in the verify state can either be closed by the tester the corrections f
11. 4 2nd defect Minor Verify UnAssign 07 29 2003 23 10 39 E Local intranet Figure 18 listing of all defects associated with the given project Kodak Continue moving forward from the listing of all defects page depicted in Figure 18 the user ends up having either Editing or Viewing the defects according to his or her permissions which has been setup by the system administrator 1 Having the edit icon E option permits the user editing the contents of the defect and its audit trail depicted in Figure 15 2 When the user s permission is not allowed to edit the defects it ends up having view icon which leads to the defect s view depicted in Figure 19 EIB BugsTracker Microsoft Internet Explorer l majki File Edit View Favorites Tools Help Back gt A A Asearch EdFavorites meda S Ey Y a aA y 2 Address la http localhost 8080 bugweb bugTrack ViewBug do Bugld 3 y Go EJB Login as guestKodak BugsTracker JavaHelp View defects no 3 Summa ry RIT s defect reported by tester Status Defer Assigned to Severity Mino Enter by Component El Version Description Home Project List Log Off Steps to Reproduce Audit Trail Updated by Defect history Updated On 1 tester New Bug Created 07 29 2003 15 55 54 2 admin Assigned to changes tester to admin 07 29 2003 15 56 10 Appending notes for audit trail A El Return El
12. 8080 bugweb userAdminEditUser do Id 5 EJB BugsTracker Login as admin pe Home Project List Project Admin User Admin Log Off JavaHelp Edit User UserName ltester Password ee First Name FName Last Name LName eMail san mailritedu Project RIT Super User c Yes No Permissions C Edit project Delete project Y Report new defects M Edit defects M Assign defects to user M Close defects Project Xerox C Edit project Delete project Y Report new defects M Edit defects M Assign defects to user M Close defects Project Kodak C Edit project Delete project Y Report new defects M Edit defects M Assign defects to user M Close defects Submit El A oanret Figure 25 Editing user permissions and its profiles 3 7 USER PERMISSIONS APPLY TO NON SUPER USER To define user permissions the administrator must first make sure required users and projects entries have been created so that administrator can get into the individual uset s edit page depicted in Figure 25 and start defining permission operating on a specific project The following are six basic types of permissions available for any non super users on a given project User who has one of the following permissions being checked on a given project will automatically be considered as members of that project 1 Edit Project 2 Delete Project 3 Reporting new defects 4 Edit defects 5 Assign defects to us
13. ANUAL 3 1 LOGGED IN PAGE EJB BugsTracker Microsoft Internet Explorer Eile Edit Yiew Favorites Tools Help Back gt Bsearch GaFavorites Meda 4 m S El y Address http localhost B080 bugweblogon jsp EJB BugsTracker JavaHelp User Na me admin Password ae Logon Suggestions to Author San H Aung El Boana y Figure 12 logged in page 3 2 WELCOME PAGE Right after logged in the user has five general categories of JSP pages to select from the top menu bar depicted in Figure 13 EJB BugsTracker Microsoft Internet Explorer File Edit view Favorites Tools Help Back gt A A ASearch Favorites Meda J B Saa Address http ocalhost 8080 bugweb logon do jsessionid 23CE4F0D5345878 139A 1236BC201C6C5 EJB Login as admin BugsTracker Home Project List Project Admin User Admin Log Off Joule Welcome admin Ei a Figure 13 Welcome page right after user logged in San H Aung Page 11 of 21 Web based Distributed EJB BugsTracker 3 3 HOME PAGE CATEGORY When the user clicks at the red hyperlink depicted in Figure 14 all defects related to or being assigned to the currently logged in user name will be listed on the home page category The goal of the home page is to help the currently logged in user managing his or her related defects effectively and easily Defects not being assigned to the currently logged in
14. ER USER VALUES 1 admin admin TRUE INSERT INTO Status id status VALUES 1 Open INSERT INTO Status id status VALUES 2 Verify INSERT INTO Status id status VALUES 3 Close INSERT INTO Status id status VALUES 4 Re Open INSERT INTO Status id status VALUES 5 Re assign INSERT INTO Status id status VALUES 6 Modify INSERT INTO Status id status VALUES 7 Cancel INSERT INTO Status id status VALUES 8 Defer HSQL Database Manager lol x File View Command Recent Options a INSERTINTO IDS ttablename nextid VALUES User Oy ra A jdbe hsqldb hsqlvlocalhost 1 476 Sees a di El VERSION INSERT IMTOIDS ftablename nextidh VALUES Project 0 E BUG INSERTINTO IDS fablename next VALUES Permission 0 Execute INSERTINTO DS tablename nextidh VALUES PHistoryBuas O E HISTORYBALIGS F El IDS 4 F El PROJECT update count a E STATUS 9e El USER l H PERMISSION Mo a E COMPONENT Properties ll Figure 8 Initializing the database with six SQL If everything goes well both database tables IDS and User should be verifiably initialized and read according to Figure 9 and Figure 10 If you get to this point the EJB BugsTracker is ready to logged in as admin admin San H Aung Page 8 of 21 Web based Distributed EJB BugsTracker HSOL Database Manager File View Command Recent Options 5 ie A jdbe hegldb hsqliocalha VE
15. Editing of existing project While editing for the project content depicted in the Figure 22 project managers have the following two options in defining the project s versions and its components 1 To create a new version for a project the project manager must click on the new versions icon Ml from Figure 22 and start defining the projects versions Create New Version Version Number Description submit 2 To create a new component for a project the project manager must also click on the new components icon from Figure 22 and start defining the sub component of the project such as Unix Windows XP and Mac Create New Component Component Name Description Submit San H Aung Page 17 of 21 Web based Distributed EJB BugsTracker 3 6 USER ADMINISTRATION CATEGORY 5 http localhost 8080 bugweb userAdmin do Microsoft Internet Explorer i o x File Edit View Favorites Tools Help Back Y gt 2 A Aseach GFavorites meda J Ey Y a BOY Address E http localhost 8080 bugweb userAdmin do EJB Login as sanl BueTracker Joutlelp Main Page BugsTracking ProjectAdmi Log Off All Available Users Login Name Email ff sanll aung sanl S an r nail rit edu EE sanl2 aung sanl san mail rit edu ALL aan y Figure 23 User administration main page where list all available users to the system The primary purpose of the User Administration depicted in Figure 23
16. MINISTRATION CATEGORY o aides 16 3 6 LISER ADMINISTRATION CA TEC e no 18 3 7 USER PERMISSIONS APPLY TO NON SUPER USER ssssssesseeseesssseeeseseeesscsessssscsecesssessesesssesees 19 3 8 DEFINITION OF THE DEFECT S STATUS ctas 21 San H Aung Page 2 of 21 Web based Distributed EJB BugsTracker FIGURES Figure 1 Setup the JAVA_HOME environment variables in Windows 2000 ceseveveveneneneneneenes 4 Figure 2 Setup the Path environment in Windows 2000 eeeeeeeeeeeeeesssseeeereeeeeeesssereeeeeesessseeereseseeeeeseeseseeeeeseeeeee 4 Figure 3 Directories structure of JBoss is on the left and the deployment files are on the right 5 Figure 4 Run JBoss server in Windows 2000 eeoorrocrrcccnonnnnnnnnonnnnon nro n nono nono rro nrn nr esse eee esse esse nro nn no nese nese sees eeaees 5 Figure 5 Completion of EJBs and Web components deployment EE N E T canccono 7 Figure 6 Running HSOL Database Manager Default eee eee ee eee eee eee eee eee errr eee eee eee eee reer ee eee eee e eee eee eee eee eee eee eee F Figure 7 HSOL Database manager connection login eee e eee eee eee eee ee eee eee eee eee eee ee ere eee eee ee ere eer eee reer eee reer ee errr ee F Figure 8 Initializing the database with six SOL POPPER eee eee eee eee ee eee eee ee ee ere eer eee ee eee eer eee ee eee eee eer ee ere eee ere eee ee re eee 38 Figure 9 Validating IDs table for generating independent primary keys rrr 9 Figure 10 Validating User
17. RSION Execute H BUG a HISTORYBLIGS 4 gt Hl Ips TABLEN AME NEXTID cil E TABLENAME Wo o n Type VARCHAR User ji Nullable false ee 0 El MEXTID A n Y Permission UO Type INTEGER History Buga oO Mullable true Version o Indices Component O E PROJECT 7 row s in O ma E STATUS H USER PERMISSION H COMPONENT Properties Figure 9 Validating IDs table for generating independent primary keys HSQL Database Manager ie ES File View Command Recent Options Select from User ci El jdbe hsqldb hsqlilocalho El VERSION E BUG HISTORYBLIGS 4 b E IDS RePRRUEE as E oa a AT eas El STATUS O Urn ssign null rill inull null true AO USER l admin admir null 1111 null true E Ip El LOGIN E PASSWORD El FIRST NAME LAST NAME E E Execute ID LOGIN PASSWORD FIRST MAME LAST NAME EMAIL SUPER USER cl 2 row s in O ms EMAIL SUPER_USER Indices El PERMISSION COMPONENT Properties Zi Figure 10 Validating User table for the first super user admin admin San H Aung Page 9 of 21 Web based Distributed EJB BugsTracker 2 OVERALL SITE MAP Before using the application one should go over all access paths of the screen depicted in Figure 11 Right after logged in the user has five main categories of JSP pages to select from the top menu bar 1 Home Page Filtering defects according to its assigned status 1 1 Editing or viewing defects with its audit trail 2
18. Web based Distributed EJB BugsTracker ROCHESTER INSTITUTE OF TECHNOLOGY Department of Computer Science User Manual Web based Distributed EJB Bugs Tracker An integration of Struts Framework at Web Server EJBs at Application Server and a Relational Database San Htun Aung sha5239 cs rit edu September 26 2003 Committee Members Advisor Dr Fereydoun Kazemian Reader Dr Rajendra K Raj Observer Dr Sidney Marshall San H Aung Page 1 of 21 Web based Distributed EJB BugsTracker TABLE OF CONTENTS PIGURE Ste eorciiacts 3 1 PROJECTENSTALLATION ie aia 4 1 1 INSTALLINGIZS DNS aa a a dl ed te ld ee 4 1 2 INSTALLING APPLICATION SERVER JBOSS ooooonononooooocoonccnnnonnnnncnnnnnnnnnnnonnnnonnnnnnnnn non non nnnnnnnnnnnos 4 1 3 RUNNING INTEGRATED SERVER TOMCAT JBOSS AND HSQL DB ccccccceeeeeeeeeeeeeeeeeees 5 1 4 DEPLOYMENT OF EJBS AND WEB SERVER COMPONENTS csccscescscecceccecesceccecescesceccecescasceseess 6 1 5 VERIFICATION OF DEPL MEN od a ed E e 6 1 6 RUNNING HSQL DATBASE MANAGER csssecccccessecccecesecccccesecccecuusecceseuuseeceseuunseceseuuneecessueneess 7 1 7 INITIALIZING THE NEW DATABASE Eo do e ao e 8 2 OVERALL SEE MAP AAO ATAA E 10 3 USER MAN DAL ae 11 3 1 LOGGEDEN PAGE e o er e o del a o O 11 3 2 WELCOME PAO E a e re pen na te de des da 11 3 3 HOMEPAGE CATEGORIA ert a hue teat neh ee ern eal e gad oe ee ld 12 3 4 PROJECT LIST CATEGORY a el smear dd a es lee 13 3 5 PROJECT AD
19. ally referred to as the deploy directory The deployment can be easily done for this BugsTracker project by copying the following files to the highlighted deployment directory as shown in the right side of the Figure 3 1 bugejb jar for EJBs container 2 bugweb WAR for web container 1 5 VERIFICATION OF DEPLOYMENT To verify that both EJBs and Web components are successfully deployed you should not see any error messages from the JBoss Server Console window in Figure 5 For EJB deployment you should see the following e EJB modules are deployed successfully e If this is a new database tables will be created automatically For web component deployment you should also see the following e Relevant Java classes and framework library such as struts jar are being deployed Shortcut C to JOSE run Starting deployment of pa ckage file fE f3bos erfdef fault deploy fbugejb jar TE jbiodu E bmod z TestBugEJ le Deploy ying IDsHandler Starting IDS succes e 2 oJje ct Bug reid table BUG successft te er Created table USER success EjbModul 5 yed Pa kage file f E jboss 3 0 7_jakarta of pac kage file E jboss IUC inaServii iced deploy ctx path bugweb warUr t 4 1 24 ser fado tmp dep lo erver defau ebappLoader bugweb Deploy ying class _Jakarta tomcat 4 1 24 tomcat 4 1 work MainEng gine WebappLoader bugweb Deploy class files WEB
20. and run the self installing executable for J2SDK software bundle After installing the JDK you will need to update your PATH variable For Windows 2000 if you want to set the PATH permanently Choose start Setting Control Panel and double click System Select the Advanced tab and then Environment Variables Choose New button from the system variables setting and create or edit the following two system variables JAVA_HOME C jdk1 3 1_05 depicted in Figure 1 Path JAVA_HOME bin depicted in Figure 2 Ed system Properties 2 x General Network Identification Hardware User Profiles Advanced Performance Path Cijck1 3 1_05bin C AWINNT systems Performance options control how applications use memory which TEMP C Documents and Settings jbuilder71L affects the speed of your computer TMP c pocuments and Settings jbullder7 Edit System Variable x 2 x a New Edit Variable JAVA _ HOME Variable Value CA your computer where to find certain System variables Variable Value 32FE HOME C j2sdkee1 3 1 Environment Variables JAWA_HOME C jdk1 3 1_05 JBOSS_HOME D Jboss 3 0 4_tomcat 4 0 6 Startup and Recovery JSDK_HOME Ci jesdkee1 3 1 A LIB C Program Files Microsoft Visual Studi y sa Startup and recovery options tell your computer how to start and a whatto do if an error causes your computer to stop New Edit Delet
21. associated with the given project depicted in Figure 18 4 EJB BugsTracker Microsoft Internet Explorer File Edit View Favorites Tools Help Back gt A A Asearch Favorites Meda J D 3 a agy Address http ocalhost 5080 bugweb bugTrackNewBug do projectID 1 EJB Login as admin BugsTracker A Home Project List Project Admin User Admin Log Off Report defects on project name Kodak Summa ry Reporting new defect for Kodak project by admin Status Open y Assigned to devKodak y Severity Minor y Enter by admin Component PC y Version 1 7 Description Detail description for this defect here Steps to Reproduce Detail steps to re proudce this defect for developer New Defect Oo B tccintranet Figure 17 Reporting new defect San H Aung Page 14 of 21 Web based Distributed EJB BugsTracker Z EJB BugsTracker Microsoft Internet Explorer x File Edit View Favorites Tools Help Ei Back gt A Asearch GuFavorites Meda 3 D 3 a aggy Address E http localhost 8080 bugweb bugTrackAllBugs do projectID 1 v Go EJB Login as admin BugsTracker Home Project List Project Admin User Admin Log Off JavoHejp Project name Kodak ix Reporting new defect All defects No Summary Severity Status Assignedlo LastModified E 1 Kodak s defect reported by tester Enhancement Open devKodak 07 29 2003 16 58 49 E
22. changes devwKodak to admin 07 29 2003 16 53 37 8 devKodak Severity changes Critical to Enhancement Assigned to changes admin to devkKodak 07 29 2003 16 58 49 Appending notes for audit trail Y Update gt yoo ire A Figure 15 Editing defects 3 4 PROJECT LIST CATEGORY The primary purpose of the Project List depicted in Figure 16 is to give the user a summary of open verify closed and total counts of the defects for each project and help the user visualize and manage defects from a different point of view that is managing defects in terms of the project view San H Aung Page 13 of 21 Web based Distributed EJB BugsTracker EJB BugsTracker Microsoft Internet Explorer BE x File Edit View Favorites Tools Help Back gt A A Asearch GFavorites meda S Ey GEM YD Address E http localhost 8080 bugweb bugTrack do v Go EJB Login as admin BugsTracker JavoHejp pome rajcr ust Project Admin User Admin Log Off Project List Projects summary Project Name Open Verify Close Others Total Counts Last Bug Update N iN RIT 07 29 2003 15 56 10 NI El B tocamtraner 4 Figure 16 Project s summary page Moving forward from the projects summary page depicted in Figure 16 the user has two options 1 Click at the new icon 4 results in reporting a new defect depicted in Figure 17 for the project 2 Click at the list icon 4 results in listing of all defects
23. de delete where it is not only deleting the project but also deleting all its related defects and its audit trail 3 http localhost 8080 bugweb prjAdminNewPrj jsp Microsoft Internet Explorer File Edit View Favorites Tools Help EBack Y gt Dll A Asearch Favorites meda 4 Br Y a gygy Address http localhost 8080 bugweb prjAdminNewPrj jsp EJB Login as sanl 3 Bug Tracker m Javallelg Main Page BugsTracking ProjectAdmin UserAdmin Log Off Creating Mew Project Name Created 05 11 2003 20 38 25 Description Last Modified Unavailable submit za mala Local intranet h Figure 21 Creating new project by system administrator 2 Done San H Aung Page 16 of 21 Web based Distributed EJB BugsTracker 3 EJB BugsTracker Microsoft Internet Explorer File Edit View Favorites Tools Help Back gt Y A A QSearch Favorites meda J E 3 a ayy Address http ocalhost B080 bugweb prjAdminEditPrj do Id 1 EJB Login as admin BugsTracker Home Project List Project Admin User Admin Log Off in Home project List project admin user Admin Loa of Editing Project 1 Project name Kodak Created 07 29 2003 14 36 44 Description Kodak Photo Div Last Modified 07 30 2003 23 54 05 New Versions N ersion Number Description Version 2 3 Version New Components lx Component Name Description Unix Env submit e fELocalintranet Z Figure 22
24. e Startup and Recovery OK Cancel OK Cancel Figure 1 Setup the JAVA_ HOME environment variables in Windows 2000 Edit System Variable ax Variable Path Variable Value ee sere oS ystemRoot syst ccor Figure 2 Setup the Path environment in Windows 2000 1 2 INSTALLING APPLICATION SERVER JBoss First you will need to download JBoss application server binaries file from http www jboss org where it has all current JBoss binaries For this project please download jboss 3 0 7_jakarta tomcat 4 1 24 zip this version of JBoss comes with a simple Database Hypersonic and Tomcat Web Server out of the box without any San H Aung Page 4 of 21 Web based Distributed EJB BugsTracker initial configuration Once you have downloaded JBoss just extract the zip file to any directory you want then the installation is complete The directory structure of JBoss is as shown in left hand side of the Figure 3 EN E jboss 3 0 7_jakarta tomcat 4 1 24 server default deploy Ele Edit view Favorites Tools Help Back gt Asearch Folders WE E X a Fay address Y E jboss 3 0 7_jakarta tomcat 4 1 24 server default deploy y Go 29 jboss 3 0 7_jakarta tomcat 4 1 24 4 http invoker sar Folder 4 8 2003 6 21 PM 3 bin Application Server a mx rmi adaptor sar File Folder 4 8 2003 6 21 PM La cient jmx console war Fil
25. e Folder 4 8 2003 6 21 PM ES 2a docs fea counter service 1KB XML Document 4 8 2003 6 21 PM Lab Select an item to view its failhnsqidb ser vice 6KB XML Document 4 8 2003 6 21 PM i Ba description laa jboss jca sar 92KB SAR File 4 8 2003 6 21 PM EY a server 33 jboss local jdbe 7 KB WINRAR archive 4 8 2003 6 21 PM Bda See also faa jbossmq service 12KB XML Document 4 8 2003 6 21 PM MD default My Documents jboss xa jdbe 12KB WinRAR archive 4 8 2003 6 21 PM con My Network Places Bimsa 24KB WINRAR archive 4 8 2003 6 21 PM po a db My Computer EMjms service 4KB XML Document 4 8 2003 6 21 PM a a hypersonic 5 jmx ejb adaptor 12KB JAR File 4 8 2003 6 21 PM laa jmx ejb connector server sar 17 KB SAR File 4 8 2003 6 21 PM la jmx invoker adaptor server sar 7KB SAR File 4 8 2003 6 21 PM Mi fed mail service 2KB XML Document 4 8 2003 6 21 PM Cy hittp invoker sar ERproperties service 2KB XML Document 4 8 2003 6 21 PM Ee jmx console war Eschedule manager service SKB XML Document 4 8 2003 6 21 PM AC jmx rmi adaptor sar 2 ejp management 28 KB JAR File 4 8 2003 6 21 PM i Hab fad jbossmq destinations service SKB XML Document 4 8 2003 6 21 PM E g log feascheduler service 2KB XML Document 4 8 2003 6 21 PM eC tmp sl service SKB XML Document 4 8 2003 6 21 PM 203 minimal aam service 2KB XML Document 4 8 2003 6 21 PM g 3 bugep 52KB JAR File 6 11 2003 1 59 AM hes Sa 762 KB WAR Fi 6 11 2003 1 59 AM ibn Web Server mad l AMES 0 common Deployment of
26. er 6 Close defects San H Aung Page 19 of 21 Web based Distributed EJB BugsTracker Recommended permission matrix for individual group of users Non super users role Add new user EA IO IA Edituser CA Deleteuser A Add mew project A l S y o Edit project A VRP Delete Project AF VR Report new defects A Edit defects A Always as default V R Recommend checking the box V O Optional Any user NOT allowed to edit the defect will have the options of viewing the defect s contents and its audit trail gt gt Ca A IE ee ae Ce ee ee vo ve IS 1 Administrator 0 1 No required to set any permission matrix the administrator usually in super user category always A qualified for operating all available features of the system 2 Different from non super users roles administrators are allowed to create edit and delete users profiles 3 In addition administrators are allowed to create a defined new project 2 Manager 1 1 Relatively different from the administrator the managers are viewed as the most powerful users in non super user category 2 It is recommended that the managers is responsible for editing and deleting his or her in charge project 3 Being able to get into the project administration page the managers should be able to incrementally define the project s new versions number and its new components without the help from the administrator
27. ixed the defect or reopened the corrections did not fix the defect CLOSE Once a defect has been corrected and verified it is put into the closed state This state signifies that the defect has been corrected CANCEL If a defect is found not to be a real problem it may be canceled Canceling a defect is the same as closing it with no further comment DEFER If late in the development cycle a defect occurs and there is no time to make the change a defect may be placed in the defer state This indicates a defect that is present in the released product Page 21 of 21
Download Pdf Manuals
Related Search