10.7.00.001: Fix Pack 1


Version Status

 The following table details the current latest version status of the App Visibility components:

Component

Status

App Visibility Collector

10.7.00 FP1

App Visibility Portal

10.7.00 FP1

App Visibility Proxy

10.7.00 FP1

App Visibility Agent for Java

10.7.00 FP1

App Visibility Agent for .NET

10.7.00 FP1

Synthetic TEA Agent

10.7.00 FP1

 

 

Fix Pack 1 corrected issues

Fix for issue TOM-31342: App Visibility portal or collector data is deleted if the database reaches 90% of the defined maximum data storage size

Fix Pack 1 corrects issue TOM-31342 where the App Visibility portal or collector database is deleted when it reaches 90% of the defined maximum data storage size. The workaround—to use only the database retention time to help control the size of the database—is no longer required.

Corrected functionality for TOM-31342

When the App Visibility portal or collector database size reaches 90% of the configured maximum storage size, the system now issues a health event as an early alert for you to take action.

To prevent your database from reaching the maximum size, adjust one or more of the following properties and then restart the component service or services:  

  • If you have space on the computer with the database, you can increase the maximum database size (in MB) properties:
    • In the portal. properties file, increase the db.max.size property.
    • In the collector. properties file, increase the db.max.size property.
  • You can control the database growth by reducing the retention time (in days) properties, which deletes data that is older than the configured time:
    • In the portal. properties file, reduce the retention.time property.
    • In the collector.properties file, reduce the retention.time property, or the retention.time.synthetic_transactions property, or both properties.

When the database size reaches 85% of the configured maximum storage size, the system closes the event.

In the properties files, you can also adjust the percentage of used database space at which the system issues the event and the percentage at which the system closes the event.

For details about changing the database properties, see Changing App Visibility portal settings and Changing-App-Visibility-collector-settings.   

Fix for issue about upgrade on Linux in an HA environment

Fix Pack 1 corrects the issue, Cannot-upgrade-App-Visibility-10-5-server-components-to-10-7-in-an-HA-environment-on-Linux.

In a high-availability environment on Linux, you can apply the fix pack to upgrade the App Visibility server components from version 10.5 to version 10.7.00.001.

 

 

Applying the fix pack

Before you apply the Fix Pack, you must have previously installed the base version of the product. For more information, see 10.7.00.001: Fix Pack 1 - TrueSight Operations Managment.

Recommended order to apply the fix pack

Apply the fix pack to components in the following recommended sequence:

  1. Apply the fix pack to the Presentation Server.
  2. If you integrate with Infrastructure Management, apply the fix pack to TrueSight Infrastructure Management.
  3. Apply the fix pack to the App Visibility server components.
  4. Apply the fix pack to App Visibility agents for Java.
  5. Apply the fix pack to App Visibility agents for .NET.
  6. Apply the fix pack to the Transaction Execution Adapter (TEA) Agents.

Note

When you start applying the fix pack to components, data collection stops, or is incomplete, until all components run the same version.

Before you begin

Before you apply the fix pack to the App Visibility Manager and Synthetic Monitor components, perform the following tasks:

To apply the fix pack to the App Visibility portal

Follow the upgrade procedure as instructed in the Applying feature packs or fix packs to App Visibility server components topic.

The version number in the fix pack upgrade utility shows 10.7.00.001.

To apply the fix pack to the App Visibility collector

Follow the upgrade procedure as instructed in the Applying feature packs or fix packs to App Visibility server components topic.

The version number in the fix pack upgrade utility shows 10.7.00.001.

To apply the fix pack to the App Visibility proxy

Follow the upgrade procedure as instructed in the Applying feature packs or fix packs to App Visibility server components topic.

The version number in the fix pack upgrade utility shows 10.7.00.001.

To apply the fix pack to the App Visibility agent for Java

Follow the upgrade procedure as instructed in the Applying feature packs or fix packs to App Visibility agents for Java topic.

The version number in the TrueSight console shows 10.7.00.001.

To apply the fix pack to the App Visibility agent for .NET

Follow the upgrade procedure as instructed in the Applying feature packs or fix packs to App Visibility agents for .NET topic.

The version number in the TrueSight console shows 10.7.00.001.

To apply the fix pack to the TEA Agent

Follow the upgrade procedure as instructed in the Applying feature packs or fix packs to TEA Agents topic.

The version number in the TrueSight console shows 10.7.00.001.

 

 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*