PM71804: PORTLET METRICS NOT BEING DISPLAYED IN TIVOLI PERFORMANCE VIEWER AFTER SERVER RESTART

Fixes are available

APAR status

Closed as program error.

Error description

Performance Monitoring Infrastructure (PMI) metrics for Portlet
are still disabled after being set and then restarting
WebSphere Portal. The following steps were taken to enable the
PMI metrics for the Portlet from the Application Server
administrative console

1. Enabled PMI with "custom" option for WebSphere_Portal, and
enabled all portlet metrics in this page:
Performance Monitoring Infrastructure (PMI) > WebSphere_Portal
> Custom monitoring level,
then in Configuration tab under "Portlet Application" module

2. Restarted WebSphere_Portal, nodeagent and dmgr

3. In this page:
Performance Monitoring Infrastructure (PMI) > WebSphere_Portal
> Custom monitoring level,
in Runtime tab under "Web Applications" module, portlet metrics
are still disabled

4. In Tivoli Performance Viewer > WebSphere_Portal, I selected
one portlet under Performance Modules/Web Applications, portlet
metrics are not displaying.

Local fix

Edit the file (backup before!):
wp_profile/config/cells/<cell-name>/nodes/<node-name>/servers/<
server-
name>/pmi-config.xml
Note: this must be done for all servers in the profile.
Find the following line:
<pmimodules ... moduleName="portletAppModule" ...>
The attribute type contains a comma separated list of PMI
modules for the Portlet-Container:
type="com.ibm.ws.portletcontainer.pmi.xml.portletAppModule,com.i
bm.ws.portletcontainer.pmi.xml.portletModule"
Append this list to the
<pmimodules ... moduleName="webAppModule" ...> XML elements
type  attribute. Make sure the commas are set properly.
Delete the <pmimodules moduleName="portletAppModule"> XML
element completly.
Start the server.
In the admin consoles PMI Configuration tab the Portlet related
Statistics are now shown beneath the Web Application bullet.
Now the
enablement of Portlet statistics in the Configuration tab
should have an
effect to the Runtime tab after a restart.

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server                                      *
****************************************************************
* PROBLEM DESCRIPTION: PMI metrics for Portlets don't show     *
*                      up in user interface after activation   *
*                      in WebSphere Application Server         *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The Portlet PMI module is not set to be part of the web
application PMI module. Therefore the Portlet PMI node
does not get activated.

Problem conclusion

The pmi-config-appserver.xml template that is applied
whenever a new profile is being created has been edited.
The stand-alone portletAppModule was removed, and the
webAppModule extended to also contain the portletModule and
the portletAppModule.

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.27, 8.0.0.6 and 8.5.0.1.  Please refer to the
Recommended Updates page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

In a given profile, modify the pmi-config.xml file and restart
server.

1. Current configuration in the pmi-config.xml for the portlet
modules.
  In pmi-config.xml file, both webAppModule & portletAppModule
are defined separately.

-<webAppModule>
-<portletAppModule>

2. Modification to the pmi-config.xml.

Before Modification :

<pmimodules xmi:id="PMIModule_121" moduleName="webAppModule"
type="com.ibm.ws.wswebcontainer.stats.webAppModuleStats,
com.ibm.ws.wswebcontainer.stats.servletStats,
com.ibm.ws.wswebcontainer.stats.urlStats" enable=""/>

<pmimodules xmi:id="PMIModule_122"
moduleName="portletAppModule"
type="com.ibm.ws.portletcontainer.pmi.xml.portletModule,
com.ibm.ws.portletcontainer.pmi.xml.portletAppModule"
enable=""/>

Remove portletAppModule which is defined as a separate module
and integrate that into "WebAppModule" statsGroup as shown
below.

After Modification :

<pmimodules xmi:id="PMIModule_121" moduleName="webAppModule"
type="com.ibm.ws.wswebcontainer.stats.webAppModuleStats,
com.ibm.ws.wswebcontainer.stats.servletStats,
com.ibm.ws.wswebcontainer.stats.urlStats,
com.ibm.ws.portletcontainer.pmi.xml.portletModule,
com.ibm.ws.portletcontainer.pmi.xml.portletAppModule"
enable=""/>

Here you can see type has portletAppModule and portletModule
and these metrics will appear in WebAppModule and allow you to
enable and disable at configuration level. These changes will
be reflected at runtime Level after server restart.

Comments

APAR Information

APAR number
PM71804
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-08-29
Closed date
2012-09-14
Last modified date
2012-09-26

APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name
WEBSPHERE APP S
Fixed component ID
5724J0800

Applicable component levels

R700 PSY
UP
R800 PSY
UP
R850 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 October 2021

Tips

PM71804: PORTLET METRICS NOT BEING DISPLAYED IN TIVOLI PERFORMANCE VIEWER AFTER SERVER RESTART

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R700 PSY

R800 PSY

R850 PSY

Document Information

Share your feedback

Need support?