Not really DRay. Firstly, we're on Windows. Second, our issue is more about the connection logged within the dashboard that references an elasticube on a given server. When the elasticubes move to another server, the dashboard has to be updated to change the connection from the old to the new server within the dashboard definition. Connection Management seems to be more about the connections in the elasticubes. We worked around this issue by updating the dashboards in mongo directly.
1. In Studio2T we used these query criteria to firstly locate the widgets that had the Seats and Tickets source from HESTIA still in place:
db.getCollection('widgets').find({"datasource.title": "My Elasticube",
"datasource.address": "server.address",
"datasource.fullname": "server.address/My Elasticube",
"datasource.id": "aSERVERLgAaADDRESS_aMYIAAaELASTICUBE",
"datasource.database" : "aMyIAAaElasticube" })
2. And we then right clicked on one of the results and selected to 'Update Dialog...'
3. We changed the dropdown in the middle of that screen to "Apply the pre defined query" which means it will update all rows returned in the query in step 1.
4. Then In the update tab, within the $Set section, we pasted in the 5 rows that we needed to set for the Seats and Tickets cube, but with the testing server references:
{
$set : {
"datasource.title": "My Elasticube",
"datasource.address": "server.address",
"datasource.fullname": "server.address/My Elasticube",
"datasource.id": "aSERVERLgAaADDRESS_aMYIAAaELASTICUBE",
"datasource.database" : "aMyIAAaElasticube"
}
}
5. We carried out the same steps as above but with the relevant values passed for each data source.
6. We then corrected anything that was still hanging around in the dashboards collection using the same scripts but with 'dashboards' as the collection.
