Introscope 8

CA Wily Introscope 8
May 2010 Contents
Release 8.2.3 ReadMe
Copyright 2010 CA. All Rights Reserved Wily Technology Inc. and Introscope are registered trademarks of CA
1. Release summary.......................................................................................... 1 2. What's new .................................................................................................. 2 2.1 Enhanced dashboards .............................................................................. 6 Performance Dashboards ............................................................................. 10 Capacity Dashboards ................................................................................... 13 2.2 Viewing Live and Historical Data in the Workstation Console ........................ 15 2.3 SmartStor Tools .................................................................................... 17 2.4 Configuring the Command Line Workstation Log......................................... 24 2.5 Metric Clamping .................................................................................... 25 2.6 Enterprise Manager health and supportability metrics ................................. 28 3. Installation and upgrade notes ...................................................................... 32 4. Backward compatibility ................................................................................ 33 5. Limitations & restrictions .............................................................................. 34 Deprecated and changed features ................................................................. 34 6. Fixed in this release .................................................................................... 34 Fixed in Service Pack Release 8.2.3 ............................................................... 34 Fixed in Service Pack Release 8.2.2 ............................................................... 34 Fixed in Service Pack Release 8.2.1.0 ............................................................ 35 Fixed in Minor Release 8.2.0.0 ...................................................................... 35 7. Known issues ............................................................................................. 37 High priority issues...................................................................................... 37 Other known issues ..................................................................................... 38 8. Introscope for SAP Solution Manager Diagnostics-related known issues............... 54 9. Introscope .NET Agent-related release notes ................................................... 55 Other Introscope .NET agent-related known issues .......................................... 57 10. Contacting Technical Support ........................................................................ 58 11. Acknowledgements ..................................................................................... 59
Release 8.2.3 is a service pack release of CA Wily's market-leading Introscope tool for
monitoring, triaging and diagnosing the health of multi-tiered applications. It is intended to replace previously installed versions of Introscope 8.2.
1. Release summary
The 8.2 release: Integrates Wilys SYSVIEW extensions with the core Introscope programs, tools and utilities. See Whats New and Integrations below. Includes several enhancements -- see sec. 2. It also includes all bug fixes performed in Introscope 8.0 service pack releases.
Introscope 8.2.3 ReadMe
May 2010
page 2
2. What's new
For a list of fixes included in this release, see Fixed in this release. Key features in Introscope 8.2 include: Platform Monitors and agents Release 8.2.3 is enhanced to support the following: Platform Monitors for AIX 6.1 (32- and 64-bit) EPAgent for JVM 1.6 .NET agent on Windows Server 2008 R2 (64-bit), IIS 7.5
Enhanced dashboards Release 8.2.2 adds a number of enhanced dashboards for use in monitoring your application. See sec. 2.1, Enhanced dashboards, below.
Ability to view live and historical data in the Workstation Console Release 8.2.2 adds the ability to view historical data in the Workstation Console. See sec. 2.2 below.
Enhancements to SmartStor Tools Release 8.2.2 adds a number of enhancements to SmartStor Tools. See sec. 2.3, SmartStor Tools, below.
Enhancements to CLW Logging Release 8.2.2 adds the ability to configure the Command Line Workstation Log file. See sec. 2.4, Configuring the Command Line Workstation Log, below.
Enhancements to Metric Clamping Release 8.2.2 adds enhancements to Metric Clamping. See sec. 2.5, Metric Clamping, below.
Enhancements to EM health and supportability metrics Release 8.2.2 adds enhancements to Enterprise Manager health and supportability metrics. See sec. 2.6 below.
CA WILY SYSVIEW Extension The Introscope Integration Pack for CA SYSVIEW is an extension that allows you to trace Customer Information Control System (CICS) transactions using the Introscope Workstation and view dashboards that summarize CICS performance in the Introscope Workstation console. This increases end-to-end visibility for quickly isolating transaction performance problems and allows you to leverage existing SYSVIEW performance data.
SharePoint Power Pack Preconfigured extension to provide overall health monitoring of SharePoint, as well as specific visualizations and artifacts to provide detailed Root Cause Diagnostic capabilities.
Enhanced WebLogic Portal Monitoring Graphical view for poor performing portal components. Enhanced WAS Portal Monitoring Graphical view for poor performing portal components. Reporting Virtual Portal performance.
May 2010
page 3
CTG Power Pack enhancements Support for CTG V6 and V7, support for the newly released IPIC TCP/IP connection option, and Global Statistics measurements relating to key CTG Gateway Server utilization.
WAS on z/OS platform support enhancements Support for WAS 7 on z/OS 1.10 z/OS PP platform support enhancements Support for z/OS 1.10 New Platform Monitor for HP-UX PA-RISC We have added platform monitor support for HP-UX PA-RISC 64-bit JVM. Support for Microsoft SQL Server 2008 The SQL Agent now supports the Microsoft SQL Server 2008 database, both 32-bit and 64-bit versions.
Options for Memory vs. Response Time The Introscope 8.2 agent has a new property that allows you to balance memory use against response time. Using the property could potentially lower memory consumption at the expense of a possible increase in response time. Add the following to your agents IntrscopeAgent.profile file, set the property to true, and uncomment it. You must restart the managed application before changes to this property take effect.
############################### #Agent Memory Overhead Setting # # ======================= # Set to true if you want to attempt to reduce the agent memory overhead introduced by architectural improvements to the 8.x Agent. # Increased Agent memory overhead only occurs in certain extreme cases. # The trade-off for the possible lower memory consumption is a possible increase in response time. # Each application is unique and will experience different variations in Memory vs. Response Time trade-offs. # This property is set to false by default and out of the box is commented out. This is not a hot property # and the managed application needs to be restarted for this flag to take effect. #introscope.agent.reduceAgentMemoryOverhead=true
Important things to know: Enable collection of filter parameters for .NET

Setting the .NET agent property introscope.agent.asp.disableHttpProperties to FALSE enables the collection of HTTP headers, parameters, attributes, in addition to the documented list of Application Name, Session ID, Context Path, Server Name, URL, Context Path and Normalized URL. For more information, see the heading Enable collection of filter parameters in the .NET Agent Guide.
May 2010
page 4
Property to set AutoProbe log size for Java Agent

You can set the size for the AutoProbe log for Java Agent. The log file is backed up after the log file reaches the specified size and a new log file gets created. To set AutoProbe log size for Java Agent:
Add the following property to the JAVA _OPTIONS
-Dcom.wily.autoprobe.logSizeInKB=1000
For example: 1 Set the following properties in the JVM arguments:
set JAVA_OPTIONS=%SAVE_JAVA_OPTIONS% javaagent:C:\sw\bea\WL10\wily\Agent.jar Dcom.wily.introscope.agentProfile=C:\sw\bea\WL10\wily\IntroscopeAgent.pro file -Dcom.wily.autoprobe.logSizeInKB=1000

2 Update the AgentAutoNamingEnabled property in the IntroscopeAgent.profile as follows: Set the property to false to disable it or set the property to true to enable it.
introscope.agent.agentAutoNamingEnabled=false introscope.agent.agentAutoNamingEnabled=true
3 Enable the dynamic instrumentation in the IntroscopeAgent.profile as follows:
introscope.autoprobe.dynamicinstrument.enabled=true
4 Start the Application Server.
The size of Autoprobe.*.log is limited to system defined value of 1000KB.
Support for MOM Failover

MOM Hot Failover can be used if a pair of Enterprise Managers share a single Introscope installation and are on different machines. The Introscope installation must reside on a network file system since both Enterprise Managers need read access to the Introscope installation, although only one Enterprise Manager at a time needs write access. For example, the Introscope installation might be shared using a Network Attached Storage (NAS) protocol such as Network File System (NFS) or Server Message Block (SMB).
Two properties added to the EM properties file

Two properties to tune the Data Tiering have been added to the EM properties file. The properties are as follows: reperiodizationOffsetHour This property specifies the time offset in hours for data tiering. Limit: 0 to 23 Default: 0 For example, if reperiodizationOffsetHour is set to 2, the data tiering will start at 2 AM.
May 2010
page 5
conversionOffsetMinute This property specifies the time offset in minutes for spool conversion to data. Limit: 0 to 59 Default: xx:00 For example, if conversionOffsetMinute is set to 10, the spool conversion to data will begin at xx:10.
CA certificates need to be restored when JRE is upgraded

Users upgrading from Introscope 8.0x to 8.2x may encounter errors in LDAP authentication after upgrading, with an error like:
2/24/10 08:22:09 PM MST [INFO] [Manager.UserManagementService] Unable to find user "russelwhavens". The LDAP server is not configured correctly. Please contact the Administrator. javax.naming.CommunicationException: simple bind failed: gdirstage:636 [Root exception is javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target]
To recover from the errors encountered in LDAP authentication after upgrading from Introscope 8.0x to 8.2x:
Copy the previous CA certificate file from where it was saved in <EM_Home>/backup/ to the <EM_Home>/jre/lib/security directory.
EPAgent script does not show the correct status if the EPAgent was previously started without using the script
You can start and stop the EPAgent using either command line arguments or by executing the EPACtrl.sh script. To start and stop the EPAgent using command line arguments: 1 Enter the following command in the command line prompt to start the EPAgent:
java Dcom.wily.introscope.epagent.properties=../IntroscopeEPAgent.properties jar EPAgent.jar

2 Enter the following command to stop the EPAgent in UNIX environment:
kill -9 PID where PID is the process ID.

In the Windows environment, stop EPAgent through services. To start, stop, and find status of the EPAgent by executing the script:
Enter the following in the command prompt:
./EPACtrl.sh start / stop / status

Note: If you start the EPAgent using the script, the script shows the correct status. Important If you start the EPAgent using command line argument, make sure that you stop the EPAgent using command line argument only. Similarly, if you start the EPAgent using the script, make sure that you stop the EPAgent using the script only. If you
May 2010
page 6
do not do so, the EPAgent may not start or stop as expected; the script may also not show the correct status for the EPAgent.
2.1 Enhanced dashboards

Introscope includes Management Modules with preconfigured dashboards that enable you to monitor the performance and capacity of an Enterprise Manager cluster consisting of one or more Collectors and a MOM. The Management Modules are:

Collector_1.jar MOM_Infra_Monitoring_MM.jar
To view dashboards in the Workstation Console: 1. Copy Collector_1.jar and MOM_Infra_Monitoring_MM.jar from <EM_Home>\examples directory to the <EM_Home>\config\modules directory. 2. Edit the Management Modules contained in these .jar files for your own environment, following the instructions under the heading Configuring metric groupings in the chapter Working with Management Modules in the Introscope Configuration and Administration Guide. Note: When you copy the sample Management Modules Collector_1.jar and MOM_Infra_Monitoring_MM.jar in the <EM_HOME>\config\modules directory and customize them to edit metrics groupings, you see that the Metrics Expressions pane for some of the metric grouping contains a hard-coded sample metrics expression:
Delete this sample metrics expression and substitute your own. 3. Configure the Workstation Console to view live data for more than 8 minutes, if required. See Viewing live query data in the Console on page 12 for details. 4. Ensure that your applications are instrumented and providing data. 5. Ensure that the Enterprise Manager is running. 6. Launch the Workstation by clicking Start > Programs > CA Wily > Introscope 8.2.2.0 > Introscope Workstation. 7. Log in to the Workstation. 8. Navigate to the Workstation Console by clicking Workstation > New Console. Now you can view the newly available dashboards. Dashboards that monitor performance The performance metrics show how fast or slow the Enterprise Manager cluster or a particular Collector or MOM is performing.

MOM - Infrastructure Overview MOM - Infrastructure Performance MOM - Cluster Clock Drift
May 2010
page 7

MOM - Cluster Ping Time MOM - Harvest Duration Detail MOM - SmartStor Duration Detail MOM - Event Handling MOM - Collector Query Performance MOM - Resources Capacity MOM - Collectors Performance EM - Collector Performance EM - Collector Harvest Duration Detail EM - Collector SmartStor Duration Detail EM - Collector Event Handling EM - Collector Query Performance EM - Collector Resources Capacity
Dashboards that monitor cluster capacity The following dashboards monitor cluster capacity. Note: Capacity metrics show whether or not the load on the Enterprise Manager cluster is balanced.

MOM - Infrastructure Overview MOM - Infrastructure Capacity MOM - Metrics Capacity Detail MOM - Collectors Capacity EM - Collector - Metrics Detail EM - Collector - Error Snapshot Events
Note: When monitoring an Enterprise Manager cluster, first view the MOM Infrastructure Overview dashboard. Navigation details You can drill down through the dashboards in particular sequences to understand specific cluster and Collector performance issues. To drill down into Collector connection performance:
Drill down from the MOM - Infrastructure Overview dashboard to one of the following dashboards:
MOM - Infrastructure Overview > MOM - Infrastructure Performance > MOM Collectors Connected MOM - Infrastructure Overview > MOM - Infrastructure Performance > MOM Cluster Clock Drift MOM - Infrastructure Overview > MOM - Infrastructure Performance > MOM Cluster Ping Time
May 2010
page 8
To drill down into MOM performance:

1 2
Drill down from the MOM - Infrastructure Overview dashboard to MOM Infrastructure Performance dashboard. Drill down from MOM - Infrastructure Performance dashboard to one of the following dashboards:

MOM - Infrastructure Performance > MOM - Harvest Duration Detail MOM - Infrastructure Performance > MOM - SmartStor Duration Detail MOM - Infrastructure Performance > MOM - Event Handling MOM - Infrastructure Performance > MOM - Collector Query Performance MOM - Infrastructure Performance > MOM - Resources Capacity
To drill down into Collector performance: 1. Drill down from one dashboard to the other in the following sequence:

MOM - Infrastructure Overview > MOM - Infrastructure Performance MOM - Infrastructure Overview > MOM - Infrastructure Performance > MOM Collectors Performance MOM - Infrastructure Overview > MOM - Infrastructure Performance > MOM Collectors Performance > EM - Collector Performance
2. Drill down from the EM - Collector Performance dashboard to the following dashboards in the following sequence:
MOM - Infrastructure Overview > MOM - Infrastructure Performance > MOM Collectors Performance > EM - Collector Performance > EM - Collector Harvest Duration Detail MOM - Infrastructure Overview > MOM - Infrastructure Performance > MOM Collectors Performance > EM - Collector Performance > EM - Collector SmartStor Duration Detail MOM - Infrastructure Overview > MOM - Infrastructure Performance > MOM Collectors Performance > EM - Collector Performance > EM - Collector Event Handling MOM - Infrastructure Overview > MOM - Infrastructure Performance > MOM Collectors Performance > EM - Collector Performance > EM - Collector Query Performance MOM - Infrastructure Overview > MOM - Infrastructure Performance > MOM Collectors Performance > EM - Collector Performance > EM - Collector Resources Capacity
You can examine capacity performance by drilling down into specific dashboards in a particular sequence. To drill down into MOM capacity:
Drill down from the MOM - Infrastructure Overview dashboard to one of the following dashboards in the sequence:

MOM - Infrastructure Overview > MOM - Infrastructure Capacity MOM - Infrastructure Overview > MOM - Infrastructure Capacity > MOM - Metrics Capacity Details
May 2010
page 9
To drill down into Collector capacity:

Drill down from the MOM - Infrastructure Overview dashboard to one of the following dashboards in the sequence:
MOM - Infrastructure Overview > MOM - Infrastructure Capacity > MOM - Collector Capacity MOM - Infrastructure Overview > MOM - Infrastructure Capacity > MOM - Collector Capacity > EM - Collector - Metrics Detail MOM - Infrastructure Overview > MOM - Infrastructure Capacity > MOM - Collector Capacity > EM - Collector - Metrics Detail > EM - Collector - Error Snapshot Events
The following dashboard is available for monitoring the performance and monitoring of Enterprise Manager cluster with Collectors and MOM:
MOM - Infrastructure Overview (Wily EM-Cluster Monitoring)
This dashboard shows the overall health of Wily EM-Cluster Monitoring. It shows alerts for Performance and Capacity. If an alert is red, you navigate to MOM - Infrastructure Performance or MOM - Infrastructure Capacity dashboard.
May 2010
page 10
Performance Dashboards
You can use these dashboards to monitor cluster performance: MOM - Infrastructure Performance (Wily Infrastructure Performance) This dashboard shows the overall health of Wily Infrastructure Performance. It shows alerts for Collectors Connected, Clock Drift, Ping Time, MOM Performance, Harvest Duration, SmartStor Duration, Number of Event Inserts, Remote Queries, CPU & Memory Resources, and Collectors Performance. If an alert is red, you double-click it and navigate to the relevant dashboard. For example, if the Connectors Connected alert is red, double-click the alert to and see the Collectors connection status. MOM - Collectors Connected (Collectors Connection Status) This dashboard shows the overall health of the Collectors Connection Status. It displays alert for Connection Status for Collector 1.
Note You can customize this dashboard to display alerts for all Collectors in the cluster.
For information on customizing dashboards, see the Introscope Workstation User Guide. MOM - Cluster Clock Drift (Collectors Clock Drift) This dashboard displays the clock skew between Collector's clock and the MOM's clock. Collectors with a clock skew greater than 3 seconds are disconnected by the MOM. The alert (per Collector) is configured with a danger threshold of 3 seconds. This dashboard displays alert for Clock Skew for Collector 1.
For information on customizing dashboards, see the Introscope Workstation User Guide. MOM - Cluster Ping Time (Collectors Ping Time) This dashboard shows the overall health of the Ping Time for all Collectors. It displays alert for Ping Time for Collector 1.
For information on customizing dashboards, see the Introscope Workstation User Guide. MOM - Harvest Duration Detail (MOM - Data Harvesting) This dashboard shows the overall health of Data Harvesting. It shows:

