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 Release summary ............................................................................................. 2 What’s new ..................................................................................................... 2 Installation and upgrade notes .............................................................................. 3 Backward compatibility ....................................................................................... 4 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 1. 2. 3. 4. 5.

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

Bug Number
61300 58950 60507 60508 60509 60510 59755 60083 54627 55686 56274

Component EM Agent EM EM EM EM EM EM EPAgent WebView Workstation

Priority of Fix Critical High High Medium Medium Medium High High Medium Critical Critical

Plugins EM Agent EM EM EM EM EM EM Agent WebView Workstation

Introscope 8.1.2.0 Release Notes

February 2010

page 2

56536 59056 59776 60118 60866 60914 61073

Agent Agent WebView Agent Agent EM Agent

High High High High Critical Critical High

Agent Agent WebView Agent Agent EM Agent

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

Introscope 8.1.2.0 Release Notes     

February 2010

page 3

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:

0 Release Notes  February 2010 page 4 Any version 8.2 or above to be compatible with 8. available through CA Wily software fulfillment.0.pdf).2. .1 functionality.1 extensions. follow the procedure documented in the “Integrating Wily Introscope with Wily CEM” chapter of the Wily CEM Integration Guide.0. SOAPerformanceManagement. Version 8.   See the Introscope Installation and Upgrade Guide for instructions on upgrading to Introscope 8.1 is backwards compatible with all supported Introscope Agents dating back to Introscope 6. so customers who upgrade to Enterprise Manager 8. then install SPM extensions using the installation instructions in the SOA Performance Management Implementation Guide (i.x.x agents will continue to work with Enterprise Manager 8.1 agents should be upgraded to 8. Other CA products Customers who intend to integrate Introscope 8. When integrating Wily CEM with Introscope . If you have a prior version of CEM. see SPM user documentation.x agent can connect to a version 8.2+ are strongly encouraged to upgrade their 8.1 agents to 8. d.0.0. 8.2+ Enterprise Manager.x or above. To enable integration between Introscope and SPM.2.Introscope 8. you must upgrade to CEM 4..0.1 Enterprise Manager.2+ agents.0.0.0.0. Upgrading agents to 8.0.0. CA-Wily Customer Experience Manager integration Integration of CA-Wily Customer Experience Manager (CEM) with Introscope 8. Version 7.0. c.x with the following CA products:  Service Quality Management (SQM)  SPECTRUM … must install the Introscope Integration Software Developer’s Kit (SDK) version 7.1.1 Enterprise Manager.2+.1 will allow you to take full advantage of version 8. 4.1. See also the note below numbered 47740.e. Refer to the Wily CEM Integration Guide for detailed information.0 or above.x requires CEM version 4.0. or 8.2+ agents are fully compatible with 8. However. Backward compatibility Introscope 8.0. except:  Version 8. For a full list and description of these. which must be installed separately.2. 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. several new properties have been added to Introscope’s Enterprise Manager and agent properties files.2.x before integrating it with Introscope 8. Integrations SOA Performance Management This release ships Wily Introscope with SPM 8. Note: Install and upgrade Introscope first.1 agents with some specific configurations are not compatible with Enterprise Manager version 8.2.1.NET agents.

2 agent to manage that application.1.3.x or above Agents and Enterprise Managers.1 supports only Introscope 8. ConcurentModificationException Agent unable to resolve collector name JVM crashed with signal 11 in libIntroscopeHpuxItaniumStats.Introscope 8. If you have a Java 1.3.x-based application.so WebView display issue in an clustered environment HP-UX platform monitor doesn't support more than 10 CPUs Wily Agent causing deadlock harvest errors after upgrade . use the Introscope 7.1 Agent causing out of memory conditions on production JVMs.0 Problem ID Description 61300 58950 60507 60508 60509 60510 59755 60083 54627 55686 56274 56536 59056 59276 60118 60866 60914 sporadic "not reporting" phases on the consoles in 8. Can tell when EPA metrics are not reporting data Problem with domains Problem with domains.1. 6. NullPointerException. Limitations & restrictions The version of SPM released with 8.2.1 Introscope Agent does not support web applications running on Java 1.0 Release Notes  February 2010 page 5 The 8.x. Fixed in this release Fixed in Service Pack Release 8. Deprecated and changed features No features are deprecated or removed in this release. 5.1. MOM hung up again Make size of server Mailmain thread pool configurable Add clamp to limit number of data points returned by query EM does not log CLW queries Slow Collector cause MOM unresponsive and dropping data Dashboards are not updating correctly.2.

so HP-UX platform monitor doesn't support more than 10 CPUs 51859 52145 52314 52690 59056 60118 . as displayed in the Workstation.so HP-UX platform monitor doesn't support more than 10 CPUs Fixed in Service Pack Release 8. A problem has been fixed which caused incorrect formatting of JDBC URLs on systems using an Informix RDBMS backend JVM crashed with signal 11 in libIntroscopeHpuxItaniumStats. A problem has been fixed which caused the Agent tree. Problem ID 52023 Description An issue preventing customers in some language locales from using historical view in WebView has been fixed.1.1.Introscope 8.2. to collapse when Agents disconnected.0 Release Notes February 2010 page 6 Problem ID Description 61073 54967 61202 61203 JMX beans on Tomcat not showing up in the investigator metrics by ChangeDetector JVM crashed with signal 11 in libIntroscopeHpuxItaniumStats.1. A problem has been fixed which caused links in dashboard objects to go to the wrong default location in the agent tree.0 The following known issues from earlier releases have been fixed in this service pack.

The Introscope 8. For SPM-related issues.2+ Enterprise Manager.2 agent to manage that application. Issues marked with  are new in this service pack. If you are using the first two files named above.ca.2 or above to be compatible with 8. For SAP-related issues. Enterprise Manager is backward-compatible with agents.1 agents should be upgraded to 8.jar  wily/ext/introscopeHpuxParisc32Stats.com/wily/support) for more information about any of these issues.tar installers requires administrators to change read-write permissions on the following files to 777:  wily/ext/introscopeHpuxItaniumStats. See the section “Load balancing when Agents prefer a specific Collector” in the Introscope Configuration Administration Guide. so you can continue to use pre-8 agents with Enterprise Manager 8.0 Enterprise Manager supports agents back to version 6. However.0.1 Enterprise Manager.0.0 Release Notes February 2010 page 7 7. by searching HP’s support website.3.so  wily/ext/introscopeHpuxParisc32Stats. 46557 The 8.1 functionality.0.  Version 8.0.1.  Upgrading agents to 8.com/wily/support. WebView does not support non-ISO-8859 characters in Introscope 8. Please note:  Any version 8.x agent can connect to a version 8.zip or . Known issues You can contact Wily Support (http://www.5 may see unnaturally high CPU overheard. use the Introscope 7.      46519 49313 1231 1310 1317 1370 1730 Installing the platform monitor on HPUX using . designate a specific Collector as the ChangeDetector agent’s “preferred” Collector. The workaround for this issue is documented in the following Knowledge Base articles on http://www. The workaround is to connect to the Enterprise Manager using Java Web Start. see Section 8 on page 16. You can download gcc.3.Introscope 8.so Make these changes after installing the agent and before starting it. High priority issues Problem ID 38182 48922 Description Customers using JVM AutoProbe with the IBM JVM version 1.0.1.0. We expect to re-establish support for this character set in subsequent versions.0. To avoid problems using load balancing with ChangeDetector. If you have a Java 1.jar  wily/ext/introscopeHpuxItaniumStats.0 Introscope Agent does not support web applications running on Java 1.ca.1 Enterprise Manager. see the ReadMe file published with your SPM download. 8. you also must install gcc before starting the agent. a compiler for C and C++. or 8.0.1 will allow you to take full advantage of version 8. 47144 47145 49131 50033 .0.x.2.2+ agents are fully compatible with 8.x-based application.

you must restart the application server before the changes can take effect. see the Introscope Java Agent Guide. users who try to review data previously displayed from that agent will see a com. In a clustered environment.” To avoid seeing this error when an agent has been disconnected or unmounted. the repeated attempts to reconnect may result in an out-of-memory error.0_03.agent. The only workaround is to correct system clocks so that they are less than 3 seconds apart. and they continue to consume resources even after the EPAgent has been stopped.2 may encounter a Java heap Out of Memory error: “java.profile property introscope.server. or to return to the default view when this error is displayed. changing the Collector's system clock may result in live metric data not being visible in the Collector.introscope. For more information. which also deal with PermGen memory issues. If you continue to encounter these errors. If a Collector’s system clock is out of sync with the MOM by more than 3 seconds.OutOfMemoryError: PermGen space” if the following three conditions apply:  The application . Customers can avoid this problem by creating well-written calculators.sampling.agent.jar file out of the extension directory.1. stalled stateless plugins are not properly killed on some platforms. See also the note for issues 38867/38868.Introscope 8.wily.lang. 30018 36025 38321 38464 38566 After making changes to the IntroscopeAgent. In order to see the previously available agent data.count property in IntroscopeAgent. When an agent is unmounted. then restart the Collector. 38636 38867 38868 . contact Wily Support.transactiontracer. the agent must be remounted using the Workstation. Users deploying an application on WebLogic Server version 9. users will get eventual OutOfMemory errors and the application will crash. On some system configurations.profile. the MOM disconnects from the Collector but checks every 15 seconds to see if the clock skew has been corrected. These orphan processes must be stopped manually. The workaround is to move the application .spec. When using dynamic instrumentation. This is a result of the way PermGen is handled in the specific JVM.ConstructNotFoundException error in the console. and many classes are re-defined. refresh the Investigator page using the browser Refresh button or by clicking the Investigator tab link. under certain JVMs including Sun HotSpot 1. The workaround is to turn off dynamic instrumentation.5.0 Release Notes Other known issues Problem ID 27488 27489 27492 25616 27812 Description February 2010 page 8 Due to a JRE issue. and  The application is instrumented with an Introscope agent.2.metric. Change Detector reports the Time Changed metric one hour off due to Daylight Savings Time differences.enabled to enable or disable FirstNPerInterval Transaction Trace sampling.ext. 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. 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. 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.jar file is deployed to the default WLS extension directory  The application directly invokes a ClassLoader to load the application .jar file. However.

resolutionseconds 39472 39497 39499 39716 Restarting the EM too quickly may fail on some operating systems. A possible workaround is to increase the memory size provided to the EM (Java -X options). Due to the way the Enterprise Manager tracks internal metrics about its own performance. To avoid this problem.which appears as part of the supportability metrics under the path CustomMetricAgent|EM|Connection|DataStor|MetaData:"Partial Metrics with Data" -. The data is preserved in historical data. There is no workaround.enterprisemanager. data for the “repeated” hour is overwritten and is lost from regular reports.agentExpression. it may cause an OOM exception in the EM and a CLW crash.serversockets. you wait for the socket to exit the TIME_WAIT. startup may fail with misleading error messages because the OS has not released the Enterprise Manager's server port (5001). This is due to an InstallAnywhere issue. The workaround is to set a property named introscope. This may lead to gaps between metric data points.reuseaddr. Filtering based on agent name uses the property introscope. It enters this state after the socket has been closed. 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.stalls. If the amount of data requested is too large. the Command Line Workstation [CLW]. 40180 When the EM is overloaded and cannot finish harvesting in the time interval. To uninstall the EM on z/OS. A valid agent expression would be ProcessName|AgentName or *|MyAgent. in transaction traces. error snapshots and ChangeDetector data.agent. To uninstall an instance of Enterprise Manager which was installed in silent mode.agent. generally 120 seconds.stalls. The socket remains in TIME_WAIT state for a system-dependent time. If you choose not to enable the introscope.4.enterprisemanager. so attempting to toggle SocketTracing during runtime will evoke an error 39884 message: Unsupported change to active AutoProbe configuration. Using existing configuration.perfmon. Customers are advised not to execute extremely large queries. you must use console mode to uninstall. or any other client). However. but this too has its own limits.0 Release Notes February 2010 page 9 Problem ID 38934 Description When system clocks roll back one hour during the change from Daylight Savings Time to Standard Time.reuseaddr to true. as it removes the protection against two Enterprise Managers using the same port.agent. it will log WARN messages about dropped time slices. If stall resolution and stall threshold are set in the Agent profile to numbers which total less than 15 (the EM harvest duration). Introscope Workstation. install JVM 1. If the EM is shut down and restarted too quickly. the Stall Count metric may show inaccurate data.pbd file.thresholdseconds introscope. then run the uninstaller. The only workaround is to restart the JVM after making changes to the .serversockets.Introscope 8. particularly Linux.should be taken as an approximate figure only. this should be used with caution. The Enterprise Manager uninstaller for z/OS will hang if run under JVM 1.5.1.2. set the following properties to total greater than 15: introscope. This allows the socket to be bound even though a previous connection is in a timeout state. the Partial Metrics with Data metric -. Dynamic Instrumentation does not support changes in Class Substitution which is used by the SocketTracing group. 41483 41566 41856 .

we need to click on the console tab.DEFAULT property in the Agent profile is not resolvable to a hostname.enterprisemanager.0 upgrader will not detect this change or perform any upgrade tasks on the directory.0. Advanced tab 3..0.webserver. Tools > Internet Options.0 web apps from the webapps dir to <customized_webapps_dir>/ :  webapps/IntroscopeHelp_Config. 1. So that the webview refreshes the page once again.2.enterprisemanager.x only: Move <customized_webapps_dir>/cem. Check “Use TLS 1. Due to a known issue with the Apache web server.” 42368 42461 45726 43217 48253 .0  When upgrading any version: Transfer the following two new 8. Collections whose size( ) method executes in time proportional to the number of objects in the Collection will have poor performance. you must manually perform the following tasks during the post-upgrade:  If upgrading 7. 4. webview is displaying confusing message. if the IPv6 address in the introscope. LeakHunter users should note: To work with LeakHunter.transport. Deleting dashboard from WS which is opened in webview throwing error popups The workaround is whenever the Webview throws a Silverlight error..war to a backup location as this file is obsolete in 8. TLS is another type of security protocol like SSL.host.0 Release Notes February 2010 page 10 Problem ID 56554 56548 Description Deleting the object link dashboard. the 8. In general.0” and “Use SSL 3. Uncheck “Use SSL 2.Introscope 8. To upgrade.” b. Such collections should be ignored. as shown in the section in the LeakHunter Guide headed “Configuring LeakHunter properties.profile.1. Open a new IE6 window and log in to EM using WebView again (using the same port 443 or whatever you’ve configured). Use the fully qualified agent name. this will have negative effects on application performance. In the dialog: a. using the ignore property in IntroscopeAgent. if the collection is such that the size( ) method takes longer and longer to execute (for example. 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. after acknowledging the pop ups.dir to be anything other than the default value webapps. 41929 If administrators have customized the Enterprise Manager property introscope. a collection’s [int size()] method must be thread-safe and actionable throughout the collection life cycle.tcp.0” will make it difficult for the user to access other websites that use SSL. a badly implemented LinkedList where to get the size of the list we traverse through each element of the list and count). Click OK. avoid using $agentname as a key for identifying a series.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.agent.war  webapps/IntroscopeHelp_Using. NOTE: Checking “Use TLS 1. In other words. 5. then the agent will not connect to EM using http tunneling port. 2. In reports.

restart your JBoss server after making changes.file wily. To date. this behavior has been observed only in IBM WebSphere MQ. CA Wily has filed an issue with IBM and is continuing to monitor this issue.tt.define.static. This exception does not affect WebView functionality and users can ignore this error. To avoid this.clw. To avoid this delay.ps.clw. users running JBoss 4. The workaround is to click the "Investigator" tab to refresh the display (or use the browser refresh button).ps. There is a workaround documented in Knowledge Base article no.force. -Xbootclasspath/a:PathToAgentJar -javaagent:PathToAgentJar -Dcom.encoding New Property introscope. Users may encounter problems when importing saved Transaction Traces. On IBM iSeries environments using the 1.tt.clw. which can be identified from the Java stack trace. This is a third party bug.dirname txn.filename introscope.2. Performing historical queries using "componentNotShown" as a query filter may return incorrect results.startup times as long as 50 minutes have been observed.0. WebView may hang If an agent is unmounted.) 46035 Because data for string-based metrics is not stored in SmartStor.5 "classic" (64-bit) JVM.0 Release Notes February 2010 page 11 Problem ID 43373 Description The following names of properties which can be configured for Command Line Workstation (CLW) have been changed: Old property wily. see the Transaction Clamping documentation in the Introscope Workstation User Guide.dirname introscope.programs=1 -Dos400. 45889 45915 46017 53233  46481 46688 46921 .Introscope 8. installing the Introscope agent results in the application server startup time to increase substantially -.console introscope.introscope.clw.log file if the logger is configured to print in the log file. For more information.wily.encoding The old property names will not be supported in future releases. There is no workaround other than avoiding redefinition of offending classes.jitc (Note: ignore the last line break. An issue with IBM WebSphere MQ produces a Java exception after Introscope redefines certain Java classes during the process of dynamic instrumentation. add these options to the command line. Administrators should allow extra time for installations on this platform.tt. The exception is logged in the IntroscopeWebView.clw.5 on a 64 bit SuSe 9 environment who make runtime changes to the j2E.ca. otherwise it is displayed in the console window. 45690 The tool tip feature in WebView.jvmti.console wily. which displays information about data points in tool tips. the Metric Count pie chart and accompanying table will not report correct metric counts in historical mode. Due to a bug in JBoss.tt.agentProfile=PathToAgentProfile -Dos400. and a WebView user tries to expand a node in the tree of the unmounted agent.clw.cache= Dos400.com/wily/support.1.pbd file may see null pointer exceptions in JBoss server logs or Introscope agent logs.tt. this can also sometimes happen when the user attempts to view many different dashboards in succession.tt.ps. 1714 on http://www. sometimes produces an IllegalArgumentException when WebView attempts to display too much information.tt.clw.disable. 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. Users should view the Metric Count pie chart only in live mode.class.

From a command prompt.0 Release Notes February 2010 page 12 Problem ID 46997 Description 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.3 64 bit Platform Monitor binaries work only on AIX machines which have Technology Level equal or greater than TL6 (5300-06). LeakHunter is supported on 64 bit . Locate and delete the following system variables:  com. Manually remove the Introscope .introscope. Users will see the message "An application error occurred. 2.AutoProbe. To see the tree proper.1.Introscope 8. (See the notes under known issue 47122 in the . Due to a known issue. Customers should ensure that their AIX machine is not less than TL6. and you must perform a manual uninstall on that platform. the ChangeDetector node cannot be viewed using WebView." There is no workaround using WebView. In WebView.)  "%WINDIR%\system32\regsvr32. choose Advanced > Environment Variables.AutoProbeConnector. include quotation marks. delete that key as well:  HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\Introscope 8. Users who then scroll up or down may get a false impression that the tree pane is blank. the tree pane scrolls automatically to the right. Users should view ChangeDetector metrics using Workstation.wily. From the System Properties control panel. when the metrics tree includes a metric with a very long name.) 4.NET frameworks.exe" /s /u "<path_to_Agent_Dir>\wily\bin\wily. You may need to wait several minutes to view the correct historical data.NET\Framework\<dotnetversion>\REgAsm. Manually remove the Wily agent DLL from the Global Assembly Cache. use scroll bars to scroll to the left. To manually uninstall the agent: 1.2. To avoid this.dll" /unregister /verbose 3.NET framework 3.NET-related issues on page 19.0.dll" 47093 47101 47148  "%WINDIR%\Microsoft. Stop the monitored web application.exe" "<path_to_Agent_Dir>\wily\bin\wily. 47204 AIX 5.jar from Sun and deploy it to the <Tomcat_Home>/common/endorsed directory before starting Tomcat. Windows 2008 server.agentProfile  Cor_Enable_Profiling  COR_PROFILER  INTROSCOPE_AUTOPROBE_SKIP_FILE 7. and . Users running the agent on Tomcat 4. The agent silent uninstaller does not work correctly on Windows XP SP2. Manually remove the following registry key:  HKEY_LOCAL_MACHINE\SOFTWARE\ComputerAssociates\Introscope\NETAgent If this step leaves the parent key empty. download jmx. (Ignore line breaks.1 with default setup and enabled JMX may see a ClassNotFoundException in the agent log. execute the following commands to unregister the following DLLs. 47276 47277 .NET Agent install folder.

include the following JVM flag in the Generic JVM Arguments field when configuring your WAS application for Introscope: -Xshareclasses:none For more information.2windows.txt) reference in the ProbeBuilder Directive file. Introscope deployments will experience a cross-site scripting vulnerability.headless property from webview. after the upgrade manually edit webview. but will not appear as correlated if saved as XML and then viewed from the XML files.introscope.ManagedFileInputStream 47308 47417 47559 49246 To avoid this problem. The workaround for the latter defect is to log out of WebView and log back in to see the newly connected agent.NoClassDefFoundError: com.1. Due to a vulnerability in Jetty. In upgrades to 8. the data displayed by the Workstation will not correctly reflect all the Collectors in the cluster.headless to true.wily.pbd.2. see "Configuring WebSphere Application Server (WAS)" in the Introscope Java Agent Guide. Instead. Customers can ensure the Workstation displays correct data by disconnecting slow Collectors from the cluster or.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. customers running WebSphere Application Server (WAS) 6.lax. 47740 When integrating CEM with Introscope Java agents. correlated Transaction Traces can be viewed in the Transaction Tracer viewer in Workstation. This could cause WebView to fail to start on non-Windows platforms. by tuning Collector performance to improve its response times.0 Release Notes February 2010 page 13 Problem ID 47280 Description In a clustered environment. There is no workaround. the MOM will drop a connection to a Collector it thinks is unresponsive. more ideally. 48011 48471 49367 .awt. the MOM will send to Workstation what data it has. The Introscope 8. This version is out of date.probe.jar and SHD.agent. its response times may exceed the two-minute time window during which the MOM listens for data from Collectors.0.zip. the upgrader fails to remove a no-longer-used java. In some cases.0 Agent. Due to a design limitation. you must deploy the CEMTracer and ServletHeaderDecorator agent extensions.io. In such circumstances. The WebView Investigator tree also sometimes does not automatically show newly connected agents and their metrics even if the user refreshes the browser. not including the data from the slow collectors which is dropped because the slow collector hasn’t responded in over 2 minutes.pbd files from CEMIntroscopeIntegrationKit-v4. you should use the SHD.awt. In extreme cases. In such cases. if a Collector is responding very slowly due to hardware or network issues.lax to set java.zip file still embeds a ServletHeaderDecorator PBD (ServletHeaderDecorator_iscope8.0.lang. The WebView Investigator tree sometimes incorrectly shows an agent and the agent’s child nodes as connected when the agent has been disconnected. To fix this problem.Introscope 8.

"Unable to select dashboard.pbd file to add the following lines: IdentifyAnnotatedClassAs: IdentifyAnnotatedClassAs: IdentifyAnnotatedClassAs: IdentifyAnnotatedClassAs: javax.ejb. be sure to start the installer using a 1. 48792 Users running Introscope on Solaris operating systems must edit the following files:   EMCtrl.messaging. For example: <java> -classpath <installer.BasePayloadHandlerSupport MessageDrivenBeanTracing 48537 When upgrading to this Service Pack.2.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. if using a jar installer for z/OS or other Unix platforms.5 Java Virtual Machine.MessageDriven MessageDrivenBeanTracing 2. specify the path to the installer.jar file includes the version number.jar> install -f <absolute_path_to_response_file> 48553 Due to an issue with Silverlight. Edit the wl8x. Enable performance counters PerfProc for processor & PerfOs for process performance object.exe 2.Stateless SessionBeanTracing javax.0 Release Notes February 2010 page 14 Problem ID 48521 48943 50132 51526 Description WLS users with EJB 3.ejb. and to prevent metrics from being displayed under $Proxynnn: If you use 7.pbd file to add the following line: SkipPackagePrefixForFlag: $Proxy SessionBeanTracing If you use 8.x agents: 1. The correct name of the extracted SNMP Adapter .x agents: To correctly display names of message-driven EJB 3.2.Entity EntityBeanTracing javax.persistence.1.0. the absolute path to the response file. When using the silent install method. Run exctrlst_setup.0 may see EJB nodes in the Workstation tree named with an unhelpful $Proxynnn name.com/download/win2000platform/exctrlst/1.em.introscope.sh EPACtrl. WebView users on machines which have been upgraded to Microsoft Silverlight 2.Stateful SessionBeanTracing javax.snmp_8.wily. and a JVM which must be versioned 1.1. After downloading the utility: 48662 48697 1.microsoft.jar.0. close and restart the browser window and connect again using WebView.sh (Bourne) shell.bin." After this the WebView display freezes and the user is unable to view other dashboards.pbd) and place it in the <Agent_Home>/hotdeploy folder with the following contents: IdentifyClassAs: com.3x who use Internet Explorer version 6.common.Introscope 8.0 beans in the Introscope metrics tree under the EJB node :  Create a custom pbd file (named <custom>.0 metrics visible. .1/nt5/enus/exctrlst_setup.0. Windows platform monitors require the Extensible Counter List utility available from : http://download.0.bea. for example: com.00.ejb. If this happens. To make EJB 3.x may see an error.exe.medrec. Edit the j2ee.5.

The Java Agent platform monitor for HPUX reports the percentage use of CPUs when more than one process is present.0 application servers.0.0 Release Notes February 2010 page 15 Problem ID 48885 49328 Description To prevent an Out Of Memory error.0 version Agent. the ws70x. this means it is using 1.tar. Users who execute cross JVM tracing for IBM WebSphere 6. and log in again to that Enterprise Manager.2.pbd does not contain trace directives for WebSphere 7 specific classes that implement J2EE classes/interfaces.1 application server. For WebSphere 7 Installations. copy your changes.2. the feature by which Transaction Traces show all correlated components was disabled for 8. 49574 When the agent is started on an application server which has the Change Detector extension enabled. restart it.2.0.”  References to 8. customers who want to turn on exception tracing with WebSphere 7 must increase the memory available to the JVM. 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.0.0.” the note should read “For WebLogic 9.1.0.0.1.Introscope 8. you should use the 8. quit or kill the Workstation application.x to 8.1 may notice that the resulting display in Workstation Trace View shows traces misaligned or out of order. 49797 49918 50078 .1.unix.0 under the data folder.x agent does not support cross JVM tracing on IBM WebSphere 7.  References to “Java 2 components” should read “J2EE components. Under certain installations.0 can generally be taken to also refer to 8.0websphere.1 CPUs. 49146 49503 49512 51631 Errata for the Java Agent Guide:  In the section “WLDF metrics. For example. increase maximum JVM heap size setting on the WebSphere application server to at least 1 GB.0.x only. if you have 4 processes.0websphere. If this happened after you upgraded Enterprise Manager from 7.1.x to 8.”  References to JavaI5DynamicInstrumentation.1. try deleting the cache in the <Agent_Home>/wily directory. For example.jar.2 version Agent for crossJVM tracing on the WebSphere 6. ChangeDetector will not detect changes.0.unix.0. Due to internal issues.tar will be NoInstaller8. To do this. To work around this problem. Due to an issue with the 8. If one process takes 110%.x Presently Transaction Traces will show only components for the selected agent rather than all correlated components. filenames such as NoInstaller8. This happens occasionally when the agents participating in the cross JVM traces are not time-synchronized.jar should be corrected to Java15DynamicInstrumentation. the maximum use of the CPU would be 400% (4 processes using 100% of the CPU).db file from 7. 49753 49788 49794 52666 49789 49790 50745 The 8. If this happens. There is no workaround.

0.42 must use the ^ (caret) character to escape a forward slash when issuing commands. Right click Command Prompt. To work around this problem.0 Release Notes February 2010 page 16 Problem ID 49998 Description System objects must be enabled for platform monitoring to work on Windows.1. place extension . The status message "Wrote report c:\path\to\report.0. For example. The User ID for Enterprise Manager is case insensitive. Go to Start > Programs > Accessories. References to . 3. place extension . 50002 Customers running Introscope Workstation on the Vista OS may encounter difficulty printing reports to a directory from Command Line Workstation. 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.1. 2. 4.wily.wily. Go to Start > Run Type perfmon and click Run.introscope.errordetector_8. 50141  50464 50767 50787  51207 51587  . then system objects are enabled. To write a report to a directory.jar file.jar. There is no workaround. To determine whether system objects are enabled: 1.RegexSqlNormalizer. Choose Run as… > Administrator.Introscope 8. 2. In the Introscope JavaAgent Guide. Due to a display problem. userid "guest" and "Guest" are the same. the Workstation will not show red and yellow higlighting for threshold and caution values in data tables.jar path> .pdf" will be erroneous because write permissions to directories are disabled by default on Vista.introscope.jar should read com. In the Add dialog.2. Customers running Oracle 10g Release 2 using Sun JDK 1. if "Process" and "Processor" performance objects are present in the drop down list box. customers who use the IntroscopeJDBC. In the dialog box click Add. Due to a change in the JDBC utilities shipped with 8. to start the agent: -Xbootclasspath^/p:<IntroscopeAgent. For example. 4.errordetector_8.ext.jar file should edit their classpath to point to a servlet .1 Service Pack A. Run the command: lod ctr /r "Process" and "Processor" objects will be enabled.jar and not wily. To enable system objects: 1. 3..jar files in the <Workstation_Home>\product\workstation\plugins directory.0 in the filename should use 8.0. 50076 50089  Users with SOA EM extensions may experience a Workstation hang when reconnecting to an Enterprise Manager after manual logout.1.jar file names in the ErrorDetector user documentation that use 8..dll. references to com.jar files in the <Introscope_Home>\products\workstation\plugins directory. If the Workstation is installed within the same folder of Enterprise Manager. 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. change the permissions on the directory before printing the report. For example.

2 to 8. users must log out. quit and restart the web browser. then open the Console. Values over 5% will not be displayed.” with an accompanying Java Null Pointer Exception in the WebView log. 52066 52180  .1. may see the error: “An application error occurred. The CPU Utilization metrics graph will not display in WebView under historical mode. then return to the Investigator tree view.2. and log in again.1 may see problems with the scale of the Overall EM Capacity % graph on the Overall Enterprise Manager Capacity %.Introscope 8. To resolve this error. To work around this problem.0 Release Notes February 2010 page 17 Problem ID 51725 Description Customers who have upgraded their Enterprise Manager from 7. manually set the y-axis of the graph to 0-100. WebView users who select the Host node under an agent.

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.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.system=HP-UXItanium #introscope.agent.platform.system=SolarisAmd64 #introscope.platform. 53129  .monitor.system=AIX53PSeries64 #introscope.monitor.agent. locate the exact matching value for your operating system and uncomment the property.agent.agent.platform.platform.system=WindowsIntelAmd64 #introscope.system=HP-UXItanium64 #introscope. or 5.Introscope 8.1. The Workstation will not display information for JVM Architecture ( Bit Mode ) for applications on an i series Classic (64 bit) JVM platform.agent.agent.agent.monitor.agent.monitor.agent.platform.2.monitor. platform monitor binaries are purely dependent on JVM architecture.system=WindowsIntelAmd32 #introscope.monitor.system=LinuxIntelAmd32 #introscope.0.platform. For more information about platform monitors.agent. The following is an update to the Java Agent Guide section called "Troubleshooting platform monitoring".platform. see the Java Agent Guide chapter "Configuring Platform Monitoring".agent.agent.platform. The available values are: #introscope.system=SolarisSparc64 #introscope.system=SolarisAmd32 #introscope.platform.system=SolarisSparc32 #introscope.agent.monitor. Under the Platform Monitor Configuration heading.monitor.monitor.monitor.platform. 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.platform.0 Release Notes February 2010 page 18 Problem ID 52789  Description 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. This is due to an IBM issue.monitor.monitor. Also.system=AIX52PSeries64 #introscope. 4.platform.0.monitor.system=AIX5PSeries32 #introscope. provided a 32-bit bit JVM is installed.monitor.system=HP-UXParisc32 #introscope.agent.platform.platform. Step two of the procedure should read as follows: 2.

Due to a regression. Problem ID 41380 Description EM startup messages are no longer displayed in the console by default.0 Release Notes February 2010 page 19 Problem ID 53130  53131 53132 Description The Java Agent Guide will be updated to list: The latest Linux binary filenames:               introscopeLinuxIntelAmd32Stats. hold the CTRL key while clicking the Export menu choice.Introscope 8.2. The installer does not automatically create an ext directory. Administrators must manually create the ext directory after the installation process. To see startup messages. view the IntroscopeEnterpriseManager.so introscopeWindowsIntelAmd32Stats.log file.properties (The system cannot find the file specified)” 47117 51644 . 8.FileNotFoundException: config\IntroscopeWebView.1. some WebView configuration properties may not be available to users of SAP Enterprise Manager.jar introscopeHpuxItaniumStats.io.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. Introscope for SAP Solution Manager Diagnostics-related known issues The following issues relate only to Introscope for SAP Solution Manager Diagnostics.jar libIntroscopeLinuxIntelAmd32Stats. To work around this issue.dll introscopeWindowsIntelAmd64Stats.jar introscopeHpuxItanium64Stats.jar introscopeHpuxParisc32Stats.so libIntroscopeLinuxIntelAmd64Stats.jar introscopeWindowsIntelAmd64Stats.jar introscopeLinuxIntelAmd64Stats.dll introscopeWindowsIntelAmd32Stats.jar libIntroscopeHpuxItaniumStats.so libIntroscopeHpuxParisc32Stats. Users may see an error “java.

Use of the IdentifyInheritedAs directive on generic Classes/Interfaces.5 Framework (v3.50727)  .2195 – SP4 / IIS Version 5.NET V3. Install the new version of the Introscope . Wily recommends following these steps: 1.NET agent. This involves a reboot of the system on which the agent is installed.NET agent configuration.0. Use of a parameterized tracer on methods with custom value types as parameters or return types.5. 2.1 Framework (v1.2. .NET agent.1  Windows 2000 5.NET agent does not support the following at this time:         Instrumentation of Microsoft XML and XSL classes.1.0 Framework (v3. Generic parameters to method types in directives (id 39682).0 (Enterprise Manager) and above This release is compatible with the following Microsoft .0  Windows Server 2003 Enterprise Edition – SP2 / IIS Version 6.NET agent (including settings.21022) This release is compatible with the following Microsoft Windows platform & IIS versions:  Windows XP Professional 2002 – SP2 / IIS Version 5. Uninstall the Introscope . 4.0 Upgrading to version 8. Introscope .Introscope 8.NET Agent Guide for instructions on uninstalling your Introscope Agent.1 for installation instructions. Limitations & restrictions The Introscope . 5.NET V3. 3.) from the backup you made in step 1.NET agent. Tracing using directives based on attributes applied on method parameters and return types.NET V1.6620  Windows Server 2003 Enterprise Edition – SP1 / IIS Version 6.0 Framework (v2.00.1. pbds. The DocumentationServerProtocol web services protocol.4322)  .1 To upgrade from a previous version of the Introscope .000.0 Release Notes February 2010 page 20 9.4056)  .NET Agent-related release notes Compatibility This release is compatible with the following Introscope versions:  Introscope 8. Back up your existing Introscope .0  Windows Server 2008 Enterprise Edition / IIS Version 7.NET V2.0. Please refer to the Introscope . Refer to the Introscope .NET agent Guide 8. If necessary. etc. Directives using nested class names longer than 256 characters (including the Namespace). Restore any customizations you used with the previous version of the Introscope . adjust any permissions to reference the new folder name.NET Framework versions:  .2195. Directives using Assembly names longer than 250 characters.

NET.NET agent and Java Agent:  The syntax for specifying fully qualified method names is different from Java.0.parameters> </com.[mscorlib]System.wily. The permissions required depend on the user identity running the application being instrumented.agent"> <section name="env. This extension can be used in Java to provide system properties and hourly metric counts in the agent log. the metric name displayed is not normalized (id 40027).System.NET. For example.parameters> <add key="com. Add a sectionGroup and a section to your application configuration file.NET agent to successfully operate.Culture=neutral.agent> <env.profile" /> </env.1.50 00.Int32".wily.parameters section.introscope.wily.<return type>(<param 1>.Introscope 8. The supportability-agent extension has not been ported to .agent> . The method signature is separated from the method name by a semicolon and has the return type before the parameters. Commonly observed differences between the Introscope .NameValueSectionHandler.NET agent and the Java Agent The following are common differences between the Introscope . it is crucial that the permissions on the Wily directory are set correctly.introscope.PublicKeyToken=b77a5c561934e089" /> </sectionGroup> 2.Void([mscorlib]System.introscope.0.parameters"    type="System.wily. For example: <com. To instrument WCF (Windows Communication Foundation) classes you must identify the classes with explicit directives.. Name them as follows: <sectionGroup name="com. Unlike the Java Agent.e.Object.2. You can then add any properties you want set to the env.introscope. when using XML documents to insert/update data in Oracle. "[mscorlib]System.[mscorlib]System.agentProfile" value="c:\\wily\\IntroscopeAgent. i. Lack of out-of-the-box metrics collection for WCF services (id 40810). The syntax is: <method name>.Int32)  For the Introscope . To set system properties (things you would set in Java with -D on the command line): 1. Types are specified with an optional assembly name included in front the of type name in square brackets.Version=1..) An example of a method name with the signature is: myMethod.NET agent does not support static ProbeBuilding.<param 2>. Refer to the documentation for detailed instructions. the Introscope . the only supported way to instrument an application is at run-time using AutoProbe.Configuration.0 Release Notes   February 2010 page 21 For ODP.

