Test Productivity Pack (TPP) version 4.4.1 software update has been officially released. TPP v4.4.1 server /client software supports all new features in the recently released DSAM firmware version 3.6.1.
This new v4.4.1 software release also includes fixes that enhance overall system stability and other minor issues. This TPP v4.4.1 server /client software upgrade is free to existing TPP customers.
This is a free upgrade for all existing versions of TPP with a valid license file. Contact JDSU Sales for more information or to purchase TPP software.
.
TPP V4.4.1 CLIENT ONLY (42MB) |
| TPP V4.4.1 SERVER/CLIENT (189MB)
PLEASE NOTE: |
If you have any DSAM meters that have been upgraded to firmware release v3.6.1, you must upgrade your TPP software to release v4.4.1. TPP v4.4.1 is required to support all the following features.
1. SmartScan
2. In-Band C/N measurement support
3. Reverse Alignment Report
4. Spectrum graphs now displaying Min Hold trace when enabled in DSAM
5. Internet Explorer 8 and Windows 7 Pro support
Users can create value-added reports, such as charts, periodical job summary, and trending reports. With these reports, users can identify failed jobs faster and determine the failure reasons, dispatch techs to targeted network segment faster, identify areas and regions that need more focus, and also conduct network trending by getting level, MER, BER on specific channels and identify outliers.
In order to take advantage of the new database architecture, the existing database needs to be migrated. It is an option that users can plan and execute according to each individual organization's need, so it is not intrusive for any organization that does not have the need to create its own reports.
For users that have the need to create their own reports, TPP v4.4.1 provides the following features to ease the database migration and access to the database.
The ability to add SQL query users via the Web client - the Test Reporting System. This will help protect the database integrity by not giving query users "root" access.
The ability to open an external port to the query users so that query users can access the database remotely on the network.
One-button click to migrate all stored data into new table formats from the existing XML data objects.
There are a total of forty three (43) separate SQL views which allow users to easily execute SQL queries to generate reports so that users do not have to dive into the complexity of the raw database schema.
Notes for the database migration:
Database migration will occur only once.
Recommended procedures for optimal database performance
Run MySQL Database Optimization before starting the "Minable Database Migration", and after migration is complete.
The best solution is to setup a nightly "Scheduled TPP Backup" of the database which includes the optimization by default.
Migration planning
Migration Schedule:
The database migration processes every file synchronized by all the DSAM meters, so it takes time to process. This involves complex database operations, including table creation, file processing, and inserting data into tables.
It is recommended that migration should be planned at a time when there is minimal DSAM and TPP interaction. The best practice is to start the database migration over the weekend.
TPP Server Specification Recommendations to Support the Migrated Database:
Your TPP Server is recommended to be on a PC with a CPU matching or exceeding Intel "Pentium 4" with 2.5 GHz speeds with SATA hard drive access.
For larger databases, we recommend a CPU matching or exceeding Intel "Core 2 Duo" speeds.
The database migration process will auto-adapt the migration speed so that the average CPU usage is under 50% for all the processes on the server. This is to accommodate communication between the TPP server and any user/DSAM activity that may occur during migration.
Certain legacy files may not be converted
On the webpage where you initiate the migration process, you may notice that there is a counter for the number of files that appears if any failed to convert to the new database structure.
Most files that failed are likely legacy files that are either not complete or corrupt when transferred from the DSAM to the server, or files that were saved with one of the earlier beta DSAM firmware versions.
Occasionally, we solicit help from our customers to conduct beta tests for a new firmware release. Files saved with these beta versions may not be supported by TPP.
If you have any order related questions regarding the Test Productivity Pack software, please contact JDSU:
For technical assistance, please contact JDSU Technical Support: