Are you concerned about the growth in RTC repository size ? Do you want to track the change in the component size in RTC ? Curious to know about the files that are eating up your repository space.
Well, here is a small, but, good dose of info for you.
You might have come across monitoring the CLM instance using MBeans or you may already have implemented it. There has been a lot of work going on in this space and starting from CLM 6.0.5, we have the capability to get the details on the size of the components and the chief memory occupiers in the RTC repository.
So, go on.. follow the below steps and to find out more...
1. Enable the MBean
From ccm/admin > Advanced Properties you can enable the MBeans under "com.ibm.team.scm.service.internal.content.metrics.VersionedContentMetricsTask"
Set the below to "true":
Enable Top File Sizes MBean
Enable Versioned Content Component Metrics MBean
Enable Versioned Content Repository Metrics MBean
Note: For details, hover over the property.
The default "Delay Between Invocation" is 604800s (7 days). If you are curious to get the details earlier, you can edit the value to say 900s(15 mins) and restart the CLM instance(required). After the set interval, you can see the MBean appear in the MxBeans list.
Caution: We recommend changing the intervals to default value after reviewing.
2. Getting the details
To get to the MBean related to the component, visit https://<CLMhost>/ccm/repodebug/mxBeans and select com.ibm.team.scm.content, based on the details required, select one of the type:
ComponentContent metrics – provides the size of the component and the number of files
topContent – provides the information on the top 8 files in terms of size in the entire CCM repository.
Clicking on the any MxBean Object, you can get the details(like the size of the component, name, size in database etc)
the top 8 files occupying maximum space in the repository.