Users must restart the system after installing the agent.. Click View List of Assemblies in the Assembly Cache.NET agents. if it is present.NET agent. Register the agent: 8.NET Configuration 1. After 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.dll you just installed.dll .1 2. You should also manually unregister the agent after uninstalling it using the automated uninstaller. Users installing the Introscope . The only workaround is to disable monitoring of the database. Go to Control Panel > Administrative Tools > . see Knowledge Base article 1610 on http://www. Unregister the agent. For example. The Introscope . 9.Agent. 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.Agent.Net application.Agent.Introscope 8.dll to the GAC or unregistered it from the GAC.g. Choose Remove. 6. Users must manually instrument the class that implements the WCF service with a combination of IdentifyClassAs and TraceOneMethodIfFlagged directives. ChangeDetector changes will only be reported by the first worker process. 5. Select wily.NET implementation of Introscope.ca. 47443 In a Web Garden configuration on the IIS when more than one worker process exists for the . "Oracle db") is not displayed. Click Add an Assembly to the Assembly Cache. There is no loss of data and the message undeliverable exception printed in the log can be ignored. Click Manage the Assembly Cache 3. you must perform registration or unregistration manually: 46589 47122 1. if it is already registered: 4. .0 Release Notes February 2010 page 22 Other Introscope . Right-click wily. Browse to the wily.com/wily/support. the backend type (e.NET with the Database Monitor configured may see a memory leak when Database Monitor is not able to connect to the database. 46270 Customers running ChangeDetector on .1.2. 10. The directives shipped with this release are not capable of automatically instrumenting WCF services in a .NET agent Installer does not complete the process of setting environment variables on a Windows 2003 system.Agent. 7.NET agent-related known issues 39906 When using the Workstation Investigator to view backend components reported by Introscope .dll.

