Designating the Details for Each DU Provider

You should give the connection details for each DU provider in separate properties file for each instance. This keeps the details separate from the selection, and helps with maintenance and security. 

The properties include provider name, which points to an associated file with connection information, and filters by status, so that users see only relevant information about the deployment units in Serena Release Manager.

To designate details for each DU provider:

  1. Navigate to the Serena Release Manager common Tomcat Web server classes folder. For example:

    C:\Program Files\Serena\common\tomcat\6.0\webapps\rlm\WEB-INF\classes

  2. Open one of your provider’s properties files. For example:

  3. The details are unique for each properties file, and variables and parameters are defined in the implementation for the provider. See Adding Provider Connections  for details if you plan to use a provider other than Dimensions CM or ChangeMan ZMF for DUs.

    For example settings for the default Dimensions CM and ChangeMan ZMF properties files, see the following examples.

  4. After updating the provider properties files, restart the Serena common Tomcat service.

See:

Designating Dimensions CM Deployment Unit Selection Criteria 

Set the Dimensions CM provider details for deployment units, or baselines, using the example dm_qlarius.properties file or a custom Dimensions CM provider properties file.

Example

Set the Dimensions CM provider details for DUs. This example sets the values needed to retrieve deployment units (baselines) from the Dimensions CM sample database, which has sample data based on a fictitious company called Qlarius.

dm_qlarius.properties

# requests provider definitions

requests.provider.name = DIM_QLARIUS

requests.provider.description = Dimensions Requests Provider for QLARIUS product

 

# deploy units provider definitions

deploy.units.provider.name = DIM_QLARIUS

deploy.units.provider.description = Dimensions Deployment Unit Provider for QLARIUS product

 

# filter requests by statuses

FILTER_REQUEST_BY_STATUSES = IN QA,IN PROGRESS,UNDER WORK,IN TEST

 

# filter deploy units by statuses

FILTER_DEPLOY_UNITS_BY_STATUSES = VERIFIED,DEPLOYED,CAPTURED

The text following the keys, requests.provider.name and deploy.units.provider.name, is documentary, and is also used in the related UI report search filter. In this example, DIM_QLARIUS describes the database from which the requests are being retrieved. The actual connection to the Dimensions CM database is defined in the dimensions.properties file. See Configuring Communication on the Dimensions CM Server.

This example tells Dimensions CM to return only requests and deployment units in a specified list of statuses.

Designating ChangeMan ZMF Deployment Unit Selection Criteria 

Set the ChangeMan ZMF provider details for deployment units, or change packages, using the example zmf_packages.properties file or a custom ZMF provider properties file.

Set the properties for the ZMF filters as follows:

Parameter

Value

deploy.units.provider.name

Deployment unit provider name.

Default value = ZMF_PACKAGES

deploy.units.provider.description

Deployment unit provider description.

Default value = ChangeMan Deployment Unit Provider for ZMF packages

FILTER_ZMF_PACKAGES_IN_DEVELOPMENT_STATUS

Change packages that are in frozen status are typically selected as deployment units that are ready to install, but you may include change packages in development status if your processes require that.

Setting this to Y will list all packages that are in FRZ and DEV status. Setting this value to N will list all packages that are in FRZ status.

Default value = N

FILTER_ZMF_PACKAGES_BY_WORKREQNO

Setting this to Y will list only packages that have an empty or null work request number value.

Default value = Y

NOTE  If you want to update the ZMF change package work request number value with the associated Serena Release Manager deployment unit’s SBM item ID, you should set this value to Y. See RELATE_DU_ITEMID_TO_ZMF_PACKAGE_WORKREQNO.

FILTER_PLANNED_PERMANENT_ZMF_PACKAGES

Include change packages with package type planned permanent. (Values Y or N)

Default value = Y

FILTER_PLANNED_TEMPORARY_ZMF_PACKAGES

Include change packages with package type planned temporary. (Values Y or N)

Default value = Y

FILTER_UNPLANNED_PERMANENT_ZMF_PACKAGES

Include change packages with package type unplanned permanent. (Values Y or N)

Default value = Y

FILTER_UNPLANNED_TEMPORARY_ZMF_PACKAGES

