nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Repository name across environments

Pedro Ventura

When installing a new system with multiple environments (for example development, quality assurance and production) which is best, having a different name for the repository for each environment (for example projectx_dev, projectx_qual and projectx_prod) or having the same name (for instance projectx_repository) accross all environments.

I'd really appreciate if you could share your reasoning behind defending one option instead of the other.

Many thanks,

Pedro

Find more posts tagged with

Comments

DCTM_Guru

From a coding perspective, its easier to have the repositories name the same, in case you need to establish docbase session through your app. From a administration/maintenance perspective, this is a nightmare, because it can be confusing when determining which environment you are in. Also keep in mind, when you use Composer or DA, you can NOT connect to two different repositories with the same name. Developers/admins sometimes do this on their local computers.

Personally, I would push the developers to parameterize any configuration setting that references the docbase name and implement different properties files for the different environments. This takes a little more extra work upfront, but it saves a lot down the road.

Francois Dauberlieu

I agree with Johnny, using the same names could prove to be very confusing and a source of errors

mszurap

To add one more perspective: If you intend to clone your docbase (for example re-create the QA env from the production environment to be the same) then you have no options, the docbase names will be the same.

Francois Dauberlieu

Miklos,

Wouldn't, officially, cloning a Docbase break the license agreement ? As far as I remember, when purchasing Documentum, you get a fixed number of Docbase ID's therefore, if you clone a Docbase, you actually have multiple Docbases with the same ID, which, I'd expect, is not what's intended by EMC.

Is there anybody from EMC able to share some insider info's about that ?

mszurap

In my mind docbase id is just because to assure you that your docbase identifier won't clash with other one so the objects (object ids) are unique between repositories. But I would also like to see some more info on this...

Francois Dauberlieu

You might be right, no idea...

EMC ?????

DCTM_Guru

I agree with Miklos, docbase ID is to prevent conflicts in a DCTM federation. AFAIK, EMC licensing was either tied to named users or CPUs, I dont think it was ever based on number of docbases.

As for cloning, it is officially supported from a testing/dev perspective. The issue here (as I aluded in my original post), cloning can cause some confusion from user perspective, especially if you dont completely isolate the various environments.

Francois Dauberlieu

Fair enough, to be honest, it's my boss handling all the legal and licensing stuff. Once again, I put my foot in my mouth

DCTM_Guru

Francois,

You are too hard on yourself Everyday I learn something new reading the forums. This is why I continue to participate after many years.

Cheers,

Johnny

Francois Dauberlieu

True enough Johnny

Pedro Ventura

Thanks for clarifying this for me Johnny (and thanks to all for your replies). I usually use a different name for each environment as you suggested but I was recently in a client where they decided to use the same name across all environments and I was wondering if this could be better than using different names. Thanks again for your answer.

DCTM_Guru

I am also at a client who decided to the clone the various environment and have same name and docbase ID for all environments. Let me reconfirm the headaches it has caused with users not knowing which environment they are in. The only way they can sure that they are in DEV (vs PROD), is that there is an additional DEV cabinet.

rdragasits1

I always get the question from managment. Why dont we have production data in our dev enironment so tesing is better. Is there a way to do this and have a different docbase name?