com/wily/support Toll free in the U. its icon in the Workstation agent tree turns gray.S. 'Licensor' shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. REPRODUCTION.Introscope 8. . Link to the survey at http://tinyurl. When an agent disconnects from the Enterprise Manager.0 Release Notes February 2010 page 23 50105 50742 52637  Due to a regression issue. even though the agent still appears to be connected. no new data will appear in the Workstation. Acknowledgements Portions of this product include software developed by the Apache Software Foundation.1. However. and socket settings of the application that the agent is monitoring (notably Microsoft IIS). Portions of this product include software developed by Mort Bay Consulting. Apache License Version 2. 10.apache. The Jetty software is distributed in accordance with the following license agreement. AND DISTRIBUTION 1. 1 U. it may take the Enterprise Manager up to 30 to 45 seconds to be informed of the disconnect. depending on the topology of your network. amount of traffic on your network. contact Wily Technical Support: http://www. Please take a short online survey to help us improve the information we provide you. 'License' shall mean the terms and conditions for use.: 1 888 GET WILY ext. overall load on the agent hardware. The Apache software is distributed in accordance with the following license agreement.ca. the time it takes for the Introscope . 11.2. During that time. reproduction. this happens within 4 to 5 seconds. please send us an email at wily-techpubs@ca.: +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. Normally. Contacting Technical Support For help with Introscope or any other product from CA′s Wily Technology Division.com/6j6ugb. January 2004 http://www. If you have other comments or suggestions about Wily documentation.NET agent to start up has increased somewhat. and distribution as defined by Sections 1 through 9 of this document.com. Definitions.S.org/licenses/ TERMS AND CONDITIONS FOR USE.0. TCP/IP configuration on your OS.

