The document lists various tools used for different tasks like comparing XML files using BeyondCompare, changing property files on servers using FileZilla, decompiling jars using jd-gui.exe, communicating using Lync, testing WSDLs using soapUI, checking logs using Putty, checking out projects from CVS, checking requirements using Caliber or Rally for agile, defect logging using QC, and tracking time sheets using CA Clarity.
The document lists various tools used for different tasks like comparing XML files using BeyondCompare, changing property files on servers using FileZilla, decompiling jars using jd-gui.exe, communicating using Lync, testing WSDLs using soapUI, checking logs using Putty, checking out projects from CVS, checking requirements using Caliber or Rally for agile, defect logging using QC, and tracking time sheets using CA Clarity.
The document lists various tools used for different tasks like comparing XML files using BeyondCompare, changing property files on servers using FileZilla, decompiling jars using jd-gui.exe, communicating using Lync, testing WSDLs using soapUI, checking logs using Putty, checking out projects from CVS, checking requirements using Caliber or Rally for agile, defect logging using QC, and tracking time sheets using CA Clarity.
BeyondCompare tool we use 2. To change the property file directly on server : FileZilla tool we use 3. To decompile the jar: jd-gui.exe tool we use. 4.Communicator Lync 5. TO test WSDL tool we use soapUI 3.6.1 6. To check the logs Putty we use we checkout project from CVS Caliber to check requirements. Now we are using Rally for AGILE. QC for defect logging. CA Clarity for time sheet.