Include change packages with package type unplanned temporary. (Values Y or N)

Default value = Y

FILTER_SIMPLE_ZMF_PACKAGES

Include change packages with the level of simple. (Values Y or N)

Default value = Y

FILTER_PARTICIPATING_ZMF_PACKAGES

Include change packages with the level of participating. (Values Y or N)

Default value = Y

FILTER_ZMF_PACKAGES_BY_PROMOTION_LEVEL

Include change packages with this promotion level and above.

The last promotion level must be greater than or equal to the promotion level filter.

For example, if you have the following promotion levels in ZMF, setting this value to 10 returns change packages in these promotion levels:

10 – INT Integration Test

20 – UAT User Acceptance Test

30 – PAT Production Acceptance Test

 

Default value = 10

FILTER_ZMF_PACKAGES_BY_AUDIT_LEVEL

Include audit return code.

The audit return code must be less than or equal to the audit level filter.

Default value = 04

RELATE_DU_ITEMID_TO_ZMF_PACKAGE_WORKREQNO

Choose whether to fill in the ZMF change package work request number with the development change request value from Serena Release Manager. (Values Y or N)

Default value = Y

RELATE_DU_ITEMID_TO_ZMF_PACKAGE_WORKREQNO

RELATE_RP_PROD_DEPLOY_DATE_TO_ZMF_PACKAGE_INSTALL_DATE

Choose whether to fill in the ZMF change package installation date with the release package stage end date from Serena Release Manager. (Values Y or N)

Default value = Y

Example

This example sets the values needed to retrieve deployment units (change packages) from a ChangeMan ZMF sample system.

zmf_packages.properties 

# deploy unit provider definitions

deploy.units.provider.name = ZMF_PACKAGES

deploy.units.provider.description = ChangeMan Deployment Unit Provider for ZMF packages 

 

# ZMF package status filter(Y/N).

Setting this to "Y" will list all packages that are in "FRZ" and "DEV" status.

FILTER_ZMF_PACKAGES_IN_DEVELOPMENT_STATUS = N

 

# ZMF work request number filter (Y/N).

Setting this to "Y" will only list packages that have work request number value that is empty is set to "NULL".

FILTER_ZMF_PACKAGES_BY_WORKREQNO = Y

 

# zmf package type filters (Y/N)

FILTER_PLANNED_PERMANENT_ZMF_PACKAGES = Y

FILTER_PLANNED_TEMPORARY_ZMF_PACKAGES = Y

FILTER_UNPLANNED_PERMANENT_ZMF_PACKAGES = Y

FILTER_UNPLANNED_TEMPORARY_ZMF_PACKAGES = Y

 

# zmf package level filters (Y/N)

FILTER_SIMPLE_ZMF_PACKAGES = Y

FILTER_PARTICIPATING_ZMF_PACKAGES = Y

 

# Numeric promotion level filter.

The last promotion level return code must be greater than or equal to the promotion level filter.

FILTER_ZMF_PACKAGES_BY_PROMOTION_LEVEL = 10

 

# Numeric audit return code filter.

The current audit return code must be less than or equal to the audit level filter.

FILTER_ZMF_PACKAGES_BY_AUDIT_LEVEL     = 04

 

#deploy unit and release package relationship filters (Y/N)

RELATE_DU_ITEMID_TO_ZMF_PACKAGE_WORKREQNO = Y

RELATE_RP_PROD_DEPLOY_DATE_TO_ZMF_PACKAGE_INSTALL_DATE = Y

 

The text following the keys, deploy.units.provider.name, is documentary, and is also used in the related UI report search filter. In this example, ZMF_PACKAGES simply describes the kind of data being retrieved. The actual connection to the ChangeMan ZMF system is defined in the zmf.properties file. See Configuring ChangeMan ZMF Communication in Release Manager.

This example tells ChangeMan ZMF to return only deployment units, or change packages, that are in FRZ status, have a blank work request number, are in promotion level 10 or above, and have passed audit with a return code of 04 or less. The relationship filters are set so that the work request number and installation dates will be updated in ChangeMan ZMF based on information stored in Serena Release Manager.

You should set your selection criteria based on your organization’s release management practices related to ChangeMan ZMF.