wM Integration Server Service Profiler

Version History

v1.5.8

This version adds to the previous version some enhancements and corrections:

v1.5.7

This version adds the previous version a feature that enhances the application of Patch #6 and makes v1.5.7 more suitable to be applied when upgrading Service Profiler from previous versions:

v1.5.6

Versions 1.5.1 to 1.5.5 were not officially published.

These versions were associated with patches, #1 to #6, which added features and/or corrected issues found in v1.5. Patches #1 to #3 were suppressed and are included in patch#4, but #5 and #6 are isolated.

This version (1.5.6) includes all patches published previously published for Service Profiler v1.5.

New Features:

Bug Corrections:

v1.5

This version updates the installation procedure and instructions for support webMethods v9.9 and v9.10.

For webMethods v9.10, the new retyling of the platform pages is not followed and a reworked version based on the previous one is used. This breaks the usual alignment with the platform's style and opens the possibility of having the presentation layer completelly reworked in the next version of the tool.

Requirements:

New Features:

Bug Corrections:

Other Corrections:

v1.4

This version updates the installation instructions for webMethods v8.2 and webMethods v9.x, including v9.71 and Java 82.

1 Introduced with build 9211.

2 Introduced with build 9348.

Requirements:

Bug Corrections:

New Features:

v1.3.4

This version is created by installation of Patch #4.

This patch updates the installation instructions for webMethods v8.2, and especially when running the Integration Server as a Windows NT Service.

Requirements:

Bug Corrections:

New Features:

v1.3.3

This version is created by installation of Patch #3.

This patch updates the installation instructions for webMethods v8.2, and especially when running the Integration Server as a Windows NT Service.

Bug Corrections:

v1.3.2

This version is created by installation of Patch #2.

This patch updates the online help to include features introduced with v1.3 of the tool.

Additionally, adds a new feature that targets the situation where the Integration Server is known in the network by multiple names, or even when it is connected to multiple sub-networks. In this environment, it is very possible that the server name reported by the IS (and that is placed at the header of the Service Profiler exported snasphots) is not the same as the one it is publicly known. This patch allows you to override the server name to whatever you like... it can even be a logical name with nothing to do with network names.

New Features:

v1.3.1

This version is created by installation of Patch #1.

Bug Corrections:

v1.3

Correct setup incompatibilities with the Integration Server v8.2. These incompatibilities affect mainly the tool's installation steps.

Bug Corrections:

New Features:

v1.2.2

This version includes all patches to v1.2.1 and updates the company logo.

v1.2.1

Upgrading to this version may be accomplished by applying patch #2 on v1.2.

Bug Corrections:

New Features:

The are no new features, other than replacing all previous patches of v1.2.

patch 1

This patch adds the Solaris native libraries for the AMD64 CPU architecture.

v1.2

Upgrading to this version may be accomplished by applying patch #4 on v1.1.

Bug Corrections:

New Features:

patch 1

This patch replaces the HP-UX native libraries to work with Java 6.

Any Service Profiler 1.2 installation can have this patch applied, but it is only required for HP-UX using Java 6, (e.g., webMethods 8.x).

patch 2

Patch #2 includes all previous patches for v1.2, and upgrades the tool to v1.2.1.

Additionally, this patch updates the implementation for use on AIX with PPC and PPC-64 CPU architectures.

v1.1

Upgrading to this version requires the complete uninstall of any previous version.

New Features:

Bug Corrections:

patch 2

Patch #2 includes patch #1.

Bug Corrections:

  • With Firefox 3.0.x (mainly, but not in exclusive), when using the browsing the tree of services, expanding the tree could make the graphical hints appear dissociated from the corresponding service icons;
  • Corrected the sorting by percentage in the Code Coverage dashboard when packages without services are being listed;
  • In the Browse Running Services dashboard, when showing thread info, the link to the blocking service thread was not working.

