Component Version Actions Configuration Details

The Component Version Actions configuration provides functionality for Deployment Automation executions, where deployment tasks deploy component versions.

Field Descriptions

The field descriptions are included in the UI. While creating or editing a base or configuration, point to a field name to view its description.

A few fields that may need additional explanation are described in the following table.

CAUTION:
Field Description Example Values

DA Server URL

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

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

The URL that points to 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

The variables passed along with the notification to the recipient ${p:request.id}:${p:finalStatus}

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 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.

Wait for Callback for Component Process

Select this to wait for the component process to respond with results.
Note: Notification from completed component processes cannot be automatically detected. You must specially configure the process in Deployment Automation. For more information, see solution S141306 on the Knowledgebase.

Show Component Process Action

Select this to enable users to select Run Component Process when using this configuration.

Use Custom URL

Select this to allow a custom URL for the application process request and component process request. This is used in conjunction with the following fields.

Application Process Request URL Template

If the Use Custom URL field is selected, this template is used to generate the hyperlink to view the content of the DA application request app#applicationProcessRequest/%REQUEST_ID%

Component Process Request URL Template

If the Use Custom URL field is selected, this template is used to generate the hyperlink to view the content of the DA component process request app#componentProcessRequest/%REQUEST_ID%
Show Application Process Action Select this to enable users to select Run Application Process when using this configuration.
Show Application Process Action (One Component) Select this to enable users to select Run Application Process (One Component) when using this configuration. This action limits the component selection to one component.
Note: Use this selection if you want to enforce a one-to-one relationship between a deployment task and a deployment unit.