Warning: This page is currently under development.
How do I create a Bridge Analysis Federations?
A Bridge Federation permits collections resident in several different federations (called Slave Federations) to be accessed through one federation: the Bridge Federation. Here, we assume that the Federations are to be used with the new CDB conditions database.
Creating a Slave Analysis Conditions Federation
The .bbobjy file used to create the Conditions federation used by the Slave Analysis Federations should use the FDB_LOCAL_NAME of:
among the other parameters needed to create the federation (such as FD_NUMBER, lock and ams host etc). Once the Federation has been created (using the gmake database.import and gmake database.load commands) and the conditions and configurations loaded the databases should be marked as readonly:
oochangedb -readonly -id <database id>
This should reduce the amount of lockserver activity and should protect the conditions databases from being accidentally modified.
Creating a Slave Analysis Federation
In the .bbobjy file the FDB_LOCAL_NAME can be set to "default" for the Slave Federation (don't forget to supply the other parameters). Once the federation has been created the databases should then be attached to the federation using:
ooattachdb -db <database name> -id <database id> -host <db server name> -filepath <full db path>
It's probably a good idea to make the databases readonly using the oochangedb command described in the previous section. Once the databases have been attached the collections need to be loaded using the following command:
setenv BDB_NO_NESTED_COLL_TRANS yes BdbDistCollLoader <collection database name>
If you wish to allow other users to write to your Analysis Federation you will need to register these users to the Federation:BdbAuthCmd ucreate Events <username> "<users name>"
To create groups and users to groups please check the extensive BdbAuthCmd help documentation (BdbAuthCmd -help).
The Conditions Analysis Federation now needs to be registered in the Slave Analysis Federation. To do this you need to divest the Slave Analysis Federation's conditions domain:
BdbDomainBootNames con <Conditions Analysis Federation bootfile> BdbDomainBootNames cfg <Conditions Analysis Federation bootfile>
Creating a Bridge Analysis Federation
The FDB_LOCAL_NAME in the .bbobjy file for the Bridge Analysis Federation can also be set to "default". To prevent users from writing event store data into the Bridge Analysis Federation execute the command:
BdbManageFdOptions -e 0
The Conditions Analysis Federation should now be registered in the Bridge Analysis federation using the BdbDomainBootNames command (described previously). If you wish to allow users to write out Bridge collections you need to authorize them using the BdbAuthCmd described previously. Finally, you need to register the Slave Analysis Federation's collections in the Bridge Analysis Federation:
BdbLoader mod talk BdbInspector coll create -b <bridge collection name> coll addTo <slave collection name>@<slave bootfile> <bridge collection name> exit exit
Each slave collection needs a "coll create" and "coll addTo" command in order to have the slave collection visible through the Bridge Analysis Federation.
BaBar Public Site | SLAC | News | Links | Who's Who | Contact Us
Page Owner: Jacek Becla
Last Update: October 27, 2002