Introscope8.1.2.0 README

CA Wily Introscope® 8 Release 8.1.2.
0 README
Copyright® 2010 CA. All Rights Reserved
Wily Technology Inc. and Introscope are registered trademarks of CA
March 5, 2010
Contents
1. Release summary ............................................................................................. 2
2. What’s new ..................................................................................................... 2
3. Installation and upgrade notes .............................................................................. 3
4. Backward compatibility ....................................................................................... 4
5. Limitations & restrictions ..................................................................................... 5
Deprecated and changed features ......................................................................... 5
6. Fixed in this release ........................................................................................... 5
Fixed in Service Pack Release 8.1.2.0..................................................................... 5
Fixed in Service Pack Release 8.1.1.0..................................................................... 6
7. Known issues .................................................................................................. 7
High priority issues ............................................................................................ 7
Other known issues ........................................................................................... 8
8. Introscope for SAP Solution Manager Diagnostics-related known issues ........................... 19
9. Introscope .NET Agent-related release notes ........................................................... 20
Other Introscope .NET agent-related known issues .................................................... 22
10. Contacting Technical Support .............................................................................. 23
11. Acknowledgements .......................................................................................... 23
Release 8.1.2.0 is a Service Pack release of Introscope. It is intended to address the

following issues:
Bug Number Component Priority of Fix Plugins
61300 EM Critical EM
58950 Agent High Agent
60507 EM High EM
60508 EM Medium EM
60509 EM Medium EM
60510 EM Medium EM
59755 EM High EM
60083 EM High EM
54627 EPAgent Medium Agent
55686 WebView Critical WebView
56274 Workstation Critical Workstation

Introscope 8.1.2.0 Release Notes February 2010 page 2
59776 WebView High WebView
60866 Agent Critical Agent
60914 EM Critical EM
1. Release summary
Release 8.1.2 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.1x.
The 8.1 release integrates Introscope’s SOA Performance Management (SPM) extensions with
the core Introscope programs, tools and utilities, with new features enabled in the SPM
extensions. See “What’s New” and “Integrations” below. It also includes all bug fixes
performed in Introscope 8.0 service pack releases.
2. What’s new
For a list of fixes included in this service pack release, see “Fixed in this Release” on page 5.
Key features in Introscope 8.1 include:
SOA Performance Management (SPM)
The Service Dependency Map presents a graphical visualization of interdependent services
within the SOA. Automatically generated from performance metrics and analysis of metrics,
errors and events. Enables the Application Support manager to instantly grasp the layout of
the SOA in a visual manner.
Real-time SOA dashboard presents a quantitative summary of the health of the SOA. Provides
an up-to-date status display and helps the Application Support team to identify trends and
changes in the SOA without needing to create manual dashboards or manually analyze or
group service metrics.
Extensible Cross-Process Transaction Tracing extends cross-process transaction tracing to
common-denominator protocols HTTP and JMS. Also includes script based extensibility
framework to enable rapid extension to new platforms and protocols.
SOA Extension for Oracle Service Bus (aka ALSB) provides OOB dashboards and performance
metrics for Oracle Service Bus, providing critical visibility to help IT operations teams quickly
troubleshoot distributed performance issues involving this important SOA platform.
The SOA Extension for Oracle Service Bus includes the following:
 Proxy Services
 Business Services
 Pipeline
 XQueries
 Transports
 UDDI
 Cross-process transaction tracing in and out of Oracle Service Bus across SOAP, HTTP,
and JMS communications protocols
WebSphere Process Server / WebSphere ESB extension provides OOB dashboards and
performance metrics for WebSphere Process Server and WebSphere ESB, providing critical
visibility to help IT operations teams quickly troubleshoot distributed performance issues
involving this important SOA Platform.
The SOA Extension for WebSphere Process Server and ESB includes the following:
 Business Process Metrics
 Business State Machine Metrics
 Business Rule Metrics
 Java Component Metrics
 Mediation Flow Metrics
 Mediation Primitives Metrics
 Human Tasks
 Selectors
 Interface Maps
 Adapters
 BO Maps
 Relationships
 Selectors
 WPS Faults
 JMS level Tracing
 Cross Process Transaction Tracing supported for HTTP binding and web services
binding
For details about how SOA Performance Management works with Introscope, see the
detailed SOA scenario in the Introscope Overview Guide.
3. Installation and upgrade notes
a. Upgrading from previous releases of Introscope 8.0x

