Designating the Details for Each DCR Provider

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

To designate details for each DCR 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 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 the example following this procedure.

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

Related Topics

Designating DCR Provider Details for Dimensions CM Requests

Example

Set the Dimensions CM provider details for DCRs. This example sets the values needed to retrieve requests 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

.

.

.

# filter requests by statuses

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

.

.

.

The text following the keys, requests.provider.name, is documentary. In this example, DIM_QLARIUS simply 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 in a specified list of statuses. 

Designating DCR Provider Details for SBM Issues

Example

Set the SBM provider details for DCRs. This example sets the values needed to retrieve requests from the SBM Issues process app.

sbm_issues.properties

# requests provider definitions

requests.provider.name  = DCR_Issues

requests.provider.description = SBM Requests Provider based on Issues solution

 

REQUESTS_TABLE_DBNAME=UBG_ISSUES

REQUESTS_FIELD_STATUS=STATE

REQUESTS_FIELD_LINK=URL

REQUESTS_FIELD_OWNER=OWNER

REQUESTS_FIELD_PROJECTNAME=PROJECTID

 

REQUESTS_QUERY_WHERE_CLAUSE =

REQUESTS_ORDER_BY_CLAUSE    =

 

# possible values

# SUBMIT_PROJECTS

# REPORT_PROJECTS

REQUESTS_PROJECTS_TYPE      = SUBMIT_PROJECTS

 

# valid only for REQUESTS_PROJECTS_TYPE = REPORT_PROJECTS  

PROJECTS_REPORT_NAME=

PROJECTS_FIELD_TITLE=

PROJECTS_FIELD_STATUS=

PROJECTS_FIELD_OWNER=

PROJECTS_FIELD_TYPE=

# end of properties specific for REQUESTS_PROJECTS_TYPE = REPORT_PROJECTS

The text following the keys, requests.provider.name and deploy.units.provider.name, is documentary. In this example, Issues simply describes the SBM primary table from which the issues, or requests, are being retrieved. The REQUESTS_TABLE_DBNAME key specifies the primary table from which to retrieve the issues.

This example shows a number of filters that can be used to restrict the list of issues to associate with DCRs in a release package.

Designating DCR Provider Details for SBM Incidents

Example

Set the SBM provider details for DCRs. This example retrieves incidents from the Incidents process app. This process app must be on the same SBM application server as your Serena Release Manager process app.

sbm_incidents.properties

# requests provider definitions

requests.provider.name=Incidents

requests.provider.description=SBM Requests Provider based on Incidents solution

 

REQUESTS_TABLE_DBNAME=UIM_INCIDENTS

REQUESTS_FIELD_STATUS=STATE

REQUESTS_FIELD_LINK=URL

REQUESTS_FIELD_OWNER=OWNER

REQUESTS_FIELD_PROJECTNAME=PROJECT_FOR_INCIDENT

 

REQUESTS_QUERY_WHERE_CLAUSE=

REQUESTS_ORDER_BY_CLAUSE=

 

# possible values

# SUBMIT_PROJECTS

# REPORT_PROJECTS

REQUESTS_PROJECTS_TYPE=REPORT_PROJECTS

 

# all properties below are valid only for REQUESTS_PROJECTS_TYPE = REPORT_PROJECTS  

PROJECTS_REPORT_NAME=Projects for Incidents

PROJECTS_FIELD_TITLE=TITLE

PROJECTS_FIELD_STATUS=STATE

PROJECTS_FIELD_OWNER=OWNER

PROJECTS_FIELD_TYPE=ISSUETYPE

# end of properties specific for REQUESTS_PROJECTS_TYPE = REPORT_PROJECTS

The text following the keys, requests.provider.name and deploy.units.provider.name, is documentary. In this example, Incidents simply describes the SBM primary table from which the incidents, or requests, are being retrieved. The REQUESTS_TABLE_DBNAME key specifies the primary table from which to retrieve the incidents.

This example shows a number of filters that can be used to restrict the list of incidents to associate with DCRs in a release package.