You have successfully installed and configured your ITCAM for WAS Agent and Data Collector to monitor a WAS server.
You can see the corresponding subnodes in TEP; however you notice missing data on TEP for some of the ITCAM WAS (YN) Agent workspaces.
It is typical that some workspaces are populated with data and some others are not, which might be normal depending on the following common reasons:
- some PMI counters need being enabled on the WAS side
- there is no or not enough ongoing traffic on WAS generating requests
- monitoring level or request collection sampling rate are not enough
- historical collections for some YN attribute groups are not started
- situations for application monitoring are not started
So the cause might be different depending on the particular workspace.
On a general basis, you can keep the following technotes as a reference for both resource-type and request-type data collected by ITCAM and eventually displayed on TEP:
For Resource (PMI) data to be displayed in TEP, the feature must be present and exercised and the PMI collection level has to be at the right level for the data to be generated.
Each TEMA Attribute corresponds to a Websphere PMI Attribute. To have an Attribute value displayed in TEP you must ensure that the corresponding PMI counter is enabled. If you disable the PMI counter, you won't have that attribute displayed on TEP. PMI counters mapped to TEMA attributes have similar names in most cases.
From Websphere PMI attribute mapping, see:
If Request Analysis workspace is blank, that could depend on the fact that there are not enough ongoing requests on your WAS.
You might either need to increase the traffic or the Request Sampling Rate, as explained in above technotes.
For the Garbage Collection Analysis workspace, you have to make sure that the corresponding historical collections have been started, as per following technote:
For Application Health workspace, you need to make sure that the provided out of the box situations to discover applications are running and the application monitoring is enabled.
Check in the Application Configuration workspace (found by right clicking on the Application Health navigator icon and selecting Application Registry) to see if the status of the application is set to "Enabled".
You can try to associate the WasAppDiscovered situation with the Application Health navigator item, e.g. this way:
(1) Right click on Application Health navigator item in the TEP
(2) Select 'Situations' and then select 'WebSphere App Server'
(3) Click on the icon to set Situation filter criteria (4 downward pointing arrows icon)
(4) Tick the box 'Eligible for association' and select OK
(5) Right click on WasAppDiscovered and select 'Associate'
(6) Ok the situations box and close
You should be able to see all discovered applications at once in the Application Health Summary view at this point.
Alternatively you can run the Take Action Set_Application_Monitoring on specific applications this way:
- Access the TEP, select the Navigator item "Application Health". Right click on this navigator item and select workspaces and then the workspace "Application Registry".
- Right click on the applications that are presented and have a status of disabled or discovered in the view then select "take action".
- Select the take action "Set_Application_Monitoring". All of the values for the take action will be filled in automatically. Change the value
Mon_Status from 0 to 1 to enable Application monitoring.