Installation Patterns - intersystems/ipm GitHub Wiki

When installing ipm on a new instance, if you desire multiple instance to use ipm, you have 2 installation patterns to choose from:

  1. (Recommended) Map the version of ipm from one namespace to all other namespaces. This can be done using
zpm "enable -map -globally"

All other namespaces will share this version of ipm, and anytime you update ipm in the namespace, this will be reflected in all other namespaces. If you installed ipm this way, running

zpm "version"

will show something like this: We can see that the version of IPM in namespace TEST is installed in USER, and thus any updates to USER will update the version in TEST.

  1. Install ipm in each namespace individually

If for some reason or other you require different versions of ipm on different namespaces in the same instance, then you can install ipm on each namespace individually. These version will not clash with each other, and will need to be updated separately.

Since mapping globally is easier, we recommend using method 1 unless you have a specific usecase.

(Note: Mixing the 2 methods is possible, but may result in some confusion. "enable -map -globally" will map ipm to all namespaces which do not already have an ipm installation. Thus, if you want a specific version of ipm on one particular namespace, you can individually install this version onto the namespace, but any updates to the original namespace from which ipm was mapped will now not change the version of our new namespace. Even rerunning "enable -map -globally" will not change the version)