An alert and a graph for Harvest Duration for Harvest Cycle. Graphs for Messaging Incoming Threads, Messaging Outgoing Threads, Internal Threads - CPU Time, and Internal Threads - Blocked Time for Threads Performance. Graphs for Metrics Evaluated by Alerts, Metrics Evaluated by Calculators, Number of Applications, and Workstations Connected for Metrics Data Subscriber.
May 2010
page 11
MOM - SmartStor Duration Detail (MOM - SmartStor Data Processing) This dashboard shows the health of SmartStor Data Processing. It shows:

An alert and a graph for SmartStor Duration for Processing Cycle. Alerts for SmartStor Query Duration, SmartStor Query Per Interval, Data Points Retrieved From Disk Per Interval, Metrics Retrieved From Disk Per Interval, and MetaData Write Duration for SmartStor Performance. An alert for Data Points Retrieved From Disk Per Interval for SmartStor Performance. Graphs for Number of Live Metrics and Number of Historical Metrics for Number of Metrics.
MOM - Event Handling (MOM - Event Handling) This dashboard shows the overall health of event handling. It shows:
Graphs for Numbers of Events Processed, Numbers of Inserts Per Interval, and Number of Dropped Per Interval for Event Storage. An alert for Numbers of Events Processed for Event Storage. Graphs for Query Duration Per Interval, Number of Queries Per Interval, Insert Duration Per Interval, and Index Insertion Duration Per Interval for Event Query Performance. Graph for Number of Events in Database for Total Events. Graph for Number of Active Sessions for Active Sessions.

MOM - Collector Query Performance (MOM - Collector Query Performance) This dashboard shows the overall health of query performance for all Collectors in a cluster. It shows:
Graphs for Sync Query Duration and Number of Sync Queries Per Interval for Sync Query Performance. Graphs for Async Query Duration, Number of Async Queries Per Interval, and Number of Sync Queries by CLW Queries Per Interval for Async Query Performance. Graphs for Data Points Returned Per Interval and Metrics Returned Per Interval for Client Returned Data. An alert for Data Points Returned Per Interval for Client Returned Data.
MOM - Resources Capacity (MOM - Resource Capacity) This dashboard shows the overall health of MOM Resource Capacity. It shows alerts for CPU Usage, GC Duration, and Free Disk Space. MOM - Collectors Performance (Collectors Performance) This dashboard shows the overall health of the Collectors Performance. It displays an alert for Collector 1. If an alert is red, you double-click it to open the EM - Collector Performance dashboard to find out the cause of Collectors performance degradation.
May 2010
page 12
For information on customizing dashboards, see the Introscope Workstation User Guide. EM - Collector Performance (EM - Collector Performance) This dashboard shows the overall health and status of Collector Performance. It shows alerts for Harvest Duration, SmartStor Duration, Number of Event Inserts, Query Performance, and CPU & Memory Resources. If an alert is red in this dashboard and you want to know the root cause, you can navigate from this dashboard to the EM - Collector Harvest Duration Detail, EM - Collector SmartStor Duration Detail, EM - Collector Event Handling, EM - Collector Query Performance, and EM - Collector Resources Capacity dashboards. EM - Collector Harvest Duration Detail (EM - Data Harvesting) This dashboard shows the health of Data Harvesting. It shows:

An alert and a graph for Harvest Duration for Harvest Cycle. Graphs for Messaging Incoming Threads, Messaging Outgoing Threads, Internal Threads - CPU Time, Internal Threads - Blocked Time for Threads Performance. Graphs for Metrics vs Handled Metrics, Number of Virtual Metrics, Workstations Connected, and Number of Applications for Metric Data Subscribers.
EM - Collector SmartStor Duration Detail (EM - SmartStor Data Processing) This dashboard shows the health of SmartStor Data Processing. It shows:

An alert and a graph for SmartStor Duration for Processing Cycle. Alerts for SmartStor Query Duration, SmartStor Query Per Interval, Data Points Retrieved From Disk Per Interval, Metrics Retrieved From Disk Per Interval, and MetaData Write Duration for SmartStor Performance. An alert for Data Points Retrieved From Disk Per Interval for SmartStor Performance. Graphs for Number of Live Metrics and Number of Historical Metrics for Number of Metrics.
EM - Collector Event Handling (EM - Event Handling) This dashboard shows the overall health of event handling. It shows:
Graphs for Numbers of Events Processed, Numbers of Inserts Per Interval, and Number of Dropped Per Interval for Event Storage. An alert for Numbers of Events Processed for Event Storage. Graphs for Query Duration Per Interval, Number of Queries Per Interval, Insert Duration Per Interval, and Index Insertion Duration Per Interval for Event Query Performance. Graph for Number of Events in Database for Total Events. Graph for Number of Active Sessions for Active Sessions.

May 2010
page 13
EM - Collector Query Performance (EM - Query Performance) This dashboard shows the overall health and status of Enterprise Manager Query Performance. It shows:
Graphs for Cache Queries Duration and Cache Queries Per Interval for Cache Query Performance. An alert for Cache Queries Duration for Cache Query Performance. Graphs for SmartStor Queries Duration and SmartStor Queries Per Interval for Historical Query Performance. An alert for SmartStor Queries Duration for Historical Query Performance. Graphs for Data Points Returned Per Interval and Metrics Returned Per Interval for Client Returned Data. An alert for Data Points Returned Per Interval. The threshold for it is the corresponding clamp metric.

EM - Collector Resources Capacity (EM - Resource Capacity) This dashboard shows the overall health and status of Enterprise Manager Resource Capacity. It shows alerts for CPU Usage, GC Duration, and Free Disk Space.
Capacity Dashboards
The following dashboards are available for monitoring cluster capacity: MOM - Infrastructure Capacity (Wily Infrastructure Capacity) This dashboard shows the overall health of Wily Infrastructure Capacity. It shows alerts for MOM Capacity and Collectors Capacity. If an alert is red, double-click it to open the relevant dashboard. For example, if MOM - Capacity alert is red, double-click it to navigate to MOM - Metrics Capacity Detail dashboard to find out which agent or agents are responsible for the capacity reduction. MOM - Metrics Capacity Detail (MOM - Capacity) This dashboard shows the overall health of MOM Capacity. It shows:
Alerts and graphs for Number of Agents, Number of Live Metrics, Number of Historical Metrics, and Number of Events Processing for MOM Metrics Stats. Graphs for Number of Collector Metrics and Collector Metrics Received Per Interval for Connected Collector Metrics.
MOM - Collectors Capacity (Collectors Capacity) This dashboard shows the overall health of the Collectors Capacity. It displays alert for Collector 1. If an alert for a Collector is red, double-click it to navigate to EM - Collector - Metrics Detail to find out which agent or agents are responsible for capacity reduction.
For information on customizing dashboards, see the Introscope Workstation User Guide.
May 2010
page 14
EM - Collector - Metrics Detail (EM - Collector Capacity) This dashboard shows the overall health and status of Collector Capacity. You navigate from this dashboard to the EM - Collector - Error Snapshot Events dashboard by clicking an alert. For example, if an alert is red, click the alert to determine which agent or agents have exceeded metric and event clamps. This dashboard displays:
Alerts and graphs for Number of Live Metrics and Number of Historical Metrics for Collector Metrics Stats. Graphs for Number of Agents and Agent Connection Status for Collector Agent Stats. An alert for Number of Agents for Collector Agent Stats. An alert and a graph for Number of Events Processed. An alert for Individual Agent Stats for Connected Agents.

EM - Collector - Error Snapshot Events (EM - Connected Agents Stats) This dashboard shows the event and metric load on the EM in Top N charts (by agents). You navigate to this dashboard from EM - Collector - Metrics Detail to see which agent or agents have exceeded the metric and event clamps This dashboard displays:
Graphs for Transaction Tracing Events Per Interval, Transaction Tracing Exceeding Limit, Errors Per Interval, and Errors Exceeding Limit for Agent events and Numbers of Metrics by Agents, Agents Exceeding Metrics Limit, and Historical Metrics by Agents for Agent Metrics. Alerts for Transaction Tracing Exceeding Limit, Errors Exceeding Limit, and Agents Exceeding Metrics Limit.
Finding more information from dashboards When you want more information about the data presented on dashboards, you can use shortcuts to get more information. To view more information using dashboards:
Right-click a graph or an alert, click Links, and navigate to the corresponding alert in the Management Module or another dashboard associated with the graph or alert. Double-click a metric from the chart displaying top 10 or 25 slowest metric data to view its details in the Investigator.
About Alerts The alerts in the dashboard are:

Threshold alert Clamping Alert
Threshold alerts are based on known numbers for Introscope. Clamping alerts are based on Enterprise Manager clamp limit values.
May 2010
page 15
You can customize the thresholds for alerts. See the Introscope Workstation User Guide for details.
2.2 Viewing Live and Historical Data in the Workstation Console

Viewing live query data in the Console You can view live query data in the Workstation Console. To view live query data and historical data in the Workstation Console with default properties:
1
Click Live to enable it and view live data. The default value for time range is 8 minutes and resolution is 15 seconds. You do not have the option of entering a custom time range and resolution for the live mode in the Console.
Note Click Live to disable it and select a Time range and Resolution from the drop-
down list to view historical data. You can also enter a custom time range. To view live query data and historical data in the Workstation Console:
To view live query data for time range greater than 8 minutes, edit the introscope.enterprisemanager.workstation.extendedLiveQuery property in the IntroscopeEnterpriseManager.properties file in the <EM_Home>\config directory as follows: introscope.enterprisemanager.workstation.extendedLiveQuery=true When this property is set to true, you can use the Time range and Resolution dropdown lists in the Workstation dashboard in the live mode. This allows you to enter custom time range and resolution for the live mode instead of the default time range of 8 minutes and resolution of 15 seconds. You can reset the time range for a greater period than the default time range of eight minutes.
Note The maximum time range for which you can view live data is 30 days. If you enter
a time range greater than 30 days, the Time Range is set to 8 minutes by default. The number of data points displayed in the dashboard is equal to (Time Range/Resolution). If (Time Range/Resolution) is less than 2, the Resolution is set to 15 seconds by default.
Important Setting the time range to greater than 8 minutes may impact the
performance of Enterprise Manager due to the disk I/O operations needed to fetch data from SmartStor. Enabling and disabling Live mode In the Workstation Console, live mode is enabled by default. You can enable or disable live mode by clicking on the Live button.
Note When the Console is in the live mode and the resolution set in the Data Options
widget of the dashboard is 15 seconds, the resolution selected from the Console (toolbar) is used to display the live data. When the Console is in the live mode and the resolution set in the Data Options widget of the dashboard is a number
May 2010
page 16
greater than 15 seconds, the resolution from the widget is used to display the live data. For more information on Data Options see the Introscope Workstation User Guide. Viewing historical data in the Console You can also view historical data. To switch from live to historical data:
Click the Live button.
With Live mode disabled, you can select a Time Range and Resolution from the dropdown list, or enter a custom time range, and view historical data.
Note In the historical mode, the time range and resolution selected from the Console is
always used to display historical data. Launching Investigator from Console If you are viewing live data in the Console and launch the Workstation Investigator from this Console, you can view live data in the Investigator also. However, in the Investigator, the default value for time range is 8 minutes and resolution is 15 seconds. You do not have the option of entering a custom time range and resolution for the live mode in the Investigator. If you are viewing historical data in the Console and launch the Workstation Investigator from this Console, you can view historical data in the Investigator also for the same time range and resolution that you selected for the historical data in the Console. Launching Console from Investigator If you are viewing live data in the Investigator and launch the Workstation Console from this Investigator, you can view live data in the Console also. However, in the Console, the default value for time range is 8 minutes and resolution is 15 seconds. You can enter a custom time range and resolution for the live mode in the Console. If you are viewing historical data in the Investigator and launch the Workstation Console from this Investigator, you can view historical data in the Console also for the same time range and resolution that you selected for the historical data in the Investigator.
May 2010
page 17
2.3 SmartStor Tools Using SmartStor tools to tune SmartStor data

Introscope provides SmartStor command-line tools that enable you to:
clean up from metric leaks and explosions For information about metric leaks and explosions, see the Introscope Sizing and Performance Guide.
merge data folder of one Enterprise Manager with the data folder of another Enterprise Manager.
The SmartStor tools start scripts are located in the <EM_Home>/tools/ directory. Run SmartStor tools in a Windows environment using the SmartStorTools.bat start script. Run SmartStor tools in a UNIX environment using the SmartStorTools.sh start script. When you run the SmartStor tools commands from the <EM_Home> command line using valid arguments, the tools perform the requested commands. If you run the SmartStor tools commands using invalid arguments, the script displays a help message.
WARNING The source Enterprise Manager must be shut down when using SmartStor
tools. CA Wily Technology recommends shutting down the source and destination Enterprise Managers when running SmartStor tools. If an Enterprise Manager is running when SmartStor tools are used, there is a risk of SmartStor corruption. This can occur if the Enterprise Manager is writing data to SmartStor when SmartStor tools are also making changes to SmartStor data.
Commands and syntax

Run these SmartStor tools commands using this format: <SmartStorTools start script> <command> <arguments>

merge remove_metrics remove_agents keep_agents prune you do not accidentally delete important data.
WARNING Use the prune tool with caution. Since this tool deletes data, take care that

test_regex list_agents
SmartStor tools commands reference

merge
Usage Merges a specified SmartStor source directory into a different destination directory
May 2010
page 18
Arguments
<destination SmartStor directory> -help Prints a help message <source SmartStor directory>
Examples
Windows SmartStorTools.bat merge <source directory> <destination directory>

For example:
SmartStorTools.bat merge <EM_Home>\data
C:\data
When the command executes successfully, all the SmartStor data present in the source directory is merged with the data in the destination directory.
UNIX SmartStorTools.sh merge <source directory> <destination directory> remove_metrics

Usage Removes metrics matching the given regular expression. Use this tool to clean up metrics leaks and explosions. WARNING Use the remove_metrics tool with caution. Since this tool deletes data, take care that you do not accidentally delete important data.

Arguments
-dest -help -metrics -src
Destination SmartStor directory Prints a help message Regular expression for metrics to remove Source SmartStor directory
Examples
Windows SmartStorTools.bat remove_metrics dest <destination directory> -metrics <metrics to be removed> -src <source directory>
For example: <EM_Home>\tools\SmartStorTools.bat remove_metrics dest
C:\SWDump\destination -metrics ".*Socket.*" -src <EM_Home>\data

When the command executes successfully, all the metrics except the socket metrics are present in the destination directory and the source directory has all the metrics intact.
UNIX SmartStorTools.sh remove_metrics dest < destination directory> -metrics <metrics to be removed> -src <source directory> remove_agents
Usage Removes agents matching the given regular expression WARNING Use the remove_agent tool with caution. Since this tool deletes data, take care that you do not accidentally delete important data.

Arguments
-agents -dest -help -src
Regular expression for agents to remove Destination SmartStor directory Prints a help message Source SmartStor directory
May 2010
page 19
Example
Windows SmartStorTools.bat remove_agents agents <Agent name> dest <destination directory> -src <source directory>
For example: <EM_Home>\tools>SmartStorTools.bat remove_agents agents
".*WebSphere.*" -dest C:\SWDump\destination -src <EM_Home>\data

When the command executes successfully, all the metrics related to WebSphere agents are removed from the destination directory and all the metrics in the source directory remain intact.
UNIX SmartStorTools.sh remove_agents agents ".*WebSphere.*" dest <destination directory> -src <source directory> keep_agents
Usage Arguments Keeps agents matching the given regular expression

-agents -dest -help -src
Regular expression for agents to keep Destination SmartStor directory Prints a help message Source SmartStor directory
Examples
Windows SmartStorTools.bat keep_agents agents <Agent(s) name> dest <destination directory> -src <source directory>
For example:
<EM_Home>\tools>SmartStorTools.bat keep_agents -agents ".*WebSphere.*" -dest C:\SWDump\destination\keepagents -src <EM_Home>/data

When the command executes successfully, all the metrics related to WebSphere agents are present in the destination directory and the contents of source directory are intact.
UNIX SmartStorTools.sh keep_agents -agents <agent(s) name> -dest <destination directory> -src <source directory> prune
Usage Finds agents that have no historical data in SmartStor, and removes all associated metric metadata. Use this tool to clean up metrics leaks and explosions. WARNING Use the prune tool with caution. Since this tool deletes data, take care that you do not accidentally delete important data. Using the prune tool requires several steps. See Pruning SmartStor metadata on page 18. Arguments

-backup -help -silent -src
Backup directory for copies of modified files Prints a help message Silent mode Source SmartStor directory
May 2010
page 20
Examples
Windows SmartStorTools.bat Prune <source directory>

For example:
backup <destination directory>
-src
<EM_Home>\tools>SmartStorTools.bat Prune -backup C:\SWDump\destination\backup -src <EM_Home>/data When the command executes successfully, a new metrics.metadata file is created in
backup directory. This metadata file will not have the pruned data in the backup directory.
UNIX SmartStorTools.sh prune -backup <destination directory> -src <source directory> test_regex
Usage Arguments Prints to the Windows or UNIX console the metrics or agents matching the given regular expression.

-help -src -agents -metrics
Prints a help message Source SmartStor directory Regular expression for agents to match Regular expression for metrics to match
Examples
Windows SmartStorTools.bat test_regex -agents <agent(s) name> src <source directory>

For example: <EM_Home>\tools>SmartStorTools.bat test_regex -agents ".*WebSphere.*" -src <EM_Home>\data
UNIX SmartStorTools.sh test_regex -agents <agent(s) name> -src <source directory> Windows SmartStorTools.bat test_regex -metrics <metrics to be removed> -src <source directory>
For example:
<EM_Home>\tools>SmartStorTools.bat test_regex -metrics ".*Socket.*" -src <EM_Home>\data UNIX SmartStorTools.sh test_regex -metrics ".*Socket.*" -src <source directory> list_agents
Usage Arguments Lists the agents matching the given regular expression.
-help -src -agents
Prints a help message Source SmartStor directory Regular expression for agents to match
Examples
Windows SmartStorTools.bat list_agents -agents <agent(s) name> src <source directory>