offer to sell. 3. non-exclusive. or merely link (or bind by name) to the interfaces of. no-charge. For the purposes of this definition. an original work of authorship. royaltyfree. sell. or other modifications represent. 2. or (iii) beneficial ownership of such entity. Derivative Works shall not include works that remain separable from. 'Derivative Works' shall mean any work. Subject to the terms and conditions of this License. each Contributor hereby grants to You a perpetual. import. worldwide. including but not limited to communication on electronic mailing lists. have made. elaborations. no-charge. to cause the direction or management of such entity. 'Source' form shall mean the preferred form for making modifications. source code control systems. including but not limited to software source code. whether by contract or otherwise. For the purposes of this License. are controlled by.2.Introscope 8. 'You' (or 'Your') shall mean an individual or Legal Entity exercising permissions granted by this License. and configuration files.1. direct or indirect. use. including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof. Subject to the terms and conditions of this License. each Contributor hereby grants to You a perpetual. as a whole. whether in Source or Object form. or written communication sent to the Licensor or its representatives. as indicated by a copyright notice that is included in or attached to the work(an example is provided in the Appendix below). that is based on (or derived from) the Work and for which the editorial revisions. whether in Source or Object form. generated documentation. annotations. Grant of Patent License. 'Work' shall mean the work of authorship. For the purposes of this definition. 'control' means (i) the power. non-exclusive. 'Object' form shall mean any form resulting from mechanical transformation or translation of a Source form. or (ii) ownership of fifty percent (50%) or more of the outstanding shares. 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. the Licensor for the purpose of discussing and improving the Work. verbal. 'submitted' means any form of electronic. or on behalf of. 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. and distribute the Work and such Derivative Works in Source or Object form. the Work and Derivative Works thereof. sublicense. 'Contribution' shall mean any work of authorship. 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. but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as 'Not a Contribution. irrevocable copyright license to reproduce. royaltyfree.0 Release Notes February 2010 page 24 'Legal Entity' shall mean the union of the acting entity and all other entities that control. worldwide. publicly perform. made available under the License. including but not limited to compiled object code.' '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. publicly display. documentation source. irrevocable (except as stated in this section) patent license to make. Grant of Copyright License. prepare Derivative Works of. then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. and issue tracking systems that are managed by. and versions to other media types. . and otherwise transfer the Work. or are under common control with that entity.

