When any UBE is submitted for the first time, the MetaData Kernel will manage the XML-to-platform dependent metadata objects for runtime consumption. This kernel loads a JVM via JNI and TAM cache files will be created and stored in the
\\spec\runtimeCache folders. These persistent cache files will be created for each report when the report is run for the first time and subsequent runs will utilize this cache. This will improves the performance of small and frequently run reports.
The folder \\spec\runtimeCache is used to store the persistent TAM cache files for UBE specs e.g. GBRLINK, GBRSPEC, RDASPEC and RDATEXT. The folder \\spec\UBEOverride is used to store version override specifications e.g. Data Selection, Data Sequencing overrides.
The runtimeCache folder is organized by Report and Version in the following file structure:
UBE Persistent cache per report:
\\spec\runtimeCache\R0006P\
GBRLNK
GBRSPEC
RDASPEC
RDATEXT
UBE Persistent cache per report per version:
\\spec\runtimeCache\R0006P\XJDE0001\
GBRLNK
GBRSPEC
RDASPEC
RDATEXT
\\spec\runtimeCache\R0006P\XJDE0002
GBRLNK
GBRSPEC
RDASPEC
RDATEXT*
Note that all TAM files in //spec or in its subdirectories are cache files that can be safely deleted at anytime and the system will automatically recreate those files.
The system will update the runtimeCache and/or UBEOverride spec files in the following ways:
1. Package Deployment will remove the persistent UBE cache. A full package deployment will remove the entire "runtimeCache" folder. An update package will remove caches of those UBEs included in the update package.
2. Upon submission of Specs Only job (i.e. when submit version specifications only is done), system will replace the persistent cache for the UBE version referenced by the Spec-Install Only.
Source: Knowledge Garden ID 656362.1
