IBM WebSphere Portal Server - Change History

TKU November 2010

In TKU November 2010 an optimization was added to the pattern so that if on a UNIX/Linux host being discovered, the pattern was triggered by an IBM WebSphere Application Server process that was spawned by another WebSphere Application Server process (one parent process spawning many child processes), the pattern realizes this and stops in order to prevent the same code being executed for each child process.

TKU February 2011

In TKU February 2011 the pattern was updated to support product v7.0. Key now includes related WAS server_name as well, profile_name was changed to profile_dir as it is more likely to be extracted. Added three additional attributes: server_name , port and profile_dir .

TKU July 2013

In TKU July 2013 pattern trigger is updated with additional arguments to enable identification of the product in cases where the process command and arguments are truncated (on certain UNIX/Linux platforms) due to their length being over 4096 bytes.

TKU September 2013

In TKU September 2013 the pattern was enhanced with an alternative approach to obtaining server name, Cell name and Node name to cater for situations where trigger process arguments are truncated (QM001800837). This approach relies on the customer having set the custom property "com.ibm.websphere.management.launcher.options=displayServerInFront" at the Cell scope.

TKU August 2014

In TKU August 2014, the pattern was updated to model additional attributes for the Software Instance:

• short_name (TKU-2353)
• listening_ports (TKU-2355)

TKU April 2019

In TKU April 2019 the following changes were made:

• Patter runCommands updated.