-
Notifications
You must be signed in to change notification settings - Fork 28
00. Concepts
Every operation IPM performs on a module, e.g. loading, compiling, testing or publishing, is expressed as a lifecycle phase. When you run a command like load or test, IPM resolves it to an ordered sequence of phases and executes them in turn against the module (and optionally its dependencies).
The lifecycle class for a module type defines a method for each phase. Resource processors attached to the module's resources can also hook into each phase, executing before or after the lifecycle method runs. This separation means the same phase sequence can behave differently depending on what resources a module contains.
Phases run in a fixed order. When you invoke a compound command (e.g. test), IPM resolves it to all the prerequisite phases automatically — you don't need to run them individually.
The canonical order is:
Clean → Initialize → Reload → Validate → ExportData → Compile →
Activate → Document → MakeDeployed → Test → Package → Verify →
Publish → Configure → Unconfigure → ApplyUpdateSteps
| Phase | What it does |
|---|---|
| Clean | Removes the module's resources from the namespace. Recurses into dependencies unless they are required by something else; use -force to remove those too. Modules with <GlobalScope> set to 1 are skipped by default; pass -global to include them. |
| Initialize | Pulls and compiles module source code from the /preload directory. Used to set up namespace mappings, globals, or other prerequisites before resources are loaded. |
| Reload | Pulls module source code into the namespace from disk. Does not compile. |
| Validate | Ensures that the module API section is up to date, that module resource processor attributes are valid, and that the resources exported to the filesystem (and possibly to source control) are consistent with what is in the database. |
| ExportData | Exports data associated with the module (globals, lookup tables, etc.). Standalone. |
| Compile | Compiles all resources within the module. |
| Activate | Performs post-compilation installation/configuration steps: runs projections, activates interoperability productions, etc. Default phase for <FileCopy>. |
| Document | Regenerates the API documentation for the module. Standalone. |
| MakeDeployed | Deploys resources within the module for which deployment is enabled (source-stripped form). |
| Test | Runs any unit tests associated with the module, in the current namespace. |
| Package | Exports the module's resources and bundles them into a module artifact (.tgz file). |
| Verify | Installs that artifact in a separate namespace, then runs integration tests (if any). |
| Publish | Saves that artifact to the repository for which deployment is enabled. Currently, there may only be one of these per namespace. |
| Configure | Applies configuration that should run after installation — e.g. setting system settings, merging CPF entries. Default phase for <Invoke>. |
| Unconfigure | Reverses configuration applied by Configure. Runs during uninstall. |
| ApplyUpdateSteps | Runs migration steps when upgrading from a prior version. |
Most commands don't run a single phase in isolation, but rather run a chain of prerequisites first. For example, the test command runs Initialize → Reload → Validate → Compile → Activate → Test. Most of these chains are defined in %IPM.Lifecycle.Base:GetCompletePhasesForOne.
However, some phases invoke others directly in the lifecycle method itself rather than declaring them as prerequisites. For example, Package explicitly calls MakeDeployed, and Publish explicitly calls Package, from within their implementations.
Standalone phases (Clean, ExportData, Document, Configure, Unconfigure) run as-is.
Custom phases let a module expose named operations that aren't part of the standard install/build/test flow. Common use cases:
- A one-off data migration step that should only run when explicitly requested, not on every install.
- Applying a CPF merge only in a specific deployment scenario.
- A developer convenience command (e.g.
seed-data,reset-config) that invokes application-specific logic.
Custom phases are not part of any command's default phase chain — they only run when explicitly requested by name.
Custom phases are defined in module.xml using the CustomPhase attribute on <Invoke> or <CPF> elements. See Custom Phase Example in the manifest reference for worked examples.
ipm> mymodule custom-phase-name
Custom phases are case-insensitive. IPM resolves them against the phases registered by the module's invokes and resource processors at runtime.
Several built-in -D flags control low-level installation behavior. They apply to install, load, and update. You can pass them on the command line or set them as persistent defaults with default-modifiers.
Note: These flags are expected to be revamped in IPM 1.0.0.
Disables the IRIS transaction that normally wraps a module load. By default, IPM wraps the entire load/install operation in a transaction so that a failure mid-way through is fully rolled back. With NoTransaction=1, any failure leaves the namespace in a partially-installed state.
Use when some modules in the install conflict with an outer wrapping transaction, or when the transaction overhead is unacceptable — wrapping a large install in a single transaction can add significant time and memory pressure.
Disables IRIS journaling at the process level for the duration of the load. Disabling the journal can drastically cut install time, making this particularly useful in dev environments where you're loading modules repeatedly. It also implicitly disables transactions (a journaled rollback is not possible without a journal), so NoJournal=1 is a strict superset of NoTransaction=1.
The trade-off is that if the process crashes mid-install, changes cannot be rolled back and the namespace may be left in an inconsistent state. Avoid this in production namespaces where data integrity matters.
Suppresses the automatic creation of global and document (class/package) mappings for the module's resources during installation. See <NoMapping> in the manifest reference for full details and examples, including how to embed this as a default in module.xml.
On the command line:
zpm "load /path/to/module -DNoTransaction=1"
zpm "install mymodule -DNoMapping=1"
zpm "install mymodule -DNoJournal=1 -DNoMapping=1"
As a persistent namespace default (applied to every subsequent command):
zpm "default-modifiers -set -DNoTransaction=1"
Embedded in module.xml (applied whenever this module is installed):
<Defaults>
<Parameter Name="NoMapping">1</Parameter>
</Defaults>