The Introscope 8.1 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.1.1

You can use the Introscope 8.1 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.1.x. Any 8.x installer will automatically upgrade
earlier 8.x versions to its level.
Enterprise Manager, Workstation and WebView are compatible only with same-revision
releases, so if you upgrade any of these components to 8.1.1, you must upgrade all of
them.
The Introscope Installation and Upgrade Guide contains special instructions for upgrading
version 6.1 agents.
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.
See the Introscope Installation and Upgrade Guide for instructions on upgrading to
Introscope 8.1.
c. SOA Performance Management extensions are downloaded and installed

separately
The SPM extensions have separate file archives which you must download and install
separately from Introscope. Note: Install and upgrade Introscope first, then install SPM
extensions using the installation instructions in the SOA Performance Management
Implementation Guide (i.e., SOAPerformanceManagement.pdf).
d. Integrations
SOA Performance Management

This release ships Wily Introscope with SPM 8.1 extensions, which must be installed
separately. To enable integration between Introscope and SPM, several new properties
have been added to Introscope’s Enterprise Manager and agent properties files. For a
full list and description of these, see SPM user documentation.
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.
4. Backward compatibility
Introscope 8.1 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.1 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.
5. Limitations & restrictions
The version of SPM released with 8.1 supports only Introscope 8.1.x or above Agents and
Enterprise Managers.
Deprecated and changed features

No features are deprecated or removed in this release.
6. Fixed in this release
Fixed in Service Pack Release 8.1.2.0
Problem Description
ID
61300 sporadic "not reporting" phases on the consoles in 8.1
58950 Agent causing out of memory conditions on production JVMs.
60507 MOM hung up again
60508 Make size of server Mailmain thread pool configurable
60509 Add clamp to limit number of data points returned by query
60510 EM does not log CLW queries
59755 Slow Collector cause MOM unresponsive and dropping data
60083 Dashboards are not updating correctly.
54627 Can tell when EPA metrics are not reporting data
55686 Problem with domains
56274 Problem with domains; NullPointerException, ConcurentModificationException
56536 Agent unable to resolve collector name
59056 JVM crashed with signal 11 in libIntroscopeHpuxItaniumStats.so
59276 WebView display issue in an clustered environment
60118 HP-UX platform monitor doesn't support more than 10 CPUs
60866 Wily Agent causing deadlock
60914 harvest errors after upgrade

Problem Description
ID
61073 JMX beans on Tomcat not showing up in the investigator
54967 metrics by ChangeDetector
Fixed in Service Pack Release 8.1.1.0

The following known issues from earlier releases have been fixed in this service pack.
Problem Description
ID
52023 An issue preventing customers in some language locales from using historical view in
WebView has been fixed.
51859 A problem has been fixed which caused the Agent tree, as displayed in the Workstation, to
52145 collapse when Agents disconnected.
52314 A problem has been fixed which caused links in dashboard objects to go to the wrong default
location in the agent tree.
52690 A problem has been fixed which caused incorrect formatting of JDBC URLs on systems
using an Informix RDBMS backend

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 service pack.

For SAP-related issues, see Section 8 on page 16.
For SPM-related issues, see the ReadMe file published with your SPM download.
High priority issues
Problem Description
ID
38182 Customers using JVM AutoProbe with the IBM JVM version 1.5 may see unnaturally high CPU
48922 overheard. The workaround for this issue is documented in the following Knowledge Base articles
on http://www.ca.com/wily/support.
 1231
 1310
 1317
 1370
 1730
46519 Installing the platform monitor on HPUX using .zip or .tar installers requires administrators to
49313 change read-write permissions on the following files to 777:
 wily/ext/introscopeHpuxItaniumStats.jar
 wily/ext/introscopeHpuxItaniumStats.so
 wily/ext/introscopeHpuxParisc32Stats.jar
 wily/ext/introscopeHpuxParisc32Stats.so
