We have an extranet site that contains multiple replicas (one replica for each of our partners which totals 10). We replicate our hub to our extranet site and all the data is then separated via selective replication formulas.
This has been working great in an R5 environment. When we move to R6, the replication of the data still works fine, but we are having issues with something as basic as the navigatenext commands to move through the views on the web. Everytime we use the links, we get prompted for a password that never will authenticate.
Has anyone done this or does anyone have any other options? We need to separate the data between the databases to make the database perform better due to lower volumes of data (each db has on average 20,000 docs. If we had one db, then there would be about 200,000 docs).
Don’t use multiple replicas of the same database on a server. That’s not a supported configuration. You’re supposed to be able to identify a database by its replica ID. If that doesn’t point to a unique database on the server you will have problems. I expect what’s going on here, is Domino generating URLs that include the replica ID.
200,000 is not so many documents. You could put them all in one database and use single-category views to let people see just their own stuff. Or, you could create copies of the database design and write your own replication program to sync with the master. Or you could use LEI replication activity for that.
Thank you for your response. Do you know why it works in R5 and not in R6?
Also, we used a data pumping tool to do before when it was a totally Notes app, but the number of cycles that were completed in a day was slowly getting less and less, where replication is much faster and we can replicate every 15 minutes. The data pumping was taking a little over an hour per cycle to all the partners and scaleability of this was limited.
I’m no server guru or anything, but has anyone partitioned a server and had replicas on each partition? With that maybe we can have a separate domain for each partner and have them directed to their partition. Would being on a separate partition fix the issue we are seeing in R6?
If your hardware can support running multiple servers you’ll probably find that to be the best solution…you’ll of course have to set up the server’s NIC with an IP for each server. Licensing shouldn’t be an issue, since it’s done per processor these days.
One of two things – either the “data pumping” tool you were using was failing to use a timestamp to detect which records had been recently modified, or else there’s some agent in this database that’s modifying every document every day, which is a big performance killer.