WebSphere Lombardi Edition 7.2 > Administer the Lombardi environments > Manage Lombardi configuration settings
Extend the maximum number of characters in tracked performance data
By default, the maximum number of characters that is allowed in performance data (variable fields that are tracked to the Performance Data Warehouse for reporting purposes) is 64. You can extend this limit by making the following changes to the property file for your Lombardi Performance Data Warehouse. The changes that you make to this property affect the column sizes in the tracking group tables.
For more information about how performance data is tracked, see Lombardi Authoring Environment User Guide or online help.
From the [Lombardi_home]\performance-data-warehouse\config\system directory, open the 00Static.xml property file in a text editor. Copy and paste the following property into the 100Custom.xml property file (located in [Lombardi_home]\performance-data-warehouse\config ):
<max-length-of-string-columns>64</max-length-of-string-columns>
To change the value, use the merge="replace" command as shown in the following example. In this example, the maximum desired length of a string is 200.
<max-length-of-string-columns merge="replace">200</max-length-of-string-columns>
You need to make this change globally in the Performance Data Warehouse because the server does not have field- or group-level specificity for the maximum string length setting. Although you can use a larger string length for a field, you should be somewhat conservative and apply this setting across the board.
In the performance database, change the column width of all tracking group fields in the TG_* tables that are VARCHAR parameters. You must also change the column width of the STRING_VALUE column in the LSW_OPTIMIZER_DATA table. Both of these values should be the same size as the value of the max-length-of-string-columns property that you specified in preceding step. For example, if you have a tracking group called Test and a tracked string in Test called longString that should be able to send 200 characters to the Performance Data Warehouse, you should alter the TG_Test table to extend TG_Test.longString to be 200 characters long. For example:
ALTER TABLE TG_Test MODIFY longString VARCHAR2(200)Consult your database administrator for the specific command that will need to be run on your performance database. If you apply the alter table command to your tracking group fields, you still need to apply the change for the maximum string length to the Performance Data Warehouse configuration in order for Lombardi to write data larger than the default maximum string length. Anything larger than the default maximum string length value will go into the errors list in the Performance Admin Console. If you increase the maximum string length value but do not increase the size of the other string fields, the amount of data written could exceed the capacity of these fields.
- After altering the TG_* tables, send definitions to the Performance Data Warehouse to recreate the corresponding view(s).
- Restart the Performance Data Warehouse.
You will see errors in your tw-perf.log file if you attempt to send data to the Performance Data Warehouse that is greater than the maximum allowed number of characters. For example:
2007-08-08 18:05:26,156 [DataTransfer Thread #2] ERROR com.lombardisoftware.server.ejb.tracking.APIServicesBean - Exception in EJB call com.lombardisoftware.core.TeamWorksException: (PFS-0062) The tracked field with external ID t193b943b74411 has a value that is 96 characters long. The maximum is 64. ...You will only see these errors in the performance logs and Performance Admin console when this occurs. No indication of an error is displayed in the Process Server. These errors are stored in the error queue where you can reprocess them using the Performance Admin Console. See Manage data transfer errors for additional information about reprocessing messages in the error queue.
Parent topic: Manage Lombardi configuration settings