wM Integration Server Service Profiler, v1.5

This version is required for compliance with Integration Server v9.9 and above. However, a few extra features have also been added, along with some corrections.

Check the Version History for information on the evolution of the new features and the corrections.

This version of the Service Profiler is still compatible with Integration Servers v6.x, v7.x, v8x and other v9.x prior to v9.9.

webMethods v9.6 and above

The file structure and 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. Nevertheless, we have managed to normalize the instructions for all Integration Server v9.x.

The v9.10 of the platform completely changes the visual style of the Integration Server pages, a visual that we choose not to follow.

However, for Integration Server v9.6 and above, the installation changed especially to normalize it and dynamically cope with the installation of FIXes:

• The updated profiles configuration file is now the custom_wrapper.conf and not the wrapper.conf;
• The Service Profiler configuration are now checked and recalculated every time the server starts up instead of just on first installed.

Changes to Installation Instructions

Since v1.4, the installation instructions are no longer in a plain text file and are neither detailed in the User Guide.

The detailed installation instructions are available as a dynamic webpage accessible from the download page at the website.

You choose your environment configuration, apply it, and the instructions text changes accordingly.

View Per Service Analysis

Added red and amber alerts to the View Per Service dashboard based on errors percentage thresholds.

These thresholds have default values that can be customized via documented properties.

Package Coverage Analysis

The analysis can now be done againts the server's Service Usage Statistics instead of just against the usage statisctics of the snapshot.

Additionally, a summary page of the server's Server Usage Statistics in tabular form, sortable by any column, has been added.

View Per User Analysis

Basic information about users has been added to the snapshots and a new View Per User dashboard has been created.

All dashboards

Package Exclusion Patterns can be completely suppressed without having to persist changes to them in the administration page, with the new Ignore ALL Package Exclusion Patterns option, added to all the dashboards.

The new user information is present in all dashboards.

JSON

Snapshots can now be exported in JSON format.

Administration

Reset counters, from the GUI, without stopping the profiler.

Top frame auto-refresh is configurable via a property.

• Correction to thread-info XML tag in the snapshot:
  • The tag was not being terminated;
  • The value of the lock-owner-name was not being encoded and sometimes generated an error when rendering.
• The Maximum Thread Count would not reset when counters were reset;
• On Integration Servers v9.6 and above, the setting for preventing the tool from loading was not working;
• Version 1.5.6 of Service Profiler is an interim version that includes patches #1 to #6, for v1.5.

  These patches correct issues found since the publication of v1.5.

  Check the Version History for details on those corrections.

No further specific effort to support IE with version less than 11, especially IE8 and previous. The repercussions may happen when rendering new or advanced visual options in the same way that most recent browser natively support and make it easier.

For upgrading from a version prior to v1.3, it is recommended to completely uninstall the previous version and install the new version from scratch.

For upgrading from v1.4:

• Install the new version of the packages;
• Hard-restart the Integration Server (shutdown followed by startup);
• Additionally, you may:
  • Recheck the installation instructions online to confirm that your installation is correct;
  • Remove the changes to the profile wrapper.conf and delete file wrapper.conf.beforeissprof. These are just redundant.

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

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.

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

^*** Only with webMethods platform v9.7 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)
• Windows 8 x64
• 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 witnessed 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.