Using the recommended spring dependency injection mechanism, as shown in the included examples, create separate properties files for provider definition and provider instance-specific parameters as follows:
Define your provider’s class and its parameter definition, but not values, in an XML definition file. See Designating the Details for Each Provider.
Define all instance-specific values for parameters in a properties file. See Telling Serena Release Manager to Use This Provider.
Using the spring dependency injection mechanism, you define your provider’s class and its parameter definition, but not values, in an XML definition file.
For example, Serena provides the provider-dm.xml file for Dimensions CM, a potential provider of DCRs and DUs and provider-sbm.xml file for SBM, a potential provider of RFCs, BCRs, and DCRs.
The following example implements the spring dependency injection mechanism for a simple file system provider.
Example
provider-fs.xml
|
Using the spring dependency injection mechanism, you define all instance-specific values for parameters in a properties file.
It is not required to use a properties file separate from the xml file in the provider implementation. However, usage of a properties file is a good practice and is included in the example provided. Using a properties file allows you to define several possible configurations so you can easily change details without code modification. Without a properties file, you must hard code name, description, and other specific parameters for your provider.
Examples
fs_example.properties
|
The text files referenced in the preceding example, requests.txt, depunits.txt, stages.txt, and areas.txt are shown in the following examples. This is a simple file-system example where the content of these could be populated by any mechanism you implement, such as JDBC, Web services, and other protocols.
requests.txt
|
depunits.txt
|
stages.txt
|
areas.txt
|