For example: <EM_Home>\tools>SmartStorTools.bat list_agents -agents ".*WebSphere.*" -src <EM_Home>\data
May 2010
page 21
When the command executes successfully, the agent names that match the regular expression are listed with their last reported date.
UNIX SmartStorTools.sh list_agents -agents <agent(s) name> -src <source directory> Pruning SmartStor metadata Use the prune SmartStor tool to find agents that have no historical data in SmartStor, then remove all associated metric metadata. Use this tool to clean up metrics leaks and explosions.
Important CA Wily Technology recommends shutting down the Enterprise Manager
when running SmartStor tools. Since Enterprise Managers create SmartStor data when running, if you use SmartStor tools, the results can be unpredictable. To prune SmartStor metadata:
1 2
Shut down the Enterprise Manager. From a command prompt, run the prune command. For example: On Windows: <EM_Home>\tools>SmartStorTools.bat prune -src <path to data directory> -backup <path to backup directory> On UNIX: <EM_Home>/tools>SmartStorTools.sh prune -src <path to data directory> -backup <path to backup directory> When the command executes successfully:

all the dead metrics are pruned from the source directory the Windows or UNIX console displays the pruned metrics during the prune operation include the >> argument in the command. For example: <EM_Home>\tools>SmartStorTools.bat prune -src <path to data directory> -backup D:\backup >>D:\console.txt
Note To redirect the Windows or UNIX console pruned metrics list to a text file,
a new metrics.metadata file without dead metrics is created in the backup folder.
Run the test_regex command on the backup directory. The Windows or UNIX console displays the command output showing all the metrics based on the regular expression you included in the command. Notice that the pruned metrics are no longer present. For example, if you were pruning a large number of socket metrics, you would run this test_regex command: On Windows: <EM_Home>\tools>SmartStorTools.bat test_regex -metrics ".*Socket.*" -src <path to backup directory> On UNIX: <EM_Home>/tools>SmartStorTools.sh test_regex -metrics ".*Socket.*" -src <path to backup directory>
Restart the Enterprise Manager.
May 2010
page 22
Trimming SmartStor data and metadata Use the SmartStor tools to trim excess SmartStor data.
Important CA Wily Technology recommends shutting down the Enterprise Manager
when running SmartStor tools. Since Enterprise Managers create SmartStor data when running, if you use SmartStor tools, the results can be unpredictable. For an example about how to find a SmartStor data problem, see Example: Using the test_regex command to find a SmartStor data problem on page 20. Also see the topics about metrics leaks and explosions in the Introscope Sizing and Performance Guide. To trim SmartStor data and metadata:
1 2
Shut down the Enterprise Manager. From a command prompt, run the test_regex command to print the current metric list. For example, if Introscope is installed in the <EM_Home> directory and SmartStor is configured to save data in the <EM_Home>\data directory, run this command: <EM_Home>\tools>SmartStorTools.bat test_regex -metrics <EM_Home>\data (".*") -src
You will see a list of fully-qualified metric names, including the host name, agent name, metric name, and metric IDs. The total line count gives an indication of total number of metrics, although it is not as accurate as the metric count you get from the supportability metrics in the Investigator. By doing line counts against specific regular expressions matching an agent or metric name, you can get an idea of what metrics are occupying the majority of the space. This also helps identify what metrics you are not interested in and would like to remove.
3 4
From the list of metrics, pick metrics from specific agents to be removed. Run the SmartStor tools remove_metrics command to remove a set of excess metrics. For example, if you have high SQL metric counts, use this command to remove all the SQL metrics: <EM_Home>\tools>SmartStorTools.bat remove_metrics dest c:\sql_metrics_removed -metrics ".*SQL.*" -src <EM_Home>\data When the command executes successfully, all the metrics except the SQL metrics are present in the destination directory and the source directory has all the metrics intact.
Note This command needs approximately as much target space (although it will
shrink by a few GB) to run as the space occupied by the original data (specified by the src option). In the example above, the new data without the SQL metrics (specified by the dest option) will now be in the c:\sql_metrics_removed directory. This command is a long-running operation and can run for a few hours.
5
If necessary, repeat the remove_metrics command on a different set of excess metrics. Sockets are another common source of leaked metrics. After running the remove_metrics command in Step 4, use this command to remove socket metrics:
May 2010
page 23
<EM_Home>\tools>SmartStorTools.bat remove_metrics dest c:\sql_and_sockets__metrics_removed -metrics ".*Sockets.*" -src c:\sql_metrics_removed This command makes use of the data derived from the first command that removed SQL metrics as the source data (the data in the c:\sql_metrics_removed directory). The data that has both SQL and socket metrics removed will then be in this location specified by the dest option: c:\sql_and_sockets__metrics_removed. Again, this command needs almost as much extra space to run as the original data.
6
Check the metrics data value for the cleaned metrics data and metadata.
a b c
Open the IntroscopeEnterpriseManager.properties file in the <EM_Home>\config directory. Make a note of the current property setting, then set the property introscope.enterprisemanager.metrics.historical.limit=500000. Make a note of the current setting, then set the property introscope.enterprisemanager.smartstor.directory= to point to the destination location for the metrics removal. For example, the example destination location in Step 5 is: c:\sql_and_sockets__metrics_removed Therefore, this property setting would be: introscope.enterprisemanager.smartstor.directory=c:\sql_and_sockets__m etrics_removed Restart the Enterprise Manager. Check the value of this metric: Enterprise Manager | Data Store | SmartStor | Metadata | Metrics with Data The value should be far below the original value. If it is not, repeat the trimming steps using suitable SmartStor tools commands against agent or metric names that are not needed. Once the historical metric count is below 300K, the Enterprise Manager will run more efficiently.
d e
If needed, reset the changed IntroscopeEnterpriseManager.properties values back to their original settings.
a b c
Shut down the Enterprise Manager. Open the IntroscopeEnterpriseManager.properties file in the <EM_Home>\config directory. Reset these properties back to the original settings noted in Step 6 (b) and (c):

introscope.enterprisemanager.metrics.historical.limit= introscope.enterprisemanager.metrics.historical.limitintroscope.ente rprisemanager.smartstor.directory=
Restart the Enterprise Manager.
Example: Using the test_regex command to find a SmartStor data problem In this example, you use the text_regex command to discover that JMX metrics data have exploded.
1
Run a test_regex command to produce a readable version of metrics.metadata.
May 2010
page 24
For example: <EM_Home>\tools>SmartStorTools.bat test_regex -metrics "(.*)" -src <EM_Home>\data The result is a list of the metadata metrics.
2
Review the metadata metrics list to determine the probable source of the metrics leak or explosion. For example, you may find a lot of metrics metadata entries for JMX metrics. (Optional) Run a script to sort and group the metrics. For example, to verify that JMX metrics are the source of the metrics explosion you can run this script: grep '|'.* | awk -F'|' '{print $1}' | sort | uniq -c If you are using a UNIX system, this would be the full test_regex command with sort script: SmartStorTools.sh test_regex -metrics -src ../data | grep '|'.* | awk F'|' '{print $1}' | sort | uniq -c
Review the sort results. For example, you might see a list of metric counts and types that looks like this:
1054327 JMX 1564 JSP 1051 OlamWebApp 889 EJB 569 CEF 496 Struts 173 Edocs 167 Servlets 36 CPU 29 Sockets
In this case, SmartStor is storing over a million metrics, and most are JMX metrics. This indicates theres been a JMX metrics explosion that can be cleaned up using SmartStor tools. For more information on metrics explosions, see the Introscope Sizing and Performance Guide.
2.4 Configuring the Command Line Workstation Log

You can configure Introscope to log Command Line Workstation commands to the Enterprise Manager console and the IntroscopeEnterpriseManager.log file, which is located in the <EM_Home>/logs directory. To configure Command Line Workstation Log:
1 2
Open the IntroscopeEnterpriseManager.properties file located in the <EM_Home>\config directory. Configure these properties in the IntroscopeEnterpriseManager.properties file to enable the logging of CLW commands in the log file and on the Enterprise Manager console:
May 2010
page 25
a Set log4j.additivity.Manager.CLW=true. Note The default value for this property is false. b Set log4j.logger.Manager.CLW=DEBUG.
The default value for this property is INFO.
2.5 Metric Clamping

Clamping The Enterprise Manager properties include a set of clamps with configurable values to allow the Enterprise Manager to remain robust when flooded with metrics and queries. These clamps limit the number of metrics, queries, agent connections, Transaction Trace events, and errors that the Enterprise Manager can process during each 15-second time slice. When any of the clamps is triggered, the Enterprise Manager is prevented from being overloaded; therefore the clamps limit the amount of processing the Enterprise Manager has to perform. For example: When the agent metrics limit clamp is triggered, all the rest of the agent metrics reported by the agent are dropped for the remainder of that interval. To configure Enterprise Manager clamps:
1 2
Navigate to the IntroscopeEnterpriseManager.properties file located in the <EM_Home>\config directory. Configure the following IntroscopeEnterpriseManager.properties clamp properties as appropriate.
For Enterprise Manager metric clamping:

The introscope.enterprisemanager.agent.metrics.limit property defines the limit for live and historical metrics per agent. For example: introscope.enterprisemanager.agent.metrics.limit=50000 The default value for this property is 50000. This property applies to both standalone Enterprise Managers and Collectors. This property prevents Enterprise Manager from being overloaded due to flooding of metrics from a single agent. This property limits the number of metrics that Enterprise Manager can receive from an agent. When the clamp is hit, all the rest of the metrics are dropped by Enterprise Manager for the remainder of that interval.
The introscope.enterprisemanager.metrics.live.limit property defines the limit for live metrics per Enterprise Manager. For example: introscope.enterprisemanager.metrics.live.limit=500000 The default value for this property is 500000. This property applies to both standalone Enterprise Managers and Collectors. This property prevents the Enterprise Manager from getting overloaded due to flooding of live metrics from a single agent. This property limits the number of live metrics that Enterprise Manager can receive from an agent. When the clamp
May 2010
page 26
is hit, all the rest of the live metrics are dropped by Enterprise Manager for the remainder of that interval.
The introscope.enterprisemanager.metrics.historical.limit property defines the limit for historical metrics retrieved from SmartStor data per Enterprise Manager. For example: introscope.enterprisemanager.metrics.historical.limit= 1200000 The default value for this property is 1200000. This property applies to both standalone Enterprise Managers and Collectors. This property prevents the Enterprise Manager from getting overloaded due to flooding of historical metrics from a single agent. This property limits the number of historical metrics that Enterprise Manager can receive from an agent. When the clamp is hit, all the rest of the historical metrics are dropped by Enterprise Manager for the remainder of that interval.
The introscope.enterprisemanager.query.datapointlimit property defines the limit for Enterprise Manager query data point retrieval. It defines the maximum number of metric data points that a Collector or standalone Enterprise Manager can retrieve from SmartStor for a particular query. This property limits the impact of a query on disk I/0. For example: introscope.enterprisemanager.query.datapointlimit=10000 The default value for this property is 0. This property applies to standalone Enterprise Managers, Collectors, and MOM. If you query for four metrics and the clamp is hit when the second metric is being processed, the Enterprise Manager does not retrieve data points for the remaining metrics.
The introscope.enterprisemanager.query.returneddatapointlimit property defines the limit for Enterprise Manager query data point return. It defines the maximum number of metric data points that a Collector or standalone Enterprise Manager can return or retrieve for a particular query. This property limits the impact of a query on memory. For example: introscope.enterprisemanager.query.returneddatapointlimit= 100000 The default value for this property is 0. This property applies to standalone Enterprise Managers, Collectors, and MOM. If you query for four metrics and the clamp is hit when the second metric is being processed, the Enterprise Manager does not retrieve data points for the remaining metrics.
For agent connection clamping:

The introscope.enterprisemanager.agent.connection.limit property defines the limit for the number of agents that can connect to an Enterprise Manager. For example: introscope.enterprisemanager.agent.connection.limit=400
May 2010
page 27
The default value for this property is 400. This property applies to both standalone Enterprise Managers and Collectors. When the clamp is hit and a new agent tries to connect to the Enterprise Manager, the Enterprise Manager logs this and does not accept the new connection.
For Transaction Trace clamping:

The introscope.enterprisemanager.events.limit property defines the limit for number of transaction events processed by the Enterprise Manager for each interval. For example: introscope.enterprisemanager.events.limit=1250 The default value for this property is 1250. This property applies to standalone Enterprise Managers, Collectors, and MOM. This clamp is applied to the total number of all transaction events generated by all agents. When the clamp is hit, all the rest of the transaction events reported by the agent are dropped for the remainder of that interval.
The introscope.enterprisemanager.agent.trace.limit property defines the limit for number of transaction events that the Enterprise Manager can handle for each agent per interval. For example: introscope.enterprisemanager.agent.trace.limit=1000 The default value for this property is 1000. This property applies to both standalone Enterprise Managers and Collectors. If the number of transaction traces that the agent reports exceeds the specified limit, all the rest of the traces are dropped by the Enterprise Manager.
For error snapshots clamping:

The introscope.enterprisemanager.agent.error.limit property defines the limit for number of error snapshots that the Enterprise Manager can handle for each agent per interval. For example: introscope.enterprisemanager.agent.error.limit=10 The default value for this property is 10. This property applies to both standalone Enterprise Managers and Collectors. If the number of error snapshots that the agent reports exceeds the specified limit, all the rest of the errors are dropped by the Enterprise Manager.
Disabling clamps You can disable the Enterprise Manager clamps. To disable Enterprise Manager clamps:
1 2
Navigate to the IntroscopeEnterpriseManager.properties file located in the <EM_Home>\config directory. To disable a particular IntroscopeEnterpriseManager.properties clamp, set the value of the clamp to 0.
May 2010
page 28
2.6 Enterprise Manager health and supportability metrics

Health and supportability metrics display information about the Enterprise Manager rather than the application it is monitoring. They appear in the Investigator tree, under: Custom Metric Host (Virtual) Custom Metric Process (Virtual) Custom Metric Agent (Virtual)(SuperDomain) Beneath this level, health and supportability metrics are arranged in the following hierarchy. Enterprise Manager node Under the Enterprise Manager node, you can find these metrics, which are new in this release:
Connections

EM Live Metric Clamped EM Historical Metric Clamped Number of Events Processed Number of Events Processed Limit Exceeded Max Number of Agent Connection Limit Exceeded Per Interval Collectors
MOM
<Collector name> - Skew Time (ms)

Collector Number of Async Queries per Interval Collector Async Queries Duration (ms) Collector Number of Sync Queries per Interval Collector Sync Queries Duration (ms) Collector Number of Sync Queries by CLW per Interval
Agent sub-node
<Agent name>

Transaction Tracing Events Per Interval Transaction Tracing Events Limit Exceeded Error Snapshot Events Per Interval Error Snapshot Events Limit Exceeded
Internal sub-node
Alerts
Total Number of Evaluated Metrics Total Number of Evaluated Metrics
Calculators
Note This metric appears in the Investigator only when a calculator is defined.
May 2010
page 29
<calculator name>
Total Number of Evaluated Metrics Data Points Retrieved From Disk Per Interval Data Points Returned Per Interval Metrics Read From Disk Per Interval Metrics Returned Per Interval Queries Exceeding Max Data Points Read From Disk Limit Per Interval Queries Exceeding Max Data Points Returned Limit Per Interval
Query

