Post-Installation Tasks → Configuring the Provider Plugins → SBM Provider Plugin Configuration Details
The default SBM Provider plugin provides functionality for SBM requests and executions, where the requests that are associated and deployment tasks that are submitted or transitioned are items in SBM projects.
The provider types are used as follows:
After adding a plugin, you can add configurations for the plugin. Multiple configurations can be added. Here are some examples on why you would use different configurations:
The fields for an example SBM Provider plugin configuration are described in the following table.
Field / Description | Example Values |
---|---|
Name: Name of the provider configuration. Be as descriptive as possible, as this distinguishes the configuration from other configurations when users are selecting it. |
Release Control Sample Applications |
Description: Description of the item, which will appear as a tooltip |
Release Control Sample Applications Configuration - Requires Manual Deployment Tasks and Sample Request process Apps |
SBM Web Services: URL for the SBM application web services |
http://<serverName>:80/gsoap/gsoap_ssl.dll?sbmappservices72 |
Use Single Sign-On (SSO): Enable single sign-on to allow the provider service to log in to the SBM system using the authentication token of the user. Note that if you are logging into a separate SBM system that doesn't share the same SSO server, you will receive the following message "An error occurred while getting collection details" when trying to find an item on the other system. |
true |
User Name: If single sign-on is not enabled for this server, use this user name to log in to this system. |
|
Password: If single sign-on is not enabled for this server, use this password to log in to this system. | |
Open in workcenter | true |
Execution Properties | |
Provider Name: A descriptive name of the execution provider |
RLC - Manual Deployment Task |
Provider Description: A more detailed description of the provider. This information appears as a tooltip. |
Release Control Manual Deployment Task Process App |
SBM Table (DBNAME): The database table name of the SBM table that you want to submit or transition execution items |
TRM_RLM_DEPLOY_TASKS |
Extended Fields: A comma-separated list of fields to populate with data when submitting or transitioning items. The values are the database names for the fields. (See the related note below the table.) |
RLM_TASK_OWNER |
queryWhereClause: A SQL query where clause that is used to search fields to return the list of possible requests to relate. Refer to the SBM documentation about the GetItemsByQuery call for more information on the queryWhereClause. |
TS_PROJECTID=@{PROJECTID} AND (TS_TITLE LIKE '%@{SEARCHTERMS}%' OR TS_DESCRIPTION LIKE '%@{SEARCHTERMS}%') |
orderByClause: A SQL statement to order the results of the query. Use this statement to place newest items first in the list or to divide them up based on projects. Refer to the SBM documentation about the GetItemsByQuery call for more information on the orderByClause. |
TS_SUBMITDATE ASC |
Transitions: A comma-separated list of transitions that will be available if you choose the "Transition Item" action |
UPDATE, RETRY, COMPLETE |
Wait for Callback: Whether to wait
for the system to respond with results
Important: If you are integrating with an
external
SBM
system and set this to
true, refer to the
Serena Release Control: SBM Plugin Quick Reference
for additional required configuration details.
|
true |
Request Properties | |
Provider Name: A descriptive name of the request provider |
RLC - Sample Request |
Provider Description: A more detailed description of the provider. This information appears as a tooltip. |
Release Control Sample Request Process App |
SBM Table (DBNAME): The database table name of the SBM table that you want to search for requests to relate |
TRM_RLM_BUSINESS_REQ |
Extended Fields: A comma-separated list of fields to populate with data when submitting or transitioning items. The values are the database names for the fields. These fields will appear when the user chooses to view the items from the report. (See the related note below the table.) |
RLM_PROJECT, RLM_PROJECT_OWNER |
queryWhereClause: A SQL query where clause that is used to search fields to return the list of possible requests to relate. Refer to the SBM documentation about the GetItemsByQuery call for more information on the queryWhereClause. |
TS_PROJECTID=@{PROJECTID} AND (TS_TITLE LIKE '%@{SEARCHTERMS}%' OR TS_DESCRIPTION LIKE '%@{SEARCHTERMS}%') |
orderByClause: A SQL statement to order the results of the query. Use to the statement to place newest items first in the list or to divide them up based on projects. Refer to the SBM documentation about the GetItemsByQuery call for more information on the orderByClause. |
TS_SUBMITDATE ASC |
Provider Types | |
Execution: Provides functionality for executing deployment tasks |
Enabled |
Deployment Unit: Provides functionality for linking deployment units |
Not Supported |
Request: Provides functionality for associating requests |
Enabled |
Date/Time field format:
2015-08-03T11:12:59+03:00
Extended Fields configuration format:
RLM_TASK_OWNER:USER,(;)CREATED_DATE:DATETIME
Extended Fields multi-values format:
admin,(;)bill
Supported types:
TEXT (Text) USER (User) MULTI_USER (Multi-User) DATETIME (Date/Time) SINGLE_SELECTION (Single Selection) MULTI_SELECTION (Multi-Selection) SINGLE_RELATIONAL (Single Relational) MULTI_RELATIONAL (Multi-Relational) NUMERIC (Numeric)
Copyright © 2012–2015 Serena Software, Inc. All rights reserved.