Make these changes after installing the agent and before starting it.
If you are using the first two files named above, you also must install gcc before starting the
agent. You can download gcc, a compiler for C and C++, by searching HP’s support website.
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.
47144 WebView does not support non-ISO-8859 characters in Introscope 8.0. We expect to re-establish
support for this character set in subsequent versions. The workaround is to connect to the
Enterprise Manager using Java Web Start.
47145 To avoid problems using load balancing with ChangeDetector, designate a specific Collector as
the ChangeDetector agent’s “preferred” Collector. See the section “Load balancing when Agents
prefer a specific Collector” in the Introscope Configuration Administration Guide.
49131 Enterprise Manager is backward-compatible with agents, so you can continue to use pre-8 agents
50033 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.
Other known issues
Problem Description
ID
27488 Due to a JRE issue, stalled stateless plugins are not properly killed on some platforms, and they
27489 continue to consume resources even after the EPAgent has been stopped. These orphan
27492 processes must be stopped manually.
25616 If a Collector’s system clock is out of sync with the MOM by more than 3 seconds, the MOM
27812 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.
30018 On some system configurations, Change Detector reports the Time Changed metric one hour off
due to Daylight Savings Time differences.
36025 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.
38321 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.
38464 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.
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.
38636 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.
38867 When using dynamic instrumentation, and many classes are re-defined, under certain JVMs
38868 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.
Problem Description
ID
38934 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.
39472 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.
39497 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.
39499 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
39716 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.
39884 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
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.
41483 Filtering based on agent name uses the property

introscope.agent.perfmon.agentExpression. A valid agent expression would be
ProcessName|AgentName or *|MyAgent.
41566 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.
41856 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.
Problem Description
ID
56554 Deleting the object link dashboard, webview is displaying confusing message. Deleting
56548 dashboard from WS which is opened in webview throwing error popups
The workaround is whenever the Webview throws a Silverlight error, after acknowledging the pop
ups, we need to click on the console tab. So that the webview refreshes the page once again.
41929 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
42030 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 you’ve configured).
NOTE: Checking “Use TLS 1.0” will make it difficult for the user to access other websites that use
SSL.
42368 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.
42461 Due to a known issue with the Apache web server, if the IPv6 address in the
45726 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.
43217 LeakHunter users should note:

48253 To work with LeakHunter, a collection’s [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.”
Problem Description
ID
43373 The following names of properties which can be configured for Command Line Workstation (CLW)
have been changed:
Old property New Property
wily.ps.clw.tt.console introscope.clw.tt.console
wily.ps.clw.tt.dirname introscope.clw.tt.dirname
txn.file introscope.clw.tt.filename
wily.ps.clw.tt.encoding introscope.clw.tt.encoding
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.
45889 Due to a bug in JBoss, users running JBoss 4.0.5 on a 64 bit SuSe 9 environment who make run-
time 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.
45915 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.
46017 On IBM iSeries environments using the 1.5 "classic" (64-bit) JVM, installing the Introscope agent
53233  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.)
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.
46481 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.
46688 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.
46921 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).
Problem Description
ID
46997 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.
47093 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.
47101 LeakHunter is supported on 64 bit .NET frameworks, Windows 2008 server, and .NET framework
3.0.
47148 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. 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.)
4. 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
7. 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
8. 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.
47276 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.
47277 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.
Problem Description
ID
47280 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 hasn’t
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.
47308 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.
47417 The WebView Investigator tree sometimes incorrectly shows an agent and the agent’s 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.
47559 In some cases, customers running WebSphere Application Server (WAS) 6.1 on the AIX platform
49246 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
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.
47740 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.
48011 Due to a vulnerability in Jetty, Introscope deployments will experience a cross-site scripting
vulnerability. There is no workaround.
48471 Due to a design limitation, correlated Transaction Traces can be viewed in the Transaction Tracer
49367 viewer in Workstation, but will not appear as correlated if saved as XML and then viewed from the
XML files.
Problem Description
ID
48521 WLS users with EJB 3.0 may see EJB nodes in the Workstation tree named with an unhelpful
48943 $Proxynnn name. To make EJB 3.0 metrics visible, and to prevent metrics from being displayed
50132 under $Proxynnn:
51526 If you use 7.2.x agents:
1. Edit the j2ee.pbd file to add the following lines:
IdentifyAnnotatedClassAs: javax.ejb.Stateless SessionBeanTracing
IdentifyAnnotatedClassAs: javax.ejb.Stateful SessionBeanTracing
IdentifyAnnotatedClassAs: javax.persistence.Entity EntityBeanTracing
IdentifyAnnotatedClassAs: 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
48537 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.
48662 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.
48697 Windows platform monitors require the Extensible Counter List utility available from :
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
… to delete the following string at the beginning of each file:
#!/bin/sh
Deleting this string will cause commands in the file to be executed using the.bin.sh (Bourne) shell.
Problem Description
ID
48885 To prevent an Out Of Memory error, customers who want to turn on exception tracing with
49328 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.
49146 For WebSphere 7 Installations, the ws70x.pbd does not contain trace directives for WebSphere 7
specific classes that implement J2EE classes/interfaces.
49503 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 Errata for the Java Agent Guide:

