Hi all,
I have 2 very different applications (thus having 2 different templates) that share some common data (partner identification forms).
I would like to make these applications replicas of each other so that I could share these common data using formula-based replication but I want them to continue to inherit their respective template.
Is it possible at all? Does anybody already set up such a replication scheme?
Best regards,
Cyrille
Subject: 2 replicas, 2 templates
Yes it is possible, we maintain an application with 5 different templates and many replicas, and it works.
With two versions, all you have to do is make one version inherit from one template, the other version from the other template (in Database properties, Design tab).
Plus you have to uncheck replication of design elements and agents, in Replication settings, Advanced section.
Edit: oh and then you can use Refresh Design (for both of them), to make design changes from templates. 
Subject: RE: 2 replicas, 2 templates
…wow…
This means, since one may not have 2 databases with the same replicaID on a single server, that you need at least 5 different servers for this(these) (5) application(s)… That sounds a little overkill though… Doesn’t?
Cyr
Subject: RE: 2 replicas, 2 templates
No, it means that you store common data in a separate database that can be replicated. Despite the name change in Notes and Domino 8, don’t confuse “application” with “database”.
Subject: RE: 2 replicas, 2 templates
Sorry, I don’t understand your point.
AFAIK, to be able to replicate, 2 databases must have the same replica ID. And having 2 databases with the same replica ID on a single serve r is not supported by IBM.
So, AFAIU, the situation explained here by Darina requires 5 different servers.
At least in Domino 6.5. Is there something new on this matter in Domino 8?
Cyrille
Subject: RE: 2 replicas, 2 templates
Wow. I didn’t think my posting was that difficult to understand.
There is ONE database that contains all of the common data (in this case, the person/contact data). That database may be replicated to as many servers as necessary – but if it is being used by multiple applications on a single server, replication is not necessary.
You can then have multiple databases, each with its own design, ACL, replica id, and so forth, that USE the data in the common database. There is no reason to replicate that data into the individual applications. The only thing these various applications would have in common is that they look up the contact info in the contacts database. (Oh, and they’ll probably have a means to modify the contacts database information without requiring the user to open the contacts db directly.)
There is no reason to assume that a Notes/Domino application has to be confined to a single database. The situation in the original posting – that there is a set of common data you want to keep in sync, but it needs to be used in multiple applications – is extremely common. Modularizing the applications by splitting them into multiple databases is the correct solution.