Deployment Automation Plugin → Deployment Automation Plugin Configuration Overview → Deployment Automation Base Configuration Details
Add a base configuration to define shared properties for a set of Deployment Automation item and action configurations.
Field Descriptions
The field descriptions are included in the UI. While creating or editing a configuration, point to a field name to view its description.
The base configuration fields are described in the following table.
| Field | Description | Example Values |
|---|---|---|
|
DA Server URL |
Enter the URL for the
DA
server.
If using DA 6.1.3 or earlier, use: http://<DA_SERVERNAME>:8080/serena_ra |
http://<DA_SERVERNAME>:8080/da |
|
DA Application Request Process link |
This link is used to open the page in the
DA
web client when the component version or snapshot link is clicked in a view.
If using DA 6.1.3 or earlier, use: /serena_ra/#applicationProcessRequest/ |
/da/#applicationProcessRequest/ |
|
DA Post Deploy URL |
Enter the URL for the location in the Release Control installation where the DA notification service is running. | http://<RLC_SERVERNAME>:8085/rlc/rest/deploy/autoprocess/notification/SDA/ |
|
DA Post Deploy Message Variables |
Enter the variables to be passed along with the notification to the recipient. | ${p:request.id}:${p:finalStatus} |
| User Name | If specified, this user name is used to log in to DA, whether or not Use Single Sign-On (SSO) is selected. If user name is not specified and Use Single Sign-On (SSO) is selected, the currently logged in SBM user is used for SSO. User name is required to log into Deployment Automation if Use Single Sign-On (SSO) is not selected. | |
| Password | DA password | |
|
Use Single Sign-On (SSO) |
Select this to allow the provider service to
log in to the
DA
system using the authentication token of the user.
If you select this, ensure that SSO is enabled for DA as documented in "Configuring Tomcat for SSO" in the Deployment Automation Integration Guide. Note: If
Use Single Sign-On (SSO) is selected,
when
DA
is accessed the first time from
Release Control,
if it doesn't exist, the corresponding user is automatically created in
DA
in the
Single Sign On Authentication Realm. Before accessing
DA
through
SSO,
either ensure that you have set the
DA
security options to give adequate default permissions to new users, or manually
create the users and assign them to the appropriate group in
DA.
|
|
| Application Filter | Enter a comma-separated list of partial names used to filter application names. The text is matched anywhere in the name. For example, DB returns Sample DB and DBUpgrader applications. | |
| Environment Filter | Enter a comma-separated list of partial names used to filter environment names. |
Related Topics
Copyright © 2012–2017 Serena Software, Inc., a Micro Focus company. All rights reserved.