IBM Sterling Control Center Monitor Web Console performance problems

The IBM® Sterling Control Center Monitor Web console performance is highly dependent on the performance of the database server. When queries initiated by the web console run slowly, the time to show data in the web console will be long.

By default, the IBM Sterling Control Center Monitor Web console typically displays a years’ worth of information when displaying data about monitored servers, including alert, completed process, and completed file transfer counts. The queries used to ascertain this information may be too onerous for the IBM Sterling Control Center Monitor database server, which will result in long delays in displaying the results.

Sometimes these performance problems may be addressed by doing index maintenance and/or retaining less data in the IBM Sterling Control Center Monitor database tables.

Tip: An engine property named DEFAULT_DAYS_OF_HISTORY, whose default is 366, may be used to limit the date range used by the queries to less (or potentially more) than a years’ worth of information, which can result in far better performance.

To see the queries initiated by the Web console, and the amount of time it takes to run them, look at the contents of the IBM Sterling Control Center Monitor web server log files. They are available at:

 <CC Install folder>/web/ccbase/logs
Look at the appropriate jettydefault.log or scc10xwebapp_default log files. If you do not see queries, and the times it takes to perform them, in either of these files, update the file jvm.options, which is found in the defaultServer folder, such that the values are TRUE for both:
  • 10x.logDebugMessagesToStandardOut
  • 10x.printStackTracesToStandardErr

You may also need to update the log4j2.xml file <CC Install folder>/web/wlp/usr/servers/defaultServer/log4j2.xml with the following changes.

Replace the following excerpt:
<!--         <Root level="DEBUG" includeLocation="false" additivity="false"> -->
<!--             <AppenderRef ref="textFile" /> -->
<!--             <AppenderRef ref="Console" level="DEBUG"/> -->
<!--         </Root> -->
	
        <Root level="INFO" includeLocation="false" additivity="false">
            <AppenderRef ref="textFile" />
            <AppenderRef ref="Console" level="ERROR"/>
        </Root>
	</Loggers>
</Configuration>
with:
<!--         <Root level="DEBUG" includeLocation="false" additivity="false"> -->
<!--             <AppenderRef ref="textFile" /> -->
<!--             <AppenderRef ref="Console" level="DEBUG"/> -->
<!--         </Root> -->
	
        <Root level="DEBUG" includeLocation="false" additivity="false">
            <AppenderRef ref="textFile" />
            <AppenderRef ref="Console" level="DEBUG"/>
        </Root>
	</Loggers>
</Configuration>

After a few moments, look at new output that is logged. Restarting the IBM Sterling Control Center Monitorweb server should not be necessary for these changes to take effect.

Tip: When you enable logging of debug messages it is best if you limit web console usage to a single user to prevent so much output being logged that you cannot find what you are looking for.

Also, know time stamp values logged may be in UTC, or local time, or a combination of the two.