Part No. ES12000413
`
`Release Notes
`eSleuth Early Adoption 1.0.0
`
`These Release Notes provide the following information about the eSleuth 1.0.0 software:
`• Overview
`• Documentation
`•
`Support
`•
`Installation requirements
`• Known problems and caveats in eSleuth
`
`Overview
`Welcome to eSleuth, the eBusiness transaction analysis software that ensures your eBusiness information gets to the right place, at
`the right time, with the right content. eSleuth traces MQSeries API calls across eBusiness systems and graphically displays the
`flow of messages between applications and queues. eSleuth enables you to pinpoint information flow failures anywhere in your
`environment and drill down into the application-specific data you need to solve them.
`
`eSleuth consists of a central Analyzer running on Windows NT and eSensors installed on each host in your eBusiness
`environment. The eSleuth product also includes the eSleuth Communication Link Editor, a tool for defining the MQSeries queue
`managers and queues to be used for communication between the eSleuth Analyzer and eSensors.
`
`Documentation
`eSleuth documentation is provided in electronic format on the eSleuth CD-ROM. The eSleuth Administrator’s Guide
`(eSleuthUserGuide100.pdf) provides instructions for installing eSleuth components and using the eSleuth Communication Link
`Editor. The eSleuth Administrator’s Guide (eSleuthAdminGuide100.pdf) provides instructions on configuring the eSleuth
`eSensors to collect events, using the eSleuth Analyzer to view event information, and troubleshooting any eSleuth problems. The
`Adobe Acrobat Reader is required to view these files.
`
`Support
`Contact customer support in any of the following ways:
`•
`Call 203 798 1007 or +1 203 798 1007 from outside the U.S.
`•
`Send email to support@bristol.com
`• Visit http://www.bristol.com/support
`
`Installation Requirements
`
`eSleuth eSensor
`The following table shows the platforms supported by eSensors along with the required operating system and MQSeries versions:
`
`Platform
`Microsoft Windows NT
`Sun Solaris
`Hewlett-Packard HP-UX
`IBM AIX
`IBM OS/390 CICS
`
`Operating Environment
`Windows NT 4.0 SP5
`Solaris 2.5.1, 2.6, and 7
`HP-UX 10.20, 11.00
`AIX 4.2, 4.3
`OS/390 V2R5 or higher
`CICS TS 1.2 or higher
`
`MQSeries
`5.0/5.1*
`5.0/5.1
`5.0/5.1
`5.0/5.1
`2.1
`
`eSleuth Release Notes
`
`1
`
`HP_1013_0001
`
`

`

`Part No. ES12000413
`* The MQSeries 5.1 for Windows NT CSD01 (DTF U200109) is recommended to prevent unexpected behavior starting or
`stopping event collection from applications connecting to an MQSeries 5.1 queue manager on Windows NT. The CSD can be
`found at ftp://ftp.software.ibm.com/software/mqseries/fixes/winnt51/U200109. More details about this CSD can be found at
`http://www4.ibm.com/software/ts/mqseries/support/apars/u200109.html.
`
`eSleuth Analyzer and Communication Link Editor
`The eSleuth Analyzer and Communication Link Editor both require Microsoft Windows NT 4.0 SP5 and MQSeries Client 5.0/5.1.
`You can use the eSleuth Analyzer to view existing projects without the MQSeries Client, but you cannot record events without it.
`
`Known Problems and Caveats
`The following are known problems or issues you should be aware of in this release:
`
`MQSeries Clustering Support
`When using eSleuth in an MQSeries Clustering environment, eSleuth does not currently associate the given queue name to the
`resolved cluster queue in the eSleuth Analyzer Component Layout view.
`
`MQSeries Integrator Support
`eSleuth supports MQSeries Integrator version 1.0.
`
`Potential Time Skew Problem
`If you have an MQSeries application that uses the MQSeries client library and runs on one host machine while the queue manager
`that it connect to as a client runs on a different host machine, you may experience data collection problems if there is a significant
`clock skew between the host running the application and the queue manager host. The time skew between the hosts may cause the
`eSensor on the application host to identify valid, current configuration messages from the Analyzer as expired. Because the
`eSensor ignores expired configuration messages, it does not collect any events in response to it.
`
`Analyzer Installation Error
`If you install the eSleuth Analyzer on a computer with Internet Explorer 2.0 installed, the following warning occurs during
`installation: “Failed to register scrobj.dll.” You can safely ignore this warning. The eSleuth Analyzer, including presentation filter
`scripts created by the Analyzer, works correctly. However, any VBScript objects present in scrobj.dll will not work in presentation
`filter scripts that you have edited on the Scripting page of the Presentation Filter dialog box.
`
`DCE MQSeries Libraries Not Supported
`eSleuth does not support the DCE version of MQSeries on HP-UX 11 or Solaris.
`
`Deleting Presentation Filters
`If views have been opened and closed with a presentation filter, you may not be able to delete that presentation filter. Close the
`project, re-open it, and then delete the presentation filter.
`
`Triggered Programs on UNIX
`eSleuth does not support triggered programs on UNIX. Triggered programs do not load the eSensor libraries. Triggered programs
`are supported on Widows NT and OS/390 CICS.
`
`Loading Shared Libraries on AIX
`In order to pick up a new library that has the same name as an existing library on AIX, you must run /usr/sbin/slibclean to clear the
`original shared library from memory.
`
`Viewing Perl Program Names
`To display Perl program names (which eSleuth sees as an argument to the Perl command) set the ESLEUTH_REPORT_ARGS
`environment variable to any value. To disable this behavior, unset ESLEUTH_REPORT_ARGS. This environment variable is
`supported on all platforms except OS/390. On Windows NT, it must be set to a value other than an empty string.
`
`eSleuth Release Notes
`
`2
`
`HP_1013_0002
`
`