Bernard - Server names are usually part of Bookmarks, and there IS support for centralised admin, import and export of bookmark lists from files...see for example:

http://forums.visokio.com/discussion/2445/new-bookmarks-importexport-link-2.9-

From the KnowledgeBase:

Updating Bookmarks
Bookmarks are used to make data sources such as specific database tables available to activated users across all their files via drag-and-drop from their DataManager Data Bars. Fully-configured (with hidden authentication) bookmarks from a reference installation can be shared and updated across multiple installations by exporting them as .ILF files which can be mailed to recipients who need new bookmarks installed or previous ones updated.

Settings > {Application-wide} Advanced > Tools > Create distributable bookmarks

Is there a naming convention - consistency in the DataManager source block naming, so that SQL DB ABC source block is always called "ABC" and that Oracle DB "X" is always called "X" in all reports where these are used?

Thanks, will try this out.

Any news on a 2.9rc - we will need to put this on our live server and we aren't allowed to put beta versions there

I can export and import bookmarks and have them refresh the imported bookmark.

If I drag a bookmark to the datamanager canvas and use it it loses the link to the bookmark. I save a bookmark file with Hostname SQL1, import it tio another omniscope and use it in datamanger. Then change the reference in the bookmark to SQL2. The imported bookmark now refers to SQL2, but the datamanager block still refers to SQL1. Is there a way to force the block to update to SQL2 when file is reopened?

You are right - once you add a database block to your workflow it is no longer linked to the bookmark, so if the bookmark changes your block will not reflect these new settings.
We will be looking to do this for the next version of DataManager (but obviously not going to be available for a while).
In the meantime, my question about the naming convention was related to the Scheduler option
File action>Reconfigure DataManager SourceBlock
so you could automate the operation.

Bernard, we would be making 2.9 RC very shortly. The first RC release of 2.9 should be available early next week either Monday or Tuesday.

Mustafa - Thanks that's great news.

On the parameter passing - the other thought we had was to have one omniscope instance that could have all the usable server names as parameters which would then be broadcast via the "Publish to LAN" option - all reports would then pick the servers required as input parameters and use these in datamanager blocks. Then a change in the parameter at the publisher would automatically change all access for the clients of the published server name.

For this to work would the publisher need to be on same machine as client?

Also the reference to the published parameter is to a file with a path specified. The path uses a drive letter. If a developer opens the file from the network and gets it publishing on his PC, will this then be transferable to the server as long as we keep a copy of the file permanently open on the server?

Bernard, we have not tested this specific scenario, but it seems workable. I believe the parameter passing will work as you describe, providing the IOK is kept open on a desktop instance on your server. Other IOKs opened on other desktops should be able to link to the server parameter. Let us know if you have difficulty getting this to work.

As discussed, 2.9 is now the Release Candidate - here is the download page:
http://forums.visokio.com/discussion/2610/announcing-omniscope-2.9-release-candidate