· Jun 7, 2023

Question on changing namespace name in Ensemble

Hi All.

Had an empty Ensemble namespace (interoperability enabled) which the customer had requested renaming before beginning development, so was wondering about best practice to achieve this.

I saw on the docs ( that this can be done with management portal and terminal commands but it seemed simpler to just create a new namespace and delete the old. The way I did this was to create a new namespace using 'Copy from' the existing, then delete the old one.

my questions are:

1. Is this good practice, or is there some reason that renaming it as per the docs would be better?

2. When copying from existing namespace the new one uses the existing databases, fortunately when deleting the old namespace in management portal these databases weren't also deleted. When deleting a namespace will it also delete the databases if they aren't in use by another namespace, or would this need to be cleaned-up manually afterwards?

Thanks in advance.

Product version: Caché 2018.1
$ZV: 2017.2
Discussion (2)1
Log in or sign up to continue

I think you hit the utility of the documented approach. To not accidentally delete the databases.

If you forgot to delete databases as part of namespace removal, they can be manually tidied up (System Administration->Configuration->System Configuration->Databases).

Questions I would also be asking when directed by Customer from a Vanilla "ENSEMBLE" name, to a purposeful named Namespace:

  • Are IRIS.DAT(s) located in the correct disk volume / Drive name. ie: Sufficient capacity for expected use. (Is it supposed to be on the same volume / location as where services are installed).
  • Is there a backup strategy. AND did I retest it yet?
  • Are the databases journal enabled.
  • Check Users don't still have "ENSEMBLE" as default namespace location
  • Check Scheduled Tasks are not expecting "ENSEMBLE" namespace
  • Update documented standard build script

One more thought. If you are using Unix / Linux for hosting IRIS, a more recent option is mergeCPF, to update both Namespace, Database and Application settings. Suitable for:

  • migration activity as a testable automated script
  • configuration and setup from vanilla docker images.

This allows applying updates with a simple text file AND it does both traditional CPF settings AND the [csp web] Application settings in one go.

Your question encouraged me to share a little web calculator for CreateApplication settings.

So less time needed to figure out Application setting names and values.