Definitions for newly added metrics Definitions for metrics, which are new in this release, are described in the following list.
Connections metrics
EM Live Metric Clamped Indicates if the number of live metrics handled by Enterprise Manager is less than or greater than the maximum limit specified in the introscope.enterprisemanager.metrics.live.limit property for Enterprise Manager clamps. The metric value is 0 if the number of live metrics for the Enterprise Manager is less than the specified limit. The metric value is 1 if the number of live metrics for the Enterprise Manager is greater than the specified limit.
Note You can define the clamp limit for
introscope.enterprisemanager.metrics.live.limit property in the IntroscopeEnterpriseManager.properties file. The IntroscopeEnterpriseManager.properties file is located in the <EM_Home>\config directory. EM Historical Metric Clamped Indicates if the number of live metrics handled by Enterprise Manager is less than or greater than the maximum limit specified in the introscope.enterprisemanager.metrics.historical.limit property for Enterprise Manager clamps. The metric value is 0 if the number of live metrics for the Enterprise Manager is less than the specified limit. The metric value is 1 if the number of live metrics for the Enterprise Manager is greater than the specified limit.
introscope.enterprisemanager.metrics.historical.limit property in the IntroscopeEnterpriseManager.properties file. The IntroscopeEnterpriseManager.properties file is located in the <EM_Home>\config directory. Number of Events Processed Indicates the total number of all events such as Transaction Traces and errors that the Enterprise Manager processes in each interval.
May 2010
page 30
Number of Events Processed Limit Exceeded The number of times the clamp limit defined in the introscope.enterprisemanager.events.limit property exceeded for a particular interval.
introscope.enterprisemanager.events.limit property in the IntroscopeEnterpriseManager.properties file. The IntroscopeEnterpriseManager.properties file is located in the <EM_Home>\config directory. Max Number of Agent Connection Limit Exceeded Per Interval The number of times the clamp limit defined in the introscope.enterprisemanager.agent.connection.limit property exceeded for a particular interval.
introscope.enterprisemanager.agent.connection.limit property in the IntroscopeEnterpriseManager.properties file. The IntroscopeEnterpriseManager.properties file is located in the <EM_Home>\config directory. MOM metrics Collector | <Collector name> | Skew Time (ms) Indicates the clock skew for a specific Collector. Collector Number of Async Queries per Interval The total number of asynchronous queries for all Collectors. Collector Async Queries Duration (ms) The total time taken for all asynchronous queries for all Collectors. Collector Number of Sync Queries per Interval The total number of synchronous queries for all Collectors. Collector Sync Queries Duration (ms) The total time taken for all synchronous queries for all Collectors. Collector Number of Sync Queries by CLW per Interval The total number of synchronous queries for all Collectors requested from all Command Line Workstations. Agent metrics <Agent name> | Transaction Tracing Events Per Interval The total number of Transaction Trace events per agent per interval.
May 2010
page 31
<Agent name> | Transaction Tracing Events Limit Exceeded The number of times the clamp limit defined in the introscope.enterprisemanager.agent.trace.limit property exceeded for a particular interval. This metric is displayed for each agent.
introscope.enterprisemanager.agent.trace.limit property in the IntroscopeEnterpriseManager.properties file. The IntroscopeEnterpriseManager.properties file is located in the <EM_Home>\config directory. <Agent name> | Error Snapshot Events Per Interval The total number of error snapshot events per agent per interval. <Agent name> | Error Snapshot Events Limit Exceeded The number of times the clamp limit defined in the introscope.enterprisemanager.agent.error.limit property exceeded for a particular interval. This metric is displayed for each agent.
introscope.enterprisemanager.agent.error.limit property in the IntroscopeEnterpriseManager.properties file. The IntroscopeEnterpriseManager.properties file is located in the <EM_Home>\config directory. Internal sub-node Alerts | Total Number of Evaluated Metrics The total number of metrics evaluated for all alerts. Calculators | Total Number of Evaluated Metrics The total number of metrics evaluated for all calculators.
Note This metric appears in the Investigator only when a calculator is defined.
<calculator name> | Total Number of Evaluated Metrics The total number of metrics evaluated for an individual calculator. Query Data Points Retrieved From Disk Per Interval The number of data points retrieved from SmartStor per interval. Data Points Returned Per Interval The number of data points that the Enterprise Manager returned to clients per interval. Metrics Read From Disk Per Interval Number of metrics read from SmartStor per interval.
May 2010
page 32
Metrics Returned Per Interval The number of unique metrics that the Enterprise Manager returned to clients. Queries Exceeding Max Data Points Read From Disk Limit Per Interval Indicates if the maximum number of metric data points specified in the introscope.enterprisemanager.query.datapointlimit property that an Enterprise Manager can retrieve for a particular query. The metric value is 0 if the number of metric data points returned by the Enterprise Manager is less than the specified limit. The metric value is 1 if the number of metric data points returned by the Enterprise Manager is greater than the specified limit.
introscope.enterprisemanager.query.datapointlimit property in the IntroscopeEnterpriseManager.properties file. The IntroscopeEnterpriseManager.properties file is located in the <EM_Home>\config directory. Queries Exceeding Max Data Points Returned Limit Per Interval Indicates if the maximum number of metric data points specified in the queryintroscope.enterprisemanager.query.returneddatapointlimit property that an Enterprise Manager can return for a particular query. The metric value is 0 if the number of metric data points returned by the Enterprise Manager is less than the specified limit. The metric value is 1 if the number of metric data points returned by the Enterprise Manager is greater than the specified limit.
introscope.enterprisemanager.query.returneddatapointlimit property in the IntroscopeEnterpriseManager.properties file. The IntroscopeEnterpriseManager.properties file is located in the <EM_Home>\config directory.
3. Installation and upgrade notes a. Upgrading from previous releases of Introscope 8.0x for Java Agent
The Introscope 8.2 installer will automatically upgrade earlier 8.x versions to its level. See the Introscope Installation and Upgrade Guide for complete information.
b. Upgrading to Introscope 8.2 for Java Agent

You can use the Introscope 8.2 installer, which supports Introscope versions 7.0, 7.1, 7.2, 8.0, 8.1 and their patch or service pack releases, to upgrade your 7.x or 8.x Enterprise Manager automatically to the latest 8.2. Any 8.x installer will automatically upgrade earlier 8.x versions to its level. The Enterprise Manager, Workstation and WebView are compatible only with samerevision releases, so if you upgrade any of these components to 8.2, you must upgrade all of them. The Introscope Installation and Upgrade Guide contains special instructions for upgrading version 6.1 agents.
May 2010
page 33
The Enterprise Manager is backward-compatible with agents, so you can continue to use pre-8 agents with Enterprise Manager 8.2. Please note: Any version 8.0.x agent can connect to a version 8.2 Enterprise Manager. However, 8.0.0. or 8.0.1 agents should be upgraded to 8.0.2 or above to be compatible with 8.0.2+ Enterprise Manager. Versions 8.1.X+ and 8.0.2+ agents are fully compatible with both 8.1 and 8.2 Enterprise Manager. Upgrading agents to 8.2 will allow you to take full advantage of version 8.2 functionality.

See the Introscope Installation and Upgrade Guide for instructions on upgrading to Introscope 8.2.
c. Integrations
CA-Wily Customer Experience Manager integration
Integration of CA-Wily Customer Experience Manager (CEM) with Introscope 8.x requires CEM version 4.2.x or above. If you have a prior version of CEM, you must upgrade to CEM 4.2.x before integrating it with Introscope 8.x. Refer to the Wily CEM Integration Guide for detailed information. See also the note below numbered 47740. When integrating Wily CEM with Introscope .NET agents, follow the procedure documented in the "Integrating Wily Introscope with Wily CEM" chapter of the Wily CEM Integration Guide.
Other CA products
Customers who intend to integrate Introscope 8.x with the following CA products: Service Quality Management (SQM) SPECTRUM must install the Introscope Integration Software Developer's Kit (SDK) version 7.2.1.0 or above, available through CA Wily software fulfillment.
d. Introscope documentation and version numbers

The core Introscope documentation set was last updated for version 8.1. All the information contained in Introscope 8.1 documentation, which is shipped with the Introscope 8.2 release, is current except as noted in these Release Notes and in any additional documentation included with the release, such as the Extension for CA SYSVIEW User Guide.
4. Backward compatibility
Introscope 8.2 is backwards compatible with all supported Introscope Agents dating back to Introscope 6.0, except: Version 8.0.1 agents with some specific configurations are not compatible with Enterprise Manager version 8.0.2, so customers who upgrade to Enterprise Manager 8.0.2+ are strongly encouraged to upgrade their 8.0.1 agents to 8.0.2+ agents. Version 7.x agents will continue to work with Enterprise Manager 8.0.2+. The 8.2 Introscope Agent does not support web applications running on Java 1.3.x. If you have a Java 1.3.x-based application, use the Introscope 7.2 agent to manage that application.
May 2010
page 34
5. Limitations & restrictions

The JDBC Driver API to access Introscope transaction details does not support the Microsecond Traces. This issue has no impact on the Workstation user interface that allows you to view transaction details. This issue only impacts the customized tools built to access transaction details using the Introscope JDBC API. The result set returned by the JDBC API does not have the indicator to differentiate between microsecond traces and normal millisecond traces.
Deprecated and changed features

No features are deprecated or removed in this release.
6. Fixed in this release

Fixed in Service Pack Release 8.2.3
The following known issues from earlier releases have been fixed in this release.
Problem ID 61438 61439 61440 Description Two problems with the platform monitor for HP-UX on IA 64 have been fixed. A problem where ChangeDetector metrics failed to appear under certain circumstances has been fixed.
Fixed in Service Pack Release 8.2.2

The following known issues from earlier releases have been fixed in this release.
Problem ID 51847 52922 53112 53187 53234 54209 54812 55370 55372 55383 56111 56570 56509 56572 56573 Description A problem with the EM writing incomplete data to an external UDB database has been fixed. A problem in which a CLW query was not producing the expected metrics has been fixed. A problem with Regex Normalizer keys has been fixed. A problem with automatic transaction trace launching has been fixed. A problem where SOA Performance Manager was causing performance problems in release 8.1 has been fixed. A datatype problem that caused miscalculations has been fixed. A problem, in which WebStart was not working after MOM hot failover had been configured, has been fixed. Some problems with functionality of the right-click menu in the Workstation Investigator have been fixed. A problem that occurred after upgrading to 8.1, having to do with duplicate metrics generated from JavaScript calculators, causing exceptions to be thrown, has been fixed. A problem with retention of aged metrics has been fixed. A problem with slow MOM response has been fixed. A problem where the MOM was failing to report metrics to the Workstation has been fixed.
May 2010
page 35
Problem ID 58060 58936 58630 58636 59219 59282 59522
Description A problem with displaying the hostname in Investigator has been fixed. A problem with web services running on NetWeaver systems has been fixed. A problem where the MOM became unresponsive after a Collector disconnected has been fixed. A problem that occurred after upgrade to 8.1, where the Collector intermittently failed to report metrics, has been fixed. A problem where the agent was causing out of memory conditions has been fixed. A problem with refreshing live data with certain time ranges and resolutions has been fixed.
Fixed in Service Pack Release 8.2.1.0

Problem ID Description
57760
Agent crashed on "java.lang.OutOfMemoryError", call dumping generated in dir StringEveryEventGatherer operates by appending its data points (which are strings) to its internal arraylist. If an harvest never happens, this arraylist can go unbounded and cause a memory leak. This fix ensures that this arraylist size is bounded.
Fixed in Minor Release 8.2.0.0

