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:
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
Open one of your provider properties files. For example:
dm_qlarius.properties
sbm_issues.properties
sbm_incidents.properties
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.
After updating the provider properties files, restart the Serena common Tomcat service.
Related Topics
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
|
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.
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
|
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.
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
|
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.