51631  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.
49574 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.
49753 Due to an issue with the 8.0.0 version Agent, you should use the 8.0.2 version Agent for cross-
49788 JVM tracing on the WebSphere 6.1 application server.
49794
52666
49789 The 8.x agent does not support cross JVM tracing on IBM WebSphere 7.0 application servers.
49790 Users who execute cross JVM tracing for IBM WebSphere 6.1 may notice that the resulting
50745 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.
49797 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.
49918 The Java Agent platform monitor for HPUX reports the percentage use of CPUs when more than
50078 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.
Problem Description
ID
49998 System objects must be enabled for platform monitoring to work on Windows.
To determine whether system objects are enabled:
1. Go to Start > Run
2. Type perfmon and click Run.
3. In the dialog box click Add.
4. In the Add dialog, if "Process" and "Processor" performance objects are
present in the drop down list box, then system objects are enabled.
To enable system objects:
1. Go to Start > Programs > Accessories.
2. Right click Command Prompt.
3. Choose Run as… > Administrator.
4. Run the command: lod ctr /r
"Process" and "Processor" objects will be enabled.
50002 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.
50076 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> ...
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.
50141  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.
50464 Due to a display problem, the Workstation will not show red and yellow higlighting for threshold
and caution values in data tables.
50767 The User ID for Enterprise Manager is case insensitive. For example, userid "guest" and "Guest"
are the same.
50787  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.
51207  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.
51587 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.
Problem Description
ID
51725 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.
52066 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.
52180  The CPU Utilization metrics graph will not display in WebView under historical mode.
Problem Description
ID
52789  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=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
The following JVMs are supported by platform monitors:

 Sun JVM
 HP Hotspot JVM
 IBM JVM ( Both Classic and J9 )
 BEA JRocket JVM
32-bit Platform Monitor binaries can be installed on a 64-bit machine, provided a 32-bit bit JVM is
installed.
52642  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.
53129  The Workstation will not display information for JVM Architecture ( Bit Mode ) for applications on
an i series Classic (64 bit) JVM platform.
Problem Description
ID
53130  The Java Agent Guide will be updated to list:

53131 The latest Linux binary filenames:
53132  introscopeLinuxIntelAmd32Stats.jar
 introscopeLinuxIntelAmd64Stats.jar
 libIntroscopeLinuxIntelAmd32Stats.so
 libIntroscopeLinuxIntelAmd64Stats.so
The latest Windows binary filenames:
 introscopeWindowsIntelAmd32Stats.dll
 introscopeWindowsIntelAmd64Stats.dll
 introscopeWindowsIntelAmd32Stats.jar
 introscopeWindowsIntelAmd64Stats.jar
The latest HP-U binary filenames:
 introscopeHpuxItaniumStats.jar
 introscopeHpuxParisc32Stats.jar
 introscopeHpuxItanium64Stats.jar
 libIntroscopeHpuxItaniumStats.so
 libIntroscopeHpuxParisc32Stats.so
 libIntroscopeHpuxItanium64Stats.so
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.
8. Introscope for SAP Solution Manager Diagnostics-related known issues
The following issues relate only to Introscope for SAP Solution Manager Diagnostics.
Problem Description
ID
41380 EM startup messages are no longer displayed in the console by default. To see startup
messages, view the IntroscopeEnterpriseManager.log file.
47117 The installer does not automatically create an ext directory. Administrators must manually create
the ext directory after the installation process.
51644 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)”
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)
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
 Windows Server 2003 Enterprise Edition – SP2 / IIS Version 6.0
 Windows Server 2008 Enterprise Edition / IIS Version 7.0
Upgrading to version 8.1

To upgrade from a previous version of the Introscope .NET agent, Wily recommends following
these 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.1 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).
 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.
 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>