Problem ID 43254 Description
EM Port added to Agent supportability metrics An EM Port metric has been added to the existing list of agent supportability metrics. This will help identify the EM to which the agent is connected, and when there are multiple EMs on the same host. Additional Enterprise Manager Supportability Metrics The following enterprise manager supportability metrics have been added: Java Process Launch Time Java Version JVM Vendor Under normal circumstances, the Java Process refers to the process ID of the Java process of the enterprise manager. For example, if it reports 1256@machine_name, 1256 would refer to the Enterprise Managers Java process ID. In addition to supportability metrics already available with the EPAgent, three other metrics have been added: Process ID Release Version EM port These metrics are supported only with Java version 1.5 and above. The Workstation will now show red and yellow highlighting for threshold and caution values in data tables.
43445
45819
50464
May 2010
page 36
Problem ID 50520
Description
Workstation alert messages can now be selected and copied Alert messages that appear on the Introscope Workstation can now be selected and copied. To copy the text, simply select the message text and use Ctrl-c to copy the message. Note: Only one message can be selected at a time Support for the Fully Qualified Domain Name (FQDN) on the agent The agent now supports the fully qualified domain name (FQDN). This capability is enabled through the following property in the agent profile: introscope.agent.display.hostName.as.fqdn=false This property is disabled by default, but can be enabled by setting the above property to true. The managed application must be restarted to take effect of the changes to the property value.
51356
52180 53613 54576 54908
The CPU Utilization metrics graph will now be displayed in WebView under historical mode. Custom mBean functionality on Tomcat restored A problem with metrics for JMX dynamic beans on the Tomcat platform has been fixed. Right-click functionality restored In the Workstation Investigator, you can search for information. From the search result pane, you can drill down to specific metrics and graphs that display these metrics. When you click the back arrow after viewing results from the search, right-click menu options are available.
May 2010
page 37
7. Known issues
You can contact Wily Support (http://www.ca.com/wily/support) for more information about any of these issues. Issues marked with are new in this version 8.2.3 For SAP-related issues, see Section 8. For SPM-related issues, see the ReadMe file published with your SPM download.
High priority issues

Problem ID 38182 48922 Description Customers using JVM AutoProbe with the IBM JVM version 1.5 may see unnaturally high CPU overheard. The workaround for this issue is documented in the following Knowledge Base articles on http://www.ca.com/wily/support.

46519 49313 56436
1317 1730 2225
Installing the platform monitor on HPUX using .zip or .tar installers requires administrators to change read-write permissions on the following files to 777: wily/ext/introscopeHpuxItanium64Stats.jar wily/ext/introscopeHpuxItaniumStats.jar wily/ext/introscopeHpuxParisc32Stats.jar wily/ext/introscopeHpuxParisc64Stats.jar wily/ext/libIntroscopeHpuxItanium64Stats.so wily/ext/libIntroscopeHpuxItaniumStats.so wily/ext/libIntroscopeHpuxParisc32Stats.so wily/ext/libIntroscopeHpuxParisc64Stats.so Make these changes after installing the agent and before starting it. If you are using a 32 bit, you also must install gcc before starting the agent. You can download gcc, a compiler for C and C++, by searching HPs support website. It is not necessary to install gcc on a 64-bit machine.
46557
The 8.0 Introscope Agent does not support web applications running on Java 1.3.x. If you have a Java 1.3.x-based application, use the Introscope 7.2 agent to manage that application. The Introscope 8.0 Enterprise Manager supports agents back to version 6.0. WebView does not support non-ISO-8859 characters in Introscope 8.0. We expect to reestablish support for this character set in subsequent versions. The workaround is to connect to the Enterprise Manager using Java Web Start. To avoid problems using load balancing with ChangeDetector, designate a specific Collector as the ChangeDetector agents preferred Collector. See the section Load balancing when Agents prefer a specific Collector in the Introscope Configuration Administration Guide. Enterprise Manager is backward-compatible with agents, so you can continue to use pre-8 agents with Enterprise Manager 8.1. Please note: Any version 8.0.x agent can connect to a version 8.1 Enterprise Manager. However, 8.0.0. or 8.0.1 agents should be upgraded to 8.0.2 or above to be compatible with 8.0.2+ Enterprise Manager. Version 8.0.2+ agents are fully compatible with 8.1 Enterprise Manager. Upgrading agents to 8.1 will allow you to take full advantage of version 8.1 functionality.
47144
47145
49131 50033
May 2010
page 38
Problem ID 53871
Description If you want to monitor web services on WebSphere Application Server 7.0 with the native IBM JVM 1.6, you must use the -javaagent option to configure the Introscope agent on the application server. For example, use arguments similar to the following: -javaagent:${WAS_INSTALL_ROOT}/wily/Agent.jar -Dcom.wily.introscope.agentProfile=${WAS_INSTALL_ROOT} /wily/IntroscopeAgent.profile If you use -Xbootclasspath to configure the agent on WebSphere Application Server 7.0 with the native IBM JVM 1.6, the Web Services node is not displayed in the Investigator and you will not be able to collect metrics for client- or server-side web services you have deployed.
56306
If user account control (UAC) is enabled on Windows 2008 server, the Introscope .Net Agent installer fails to register the wily.agent.dll file into the GAC and errors are logged in the installation log. If this error is encountered, the following workaround (to be applied manually) will resolve the issue: 1. Open a command prompt with "Run as Administrator" option i. Go to C:\Windows\System32 ii. Right click on cmd and select "Run as Administrator" 2. Type the following two commands to open two folders in Windows Explorer: explorer C:\Windows\assembly explorer <Agent_Home>\wily\bin Drag and drop the wily.agent.dll file from wily\bin to C:\Windows\assembly Restart IIS
3. 4.
Other known issues

Problem ID 27488 27489 27492 25616 27812 Description Due to a JRE issue, stalled stateless plugins are not properly killed on some platforms, and they continue to consume resources even after the EPAgent has been stopped. These orphan processes must be stopped manually. If a Collectors system clock is out of sync with the MOM by more than 3 seconds, the MOM disconnects from the Collector but checks every 15 seconds to see if the clock skew has been corrected. In a clustered environment, the repeated attempts to reconnect may result in an out-of-memory error. The only workaround is to correct system clocks so that they are less than 3 seconds apart, then restart the Collector. However, changing the Collector's system clock may result in live metric data not being visible in the Collector. On some system configurations, Change Detector reports the Time Changed metric one hour off due to Daylight Savings Time differences. The Metric Count metric will now appear by default under the Custom Metric Agent node and not under the Agent Stats node. You can set it to appear under the Agent Stats node by setting a new introscope.ext.agent.metric.count property in IntroscopeAgent.profile. For more information, see the Introscope Java Agent Guide.
30018
36025
May 2010
page 39
Problem ID 38321
Description When an agent is unmounted, users who try to review data previously displayed from that agent will see a com.wily.introscope.spec.server.ConstructNotFoundException error in the console, and WebView users who browse to the Investigator page that had been displaying data from that agent will see an error reading An application error occurred. To avoid seeing this error when an agent has been disconnected or unmounted, or to return to the default view when this error is displayed, refresh the Investigator page using the browser Refresh button or by clicking the Investigator tab link. In order to see the previously available agent data, the agent must be remounted using the Workstation. Users deploying an application on WebLogic Server version 9.2 may encounter a Java heap Out of Memory error: java.lang.OutOfMemoryError: PermGen space if the following three conditions apply: The application .jar file is deployed to the default WLS extension directory The application directly invokes a ClassLoader to load the application .jar file, and The application is instrumented with an Introscope agent. The workaround is to move the application .jar file out of the extension directory. See also the note for issues 38867/38868, which also deal with PermGen memory issues.
38464
38566
After making changes to the IntroscopeAgent.profile property introscope.agent.transactiontracer.sampling.enabled to enable or disable FirstNPerInterval Transaction Trace sampling, you must restart the application server before the changes can take effect. Metrics created by poorly written JavaScript calculators will persist in the Investigator tree and show up as active (not grayed out) even if they are reporting no data. Customers can avoid this problem by creating well-written calculators. When using dynamic instrumentation, and many classes are re-defined, under certain JVMs including Sun HotSpot 1.5.0_03, users will get eventual OutOfMemory errors and the application will crash. This is a result of the way PermGen is handled in the specific JVM. The workaround is to turn off dynamic instrumentation. If you continue to encounter these errors, contact Wily Support. When system clocks roll back one hour during the change from Daylight Savings Time to Standard Time, data for the repeated hour is overwritten and is lost from regular reports. The data is preserved in historical data, in transaction traces, error snapshots and ChangeDetector data. The Enterprise Manager uninstaller for z/OS will hang if run under JVM 1.4. To uninstall the EM on z/OS, install JVM 1.5, then run the uninstaller. The EM currently loads all the data requested by a query in memory prior to sending it over to the requesting client (a JDBC driver, the Command Line Workstation [CLW], Introscope Workstation, or any other client). If the amount of data requested is too large, it may cause an OOM exception in the EM and a CLW crash. Customers are advised not to execute extremely large queries. A possible workaround is to increase the memory size provided to the EM (Java -X options), but this too has its own limits. If stall resolution and stall threshold are set in the Agent profile to numbers which total less than 15 (the EM harvest duration), the Stall Count metric may show inaccurate data. To avoid this problem, set the following properties to total greater than 15:
introscope.agent.stalls.thresholdseconds introscope.agent.stalls.resolutionseconds
38636
38867 38868
38934
39472
39497
39499
May 2010
page 40
Problem ID 39716
Description Restarting the EM too quickly may fail on some operating systems, particularly Linux. If the EM is shut down and restarted too quickly, startup may fail with misleading error messages because the OS has not released the Enterprise Manager's server port (5001). The workaround is to set a property named introscope.enterprisemanager.serversockets.reuseaddr to true. This allows the socket to be bound even though a previous connection is in a timeout state. However, this should be used with caution, as it removes the protection against two Enterprise Managers using the same port. If you choose not to enable the introscope.enterprisemanager.serversockets.reuseaddr, you wait for the socket to exit the TIME_WAIT. It enters this state after the socket has been closed. The socket remains in TIME_WAIT state for a system-dependent time, generally 120 seconds. Dynamic Instrumentation does not support changes in Class Substitution which is used by the SocketTracing group, so attempting to toggle SocketTracing during runtime will evoke an error
39884
message:
Unsupported change to active AutoProbe configuration. Using existing configuration.
The only workaround is to restart the JVM after making changes to the .pbd file. 40180 When the EM is overloaded and cannot finish harvesting in the time interval, it will log WARN messages about dropped time slices. This may lead to gaps between metric data points. Filtering based on agent name uses the property introscope.agent.perfmon.agentExpression. A valid agent expression would be ProcessName|AgentName or *|MyAgent. To uninstall an instance of Enterprise Manager which was installed in silent mode, you must use console mode to uninstall. This is due to an InstallAnywhere issue. There is no workaround. Due to the way the Enterprise Manager tracks internal metrics about its own performance, the Partial Metrics with Data metric -- which appears as part of the supportability metrics under the path CustomMetricAgent|EM|Connection|DataStor|MetaData:"Partial Metrics with Data" -- should be taken as an approximate figure only. If administrators have customized the Enterprise Manager property introscope.enterprisemanager.webserver.dir to be anything other than the default value webapps, the 8.0 upgrader will not detect this change or perform any upgrade tasks on the directory. To upgrade, you must manually perform the following tasks during the post-upgrade: If upgrading 7.x only: Move <customized_webapps_dir>/cem.war to a backup location as this file is obsolete in 8.0 When upgrading any version: Transfer the following two new 8.0 web apps from the webapps dir to <customized_webapps_dir>/ : webapps/IntroscopeHelp_Config.war webapps/IntroscopeHelp_Using.war
41483
41566
41856
41929
May 2010
page 41
Problem ID 42030
Description Customers on AIX who have configured WebView to use SSL and whose users use Microsoft Internet Explorer 6 should configure IE 6 to use the TLS protocol instead of SSL. 1. Tools > Internet Options... 2. Advanced tab 3. In the dialog: a. Uncheck Use SSL 2.0 and Use SSL 3.0. b. Check Use TLS 1.0. TLS is another type of security protocol like SSL. 4. Click OK. 5. Open a new IE6 window and log in to EM using WebView again (using the same port 443 or whatever youve configured). NOTE: Checking Use TLS 1.0 will make it difficult for the user to access other websites that use SSL. In reports, time series bar charts can contain misleading data labels when the item label is not a unique name for identifying a series in a metric group. In general, avoid using $agentname as a key for identifying a series. Use the fully qualified agent name. Due to a known issue with the Apache web server, if the IPv6 address in the introscope.agent.enterprisemanager.transport.tcp.host.DEFAULT property in the Agent profile is not resolvable to a hostname, then the agent will not connect to EM using http tunneling port. LeakHunter users should note: To work with LeakHunter, a collections [int size()] method must be thread-safe and actionable throughout the collection life cycle. Collections whose size( ) method executes in time proportional to the number of objects in the Collection will have poor performance. In other words, if the collection is such that the size( ) method takes longer and longer to execute (for example, a badly implemented LinkedList where to get the size of the list we traverse through each element of the list and count), this will have negative effects on application performance. Such collections should be ignored, using the ignore property in IntroscopeAgent.profile, as shown in the section in the LeakHunter Guide headed Configuring LeakHunter properties. The following names of properties which can be configured for Command Line Workstation (CLW) have been changed: Old property wily.ps.clw.tt.console wily.ps.clw.tt.dirname txn.file wily.ps.clw.tt.encoding New Property introscope.clw.tt.console introscope.clw.tt.dirname introscope.clw.tt.filename introscope.clw.tt.encoding
42368
42461 45726
43217 48253
43373
The old property names will not be supported in future releases. 45690 The tool tip feature in WebView, which displays information about data points in tool tips, sometimes produces an IllegalArgumentException when WebView attempts to display too much information; this can also sometimes happen when the user attempts to view many different dashboards in succession. The exception is logged in the IntroscopeWebView.log file if the logger is configured to print in the log file; otherwise it is displayed in the console window. This exception does not affect WebView functionality and users can ignore this error. In addition to supportability metrics already available with the EPAgent, three other metrics have been added: Process ID Release Version EM port These metrics only function with Java version 1.5 and above.
45819
May 2010
page 42
Problem ID 45889
Description Due to a bug in JBoss, users running JBoss 4.0.5 on a 64 bit SuSe 9 environment who make runtime changes to the j2E.pbd file may see null pointer exceptions in JBoss server logs or Introscope agent logs. This is a third party bug. To avoid this, restart your JBoss server after making changes. An issue with IBM WebSphere MQ produces a Java exception after Introscope redefines certain Java classes during the process of dynamic instrumentation. To date, this behavior has been observed only in IBM WebSphere MQ. There is no workaround other than avoiding redefinition of offending classes, which can be identified from the Java stack trace. CA Wily has filed an issue with IBM and is continuing to monitor this issue. On IBM iSeries environments using the 1.5 "classic" (64-bit) JVM, installing the Introscope agent results in the application server startup time to increase substantially -- startup times as long as 50 minutes have been observed. Administrators should allow extra time for installations on this platform. To avoid this delay, add these options to the command line; -Xbootclasspath/a:PathToAgentJar -javaagent:PathToAgentJar -Dcom.wily.introscope.agentProfile=PathToAgentProfile -Dos400.disable.static.programs=1 -Dos400.define.class.cache= Dos400.jvmti.force.jitc (Note: ignore the last line break.)
45915
46017 53233
46035
Because data for string-based metrics is not stored in SmartStor, the Metric Count pie chart and accompanying table will not report correct metric counts in historical mode. Users should view the Metric Count pie chart only in live mode. Performing historical queries using "componentNotShown" as a query filter may return incorrect results. The result set or queries returned is potentially a superset of what should be returned by the query due to the fact that Lucene range query syntax is lexicographical and not numerical. For more information, see the Transaction Clamping documentation in the Introscope Workstation User Guide. Users may encounter problems when importing saved Transaction Traces. There is a workaround documented in Knowledge Base article no. 1714 on http://www.ca.com/wily/support. WebView may hang If an agent is unmounted, and a WebView user tries to expand a node in the tree of the unmounted agent. The workaround is to click the "Investigator" tab to refresh the display (or use the browser refresh button). Newly-created Management Module elements may not correctly display data if you try to view them using a historical time range immediately upon creating and saving them. You may need to wait several minutes to view the correct historical data. Users running the agent on Tomcat 4.1 with default setup and enabled JMX may see a ClassNotFoundException in the agent log. To avoid this, download jmx.jar from Sun and deploy it to the <Tomcat_Home>/common/endorsed directory before starting Tomcat. LeakHunter is supported on 64 bit .NET frameworks, Windows 2008 server, and .NET framework 3.0.
46481
46688
46921
46997
47093
47101
May 2010
page 43
Problem ID 47148
Description The agent silent uninstaller does not work correctly on Windows XP SP2, and you must perform a manual uninstall on that platform. To manually uninstall the agent: 1. Stop the monitored web application. 2. From a command prompt, execute the following commands to unregister the following DLLs. (Ignore line breaks; include quotation marks.)
"%WINDIR%\system32\regsvr32.exe" /s /u
"<path_to_Agent_Dir>\wily\bin\wily.AutoProbeConnector.dll"
"%WINDIR%\Microsoft.NET\Framework\<dotnetversion>\REgAsm.exe"
"<path_to_Agent_Dir>\wily\bin\wily.AutoProbe.dll" /unregister /verbose 3. 4. Manually remove the Wily agent DLL from the Global Assembly Cache. (See the notes under known issue 47122 in the .NET-related issues on page 19.) From the System Properties control panel, choose Advanced > Environment Variables. Locate and delete the following system variables:

com.wily.introscope.agentProfile Cor_Enable_Profiling COR_PROFILER INTROSCOPE_AUTOPROBE_SKIP_FILE
1. Manually remove the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\Introscope\NETAgent If this step leaves the parent key empty, delete that key as well: HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\Introscope 2. Manually remove the Introscope .NET Agent install folder.
47204 AIX 5.3 64 bit Platform Monitor binaries work only on AIX machines which have Technology Level equal or greater than TL6 (5300-06). Customers should ensure that their AIX machine is not less than TL6. Due to a known issue, the ChangeDetector node cannot be viewed using WebView. Users will see the message "An application error occurred." There is no workaround using WebView. Users should view ChangeDetector metrics using Workstation. In WebView, when the metrics tree includes a metric with a very long name, the tree pane scrolls automatically to the right. Users who then scroll up or down may get a false impression that the tree pane is blank. To see the tree proper, use scroll bars to scroll to the left. In a clustered environment, if a Collector is responding very slowly due to hardware or network issues, its response times may exceed the two-minute time window during which the MOM listens for data from Collectors. In such cases, the MOM will send to Workstation what data it has, not including the data from the slow collectors which is dropped because the slow collector hasnt responded in over 2 minutes. In extreme cases, the MOM will drop a connection to a Collector it thinks is unresponsive. In such circumstances, the data displayed by the Workstation will not correctly reflect all the Collectors in the cluster. Customers can ensure the Workstation displays correct data by disconnecting slow Collectors from the cluster or, more ideally, by tuning Collector performance to improve its response times. In upgrades to 8.0, the upgrader fails to remove a no-longer-used java.awt.headless property from webview.lax. This could cause WebView to fail to start on non-Windows platforms. To fix this problem, after the upgrade manually edit webview.lax to set java.awt.headless to true.
47276
47277
47280
47308
May 2010
page 44
Problem ID 47417
Description The WebView Investigator tree sometimes incorrectly shows an agent and the agents child nodes as connected when the agent has been disconnected. The WebView Investigator tree also sometimes does not automatically show newly connected agents and their metrics even if the user refreshes the browser. The workaround for the latter defect is to log out of WebView and log back in to see the newly connected agent. In some cases, customers running WebSphere Application Server (WAS) 6.1 on the AIX platform who have both Introscope-enabled and non-Introscope-enabled applications on the same machine may see the following error thrown by the non-Introscope-enabled applications:
java.lang.NoClassDefFoundError: com.wily.introscope.agent.probe.io.ManagedFileInputStream
47559 49246
To avoid this problem, include the following JVM flag in the Generic JVM Arguments field when configuring your WAS application for Introscope:
-Xshareclasses:none
For more information, see "Configuring WebSphere Application Server (WAS)" in the Introscope Java Agent Guide. 47683 When using the ./EMCtrl.sh stop control script in a z/OS environment, the control script does not stop the Enterprise Manager. When integrating CEM with Introscope Java agents, you must deploy the CEMTracer and ServletHeaderDecorator agent extensions. The Introscope 8.0 Agent.zip file still embeds a ServletHeaderDecorator PBD (ServletHeaderDecorator_iscope8.0.pbd.txt) reference in the ProbeBuilder Directive file. This version is out of date. Instead, you should use the SHD.jar and SHD.pbd files from CEMIntroscopeIntegrationKit-v4.2windows.zip. Due to a vulnerability in Jetty, Introscope deployments will experience a cross-site scripting vulnerability. There is no workaround. Due to a design limitation, correlated Transaction Traces can be viewed in the Transaction Tracer viewer in Workstation, but will not appear as correlated if saved as XML and then viewed from the XML files. WLS users with EJB 3.0 may see EJB nodes in the Workstation tree named with an unhelpful $Proxynnn name. To make EJB 3.0 metrics visible, and to prevent metrics from being displayed under $Proxynnn: If you use 7.2.x agents:
47740
48011
48471 49367
48521 48943 50132 51526
1. Edit the j2ee.pbd file to add the following lines:

IdentifyAnnotatedClassAs: IdentifyAnnotatedClassAs: IdentifyAnnotatedClassAs: IdentifyAnnotatedClassAs: javax.ejb.Stateless SessionBeanTracing javax.ejb.Stateful SessionBeanTracing javax.persistence.Entity EntityBeanTracing javax.ejb.MessageDriven MessageDrivenBeanTracing
2. Edit the wl8x.pbd file to add the following line:

SkipPackagePrefixForFlag: $Proxy SessionBeanTracing
If you use 8.0.x agents: To correctly display names of message-driven EJB 3.0 beans in the Introscope metrics tree under the EJB node :
Create a custom pbd file (named <custom>.pbd) and place it in the <Agent_Home>/hotdeploy folder with the following contents:
IdentifyClassAs: com.bea.medrec.common.messaging.BasePayloadHandlerSupport MessageDrivenBeanTracing
May 2010
page 45
Problem ID 48537
Description When upgrading to this Service Pack, if using a jar installer for z/OS or other Unix platforms, be sure to start the installer using a 1.5 Java Virtual Machine. When using the silent install method, specify the path to the installer, the absolute path to the response file, and a JVM which must be versioned 1.5. For example:
<java> -classpath <installer.jar> install -f <absolute_path_to_response_file>
48553
Due to an issue with Silverlight, WebView users on machines which have been upgraded to Microsoft Silverlight 2.0.3x who use Internet Explorer version 6.x may see an error, "Unable to select dashboard." After this the WebView display freezes and the user is unable to view other dashboards. If this happens, close and restart the browser window and connect again using WebView. The correct name of the extracted SNMP Adapter .jar file includes the version number, for example: com.wily.introscope.em.snmp_8.1.0.jar. Windows platform monitors require the Extensible Counter List utility available from:
48662
48697
http://download.microsoft.com/download/win2000platform/exctrlst/1.00.0.1/nt5 /en-us/exctrlst_setup.exe. After downloading the utility: 1. Run exctrlst_setup.exe 2. Enable performance counters PerfProc for processor & PerfOs for process performance object.
48792 Users running Introscope on Solaris operating systems must edit the following files:

EMCtrl.sh EPACtrl.sh
#!/bin/sh
to delete the following string at the beginning of each file: Deleting this string will cause commands in the file to be executed using the.bin.sh (Bourne) shell. 48885 49328 To prevent an Out Of Memory error, customers who want to turn on exception tracing with WebSphere 7 must increase the memory available to the JVM. To do this, increase maximum JVM heap size setting on the WebSphere application server to at least 1 GB. For WebSphere 7 Installations, the ws70x.pbd does not contain trace directives for WebSphere 7 specific classes that implement J2EE classes/interfaces. Under certain installations, ChangeDetector will not detect changes. To work around this problem, try deleting the cache in the <Agent_Home>/wily directory. If this happened after you upgraded Enterprise Manager from 7.2.x to 8.0.1.0, copy your changes.db file from 7.2.x to 8.0.1.0 under the data folder. 49512 51631 Errata for the Java Agent Guide: In the section WLDF metrics, the note should read For WebLogic 9.x only. References to JavaI5DynamicInstrumentation.jar should be corrected to Java15DynamicInstrumentation.jar. References to Java 2 components should read J2EE components. References to 8.0 can generally be taken to also refer to 8.1. For example, filenames such as NoInstaller8.0.0.0websphere.unix.tar will be NoInstaller8.1.0.0websphere.unix.tar.
49146
49503
May 2010
page 46
Problem ID 49574
Description When the agent is started on an application server which has the Change Detector extension enabled, when a user selects or expands the Change Detector node in the Workstation Investigator tree the Workstation will lose the connection to the Enterprise Manager and log out. If this happens, quit or kill the Workstation application, restart it, and log in again to that Enterprise Manager. Due to an issue with the 8.0.0 version Agent, you should use the 8.0.2 version Agent for crossJVM tracing on the WebSphere 6.1 application server.
49753 49788 49794 52666 49789 49790 50745
The 8.x agent does not support cross JVM tracing on IBM WebSphere 7.0 application servers. Users who execute cross JVM tracing for IBM WebSphere 6.1 may notice that the resulting display in Workstation Trace View shows traces misaligned or out of order. This happens occasionally when the agents participating in the cross JVM traces are not time-synchronized. There is no workaround. Due to internal issues, the feature by which Transaction Traces show all correlated components was disabled for 8.0.x Presently Transaction Traces will show only components for the selected agent rather than all correlated components. The Java Agent platform monitor for HPUX reports the percentage use of CPUs when more than one process is present. For example, if you have 4 processes, the maximum use of the CPU would be 400% (4 processes using 100% of the CPU). If one process takes 110%, this means it is using 1.1 CPUs. System objects must be enabled for platform monitoring to work on Windows. To determine whether system objects are enabled:
49797
49918 50078
49998
1. 2. 3. 4. To 1. 2. 3. 4.
50002
Go to Start > Run Type perfmon and click Run. In the dialog box click Add. In the Add dialog, if "Process" and "Processor" performance objects are present in the drop down list box, then system objects are enabled. enable system objects: Go to Start > Programs > Accessories. Right click Command Prompt. Choose Run as > Administrator. Run the command: lod c t r / r
"Process" and "Processor" objects will be enabled. Customers running Introscope Workstation on the Vista OS may encounter difficulty printing reports to a directory from Command Line Workstation. The status message "Wrote report c:\path\to\report.pdf" will be erroneous because write permissions to directories are disabled by default on Vista. To write a report to a directory, change the permissions on the directory before printing the report. Customers running Oracle 10g Release 2 using Sun JDK 1.42 must use the ^ (caret) character to escape a forward slash when issuing commands. For example, to start the agent:
-Xbootclasspath^/p:<IntroscopeAgent.jar path> ...
50076
50089
Users with SOA EM extensions may experience a Workstation hang when reconnecting to an Enterprise Manager after manual logout. To work around this problem, place extension .jar files in the <Workstation_Home>\product\workstation\plugins directory. If the Workstation is installed within the same folder of Enterprise Manager, place extension .jar files in the <Introscope_Home>\products\workstation\plugins directory.
May 2010
page 47
Problem ID 50141
Description Users who log out of WebView and log back in again may see a missing or erroneous System Overview alert indicator on the "An Intro to Introsocope" dashboard. There is no workaround. Due to a Silverlight issue, WebView users may have problems viewing console dashboards. To work around this problem:
50310
1. In the Microsoft Internet Explorer browser, go to Tools > Internet Options 2. In the General tab, under Temporary Internet Files, click Settings. 3. Under Check for newer versions of stored pages, select Every visit to the page. 4. Click OK. 5. Click OK.
50767 The User ID for Enterprise Manager is case insensitive. For example, userid "guest" and "Guest" are the same. In the Introscope JavaAgent Guide, the paragraph on page 156 beginning with the sentence The SQL Agent ships with an extension that normalizes SQL statements based on configurable regular expressions (regex) should refer to the file RegexNormalizerExtension.jar and not wily.RegexSqlNormalizer.ext.dll. Due to a change in the JDBC utilities shipped with 8.1 Service Pack A, customers who use the IntroscopeJDBC.jar file should edit their classpath to point to a servlet .jar file. References to .jar file names in the ErrorDetector user documentation that use 8.0 in the filename should use 8.1. For example, references to com.wily.introscope.errordetector_8.0.0.jar should read com.wily.introscope.errordetector_8.1.0.jar. Due to an issue with third party software XALAN (http://issues.apache.org/jira/browse/XALANJ1974), the ChangeDetector configuration file is added with one extra new line character whenever it is modified. Customers who have upgraded their Enterprise Manager from 7.2 to 8.1 may see problems with the scale of the Overall EM Capacity % graph on the Overall Enterprise Manager Capacity %. Values over 5% will not be displayed. To work around this problem, manually set the y-axis of the graph to 0-100. WebView users who select the Host node under an agent, then open the Console, then return to the Investigator tree view, may see the error: An application error occurred, with an accompanying Java Null Pointer Exception in the WebView log. To resolve this error, users must log out, quit and restart the web browser, and log in again. ChangeDetector running against a WebSphere 7.0 application and Oracle DB on AIX 5.3 may throw an unexpected exception like:
java.security.AccessControlException: Access denied (java.net.SocketPermission hostname:port connect,resolve) at java.security.AccessController.checkPermission(AccessController.java:104)
50787
51207
51587
51676
51725
52066
52136 60447
To work around this problem, uncheck Enable application security in WebSphere settings: 1. Login to the WebSphere 7.0 Admin Console. 2. Under Security heading in the left pane, click Global Security. 3. Uncheck Enable application security and press Apply. 52593 For instructions on instrumenting applications on a WebSphere 7 platform on z/OS with JVM 1.5, see Knowledge Base article 2334 on the CA Wily support site:
http://www.ca.com/wily/support
May 2010
page 48
Problem ID 52642
Description Users who install the Java Agent on a WebSphere 7 application server on the 64bit-Classic JVM platform on OS400 may experience problems accessing the instrumented application using a web browser console. This is due to an IBM issue. The following is an updated list of operating systems monitored by the Java Agent: Solaris Windows Server 2003 Windows 2000 Professional/Server/Advanced Server/Datacenter Server Windows XP Professional AIX 4 or 5 RedHat 3.0, 4.0, or 5.0 SUSE Linux 9 or 10 HP-UX HP-UX IA 64 bit Please note that platform monitor binaries are independent of application server and operating system bit modes. Also, platform monitor binaries are purely dependent on JVM architecture. For more information about platform monitors, see the Java Agent Guide chapter Configuring Platform Monitoring. The following is an update to the Java Agent Guide section called Troubleshooting platform monitoring. Step two of the procedure should read as follows: 2. Under the Platform Monitor Configuration heading, locate the exact matching value for your operating system and uncomment the property. The available values are:
#introscope.agent.platform.monitor.system=SolarisAmd32 #introscope.agent.platform.monitor.system=SolarisAmd64 #introscope.agent.platform.monitor.system=SolarisSparc32 #introscope.agent.platform.monitor.system=SolarisSparc64 #introscope.agent.platform.monitor.system=AIX5Pseries32 #introscope.agent.platform.monitor.system=AIX53Pseries64 #introscope.agent.platform.monitor.system=AIX52Pseries64 #introscope.agent.platform.monitor.system=HP-UXItanium #introscope.agent.platform.monitor.system=HP-UXItanium64 #introscope.agent.platform.monitor.system=HP-UXParisc32 #introscope.agent.platform.monitor.system=WindowsIntelAmd32 #introscope.agent.platform.monitor.system=WindowsIntelAmd64 #introscope.agent.platform.monitor.system=LinuxIntelAmd32 #introscope.agent.platform.monitor.system=LinuxIntelAmd64
52789
The following JVMs are supported by platform monitors: Sun JVM HP Hotspot JVM IBM JVM ( Both Classic and J9 ) JRockit JVM 32-bit Platform Monitor binaries can be installed on a 64-bit machine, provided a 32-bit bit JVM is installed. 53129 The Workstation will not display information for JVM Architecture ( Bit Mode ) for applications on an R series Classic (64 bit) JVM platform.
May 2010
page 49
Problem ID 53130 53131 53132
Description The Java Agent Guide will be updated to list: The latest Linux binary filenames:
introscopeLinuxIntelAmd32Stats.jar introscopeLinuxIntelAmd64Stats.jar libIntroscopeLinuxIntelAmd32Stats.so libIntroscopeLinuxIntelAmd64Stats.so introscopeWindowsIntelAmd32Stats.dll introscopeWindowsIntelAmd64Stats.dll introscopeWindowsIntelAmd32Stats.jar introscopeWindowsIntelAmd64Stats.jar introscopeHpuxItaniumStats.jar introscopeHpuxParisc32Stats.jar introscopeHpuxItanium64Stats.jar libIntroscopeHpuxItaniumStats.so libIntroscopeHpuxParisc32Stats.so libIntroscopeHpuxItanium64Stats.so
The latest Windows binary filenames:
The latest HP-U binary filenames:
53372
WebView users on IE version 7 who zoom in on a graph will not be able to export the graph. To work around this issue, hold the CTRL key while clicking the Export menu choice. Occasionally the Java Agent will cease functioning correctly with IBM JVM 1.6. IBM has a fix for this issue. CA Wily recommends requesting the fix from IBM, referencing PMR 54693,756,000. In the WebView Guide, the section on Configuring WebView to use SSL and non-secure ports is confusing about which file to edit to configure ports. For non-SAP implementations, edit the webview-jetty-config.xml file. For SAP implementations, edit the em-jetty-config.xml file. Occasionally hot-deploy does not function correctly when an existing web application WAR file is replaced by a more current version of the same file. When an existing web application is replaced, the last modified time of old and modified web applications are compared and if they are different, Introscope redeploys the modified web application in Jetty Server. The issue occurs when the Jetty code has to handle the rest of the implementation. Jetty checks to see if the timestamp of the modified web application is greater than the timestamp of web application temporary folder (located here: <EM_Home>/work/WEBAPP_TEMP_FOLDER). If the timestamp is greater, then Jetty redeploys the web application in Jetty. Otherwise, Jetty ignores the Introscope request to redeploy the web application. To address this issue, you should manually change the timestamp of the modified web application to the current time and then redeploy the modified web application so Jetty will accept and redeploy the web application.
53425
54048
54282
54366
In the Introscope Workstation User Guide, in the Using the Transaction Trace Viewer section, the following are additional types of information you can see in the transaction trace row: Sampled (R) A transaction chosen at random. Stalled (S) A stalled transaction.
May 2010
page 50
Problem ID 54373
Description In the Introscope ChangeDetector user documentation, in section Manually configure the Database Monitor properties, the information in the table on page 45 should read as follows: url The JDBC URL to be used to connect to the database. Username Password The username to be used to connect to the database. This value will be obfuscated during subsequent agent restarts. The password to be used to connect to the database. This value will be obfuscated during subsequent agent restarts.
54374
In the Introscope ChangeDetector user documentation, in section Modifying the Agent Configuration File, the paragraph at the top of page 59 should read: When entering a path name, use the absolute path name and two back slashes. For example, if you are referencing a WebLogic application server, the path entered in the property value would look something like this: <WebLogic_Home>//<Agent_Home>. The example given should read: <WebLogic_Home>\\<Agent_Home>
54542
In mixed IPV4/IPV6 environments, the default user settings bind the Java Agent to IPV4 addresses. While TCP settings may provide stacks for both IPV4 and IPV6, the Java Agent must be positively binding to the TCP stack in order to access both IPV4 and IPV6 addresses. To change the user settings to access both IPV4 and IPV6 addresses: 1. If the Java Agent is configured to run as a standalone agent, such as runAgent.sh for a standalone Java application, the following environmental variable statement must be set in runAgent.sh: export_BPXK_SETIBMOPT_TRANSPORT=TCPIP 2. If the Agent is configure to run in an application server environment such as WAS6.1 or WAS7.0, ensure that WAS environment variables contain similar settings.
54604
Introscope uses XALAN APIs to write into the ChangeDetector configuration file. Due to an issue in XALAN (http://issues.apache.org/jira/browse/XALANJ-1974), an extra newline character is written when the ChangeDetector configuration file is modified. In the Introscope 8.2 release, the Dwily.ps.workstation.clws.gettracebody command for the CLW does not work. In the Introscope Configuration and Administration Guide, the section called Return only header data contains incorrect information regarding the gettracebody command. Disregard the information in this section and do not use the get gettracebody command. Customers running Introscope on WebSphere Application Server (WAS) 6.1 must install the Java SDK 1.5 SR6 to resolve issues that prevent the correct functioning of the Introscope agent. When running WebSphere Application Server (WAS) 5.x or 6.0.x that has been instrumented with version 8.x of the agent, some users find that metrics are not being recorded. This is caused when custom properties used with the IBM 1.4.2 JVM are not processed at the same time as other JVMs. This results in the IntroscopeAgent.profile being processed before the default encoding (com.wily.introscope.default.encoding) is recognized, making WAS expect the profile to be in ASCII encoding. To work around this problem, you can convert your IntroscopeAgent.profile to ASCII. See the Wily Knowledge Base article 2453 for instructions on how to convert your profile to ASCII. The article also contains instructions for how to convert the profile back to EBCDIC. Visit CA Wily support to access Knowledge Base articles: http://www.ca.com/wily/support
55151
55183
55300
55507
The JDBC Driver API to access Introscope transaction details does not support the Microsecond Traces. This issue has no impact on the Workstation user interface that allows you to view transaction details. This issue only impacts the customized tools built to access transaction details using the Introscope JDBC API. The result set returned by the JDBC API does not have the indicator to differentiate between microsecond traces and normal millisecond traces.
May 2010
page 51
Problem ID 55585
Description When running the Introscope WebView with IBM J9 JVM on OS/400, the following additional JVM arguments must be added to JVM_ARGS. Edit the runwv.sh file and add the following in JVM_ARGS: -Dorg.osgi.framework.bootdelegation=org.apache.xpath When exporting the SOA Dependency Map as a PDF file, no data is written to the file. You can however export the map in other file formats, such as JPG or PNG. WebView not fully functional on NAS WebView which has been installed as a service on Network Attached Storage (NAS) machine may not properly display graphical metrics displays in the Investigator tab. Users may see the metric tree on the left side, but the right side of the viewer may be blank or may display an HTTP 500 error message. To work around this issue, run WebView as a standalone process on the machine from which you are accessing the NAS, or install and run WebView on the machine from which you are accessing the NAS, either as a standalone process or as a service. When Introscope 8.2 is integrated with Spectrum 9.0, there is an issue that occurs when Spectrum SNMP traps are created and configured. When an action is created to send an SNMP trap to Spectrum, the action is created successfully. However, when you drill down to the Spectrum SNMP trap action node under the Management Module tree, the configuration details pane for the action does not appear immediately. If this occurs, click on a different node within the tree before navigating back to the Spectrum SNMP trap action node. In the Workstation, when you right click an agent in the Investigator Browse tree, you can choose to shut off or unmount the selected agent. Shutting off an agent severs the connection between the agent and the Enterprise Manager. Unmounting an agent removes the agent from view in the Investigator tree. You may want to unmount an agent if it has been disconnected or appears grayed out in the Investigator. To mount (or remount) an agent: 1. Navigate to Manager > Mount Agent. An Agent Chooser dialog appears. 2. From the list, select an agent to remount. 3. Click OK. The Browse tree displays the disconnected agents, and you can browse the data stored in the SmartStor database. In the case where you want the Enterprise Manager to stop storing data from an agent that is still running, you can stop data collection without stopping the app server by choosing the Shut Off command. Minimum RAM requirement for Introscope Workstation as of version 8.2x is 256 MB. The following properties are not hot config, as said in documentation: introscope.enterprisemanager.clock.skewtoleranceseconds introscope.enterprisemanager.clock.skewsuppresswarn The 'Setting the Maximum Data Point Retrieval Property' section in the Introscope Configuration and Administration Guide erroneously tells customers to set the property in the Introscope Enterprise Manager.lax file. The property should be set in IntroscopeEnterpriseManager.properties. The lax file should mainly be used for runtime system properties. Enterprise Manager properties, especially hot config properties, should be configured in the properties file.
55629
55762
55878
56180 56181
56379 56454
56532 57578
May 2010
page 52
Problem ID 57225 53871
Description If you use -Xbootclasspath to configure the agent on WebSphere Application Server 7.0 with the native IBM JVM 1.6, the WebServices node is not displayed in the Investigator and you will not be able to collect metrics for client- or server-side web services you have deployed. If you want to monitor web services on WebSphere Application Server 7.0 with the native IBM JVM 1.6, you must use the -javaagent option to configure the Introscope agent on the application server. For example, use arguments similar to the following:
-javaagent:${WAS_INSTALL_ROOT}/wily/Agent.jar -Dcom.wily.introscope.agentProfile=${WAS_INSTALL_ROOT}/wily/IntroscopeAgent.profile
For more details on this issue and how to address it, see Knowledge Base article no. 2503 on http://www.ca.com/wily/support. 59406 After you upgrade Introscope from 8.1x to 8.2x, you may get a WebView error like:
12/31/09 03:16:03 PM PST [ERROR] [org.mortbay.log] /jsp/login.jsf 2009/12/31 15:16:03 | javax.faces.FacesException: /jsp/login.jsp(9,40) PWC6226: Could not add one or more tag libraries
To fix this problem: 1) Stop WebView on the EM host machine. 2) Open <EM_HOME>\product\webview\configuration directory and delete the following directories: org.eclipse.core.runtime org.eclipse.equinox.app org.eclipse.osgi org.eclipse.update 3) Restart WebView on the EM host machine. 59412 In a clustered environment, customers using Introscope PowerPacks for WebSphere or WebLogic Server should place calculators on the collector machine, not on the MOM. You can use the "Calculators:Total Number of Evaluated Metrics" metric, which appears in the Investigator tree under Enterprise Manager | Internal | Calculators, during Management Module editing to verify that metrics produced by new calculators don't cause your Manager of Managers (MOM) to exceed the maximum number of metric subscriptions specified in the Sizing Guide. Users who inactivate a dashboard in an active Management Module may subsequently see a Null Pointer Exception error message in WebView instead of a message stating that the dashboard is inactive. A Knowledge Base article for this issue has been requested; see http://www.ca.com/wily/support. Accessing documentation Users attempting to access Introscope documentation through WebView or the Workstation may encounter a directory listing of /IntroscopeHelp_Using/ or IntroscopeHelp_Config/. If you see this listing in your browser: Click IntroscopeHelp_Using/ to access: Overview Guide Workstation User Guide WebView Guide ChangeDetector Guide Click IntroscopeHelp_Config/ to access: Overview Guide Configuration and Administration Guide Java Agent Guide Environment Performance Agent Guide You can also access Introscope documentation through http://www.ca.com/wily/support.
59575
59736
59923 60221
May 2010
page 53
Problem ID 60014
Description Under some circumstances, Introscope users on z/OS may see null pointer exceptions in the Enterprise Manager log. This happens after the Workstation user goes into historical query mode or after the user moves the time range slider control. No data is lost or incorrectly reported, and users can ignore these log entries. A fix for this issue is being worked on. Example of the NPE log message:
[Manager] Uncaught Exception in thread Async MDQ 6 java.lang.NullPointerException at com.wily.isengard.messageprimitives.callback.CallbackConnector.<init>(CallbackConnec tor.java:34) at com.wily.introscope.server.beans.metricdata.ResultSetConnector.<init>(ResultSetConne ctor.java:18) at com.wily.introscope.server.beans.metricdata.live.LiveMetricSubscriptionManager.creat eResultSetConnector(LiveMetricSubscriptionManager.java:328) at com.wily.introscope.server.beans.metricdata.MetricDataManager$ExecuteAsyncCommand.ru n(MetricDataManager.java:533) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:678) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:703) at java.lang.Thread.run(Thread.java:811)
60285
Management modules alerts An agent expression using the IP address instead of the host name may not match correctly, and users may see the alert indicator grayed out in the dashboard. To work around this issue, use host name instead of IP address. SmartStor tools -Prune command If the execution of the "prune" command does not result in any metrics being pruned, then the metadata file is not copied to the backup folder. The data files are copied to the backup folder irrespective of the command result. Threshold lines in graphs When metrics are reported to an Enterprise Manager running on Solaris OS, threshold lines may not appear where they have been configured in graphs, and the graph scale may not be adjusted for threshold values. To work around this issue, select another alert, then select the affected alert again. In the metrics appendix of the Introscope Workstation Guide, the discussion of count in the context of Concurrent Invocations metrics requires clarification. Concurrent invocations should be defined as the number of requests still in flight at the end of the interval. For concurrent invocations, the value measures the number of in-flight requests, and the count measures the number of times that the number of in-flight requests changed (either increasing or decreasing). Live metric data may not be visible If you restart the collector, the live metric data in the alert graph may not be visible. To work around this issue, select another metric in the Management Module and then select the affected metric again. Exceptions in historical query mode You may see exceptions in the Enterprise Manager log when you change to historical query mode in the Workstation. However, no data is lost or incorrectly reported. You can ignore these log entries.
60289
60296
60406
62823
63048
May 2010
page 54
8. Introscope for SAP Solution Manager Diagnostics-related known issues
The following issues relate only to Introscope for SAP Solution Manager Diagnostics.
Problem ID 41380 Description
EM startup messages are no longer displayed in the console by default. To see startup messages, view the IntroscopeEnterpriseManager.log file. The installer does not automatically create an ext directory. Administrators must manually create the ext directory after the installation process. Due to a regression, some WebView configuration properties may not be available to users of SAP Enterprise Manager. Users may see an error java.io.FileNotFoundException: config\IntroscopeWebView.properties (The system cannot find the file specified)
47117
51644
May 2010
page 55
9. Introscope .NET Agent-related release notes