and (c) You must retain. including. Licensor provides the Work (and each Contributor provides its Contributions) on an 'AS IS' BASIS. without limitation. contract. 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. without any additional terms or conditions. reproduction. or. special. indirect. 8. and (d) If the Work includes a 'NOTICE' text file as part of its distribution. and attribution notices from the Source form of the Work. The contents of the NOTICE file are for informational purposes only and do not modify the License. including any direct. if provided along with the Derivative Works. 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. provided Your use. This License does not grant permission to use the trade names. provided that such additional attribution notices cannot be construed as modifying the License. In no event and under no legal theory. trademark. any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License. or FITNESS FOR A PARTICULAR PURPOSE. nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions.1.Introscope 8. Notwithstanding the above. 7. NON-INFRINGEMENT. alongside or as an addendum to the NOTICE text from the Work. Redistribution. any warranties or conditions of TITLE. with or without modifications. reproduction. unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing. trademarks.2. Unless required by applicable law or agreed to in writing. within a display generated by the Derivative Works. whether in tort (including negligence). Disclaimer of Warranty. You may add Your own attribution notices within Derivative Works that You distribute. . and in Source or Object form. 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. WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND. then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file. even if such Contributor has been advised of the possibility of such damages. service marks. Submission of Contributions. 6. Trademarks. patent. Limitation of Liability. if and wherever such third-party notices normally appear.0 Release Notes February 2010 page 25 4. MERCHANTABILITY. in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works. excluding those notices that do not pertain to any part of the Derivative Works. shall any Contributor be liable to You for damages. or for any such Derivative Works as a whole. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium. or product names of the Licensor. in the Source form of any Derivative Works that You distribute. or any and all other commercial damages or losses). excluding those notices that do not pertain to any part of the Derivative Works. or otherwise. within the Source form or documentation. Unless You explicitly state otherwise. either express or implied. except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use. work stoppage. computer failure or malfunction. and distribution of the Work otherwise complies with the conditions stated in this License. or distribution of Your modifications. 5. all copyright. incidental.