</com.wily.introscope.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.
46154 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
TraceOneMethodIfFlagged: WCFServiceTracing Multiply BlamePointTracer
TraceOneMethodIfFlagged: WCFServiceTracing Divide BlamePointTracer
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.
46589 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.
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.
50105 Due to a regression issue, the time it takes for the Introscope .NET agent to start up has
50742 increased somewhat.
52637  When an agent disconnects from the Enterprise Manager, its icon in the Workstation agent tree
turns gray. Normally, this happens within 4 to 5 seconds. However, depending on the topology
of your network, amount of traffic on your network, TCP/IP configuration on your OS, overall load
on the agent hardware, and socket settings of the application that the agent is monitoring (notably
Microsoft IIS), it may take the Enterprise Manager up to 30 to 45 seconds to be informed of the
disconnect. During that time, no new data will appear in the Workstation, even though the agent
still appears to be connected.
10. Contacting Technical Support
For help with Introscope or any other product from CA′s Wily Technology Division, contact
Wily Technical Support:
http://www.ca.com/wily/support
Toll free in the U.S.: 1 888 GET WILY ext. 1
U.S.: +1 630 505 6966
Europe: +44 (0)870 351 6752
Asia-Pacific: +81 3 6868 2300
Toll free in Japan: 0120 974 580
Latin America +55 11 5503 6167
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 e-
mail at wily-techpubs@ca.com.
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:
(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, NON-INFRINGEMENT,
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.
====
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

The above-referenced libraries (collectively, the ?LGPL Software?) are open source software
libraries that are used with the CA Wily Introscope 8.0 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:
o Redistributions of source code must retain the above copyright notice, this list of conditions
and the following disclaimer.
o 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.
o 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:
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
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
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.
====
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
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
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
====

Introscope8.1.2.0 README

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Introscope8.1.2.0 README

Hochgeladen von

Copyright:

Verfügbare Formate

CA Wily Introscope® 8 Release 8.1.2.

Release 8.1.2.0 is a Service Pack release of Introscope. It is intended to address the

Bug Number Component Priority of Fix Plugins

58950 Agent High Agent

54627 EPAgent Medium Agent

55686 WebView Critical WebView

56274 Workstation Critical Workstation

56536 Agent High Agent

59056 Agent High Agent

59776 WebView High WebView

60118 Agent High Agent

60866 Agent Critical Agent

61073 Agent High Agent

3. Installation and upgrade notes

a. Upgrading from previous releases of Introscope 8.0x

b. Upgrading to Introscope 8.1.1

c. SOA Performance Management extensions are downloaded and installed

SOA Performance Management

CA-Wily Customer Experience Manager integration

5. Limitations & restrictions

Deprecated and changed features

6. Fixed in this release

Fixed in Service Pack Release 8.1.2.0

61300 sporadic "not reporting" phases on the consoles in 8.1

58950 Agent causing out of memory conditions on production JVMs.

60507 MOM hung up again

60508 Make size of server Mailmain thread pool configurable

60509 Add clamp to limit number of data points returned by query

60510 EM does not log CLW queries

59755 Slow Collector cause MOM unresponsive and dropping data

60083 Dashboards are not updating correctly.

55686 Problem with domains

56274 Problem with domains; NullPointerException, ConcurentModificationException

56536 Agent unable to resolve collector name

59056 JVM crashed with signal 11 in libIntroscopeHpuxItaniumStats.so

59276 WebView display issue in an clustered environment

60118 HP-UX platform monitor doesn't support more than 10 CPUs

60866 Wily Agent causing deadlock

60914 harvest errors after upgrade

61073 JMX beans on Tomcat not showing up in the investigator

54967 metrics by ChangeDetector

61202 JVM crashed with signal 11 in libIntroscopeHpuxItaniumStats.so

61203 HP-UX platform monitor doesn't support more than 10 CPUs

Fixed in Service Pack Release 8.1.1.0

59056 JVM crashed with signal 11 in libIntroscopeHpuxItaniumStats.so

60118 HP-UX platform monitor doesn't support more than 10 CPUs

Issues marked with  are new in this service pack.

High priority issues

Other known issues

38566 After making changes to the IntroscopeAgent.profile property

41483 Filtering based on agent name uses the property

41929 If administrators have customized the Enterprise Manager property

43217 LeakHunter users should note:

47308 In upgrades to 8.0, the upgrader fails to remove a no-longer-used java.awt.headless

2. Edit the wl8x.pbd file to add the following line:

49512 Errata for the Java Agent Guide:

The following JVMs are supported by platform monitors:

53130  The Java Agent Guide will be updated to list:

8. Introscope for SAP Solution Manager Diagnostics-related known issues

9. Introscope .NET Agent-related release notes

Upgrading to version 8.1

Limitations & restrictions