Trading Networks 10.3 | Administering and Monitoring B2B Transactions | Using Terracotta with webMethods Products | System Caches Used by the webMethods Product Suite | Software AG Command Central
 
Software AG Command Central
 
com.softwareag.plm.cce.cache.alert
com.softwareag.plm.cce.cache.attributes
com.softwareag.plm.cce.cache.basicmonitoringstatecached
com.softwareag.plm.cce.cache.configurationDataInfo
com.softwareag.plm.cce.cache.configurationInstanceInfo
com.softwareag.plm.cce.cache.configurationTypeInfo
com.softwareag.plm.cce.cache.environment
com.softwareag.plm.cce.cache.fixInfo
com.softwareag.plm.cce.cache.licenseKeyContainer
com.softwareag.plm.cce.cache.licenseMeteringReport
com.softwareag.plm.cce.cache.licenseMeteringAggregateReport
com.softwareag.plm.cce.cache.licenseMeteringConfigurationAggregationStatus
com.softwareag.plm.cce.cache.licenseMeteringRequiredStatus
com.softwareag.plm.cce.cache.manifest
com.softwareag.plm.cce.cache.node
com.softwareag.plm.cce.cache.platformInfo
com.softwareag.plm.cce.cache.productInfo
com.softwareag.plm.cce.cache.repositories
com.softwareag.plm.cce.cache.runtimeComponentInfo
com.softwareag.plm.cce.cache.runtimeMetadata
The size of most Command Central cache elements can be measured in tens of bytes. The size of most caches depends on these factors:
*Number of managed nodes in the landscape. This number can vary from a few nodes to up to hundreds or even thousands for very large installations.
*Number of managed components on each node. This number typically varies from a few managed components to tens of managed components.
*Number of configuration instances for each component and node. Although there are typically only tens of configuration instances for each node, there can be hundreds of configuration instances for larger installations.
It is expected that all data resides in memory. If the caches are not large enough, severe performance degradation can occur.