New Features:

  • Added native libraries for support of the Service Profiler on AIX (ppc 32 & 64-bit);
    Experimental. Any feedback is welcome.
  • Added new public services to start & stop the profiler.
    • wia.pub.issprofiler.admin:startProfiler
    • wia.pub.issprofiler.admin:stopProfiler

    These avoid some potential issues with frozen snapshots and also having to use the UI services.
  • Added the count of services of each package in the Code Coverage dashboard;
  • Show the calling service name on service details when browsing the service call tree.
    It is only shown for False Roots.

patch 3

Must have package WiaServiceProfiler v1.1, with patch #2, already installed.

New Features:

  • This patch just introduces a new thread-blocked icon for the Browse Running Services dashboard;
    Before, any blocked thread would be shown with the same identifying icon: a gear being blocked by a glowing red ball.
    However, the thread info gathering process may also (momentarily) block a thread. This may generate many threads in that situation, being mixed with all other blocked cases, forcing a one-by-one checking.
    This patch changes the icon of threads blocked by the thread info gathering process to show a glowing green ball, instead of a red one. This way all blocked threads are still visually identified but the ones with the red glowing ball are the ones of interest.

patch 4

Patch #4 includes all previous patches for v1.1, and upgrades the tool to v1.2.

v1.0.3

Integrate all patches of v1.0.2.

patch 1

Bug Corrections:

  • The Calling Service name was not included as part of the CSV exported file.

v1.0.2

Integrate all patches of v1.0.1.

Added support for HP-UX Itanium, 32-bit and 64-bit.

patch 3

This patch includes, replaces and deprecates all previous patches for v1.0.2.

New supported platforms:

  • Linux RedHat 64-bit (AMD64);
  • Windows 2003 Server x64 (AMD64);
  • Mac OS X (32 & 64-bit) (intel).
  • AIX (32 & 64-bit) (ppc).

Bug Corrections:

  • The starting of the Service Profiler in an Integration Server, in Windows systems, that has been installed in a path that contains spaces (e.g., C:\Program Files\webMethods) raises an error.
  • In a singular situation, the server name was reported in the snapshot identification data with port -1.
    This is a network system problem, but this patch implements an workaround that allows the name of the server to be set with the correct port number.
  • Java error message "JVMPI not supported with this garbage collector; please refer to the GC/JVMPI documentation";
    This problem is resolved, with exception of the following supported platforms:
    • HP-UX (PA & itanium);
    • Solaris.

patch 4

This patch depends on patch 3.

New supported platforms:

  • Solaris 9 64-bit (SPARC);

Bug Corrections:

  • Java error message "JVMPI not supported with this garbage collector; please refer to the GC/JVMPI documentation";
    This problem is resolved, with exception of the following supported platforms:
    • HP-UX (PA & itanium);

    Workaround:
    Alter the Integration Server start script to add one of the following Java options to the JVM command line:
    • -client
    • -XX:-JVMPICheckGCCompatibility
  • Java error "java.lang.NoSuchMethodError: com.wrightia.wm.is.profiler.intercept.IssprofClassLoaderTransformationHelper.beforeDefineClassCall (Ljava/lang/ClassLoader;Ljava/lang/String;Ljava/nio/ByteBuffer;IILjava/security/ProtectionDomain;)[B" when loading the some of webMethods packages (e.g.; WmFlatFile).
    The packages are left loaded as 'partial' and every attempt to use its services will issue the error message above.

v1.0.1

Auto-pagination of the Browse Snapshot and Browse Running Services dashboards.

This feature was added in response to a timeout or long-running script warning message from the browsers when the navigation tree contained a large number of nodes. A large number would vary from browser-to-browser and from environment-to-environment, but would normally be a number above 1000 nodes. In some enviroments, it would only manifest itself above 3000 nodes.
The implemented improvement simplifies the script generation (speeding generation and page load) and automatically creates pagination control on a threshold of 1000 nodes-per-page. This value is the default, and can be overriden through a configuration setting.
Check the Troubleshooting section of the User Guide manual for detailed information.

v1.0

First delivered version.