Document Revision History

Transcription

1 ENAD505 Doc.No Issued By Date Page Project Gantt Artha.M.Wijendra (7) Title THIS DOCUMENT IS FOR INFORMATIONAL PURPOSES ONLY. IT IS NOT A COMMITMENT TO DELIVER AND MAY NOT BE INCORPORATED INTO ANY CONTRACT. Revision Date By Remarks A ARWILK Created. 1. Introduction Document Revision History The Gantt solution for web is implemented as an applet using JGantt.jar that is developed by Netronic (http// 2. Mechanism Only a couple of values like "Base URL", "Page ID", "Project ID" are passed as applet parameters from the web page. For all the other data requirements + data submission, the applet sends data to the servlet page as a GET/POST request. To make a request (GET/POST) to the associated servlet page, the applet calls the related JavaScript methods in "projw/scripts/ganttclientscript.js". The applet calls the JavaScript methods through liveconnect (JSObject). Liveconnect was developed by Netscape and is now distributed with J2SE as a separate plug-in (JAVA_HOME/jre/lib/plugin.jar). There are occasions when the request URL becomes larger than 2K and as such the request should be "POST" in certain occasions (Ex When sending applet changes back to the page in order to save in the database).the current framework (Sparx release) function " connect in common/scripts/clientscript.js" supports only GET requests, thus the new "projw/scripts/ganttclientscript.js" file was written for this purpose. (Uses Microsoft.XMLHTTP for IE and XMLHttpRequest for other browser types) The applet makes a request to populate the Gantt diagram and the servlet page sends the response XML. (The structure is shown below)

2 ENAD505 Doc.No Issued By Date Page Project Gantt Artha.M.Wijendra (7) Title (NOTE There might be small changes in the structure because at the last moment we had to change the code to support DOM Level 2 Specification. This is because APP7 SP3 uses java and the JAXP version associated with java uses DOM Level 2) All the XML generation (server + applet side) is done using JAXP API. All the translations of the applet are done at the servlet page side and sent back to the applet using the above mentioned XML structure.

3 ENAD505 Doc.No Issued By Date Page Project Gantt Artha.M.Wijendra (7) Title User specific Gantt properties can be specified using the "Gantt Properties" dialog window (shown below) and once changes are made they will be saved in the database using the user profile functionality provided in the framework. A sample property structure is shown below. The Properties XML is made to store two setting types. 1. Property_Dlg - This element stores the settings the user has selected on Gantt Properties dialog. 2. Toolbar_Settings - Certain Gantt toolbar settings can be stored in the user profile using this element. The user can save his toolbar setting to profile only if he/she has ticked the "Save Toolbar Settings" checkbox in Gantt Properties Dialog. (This sort of restriction is put in place because profile save/load takes some time)

4 ENAD505 Doc.No Issued By Date Page Project Gantt Artha.M.Wijendra (7) Title 3. Harvest Structure The main jar files that are required for the Gantt applet are shown above. Jar File Name Information JGantt.jar The Java Gantt solution by Netronic plugin.jar Contains classes used to make liveconnection (applet <---> javascript communication) projwapplets.jar Contains the IFS built applets and utility classes. Even though applet related source code is checked in to harvest the current solution does not provide automatic applet jar creation at build time. Thus the developer should make sure to compile all the applet related class files into this projwapplets.jar file swing-layout-1.0.jar Swing components with additional functionality from Netbeans Applet source files should be placed in "projw/source/projw/applets/src" folder whilst JGantt.jar should be placed in two locations. Applet Converting rowset data to JGantt appdata Place JGantt.jar in "projw/webclient/applications/b2e/projw/lib" folder. Place JGantt.jar in "projw/webclient/applications/b2e/web- INF/lib" folder.

5 ENAD505 Doc.No Issued By Date Page Project Gantt Artha.M.Wijendra (7) Title 4. Viewing Applets To view the applets the client must have a java enabled browser. One of the certified java plug-in must be installed for the JGantt functionality to work. The might be more than one plug-in installed for your browser in which case you need to specify which one is to be used. (Please check the documentation for your browser on how to enable this option) For IE 7 For IE All Installed java plug-ins will be listed under the "Tools/Internet Options/Advanced" tab. You need to select one of the certified java plug-ins for the JGantt solution to work. For Firfox For Firefox you need to select the "Enable Java" plugin checkbox (The "Enable Javascript" option should also be selected for liveconnect to work. But if you are already testing normal IFS web pages using Firefox this option should already be enabled). The Firefox browser will select the plug-in installed under JAVA_HOME, if you need to test under a different plug-in then just change your environment variable JAVA_HOME to that path and restart the browser.

6 ENAD505 Doc.No Issued By Date Page Project Gantt Artha.M.Wijendra (7) Title 5. Configuring the IDE for JGantt The configuration for JBuilder can be found in the JGantt Use Guide. If you want to add JGantt to Netbeans IDE then please follow the normal procedure for adding a pallate component. For the convenience this procedure is mentioned below. 1. Go to "Tools/Library Manager" press the Button "New Library" to create a new library called "JGantt". 2. Select the newly created library and then Add JGantt.jar to this library using "Add JAR/Folder..." option. 3. Go to "Tools/Pallete Manager/Swing AWT Components" and then select an existing pallete category or cerate a new one (EX Netronic). 4. Then choose "Add From Library..." to add the library. Follow the steps in the wizard to the finish. Now the Netbeans IDE can be used for JGantt development.

7 ENAD505 Doc.No Issued By Date Page Project Gantt Artha.M.Wijendra (7) Title 6. Other Considerations XML Handling on the servlet side is currently done using JAXP API. This was selected after considering several available options (shown below). XML API File Name Issue JDOM jdom.jar Has problems with "IBM -Websphere" and Oracle application servers and gives runtime exceptions. StAX Xerces DOM jsr173_api.jar (comes packed with the framework) xercesimpl.jar (comes packed with the framework) Supports cursor-based and event-based XML handling. (Performance Issues in XML document writing/modifying when inserting sub-elements into existing elements) Other components use this, but have problems with Oracle application server and gives runtime exceptions. JAXP Comes as a part of J2SE J2SE Supports DOM Level 2 specification whilst J2SE upwards supports DOM Level 3 specification. Because the JGantt solution needs to work on APP7 SP3 the DOM Level 2 specification based methods are used for the current JGantt solution. (Check the code comments for more details) If you change the structure of the property XML then the users may need to delete the entry (for your user) in solution manager (User/Web/b2e/Global/Custom Values/GANTT_USER_PROPERTIES). Then clear the profile cache using common/scripts/webclientadmin.page.