Yes SBM maintains a counter in the database and on the cache refresh interval (configured in the System Administrator) each of the web servers checks with the DB to see if it needs to refresh .
This is a safe place where configuration changes and/or upgrades can be tested without affecting the production user base. When you start a new testing cycle, you may want to " refresh " the staging environment with a newer copy of the production data. This document is designed to guide you through a refresh.
If you change the OE database connection information in SBM Configurator to point to a new database DB (or replace an existing OE database , ie during a database refresh ), orchestrations from the prior database will be redeployed when SBM Tomcat starts.
If you have customized any of the SBM templates you have to open System Administrator and use the "Put Files to to Database" option. Those changes don't take affect until you restart IIS. However, you can use the url below to force the cache to refresh without restarting IIS.
1. DCS 2.0a addressed this issue for DCS 2.0. 2. Turn off refresh timer in the DCSSYS.INI (PTKSYS.INI) file. Set 'refresh_time=0' under the [Notify] section of the file.
1. Login to a database that has the scorecard defined along with the sub views that control the data in the chart. The easiest thing to do is login to the support instance called "Serena Support MOD92"
Later, they add a second database for production run-time data. As time goes by, you may want to " refresh " the QA run-time data with the production run-time data. To do this, the Application Repository must first be separated into its own database.
