For release 11.500 and later: VW PM looks at the dbspaces listed in the $METRO_HOME/MetroUI/config/local.json or default.json file for the ds.databases.scout.dbspaces entries "eoam5m", "eoam1h", "eoam1d" to determine which dbspaces are available to build the PM switch tables in. If block is in both json files, local.json takes precedence over default.json. Example of block: "ds": { "enabled": true, "port": 8083, "databases": { "scout": { "url": "jdbc:informix-sqli://localhost:9005/scout:INFORMIXSERVER=metrotcp;IFX_ISOLATION_LEVEL=1;IFX_LOCK_MODE_WAIT=120", "user": "smartsys", "password": "1ad29158d110dd0e7056f90f43cacfc2", "dbspaces": { "video5m": [ "vscout5m" ], "video1h": [ "vscout1h" ], "video1d": [ "vscout1d" ], "eoam5m": [ "scout5m", "scout5ma" ], "eoam1h": [ "scout1h", "scout1ha" ], "eoam1d": [ "scout1d", "scout1da" ] }, VW PM will choose the dbspace with the fewest number of tables currently built. So in example above for building the 5m table, if scout5m currently has 5 switch tables built and scout5ma has 4 switch tables built, the next switch to get built will be put in dbspace scout5ma. To change which dbspaces are available for the UI to build new switches, the json file would be modified and then MetroUI must be restarted. For releases prior to 11.500: STCLive PM looks at the dbspaces listed in /spirent/metro/escout/scripts/dbspaceProperties.txt file and then counts the number of switch tables in each of the dbspaces listed. STCLive PM picks the db space which has the least number of switch tables and then builds the new table there.
DBSPACE_MAIN=dbs03
DBSPACE_ALARM=dbs04
DBSPACE_EVENT=dbs05
DBSPACE_VIDEO5MIN=dbs10,dbs17
DBSPACE_VIDEO1HOUR=dbs11,dbs18
DBSPACE_VIDEO1DAY=dbs12,dbs19
DBSPACE_EOAM5MIN=dbs07,dbs14
DBSPACE_EOAM1HOUR=dbs08,dbs15
DBSPACE_EOAM1DAY=dbs09,dbs16
DBSPACE_15SECONDS=dbs06