Most of us create a Documentum application for a specific purpose or user group. We create custom types, groups, acl templates/alias sets, lifecycles, and workflows that are used by the application and all of these custom objects are stored in repository used by the application. Assuming the application is a success, you might generate interest from other user groups to develop a Documentum application for them. Here’s the $10,000 (or $1,000,000 if you adjust for inflation) question:
Should we use the same repository or create another one?
There are many factors that may come into play when deciding on whether to share one common repository have multiple repositories for each application. Here’s a few off the top of my head:
1. Are the sames users going to access both applications? If so, creating a second repository would require you to create user objects in both repositories. This maintenance can be minimized by setting up a Federation, but that is a different story.
2. Do you plan on sharing documents between the applications? If so, keeping one repository is simpler than trying to replicate content between the two repositories.
These two questions really focus on the back-end customization of the repository. If you are using Webtop, there are also several options from a customization perspective.
1. You can have separate Webtop applications connecting to the same repository, each with its own unique features.
2. You can have a single Webtop instance with customizations that are specific to which repository you are connecting to. For example, you can have a Contracts menu item that is only visible when connecting to Contracts repository.
I know there are probably other factors that I have not thought about. Please feel free to share your experiences.