Compatibility
This release is compatible with the following Introscope versions: Introscope 8.0 (Enterprise Manager) and above This release is compatible with the following Microsoft .NET Framework versions: .NET V1.1 Framework (v1.1.4322) .NET V2.0 Framework (v2.0.50727) .NET V3.0 Framework (v3.0.4056) .NET V3.5 Framework (v3.5.21022) This release is compatible with the following Microsoft Windows platform & IIS versions: Windows XP Professional 2002 SP2 / IIS Version 5.1 Windows 2000 5.000.2195 SP4 / IIS Version 5.00.2195.6620 Windows Server 2003 Enterprise Edition SP1 / IIS Version 6.0 (32 & 64-bit) Windows Server 2003 Enterprise Edition SP2 / IIS Version 6.0 (32 & 64-bit) Windows Server 2008 Enterprise Edition / IIS Version 7.0 (32 & 64-bit) This release supports the following databases for ADO.NET monitoring: SQL Server 2000 Version 8.00.2039 SP4 SQL Server 2005 Version 9.00.1399.06 Oracle 9i and 10g via ODP.NET version 10.2.0.1x, 10.2.0.2x, and 10.2.0.4x (Oracle versioning; Windows versioning [same driver] 1.102.2.20 [for Framework 1.1] & 2.102.2.20 [for Framework 2.0])
Upgrading to version 8.2

