Specify the instance of SBM if you are using SBM as a provider for Development Change Requests (DCRs). These must reside in the same SBM system as Serena Release Manager, as some of the functions implemented in Serena Release Manager use the Web services to implement the calls and use the provider to determine the instance of SBM.
IMPORTANT! The sbm-client-connection.properties file must have valid connection information to enable the creation of objects in Serena Release Control. If this connection is not configured properly, you will receive a checkuniquness error.
To update the SBM connection information:
On the SBM tab, make sure the variables are set to the correct connection information for your installation of SBM as follows:
| Parameter | Value |
|---|---|
|
SBM_APPWS_URL |
URL to the SBM server that provides the DCRs, in the form of: http://<sbm_hostname>:<port>/gsoap/gsoap_ssl.dll?sbmappservices72 |
|
sbm.service.user |
User ID with access to the appropriate SBM projects and tables controlled by Serena Release Manager. This user ID must exist in SBM. |
|
|
Password for the SBM user ID. |
Example
Set the SBM provider connection for DCRs. This example gives Serena Release Manager the URL to connect to the SBM application server on port 80 of host almhost.
sbm-client-connection.properties
|
SBM_APPWS_URL = http://almhost:80/gsoap/gsoap_ssl.dll?sbmappservices72 sbm.service.user = almadmin sbm.service.password = almadmin_test |