Browse Prior Art Database

genNLV - A Web-based, Direct Install Image, Translation Verification Testing Tool Disclosure Number: IPCOM000019214D
Original Publication Date: 2003-Sep-05
Included in the Prior Art Database: 2003-Sep-05
Document File: 1 page(s) / 72K

Publishing Venue



genNLV - A Web-based, Direct Install Image, Translation Verification Testing (TVT) Tool. A user submits a translated resource file through a simple web interface and receives the compiled file required in their existing install image. The input file is processed in the standard DB2 build environment which is made accessible through a web server. The tool improves the TVT process by allowing testers to make translation changes and verify the results immediately on all Universal Database (UDB) supported platforms (Linux, Sun, AIX, Windows). In the past testers would submit their files to Lab file handlers and wait for a patch (which required manual handling and was error-prone), or a new install image to be made available - a process that takes days due to the many products and platforms that DB2 gets built into with every new build. With the genNLV tool, the cost of translation testing is reduced and the overall quality of the product is improved.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 75% of the total text.

Page 1 of 1

genNLV - A Web-based, Direct Install Image, Translation Verification Testing Tool

  Technical innovation was achieved by exposing the DB2 build environment, previously available to the NLV build personnel only, to Translation Testers through a Web interface. After submitting their Programmable Integrated Information (PII) resource files, testers obtain the generated files and update their existing DB2 install-image without the need to reinstall.

Following is a general description of how the tool builds a file.

1) A translated resource file is uploaded to the build web server via MultiPart request from the web browser
2) Based on file type and language, the appropriate build functions are invoked. The file-type is associated with specifically designated classes which contain the necessary build parameters needed to place the input file in the correct location in the build tree. A Controller Servlet manages the build invocation using the standard Java Runtime Process., and then monitors the output streams of the build to be able to return output files to the user.
3) The resulting compiled file and a batch script are made available as hypertext links. A batch file is generated and returned to the user for the convenience.
4) The tester downloads both files and executes the batch script. When executed on the client workstation, the local install image is updated with the new resource.
5) Testing can be performed immediately. Typically this involves person translation ver...