*Under Construction* ERM Doors Next Module Structure Integrity Check during change set delivery

Authors: DianaKraaijeveld
Build basis: ERM Doors Next, version 7.0.3, 7.1 and up

Information on how to enable and use the ERM Doors Next 'Module integrity check during change set delivery' feature. Enabling this feature will enforce a data consistency check on module structures for modules that get updated by a changeset delivery.

Enabling module integrity check during change set delivery

In Doors Next v7.0.3-Ifix015 and v7.1-Ifix004, an advanced property was introduced, called Enable module integrity check during change set delivery. It can be set to true by a Jazz Admin in the /rm/admin >Advanced Properties, under 'RM Delivery component':

Activating this feature does not require a server restart.

Note Before enabling this feature, we strongly recommend to check your modules in your active streams. See this technote for more details

Deliveries done in the RM UI

If the is property is enabled, the module structure of each module that will be updated by the delivery, will be checked for inconsistencies that will occur if the delivery is processed. This check occurs in the background by the Module Analyser. If it detects modules that will have a structure inconsistency after the delivery, it will check these modules in the source configuration, the target stream and the future target stream. -This check happens after clicking the 'Deliver' button. -This check happens for all types of deliveries.

If a problem is found for a module, a message will pop up with information about the module and the configuration. When the warning shows up: -Clicking on Cancel will cancel the delivery. -The delivery will proceed when clicking on OK.

Example where the delivery is causing a module structure inconsistency in the target:

Example where a module structure inconsistency is caused by a problem in the source configuration:

Deliveries done with API

The property dng_config:checkModuleIntegrity was introduced to control the integrity check from the client’s side as part of the API call:

-If set to true: A module structure check is run as part of the API delivery. If a structure issue is detected, the delivery will fail with information on the relevant module(s).

-If it’s set to false: A module structure check is not run as part of the API delivery.

-If it is not set at all: The default is False, so a module structure check is not run as part of the API delivery.

Note that this property can only be used when the rm advanced property Module integrity check during change set delivery is also set to True.

Example body request when triggering the delivery PUT with a delivery including a Module structure issue:

You can see here that the delivery integrity is set to true :

Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text

What to do when a warning shows for one or more modules

Audit logging

Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text Sub-Section text

Related topics: Deployment web home, Deployment web home

External links:

• IBM

Additional contributors: TWikiUser, TWikiUser