(?CA?). acceptance of support. or claims asserted against. INCLUDING. indemnity. distribution and modification of the LGPL Software is governed by the GNU Lesser General Public License (?LGPL?) version 2..ca. 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. and charge a fee for.Introscope 8. not by the LGPL license.org/licenses/lgpl-2.3. in accepting such obligations. You cannot use. EITHER EXPRESS OR IMPLIED.0. CA makes the source code for the LGPL Software. To apply the Apache License to your work. copying. 59 Temple Place.0 (the "JAXB Component"). Additionally. Use. or other liability obligations and/or rights consistent with this License. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. not on behalf of any other Contributor. including any modifications.0" This product contains portions of the "Java Architecture for XML Binding" (JAXB) 2.3 (the 'Eclipse Product'). ==== "Java Architecture for XML Binding (JAXB) 2. JasperReports 1.3.ca. The LGPL Software is provided ?AS IS? WITHOUT WARRANTY OR CONDITION OF ANY KIND.com/ips/osgi/ in the archive file in which the LGPL Software is distributed.1. ==== JHotDraw 5.com. defend. with the fields enclosed by brackets '[]' replaced with your own identifying information. Further details of the disclaimer of warranty with respect to the LGPL Software can be found in the LGPL license itself. Accepting Warranty or Additional Liability. Inc. and includes a copy of the source code in the same archive file as the executable code. modify or redistribute any Introscope code except as may be expressly set forth in the EULA.opensource.org/downloads/ or here http://opensrcd. available at http://opensrcd. the ?LGPL Software?) are open source software libraries that are used with the CA Wily Introscope 8. ==== This product contains Eclipse 3. Boston. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work.eclipse.com/ips/osgi/. Suite 330. and only if You agree to indemnify.8 The above-referenced libraries (collectively. Use of the Introscope software is governed solely by the CA end user license agreement (?EULA?). To the full extent permitted under applicable law. attach the following boilerplate notice.3.php or write to the Free Software Foundation.1. The LGPL Software is not owned by CA.0 Release Notes February 2010 page 26 9. However. THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. You may act only on Your own behalf and on Your sole responsibility. warranty.ca. Use of the JAXB Component is governed by the Common Development . such Contributor by reason of your accepting any such warranty or additional liability. Use of the Eclipse Product is governed by the Eclipse Public License 1.1. JFreeCharts 1. The source code for Eclipse Product may be found here http://www. Inc. copy.0. WITHOUT LIMITATION. a copy of the LGPL license can be found at: http://www. A copy of the LGPL license can be found at http://opensrcd.0 software (?Introscope?). and hold each Contributor harmless for any liability incurred by.2. MA 02111-1307 USA. While redistributing the Work or Derivative Works thereof. CA disclaims all warranties and liability arising from or related to any use of the LGPL Software. You may choose to offer.