To upgrade from a previous version of the Introscope .NET agent, perform the following steps: 1. Back up your existing Introscope .NET agent configuration. 2. Uninstall the Introscope .NET agent. This involves a reboot of the system on which the agent is installed. Please refer to the Introscope .NET Agent Guide for instructions on uninstalling your Introscope Agent. 3. Install the new version of the Introscope .NET agent. Refer to the Introscope .NET agent Guide 8.2 for installation instructions. 4. Restore any customizations you used with the previous version of the Introscope .NET agent (including settings, pbds, etc.) from the backup you made in step 1. 5. If necessary, adjust any permissions to reference the new folder name.
Limitations & restrictions

The Introscope .NET agent does not support the following at this time: Instrumentation of Microsoft XML and XSL classes. Directives using Assembly names longer than 250 characters. Directives using nested class names longer than 256 characters (including the Namespace). Use of a parameterized tracer on methods with custom value types as parameters or return types. Use of the IdentifyInheritedAs directive on generic Classes/Interfaces. Generic parameters to method types in directives (id 39682).
May 2010
page 56

The DocumentationServerProtocol web services protocol. Tracing using directives based on attributes applied on method parameters and return types. For ODP.NET, when using XML documents to insert/update data in Oracle, the metric name displayed is not normalized (id 40027). Lack of out-of-the-box metrics collection for WCF services (id 40810). To instrument WCF (Windows Communication Foundation) classes you must identify the classes with explicit directives.
Commonly observed differences between the Introscope .NET agent and the Java Agent
The following are common differences between the Introscope .NET agent and Java Agent: The syntax for specifying fully qualified method names is different from Java. Types are specified with an optional assembly name included in front the of type name in square brackets. For example, "[mscorlib]System.Int32". The method signature is separated from the method name by a semicolon and has the return type before the parameters. The syntax is:
<method name>;<return type>(<param 1>;<param 2>...)
An example of a method name with the signature is:

myMethod;[mscorlib]System.Void([mscorlib]System.Object;[mscorlib]System.Int32)
For the Introscope .NET agent to successfully operate, it is crucial that the permissions on the Wily directory are set correctly. The permissions required depend on the user identity running the application being instrumented. Refer to the documentation for detailed instructions. The supportability-agent extension has not been ported to .NET. This extension can be used in Java to provide system properties and hourly metric counts in the agent log. Unlike the Java Agent, the Introscope .NET agent does not support static ProbeBuilding. i.e. the only supported way to instrument an application is at run-time using AutoProbe. Unlike the Java Agent, you cannot set AutoProbe log size for the Introscope .NET agent. Note: For information on how to set AutoProbe log size for Java agent, see Important things to know section.

To set system properties (things you would set in Java with -D on the command line): 1. Add a sectionGroup and a section to your application configuration file. Name them as follows:
<sectionGroup name="com.wily.introscope.agent"> <section name="env.parameters"
type="System.Configuration.NameValueSectionHandler,System,Version=1.0.50 00.0,Culture=neutral,PublicKeyToken=b77a5c561934e089" />

</sectionGroup>
2. You can then add any properties you want set to the env.parameters section. For example: <com.wily.introscope.agent> <env.parameters> <add key="com.wily.introscope.agentProfile" value="c:\\wily\\IntroscopeAgent.profile" /> </env.parameters>
May 2010
page 57
</com.wily.introscope.agent> In Java environments, when the application server starts up, the Java Agent connects to the Enterprise Manager. Often there are no metrics until load is applied, but the Java Agent is visible. In .NET environments, the ASP.NET worker process is not started until the application is accessed. The .NET Agent is not started until a .NET-based page is accessed. An example would be an .ASPX/.ASMX page or a simple ASP page loading a .NET component. o o The .NET Agent is not tied to the application server (IIS), and restarting IIS does not bootstrap the agent. The .NET Agent is tied to the ASP.NET worker process and the .NET Agent bootstraps only when a page using a .NET component for that application (tied to that worker process) is accessed.
There is no .NET Agent visible at start up, and no metrics are reported until a .NET page is accessed. The metrics Introscope reports from the SQL Agent will be slightly different from the Java metrics in the following ways: o o Normalized SQL metrics are displayed under each backend instance instead of under a JDBC (or NET) node. The database name is currently using the database name provided by the driver, which does not match the formatting from the Java SQL Agent.
Other Introscope .NET agent-related known issues

39906 When using the Workstation Investigator to view backend components reported by Introscope .NET agents, the backend type (e.g. "Oracle db") is not displayed. The directives shipped with this release are not capable of automatically instrumenting WCF services in a .NET implementation of Introscope. Users must manually instrument the class that implements the WCF service with a combination of IdentifyClassAs and TraceOneMethodIfFlagged directives. For example, to instrument CalendarService:
SetFlag: WCFServiceTracing TurnOn: WCFServiceTracing IdentifyClassAs: CalendarService WCFServiceTracing TraceOneMethodIfFlagged: WCFServiceTracing Add BlamePointTracer "WCFService|{classname}|{method}" TraceOneMethodIfFlagged: WCFServiceTracing Subtract BlamePointTracer "WCFService|{classname}|{method}" TraceOneMethodIfFlagged: WCFServiceTracing Multiply BlamePointTracer "WCFService|{classname}|{method}" TraceOneMethodIfFlagged: WCFServiceTracing Divide BlamePointTracer "WCFService|{classname}|{method}"
46154
For more information, see Knowledge Base article 1610 on
http://www.ca.com/wily/support.
46270 Customers running ChangeDetector on .NET with the Database Monitor configured may see a memory leak when Database Monitor is not able to connect to the database. The only workaround is to disable monitoring of the database. The Introscope .NET agent Installer does not complete the process of setting environment variables on a Windows 2003 system. Users must restart the system after installing the agent.
46589
May 2010
page 58
47122
Users installing the Introscope .NET agent on Windows Vista and Windows Server 2008 will encounter a problem in which the installer will not successfully register wily.Agent.dll to the GAC or unregistered it from the GAC. After installing the Introscope .NET agent, you must perform registration or unregistration manually:
1. Go to Control Panel > Administrative Tools > .NET Configuration 1.1 2. Click Manage the Assembly Cache 3. Unregister the agent, if it is already registered: 4. Click View List of Assemblies in the Assembly Cache. 5. Right-click wily.Agent.dll , if it is present. 6. Choose Remove. 7. Register the agent: 8. Click Add an Assembly to the Assembly Cache. 9. Browse to the wily.Agent.dll you just installed. 10. Select wily.Agent.dll..
You should also manually unregister the agent after uninstalling it using the automated uninstaller. 47443 In a Web Garden configuration on the IIS when more than one worker process exists for the .Net application, ChangeDetector changes will only be reported by the first worker process. There is no loss of data and the message undeliverable exception printed in the log can be ignored. Due to the fact that the .Net agent uses the .Net framework version 1.1 for DNS resolution, you must use the IPv6 address to refer to hosts instead of the hostname.
59718 60203
10. Contacting Technical Support

