wM Integration Server Service Profiler, v1.3

This version is mainly to increase the compliance with v8.2 of the Integration Server. However, a few extra features have also been added.

Check the Version History for information about any corrections or new features introduced by released patches.

webMethods v8.2

The startup of the Integration Server has been changed considerably, affecting the setup of the environment for the Service Profiler and which files need to be edited and also the nature of the changes.

The most impact has been in the way the Integration Server is configured to run as a Windows NT Service. Previous versions of the Service Profiler cannot be used with Integration Servers v8.2 running as Windows NT Service.

Administration Page

• Added a setting that indicates that the Service Profiler should automatically be started upon its package (re)load;
• Added a setting that indicates that a (last) snapshot documents is published upon the Service Profiler's package unload.
  A trigger and a service that processes that published document can be developed to, for instance, save it into a database.

Services

• Added export services to directly download the snapshot as a CSV or XML file, with option to reset counters.
  These services fill the gap of providing the UI functionality without using UI-specific services.
  They are usefull to, for instance, scripted remote retrieval of the snapshot with wget:
  • wia.pub.issprofiler.export:as_csv_download
  • wia.pub.issprofiler.export:as_xml_download

• Stack Trace info being shown as HTML text;

  This might happen with any Integration Server version since v8.0, due to cross-scripting protection added to the %value% tag.

  This problem has been corrected.

• The field ExceptionCount was missing on the snapshot public document;
• In the Admin page, when there was only one Package Exclusion Filter in the list, it could not be removed.

  This is caused by changes introduced by Integration Server v8.2 to the default behavior of the HTTP parameter processing.

  The issue is that, on v8.2, by default, it cannot distinguish between single value parameter and a single item array on requests from DSPs, when the parameter only has one value (i.e., like in a single item array).

  To recover the previous version default behavior, Software AG directs you to set an extended parameter in ISAdmin > Settings > Extended: watt.server.http.listRequestVars=always

  The corrections made to Service Profiler assure the correct behavior independently of Integration Server version or the setting of the before mentioned extend property.

None.

For upgrading from a version prior to v1.2.2, it is recommended to completely uninstall the previous version and install the new version from scratch. The scope of the introduced changes reach the replacement of the WiaUtilities package, the entire set of libraries (both native and Java) and also the script code added to the server.(bat|sh) file.

For upgrading from v1.2.2 to v1.3, a patch is available.

The Service Profiler has been successfully tested using SUN, HP and IBM JVMs v1.3.1, v1.4.x, v1.5.0 and v1.6^*.

When using JREs other than the Integration default one, make sure to make the tools.jar available, usually by putting it into the ext folder. This library is not included with the JRE installations, but is part of the JDK. The Integration Server default JVM includes this library (even though it is not guaranteed that it will always do so) for it's needed for some functionality, such as JSPs.

^*Only with webMethods platform v8.0 or above.

The Service Profiler can run in any of the Operating Systems and CPU architectures supported by the webMethods Integration Server. However, it is not ready available in all of them.

The list of currently ready-available Operating and CPU architectures are as follows^**:

• Windows 2000, XP & 2003 Server (intel 32-bit)
• Windows 2003 Server x64 (AMD 64-bit)
• Linux Redhat (intel 32-bit) (AMD 64-bit)
• Linux Suse (intel 32)
• SUN Solaris 8 (SPARC 32-bit)
• SUN Solaris 9 (SPARC 32-bit & 64-bit)
• SUN Solaris 10 (AMD 64-bit)
• HP-UX B10 & B11 (PA RISC 32-bit & 64-bit) (Itanium 32-bit & 64-bit)
• Mac OS X (intel 32 & 64-bit)
• AIX (ppc 32 & 64-bit)

^**The list of supported Operating Systems may change through the release of new patches.

• When the command-line profiler options are actived Norton Internet Security may prevent the Integration Server from starting;
  Manually adding the java.exe file to the permitted files of the firewall configuration usually overcomes this problem.
  If it does not work, disable Norton Internet Security while the server is starting.
  This situation may also happen with other security/firewall software, even though it has not been tested.
• Globalization;
  The tool is only available in English language.
• Missing menu link;
  The Licensing menu link may happen to not appear at all.
  The reason for this is not yet known, and usually refreshing the page makes it reappear.
• Grayed/disabled links.
  This is not an issue.
  When functionality menu links are disabled, this means that either the installation of the tool is incomplete or some error/setting is preventing the tool core libraries from loading.
  Check logs and if it is a problem, please call for support.
• Files downloaded with Save As... option of the browser are truncated/corrupted.
  This has been withnessed with Mozilla v1.7.12.
  Neither IExplorer or Firefox v1.5.x have reproduced this behaviour.
  This problem has been noted when copying the PDF documents in the info page or the (link) files generated on the Export To File functionality.
  Alternative workaround is to open the file by clicking its link and:
  • PDF;
    Use the Save Copy toolbar button of the plug-in.
  • CSV or XML.
    Use the This Frame / View Frame Source context menu and save it to a file.
• Pagination of the tree of service nodes limits find feature;
  If the number of nodes in a Snapshot triggers the tree pagination in the dashboard, the find a node in the tree is limited to the current page.
  On the special case of the navigation link from the View Per Service to the Browse Snapshot, the navigation & find is always (and only) made onto the first page. However, jumping to the next/previous page and repeat the find is always possible, but hits on the entire snapshot are not seen all at once.
• In the snapshot identification the host port may appear as -1 or missing.
  This will not happen if using the Service Profiler manually; i.e., start the profiling when the Integration Server has already completed its startup sequence, and the Service Profiler is also already loaded.
  The -1 value will happen if the port is inquired to the Integration Server during a package startup sequence.
  During the Integration Server startup sequence, its listening port number is also undetermined. Depending how it is inquired, it may result in -1 or nothing at all.