Adding Action and Item Configurations

Plugin configurations provide connection information, product-specific details, and filters telling the plugin what data to obtain from the integrating product. You may use multiple configurations to point to different systems or projects, to use different versions of an integrating product or plugin, or to use different filters.

Before you can use a plugin, you must at minimum update it with your specific connection information for the configuration. Each of the plugin configurations in the default implementation have example values, but you'll need to update these according to your own implementation.

If you are using one of the plugins with example configurations, you can update the example configurations with your connection information and other details or you can add new configurations.

Tip: You can clone existing configurations to add new ones. Just select the configuration you want to clone and click the Clone option (). During the clone you can change settings and select a different existing base from the same plugin.

Any password or other secure fields are included, but will remain shown as asterisks in the clone configuration.

Important: The Release Control Administration options can be performed only by users with Managed Administrator privileges.

To add a plugin configuration:

1. In your Web browser, enter the URL for Release Control Administration. For example:

   http://serverName/workcenter/tmtrack.dll?StdPage&Template=rlc/admin

   Tip: The link for your installation is in SBM Configurator on the Release Control page.
2. Select Administration > Configurations.
3. Click the + beside the base that you want to use to create the configuration.
4. Give a unique title and description for the configuration.
   Tip: The configuration title is the name that appears in the drop-down selection when adding objects such as requests, deployment units, and deployment tasks. Consider including the server name if you have configurations for multiple servers. You may also want to include integrating product version, plugin version, or other distinguishing information.
5. In the Plugin Instance field, select the name of the plugin you want to use for this instance.
6. In the Type Name field, select the specific implementation of the provider type that you want to use, such as an item or actions implementation.
7. Ensure that the Base Configuration field has the correct base selected.
   Note: When creating directly from an existing base using the + option, you cannot change the base configuration name. When creating a configuration through the Add Configuration button, you can select a base or select New to create a new one.
8. Fill out the remaining fields.
9. To enter different information in any grayed out fields, select Override.

   The following figure shows a plugin configuration with overrides for the fields Application Filter and Environment Filter.

   

   These overrides:

   • Limit field value selections when adding objects in collections, such as requests, deployment units, and deployment tasks.
   • Are used by the system when it validates and executes tasks.

   If you need to override at a broader level, such as for an entire release package or deployable release train, see Auxiliary Table Level Configuration Overrides.