• Spaces
  • People
  • Help
    • BMC Support Central BMC Community BMC.com
    ×
    BMC TrueSight App Visibility Manager 10.5

    Page tree

    Skip to end of metadata
    Go to start of metadata

    TrueSight App Visibility Manager 10.5.00.001 offers improvements in functionality and corrected issues.

    For information about integrated products, see 10.5.00.001: Fix Pack 1 - TrueSight Operations Management .

    This topic contains the following sections:

    Related topic

    10.5.00.001: Fix Pack 1 - TrueSight Operations Managment

    Fix Pack 1 improvements

    For information about issues corrected in this Fix Pack, see Known and corrected issues - App Visibility Manager .

    Improvements for App Visibility agent for .NET

    • You can now monitor standalone services that run on a supported version of .NET Framework and use Windows Communication Foundation (WCF). For more information, see Monitoring standalone services for .NET Framework.
    • For .NET Framework applications, including standalone services, you can now see the DateTime and GUID values with the code-level transaction information. The values are displayed with the transaction trace details, as "Custom Information."
    • You can now see the module name for methods with the code-level transaction information. The module name is displayed with the transaction trace details, as "Custom Information."

      For general information about code-level details, see Viewing a trace at the code level.

    Applying the fix pack

    As described in this section, you can apply the Fix Pack to the following components by using the fix pack installation/upgrade utilities:

    • App Visibility agent for Java
    • App Visibility agent for .NET

    The following components require manually replacing files:

    • App Visibility server
    • TEA Agent

    Before you apply the Fix Pack, you must have previously installed the base version of the product. For more information, see  10.5.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. If you install a new App Visibility server, install version 10.5.00 and then apply the fix pack.

      Warning

      Do not delete the App Visibility portal from the Presentation Server before you apply a fix pack. If you delete the portal before you apply the fix pack, you will lose historic synthetic monitoring data.

    4.   Apply the fix pack to the App Visibility diagnostic agents and synthetic transaction monitoring agents:
      • App Visibility agents for Java.
      • App Visibility agents for .NET.
      • Transaction Execution Adapter (TEA) Agents  . If you install new TEA Agents, install version 10.5.00 and then apply the fix pack.

    Note

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

    Before you begin

    • Download the fix pack installation files. For instructions, see  Downloading the Fix Pack .
    • In a new environment, install the App Visibility server components , and then apply the fix pack.

    Applying Fix Pack 1 to the App Visibility server

    When you apply the fix pack to the App Visibility portal and collector, ensure that you are prepared for the following:

    • Do not delete the App Visibility portal from the Presentation Server before you apply a fix pack . If you delete the portal before you apply the fix pack , you will lose historic synthetic monitoring data.
    • Expect gaps in data until all you apply  the fix pack to components run the same version.
    • In a high-availability environment, apply the fix pack to the standby node first, and then the active node.

    The App Visibility proxy component does not have any changes. The version included with Fix Pack 1 is the same as the previous version.

     

    To apply the fix pack to the App Visibility server on Windows

     Click here for instructions about applying the fix pack.

    1. Back up the following files up to a folder outside the installation directory.

      For the App Visibility portal:
      • portal.jar (default directory C:\Program Files\BMC Software\App Visibility\portal\lib)
      • portal-console.war (default directory C:\Program Files\BMC Software\App Visibility\portal\webapps)
      • adops-common-infra.jar (default directory C:\Program Files\BMC Software\App Visibility\common\lib)
      • common-server.jar (default directory C:\Program Files\BMC Software\App Visibility\common\lib)
      For the App Visibility collector:
      • collector.jar (default directory C:\Program Files\BMC Software\App Visibility\collector\lib)
      • adops-common-infra.jar (default directory C:\Program Files\BMC Software\App Visibility\common\lib)
      • common-server.jar (default directory C:\Program Files\BMC Software\App Visibility\common\lib)
    2. Stop the App Visibility portal service.
    3. Stop the App Visibility collector service.
    4. Replace the existing files listed above with the new files.
    5. On the portal computer, delete the C:\Program Files\BMC Software\App Visibility\portal\webapps\portal-console directory
    6. Start the portal service and collector services.

    To apply the fix pack to the App Visibility server on Linux

     Click here for instructions about applying the fix pack.
    1. Back up the following files up to a folder outside the installation directory.
      For the App Visibility portal:
      • portal.jar (default directory /opt/bmc/App_Visibility/portal/lib)
      • portal-console.war (default directory /opt/bmc/App_Visibility/portal/webapps)
      • adops-common-infra.jar (default directory /opt/bmc/App_Visibility/common/lib)
      • common-server.jar (default directory /opt/bmc/App_Visibility/common/lib)
      For the App Visibility collector:
      • collector.jar (default directory /opt/bmc/App_Visibility/collector/lib)
      • adops-common-infra.jar (default directory /opt/bmc/App_Visibility/common/lib)
      • common-server.jar (default directory /opt/bmc/App_Visibility/common/lib)
    2. Stop the App Visibility portal service.
    3. Stop the App Visibility collector service.
    4. Replace the existing files listed above with the new files.

    5. On the portal computer, navigate to /opt/bmc/App_Visibility/portal/webapps and run the following command to apply permissions to the portal-console.war file:

      chmod -R 775 ./portal-console.war
    6. On the portal computer, delete the /opt/bmc/App_Visibility/portal/webapps/portal-console directory
    7. Start the portal service and collector services.

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

    Follow the upgrade procedure as instructed in the Upgrading App Visibility agents for Java topic.

    For an interactive upgrade, open a command shell and use the -skipExistingVerCheck option:

    • (Windows) adops-agent-upgrade.bat -skipExistingVerCheck
    • (Linux) adops-agent-upgrade.sh -skipExistingVerCheck

     

    For a silent upgrade, use the -skipExistingVerCheck option:

    • (Windows) adops-agent-upgrade.bat -s -skipExistingVerCheck -d <installationDirectory>

    • (Linux) ./adops-agent-upgrade.sh -s -skipExistingVerCheck -d <installationDirectory>

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

    Follow the upgrade procedure as instructed in the Upgrading App Visibility agents for .NET topic.

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

    To apply the fix pack to the TEA Agent

    For Oracle RAC databases, Fix Pack 1 corrects issues with the Migration Tool from TM ART.

    1. For a new environment, install a BMC Synthetic Transaction Execution Adapter Agent .
    2. Back up the ConfigMigrationTool-10.5.00.jar file up to a folder outside the installation directory.
      The default directory is \Disk1\utility\ConfigurationMigrationTool\lib

    3. Replace the existing file with the new file from the Fix Pack.

    © Copyright 2005-2021 BMC Software, Inc. Use of this site signifies your acceptance of BMC’s Terms of Use . BMC, the BMC logo, and other BMC marks are assets of BMC Software, Inc. These trademarks are registered and may be registered in the U.S. and in other countries.