INCIDENTAL. OR PROFITS.pdfbox. Redistribution and use in source and binary forms. BUT NOT LIMITED TO. BUT NOT LIMITED TO. with or without modification. The BSD License for the JGoodies Looks ====================================== Copyright (c) 2001-2007 JGoodies Karsten Lentzsch. OR CONSEQUENTIAL DAMAGES (INCLUDING.com/ips/01189_1/. Redistribution and use in source and binary forms. Redistributions of source code must retain the above copyright notice. this list of conditions and the following disclaimer. WHETHER IN CONTRACT. 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. OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY.org/NPL/ and is made available for download from http://opensrcd. .ca.dev. SPECIAL. ==== The source code version of Rhino 1.com/ips/2584_6 or here https://jaxb. OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE.net/. www. STRICT LIABILITY. this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. INCLUDING. All rights reserved.com/) and is distributed in accordance with the following license agreement. PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES.org All rights reserved. LOSS OF USE. with or without modification. DATA.0 Release Notes February 2010 page 27 and Distribution License v1.mozilla.jgoodies. INDIRECT.0. ==== Portions of this product include software developed by JGoodies (http://www.ca. o Redistributions in binary form must reproduce the above copyright notice. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES.6 Release 2 is licensed under the Netscape Public License Version 1.1 which can be found at http://www.Introscope 8. this list of conditions and the following disclaimer. are permitted provided that the following conditions are met: o Redistributions of source code must retain the above copyright notice. are permitted provided that the following conditions are met: 1.1. EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. ==== Copyright (c) 2003.2. 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.java. EXEMPLARY. The source code for the JAXB Component may be found here: http://opensrcd.

DAMAGES OR OTHER LIABILITY. this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.bouncycastle. Redistributions in binary form must reproduce the above copyright notice.Introscope 8. this list of conditions and the following disclaimer in the documentation and/or other materials with the distribution.2. Redistributions in binary form must reproduce the above copyright notice. WITHOUT WARRANTY OF ANY KIND. . OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE. THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.1. Copyright (c) 2000 . 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. ==== Portions of this product include software developed by The Legion of the Bouncy Castle. publish. SPECIAL. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES.0 Release Notes February 2010 page 28 2. THE SOFTWARE IS PROVIDED "AS IS". and to permit persons to whom the Software is furnished to do so. OR CONSEQUENTIAL DAMAGES (INCLUDING. PERWAPI Copyright Copyright 1998 . BUT NOT LIMITED TO.2005 Queensland University of Technology (QUT). WHETHER IN AN ACTION OF CONTRACT. distribute. including without limitation the rights to use. with or without modification are permitted provided that the following conditions are met: 1. ARISING FROM.org) Permission is hereby granted. INCIDENTAL. 3. 2. copy. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT. BUT NOT LIMITED TO. The QUT software is distributed in accordance with the following license agreement. DATA. OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY. to deal in the Software without restriction. nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. and/or sell copies of the Software. OR PROFITS. All rights reserved. free of charge. PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES. Neither the name of pdfbox. INCLUDING. modify. STRICT LIABILITY. TORT OR OTHERWISE. INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY.2006 The Legion Of The Bouncy Castle (http://www. EXPRESS OR IMPLIED. EXEMPLARY. EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. INDIRECT. Redistribution of source code must retain the above copyright notice. ==== Portions of this product include software developed by Queensland University of Technology. Redistribution and use in source and binary forms. to any person obtaining a copy of this software and associated documentation files (the "Software"). FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. WHETHER IN CONTRACT. merge. LOSS OF USE. this list of conditions and the following disclaimer. OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM. sublicense. The Bouncy Castle software is distributed in accordance with the following license agreement.

(www. INCLUDING. EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.com). BUT NOT LIMITED TO PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES. with or without modification.1. OR CONSEQUENTIAL DAMAGES (INCLUDING.isomorphic. OR PROFITS. Redistributions in binary form must reproduce the above copyright notice. Redistribution and use in source and binary forms. SPECIAL. All rights reserved. Inc. SPECIAL. . ==== Portions of this product include software developed by the NMock 2 Development Team. BUT NOT LIMITED TO. STRICT LIABILITY. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES. EXEMPLARY. IN NO EVENT SHALL THE GPCP PROJECT OR QUT BE LIABLE FOR ANY DIRECT. OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE. DATA. THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. The NMock software is distributed in accordance with the following license agreement. BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE HEREBY DISCLAIMED. INDIRECT. LOSS OF USE. STRICT LIABILITY. NMock 2 Development Team. ==== Isomorphic SmartClient web presentation layer (c) 2000-2004 Isomorphic Software. PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES. this list of conditions and the following disclaimer. OR PROFITS. of the GPCP project or QUT. EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. All rights reserved. EXEMPLARY. INCLUDING.0 Release Notes February 2010 page 29 THIS SOFTWARE IS PROVIDED BY THE GPCP PROJECT ?AS IS? AND ANY EXPRESS OR IMPLIED WARRANTIES. LOSS OF USE. are permitted provided that the following conditions are met: Redistributions of source code must retain the above copyright notice. INCIDENTAL.Introscope 8. INCIDENTAL. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT. DATA. OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY. Copyright (c) 2005-2006. OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE. INDIRECT. WHETHER IN CONTRACT. ==== Portions of this product include the Guiffy Java API package licensed from Guiffy Software.2. 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. either expressed or implied. WHETHER IN CONTRACT. OR CONSEQUENTIAL DAMAGES (INCLUDING. The views and conclusions contained in the software and documentation are those of the authors and should not be interpreted as representing official policies. OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY. BUT NOT LIMITED TO.

1. WITHOUT WARRANTY OF ANY KIND. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM.Introscope 8. to any person obtaining a copy of this software and associated documentation files (the "Software"). copy. Version 1. INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY.org Permission is hereby granted.org.0 Release Notes ==== February 2010 page 30 Portions of this product include software developed by the TanukiSoftware. WHETHER IN AN ACTION OF CONTRACT. 2003 TanukiSoftware. distribute. merge. ==== CONTAINS IBM(R) 32-bit Runtime Environment for AIX(TM). and/or sell copies of the Software. including without limitation the rights to use.2. and to permit persons to whom the Software is furnished to do so. Java(TM) 2 Technology Edition. to deal in the Software without restriction. TORT OR OTHERWISE. EXPRESS OR IMPLIED. 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. free of charge.5 Modules (c) Copyright IBM Corporation 1999. sub-license . modify. ARISING FROM. The Tanuki software is distributed in accordance with the following license agreement. OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. THE SOFTWARE IS PROVIDED "AS IS". 2002 All Rights Reserved ==== . publish. Copyright (c) 1999. FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. DAMAGES OR OTHER LIABILITY.