For help with Introscope or any other product from CAs Wily Technology Division, contact Wily Technical Support: http://www.ca.com/wily/support Toll-Free U.S.: 1 888 GET WILY ext. 1 U.S.: +1 630 505 6966 Latin America: +55 11 5503 6167 Europe: +44 (0)1753 242763 Asia-Pacific: +81 3 6868 2300 Toll-Free Japan: 0120 974 580 Singapore: +65 6432 8641 Australia: +61 2 8898 2963 We value your feedback CA-Wily Tech Pubs wants to know what you think about our documentation. Please take a short online survey to help us improve the information we provide you. Link to the survey at http://tinyurl.com/6j6ugb. If you have other comments or suggestions about Wily documentation, please send us an email at wily-techpubs@ca.com.
May 2010
page 59
11. Acknowledgements
Portions of this product include software developed by the Apache Software Foundation. The Apache software is distributed in accordance with the following license agreement. Portions of this product include software developed by Mort Bay Consulting. The Jetty software is distributed in accordance with the following license agreement. Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. 'License' shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. 'Licensor' shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. 'Legal Entity' shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, 'control' means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. 'You' (or 'Your') shall mean an individual or Legal Entity exercising permissions granted by this License. 'Source' form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. 'Object' form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and versions to other media types. 'Work' shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work(an example is provided in the Appendix below). 'Derivative Works' shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. 'Contribution' shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, 'submitted' means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as 'Not a Contribution.' 'Contributor' shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s)with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions:
May 2010
page 60
(a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a 'NOTICE' text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an 'AS IS' BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NONINFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets '[]' replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same 'printed page' as the copyright notice for easier identification within third-party archives. ==== Eclipse Equinox Aspects Eclipse Equinox Aspects was obtained under the Eclipse Public License v.1.0, the terms and conditions of which are set forth below. Eclipse is distributed by CA for use with this CA product in unmodified, object code form, under the CA End User License Agreement. Any provisions in the CA End User License Agreement that differ from the Eclipse Public License are offered by CA alone and not by any other party. CA makes the source code for Eclipse available at http://opensrcd.ca.com/ips/P04639_6/ under the terms of the Eclipse Public License v.1.0. ====
May 2010
page 61
This product contains Eclipse 3.3 (the 'Eclipse Product'). Use of the Eclipse Product is governed by the Eclipse Public License 1.0. The source code for Eclipse Product may be found here http://www.eclipse.org/downloads/ or here http://opensrcd.ca.com. ==== JHotDraw 5.3; JasperReports 1.3.3; JFreeCharts 1.0.8; jxDBCon The above-referenced libraries (collectively, the "LGPL Software") are open source software libraries that are used with the CA Wily Introscope software ("Introscope"). The LGPL Software is not owned by CA, Inc. ("CA"). Use, copying, distribution and modification of the LGPL Software is governed by the GNU Lesser General Public License ("LGPL") version 2.1. A copy of the LGPL license can be found at http://opensrcd.ca.com/ips/osgi/ in the archive file in which the LGPL Software is distributed. Additionally, a copy of the LGPL license can be found at http://www.opensource.org/licenses/lgpl-2.1.php or write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA. CA makes the source code for the LGPL Software, including any modifications, available at http://opensrcd.ca.com/ips/osgi/, and includes a copy of the source code in the same archive file as the executable code. Use of the Introscope software is governed solely by the CA end user license agreement ("EULA"), not by the LGPL license. You cannot use, copy, modify or redistribute any Introscope code except as may be expressly set forth in the EULA. The LGPL Software is provided "AS IS" WITHOUT WARRANTY OR CONDITION OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Further details of the disclaimer of warranty with respect to the LGPL Software can be found in the LGPL license itself. To the full extent permitted under applicable law, CA disclaims all warranties and liability arising from or related to any use of the LGPL Software. ==== "Java Architecture for XML Binding (JAXB) 2.0" This product contains portions of the "Java Architecture for XML Binding" (JAXB) 2.0 (the "JAXB Component"). Use of the JAXB Component is governed by the Common Development and Distribution License v1.0. The source code for the JAXB Component may be found here: http://opensrcd.ca.com/ips/2584_6 or here https://jaxb.dev.java.net/. ==== The source code version of Rhino 1.6 Release 2 is licensed under the Netscape Public License Version 1.1 which can be found at http://www.mozilla.org/NPL/ and is made available for download from http://opensrcd.ca.com/ips/01189_1/. ==== Portions of this product include software developed by JGoodies (http://www.jgoodies.com/) and is distributed in accordance with the following license agreement. The BSD License for the JGoodies Looks ====================================== Copyright (c) 2001-2007 JGoodies Karsten Lentzsch. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. Neither the name of JGoodies Karsten Lentzsch nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. ==== Copyright (c) 2003, www.pdfbox.org All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
May 2010
page 62
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. Neither the name of pdfbox; nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. ==== Portions of this product include software developed by The Legion of the Bouncy Castle. The Bouncy Castle software is distributed in accordance with the following license agreement. Copyright (c) 2000 - 2006 The Legion Of The Bouncy Castle (http://www.bouncycastle.org) Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. ==== Portions of this product include software developed by Queensland University of Technology. The QUT software is distributed in accordance with the following license agreement. PERWAPI Copyright Copyright 1998 - 2005 Queensland University of Technology (QUT). All rights reserved. Redistribution and use in source and binary forms, with or without modification are permitted provided that the following conditions are met: 1. Redistribution of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials with the distribution. THIS SOFTWARE IS PROVIDED BY THE GPCP PROJECT AS IS AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE HEREBY DISCLAIMED. IN NO EVENT SHALL THE GPCP PROJECT OR QUT BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. The views and conclusions contained in the software and documentation are those of the authors and should not be interpreted as representing official policies, either expressed or implied, of the GPCP project or QUT. ==== Isomorphic SmartClient web presentation layer (c) 2000-2004 Isomorphic Software, Inc. (www.isomorphic.com). All rights reserved. ==== Portions of this product include the Guiffy Java API package licensed from Guiffy Software.
May 2010
page 63
==== Portions of this product include software developed by the NMock 2 Development Team. The NMock software is distributed in accordance with the following license agreement. Copyright (c) 2005-2006, NMock 2 Development Team. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. Neither the name of NMock nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. ==== Portions of this product include software developed by the TanukiSoftware.org. The Tanuki software is distributed in accordance with the following license agreement. Copyright (c) 1999, 2003 TanukiSoftware.org Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sub-license, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. ==== CONTAINS IBM(R) 32-bit Runtime Environment for AIX(TM), Java(TM) 2 Technology Edition, Version 1.5 Modules (c) Copyright IBM Corporation 1999, 2002 All Rights Reserved ==== Portions of this product include software developed by the Knopflerfish Project (http://www.knopflerfish.org/) and is distributed in accordance with the following license agreement: Copyright (c) 2003-2006, KNOPFLERFISH project All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: - Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. - Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. - Neither the name of the KNOPFLERFISH project nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
May 2010
page 64
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. ==== This product includes TableSorter v.2.0 software distributed pursuant to the following terms: Copyright (c) 1995 - 2008 Sun Microsystems, Inc. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: - Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. - Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. - Neither the name of Sun Microsystems nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. ==== This product includes Doug Lea Concurrent Utilities 1.3.4. Portions of the CopyOnWriteArrayList and ConcurrentReaderHashMap classes are adapted from Sun JDK source code. These are copyright of Sun Microsystems, Inc, and are distributed in accordance with the following terms: TECHNOLOGY LICENSE FROM SUN MICROSYSTEMS, INC. TO DOUG LEA Whereas Doug Lea desires to utlized certain Java Software technologies in the util.concurrenttechnology; and Whereas Sun Microsystems, Inc. ("Sun") desires that Doug Lea utilize certain Java Software technologies in the util.concurrent technology; Therefore the parties agree as follows, effective May 31, 2002: "Java Software technologies" means classes/java/util/ArrayList.java, and classes/java/util/HashMap.java. The Java Software technologies are Copyright (c) 1994-2000 Sun Microsystems, Inc. All rights reserved. Sun hereby grants Doug Lea a non-exclusive, worldwide, non-transferrable license to use, reproduce, create derivate works of, and distribute the Java Software and derivative works thereof in source and binary forms as part of a larger work, and to sublicense the right to use, reproduce and distribute the Java Software and Doug Lea's derivative works as the part of larger works through multiple tiers of sublicensees provided that the following conditions are met: -Neither the name of or trademarks of Sun may be used to endorse or promote products including or derived from the Java Software technology without specific prior written permission; and -Redistributions of source or binary code must contain the above copyright notice, this notice and the following disclaimers: This software is provided "AS IS," without a warranty of any kind. ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE HEREBY EXCLUDED. SUNMICROSYSTEMS, INC. AND ITS LICENSORS SHALL NOT BE LIABLE FOR ANY DAMAGES SUFFERED BY LICENSEE AS A RESULT OF USING, MODIFYING OR DISTRIBUTING THE SOFTWARE OR ITS DERIVATIVES. IN NO EVENT WILL SUN MICROSYSTEMS, INC. OR ITS LICENSORS BE LIABLE FOR ANY LOST REVENUE,PROFIT OR DATA, OR FOR DIRECT, INDIRECT, SPECIAL, CONSEQUENTIAL,INCIDENTAL OR PUNITIVE DAMAGES, HOWEVER CAUSED AND REGARDLESS OF THE THEORY OF
May 2010
page 65
LIABILITY, ARISING OUT OF THE USE OF OR INABILITY TO USE SOFTWARE, EVEN IF SUN MICROSYSTEMS, INC. HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. You acknowledge that Software is not designed, licensed or intended for use in the design, construction, operation or maintenance of any nuclear facility. ==== Portions of this product include software provided by Intalio, Inc. and is distributed in accordance with the following license agreement: Copyright 1999-2004 (C) Intalio Inc., and others. All Rights Reserved. Redistribution and use of this software and associated documentation ("Software"), with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain copyright statements and notices. Redistributions must also contain a copy of this document. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. The name "ExoLab" must not be used to endorse or promote products derived from this Software without prior written permission of Intalio Inc. For written permission, please contact info@exolab.org. 4. Products derived from this Software may not be called "Castor" nor may "Castor" appear in their names without prior written permission of Intalio Inc. Exolab, Castor and Intalio are trademarks of Intalio Inc. 5. Due credit should be given to the ExoLab Project (http://www.exolab.org/). THIS SOFTWARE IS PROVIDED BY INTALIO AND CONTRIBUTORS ``AS IS|&"&| AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL INTALIO OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. ==== This product includes LsaUtility software published at The Code Project (http://www.codeproject.com/KB/cs/lsadotnet.aspx). LsaUtility is distributed in accordance with the terms of the following: Preamble This License governs Your use of the Work. This License is intended to allow developers to use the Source Code and Executable Files provided as part of the Work in any application in any form. The main points subject to the terms of the License are: Source Code and Executable Files can be used in commercial applications; Source Code and Executable Files can be redistributed; and Source Code can be modified to create derivative works.
No claim of suitability, guarantee, or any warranty whatsoever is provided. The software is provided "as-is". The Article(s) accompanying the Work may not be distributed or republished without the Author's consent This License is entered between You, the individual or other entity reading or otherwise making use of the Work licensed pursuant to this License and the individual or other entity which offers the Work under the terms of this License ("Author"). License THE WORK (AS DEFINED BELOW) IS PROVIDED UNDER THE TERMS OF THIS CODE PROJECT OPEN LICENSE ("LICENSE"). THE WORK IS PROTECTED BY COPYRIGHT AND/OR OTHER APPLICABLE LAW. ANY USE OF THE WORK OTHER THAN AS AUTHORIZED UNDER THIS LICENSE OR COPYRIGHT LAW IS PROHIBITED. BY EXERCISING ANY RIGHTS TO THE WORK PROVIDED HEREIN, YOU ACCEPT AND AGREE TO BE BOUND BY THE TERMS OF THIS LICENSE. THE AUTHOR GRANTS YOU THE RIGHTS CONTAINED HEREIN IN CONSIDERATION OF YOUR ACCEPTANCE OF SUCH TERMS AND CONDITIONS. IF YOU DO NOT AGREE TO ACCEPT AND BE BOUND BY THE TERMS OF THIS LICENSE, YOU CANNOT MAKE ANY USE OF THE WORK. Definitions. "Articles" means, collectively, all articles written by Author which describes how the Source Code and Executable Files for the Work may be used by a user. "Author" means the individual or entity that offers the Work under the terms of this License.
May 2010
page 66
"Derivative Work" means a work based upon the Work or upon the Work and other pre-existing works. "Executable Files" refer to the executables, binary files, configuration and any required data files included in the Work. "Publisher" means the provider of the website, magazine, CD-ROM, DVD or other medium from or by which the Work is obtained by You. "Source Code" refers to the collection of source code and configuration files used to create the Executable Files. "Standard Version" refers to such a Work if it has not been modified, or has been modified in accordance with the consent of the Author, such consent being in the full discretion of the Author. "Work" refers to the collection of files distributed by the Publisher, including the Source Code, Executable Files, binaries, data files, documentation, whitepapers and the Articles. "You" is you, an individual or entity wishing to use the Work and exercise your rights under this License. Fair Use/Fair Use Rights. Nothing in this License is intended to reduce, limit, or restrict any rights arising from fair use, fair dealing, first sale or other limitations on the exclusive rights of the copyright owner under copyright law or other applicable laws. License Grant. Subject to the terms and conditions of this License, the Author hereby grants You a worldwide, royalty-free, nonexclusive, perpetual (for the duration of the applicable copyright) license to exercise the rights in the Work as stated below: You may use the standard version of the Source Code or Executable Files in Your own applications. You may apply bug fixes, portability fixes and other modifications obtained from the Public Domain or from the Author. A Work modified in such a way shall still be considered the standard version and will be subject to this License. You may otherwise modify Your copy of this Work (excluding the Articles) in any way to create a Derivative Work, provided that You insert a prominent notice in each changed file stating how, when and where You changed that file. You may distribute the standard version of the Executable Files and Source Code or Derivative Work in aggregate with other (possibly commercial) programs as part of a larger (possibly commercial) software distribution. The Articles discussing the Work published in any form by the author may not be distributed or republished without the Author's consent. The author retains copyright to any such Articles. You may use the Executable Files and Source Code pursuant to this License but you may not repost or republish or otherwise distribute or make available the Articles, without the prior written consent of the Author. Any subroutines or modules supplied by You and linked into the Source Code or Executable Files this Work shall not be considered part of this Work and will not be subject to the terms of this License. Patent License. Subject to the terms and conditions of this License, each Author hereby grants to You a perpetual, worldwide, nonexclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, import, and otherwise transfer the Work. Restrictions. The license granted in Section 3 above is expressly made subject to and limited by the following restrictions: You agree not to remove any of the original copyright, patent, trademark, and attribution notices and associated disclaimers that may appear in the Source Code or Executable Files. You agree not to advertise or in any way imply that this Work is a product of Your own. The name of the Author may not be used to endorse or promote products derived from the Work without the prior written consent of the Author. You agree not to sell, lease, or rent any part of the Work. This does not restrict you from including the Work or any part of the Work inside a larger software distribution that itself is being sold. The Work by itself, though, cannot be sold, leased or rented. You may distribute the Executable Files and Source Code only under the terms of this License, and You must include a copy of, or the Uniform Resource Identifier for, this License with every copy of the Executable Files or Source Code You distribute and ensure that anyone receiving such Executable Files and Source Code agrees that the terms of this License apply to such Executable Files and/or Source Code. You may not offer or impose any terms on the Work that alter or restrict the terms of this License or the recipients' exercise of the rights granted hereunder. You may not sublicense the Work. You must keep intact all notices that refer to this License and to the disclaimer of warranties. You may not distribute the Executable Files or Source Code with any technological measures that control access or use of the Work in a manner inconsistent with the terms of this License. You agree not to use the Work for illegal, immoral or improper purposes, or on pages containing illegal, immoral or improper material. The Work is subject to applicable export laws. You agree to comply with all such laws and regulations that may apply to the Work after Your receipt of the Work. Representations, Warranties and Disclaimer. THIS WORK IS PROVIDED "AS IS", "WHERE IS" AND "AS AVAILABLE", WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES OR CONDITIONS OR GUARANTEES. YOU, THE USER, ASSUME ALL RISK IN ITS USE, INCLUDING COPYRIGHT INFRINGEMENT, PATENT INFRINGEMENT, SUITABILITY, ETC. AUTHOR EXPRESSLY DISCLAIMS ALL EXPRESS, IMPLIED OR STATUTORY WARRANTIES OR CONDITIONS, INCLUDING WITHOUT LIMITATION, WARRANTIES OR CONDITIONS OF MERCHANTABILITY, MERCHANTABLE QUALITY OR FITNESS FOR A PARTICULAR PURPOSE, OR ANY WARRANTY OF TITLE OR NON-INFRINGEMENT, OR THAT THE WORK (OR ANY PORTION THEREOF) IS CORRECT, USEFUL, BUG-FREE OR FREE OF VIRUSES. YOU MUST PASS THIS DISCLAIMER ON WHENEVER YOU DISTRIBUTE THE WORK OR DERIVATIVE WORKS.
May 2010
page 67
Indemnity. You agree to defend, indemnify and hold harmless the Author and the Publisher from and against any claims, suits, losses, damages, liabilities, costs, and expenses (including reasonable legal or attorneys fees) resulting from or relating to any use of the Work by You. Limitation on Liability. EXCEPT TO THE EXTENT REQUIRED BY APPLICABLE LAW, IN NO EVENT WILL THE AUTHOR OR THE PUBLISHER BE LIABLE TO YOU ON ANY LEGAL THEORY FOR ANY SPECIAL, INCIDENTAL, CONSEQUENTIAL, PUNITIVE OR EXEMPLARY DAMAGES ARISING OUT OF THIS LICENSE OR THE USE OF THE WORK OR OTHERWISE, EVEN IF THE AUTHOR OR THE PUBLISHER HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Termination. This License and the rights granted hereunder will terminate automatically upon any breach by You of any term of this License. Individuals or entities who have received Derivative Works from You under this License, however, will not have their licenses terminated provided such individuals or entities remain in full compliance with those licenses. Sections 1, 2, 6, 7, 8, 9, 10 and 11 will survive any termination of this License. If You bring a copyright, trademark, patent or any other infringement claim against any contributor over infringements You claim are made by the Work, your License from such contributor to the Work ends automatically. Subject to the above terms and conditions, this License is perpetual (for the duration of the applicable copyright in the Work). Notwithstanding the above, the Author reserves the right to release the Work under different license terms or to stop distributing the Work at any time; provided, however that any such election will not serve to withdraw this License (or any other license that has been, or is required to be, granted under the terms of this License), and this License will continue in full force and effect unless terminated as stated above. Publisher. The parties hereby confirm that the Publisher shall not, under any circumstances, be responsible for and shall not have any liability in respect of the subject matter of this License. The Publisher makes no warranty whatsoever in connection with the Work and shall not be liable to You or any party on any legal theory for any damages whatsoever, including without limitation any general, special, incidental or consequential damages arising in connection to this license. The Publisher reserves the right to cease making the Work available to You at any time without notice Miscellaneous This License shall be governed by the laws of the location of the head office of the Author or if the Author is an individual, the laws of location of the principal place of residence of the Author. If any provision of this License is invalid or unenforceable under applicable law, it shall not affect the validity or enforceability of the remainder of the terms of this License, and without further action by the parties to this License, such provision shall be reformed to the minimum extent necessary to make such provision valid and enforceable. No term or provision of this License shall be deemed waived and no breach consented to unless such waiver or consent shall be in writing and signed by the party to be charged with such waiver or consent. This License constitutes the entire agreement between the parties with respect to the Work licensed herein. There are no understandings, agreements or representations with respect to the Work not specified herein. The Author shall not be bound by any additional provisions that may appear in any communication from You. This License may not be modified without the mutual written agreement of the Author and You. ==== AspectJ v.1.5.3 AspectJ v.1.5.3 was obtained under the Eclipse Public License v.1.0, except where noted below, and is distributed by CA for use with this CA product in unmodified, object code form, under the CA license agreement. Any provisions in the CA license agreement that differ from the Eclipse Public License are offered by CA alone and not by any other party. CA makes the source code for the EPL licensed portions of AspectJ available at http://opensrcd.ca.com/ips/P05029_11/ under the terms of the Eclipse Public License v.1.0. Alternatively, you may obtain the source code from www.eclipse.org. Additional information concerning this component may be found in its applicable Eclipse About.HTML files. BCEL v5.1 This component contains software developed by the Apache Software Foundation (http://www.apache.org). AspectJ includes a modified version of the Apache Jakarta Byte Code Engineering Library (BCEL) v5.1. BCEL is available at http://jakarta.apache.org/bcel/. Source code for the modified version of BCEL is available at Eclipse.org in the AspectJ source tree. This code was made available under the Apache Software License v1.1 ==================================================================== The Apache Software License, Version 1.1 Copyright (c) 2001 The Apache Software Foundation. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
May 2010
page 68
3. The end-user documentation included with the redistribution, if any, must include the following acknowledgment: "This product includes software developed by the Apache Software Foundation (http://www.apache.org/)."Alternately, this acknowledgment may appear in the software itself, if and wherever such third-party acknowledgments normally appear. 4. The names "Apache" and "Apache Software Foundation" and "Apache BCEL" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact apache@apache.org. 5. Products derived from this software may not be called "Apache", "Apache BCEL", nor may "Apache" appear in their name, without prior written permission of the Apache Software Foundation. THIS SOFTWARE IS PROVIDED ``AS IS|&"&| AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. ==================================================================== This software consists of voluntary contributions made by many individuals on behalf of the Apache Software Foundation. For more information on the Apache Software Foundation, please see ASM v2.2.1 AspectJ includes a binary version of ASM v2.2.1 (http://asm.objectweb.org/) The source code for ASM is available from the ObjectWeb download site at http://asm.objectweb.org/download/. The ASM license is available at http://asm.objectweb.org/license.html. The license is also reproduced here: Copyright (c) 2000-2005 INRIA, France Telecom All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. Neither the name of the copyright holders nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Introscope 8

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Introscope 8

Загружено:

Авторское право:

Доступные форматы

CA Wily Introscope 8

May 2010 Contents

Release 8.2.3 ReadMe

Introscope 8.2.3 ReadMe

Introscope 8.2.3 ReadMe

Important things to know: Enable collection of filter parameters for .NET

Introscope 8.2.3 ReadMe

Property to set AutoProbe log size for Java Agent

Add the following property to the JAVA _OPTIONS

set JAVA_OPTIONS=%SAVE_JAVA_OPTIONS% javaagent:C:\sw\bea\WL10\wily\Agent.jar Dcom.wily.introscope.agentProfile=C:\sw\bea\WL10\wily\IntroscopeAgent.pro file -Dcom.wily.autoprobe.logSizeInKB=1000

The size of Autoprobe.*.log is limited to system defined value of 1000KB.

Support for MOM Failover

Two properties added to the EM properties file

Introscope 8.2.3 ReadMe

CA certificates need to be restored when JRE is upgraded

java Dcom.wily.introscope.epagent.properties=../IntroscopeEPAgent.properties jar EPAgent.jar

kill -9 PID where PID is the process ID.

Enter the following in the command prompt:

./EPACtrl.sh start / stop / status

Introscope 8.2.3 ReadMe

2.1 Enhanced dashboards

Introscope 8.2.3 ReadMe

Introscope 8.2.3 ReadMe

To drill down into MOM performance:

Introscope 8.2.3 ReadMe

To drill down into Collector capacity:

MOM - Infrastructure Overview (Wily EM-Cluster Monitoring)

Introscope 8.2.3 ReadMe

Introscope 8.2.3 ReadMe

Introscope 8.2.3 ReadMe

Introscope 8.2.3 ReadMe

Introscope 8.2.3 ReadMe

About Alerts The alerts in the dashboard are:

Threshold alert Clamping Alert

Introscope 8.2.3 ReadMe

2.2 Viewing Live and Historical Data in the Workstation Console

Introscope 8.2.3 ReadMe

Click the Live button.

Introscope 8.2.3 ReadMe

2.3 SmartStor Tools Using SmartStor tools to tune SmartStor data

Commands and syntax

SmartStor tools commands reference

Introscope 8.2.3 ReadMe

Windows SmartStorTools.bat merge <source directory> <destination directory>

SmartStorTools.bat merge <EM_Home>\data

UNIX SmartStorTools.sh merge <source directory> <destination directory> remove_metrics

-dest -help -metrics -src

C:\SWDump\destination -metrics ".*Socket.*" -src <EM_Home>\data

-agents -dest -help -src

Introscope 8.2.3 ReadMe

".*WebSphere.*" -dest C:\SWDump\destination -src <EM_Home>\data

-agents -dest -help -src

<EM_Home>\tools>SmartStorTools.bat keep_agents -agents ".*WebSphere.*" -dest C:\SWDump\destination\keepagents -src <EM_Home>/data

-backup -help -silent -src

Introscope 8.2.3 ReadMe

Windows SmartStorTools.bat Prune <source directory>

backup <destination directory>

-help -src -agents -metrics

Windows SmartStorTools.bat test_regex -agents <agent(s) name> src <source directory>

Windows SmartStorTools.bat list_agents -agents <agent(s) name> src <source directory>

Introscope 8.2.3 ReadMe

Restart the Enterprise Manager.

Introscope 8.2.3 ReadMe

Introscope 8.2.3 ReadMe

C:\SWDump\destination -metrics ".Socket." -src <EM_Home>\data

".WebSphere." -dest C:\SWDump\destination -src <EM_Home>\data

<EM_Home>\tools>SmartStorTools.bat keep_agents -agents ".WebSphere." -dest C:\SWDump\destination\keepagents -src <EM_Home>/data