I just placed a database link to a specific server replica (‘North’ server) in our desktop settings policy document and all the users received a link to the replica on our ‘Brookfield’ server.
Is this that ‘Notes chooses first replica alphabetically by server’ thing? Any ideas why this is happening and how to get around it (besides deleteing all other replicas except desired server replica)? Trying to avoid unnecessary WAN traffic.
Subject: Desktop Settings Policy Document deploying bookmark to different server replica of database
yup, that’s it - but deciding which server is accessed is based on desktop’s top icon on stack (good old desktop will never die:)
there are different types of bookmark-links:
one that are completly relativ (have no server at all): if you have never opened this db on server or have a local replica, you won’t be able to open db.
hinted bookmarks: those that you deployed. but server is only considered if there’s no such icon on desktop. it opens a local replica if any, than gets first icon on stacks servername and tries this server.
absolute bookmarks: those that you’d like, but can’t get. they can be set programmatically (via api) but you can’t do it in ui.
if you’d ask me for the reason why, i’d say that this is somewhat similar to restricting agents on server to only be able to access local dbs. notes philisophy is (i guess) that: user know which server he prefers (the fastest one maybe), thus don’t make any hardlinks.
if you are interested: we have a tool that (beside many other features, it’s a complete remote client managment tool) allows you to set absolute bookmark links.
you can get a trial at:
little overview of what you can do:
Markus Seitz