Adding Base Configurations

A base plugin configuration must be created for each set of configurations. It stores connection information and other shared properties and enables you to quickly create configurations of different types using that information.

Tip: You can clone existing base configurations to add new ones. Just select the base you want to clone and click the Clone option (). During the clone you can change settings as needed for the new base.

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 base 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 Add Configuration button ( ).
4. Give a unique title for the base that encompasses the scope of the configurations that will inherit its settings.
   Tip: Consider including the server name if you have configurations for multiple servers, integrating product version, plugin version, or any 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 BASE.
7. Fill out the remaining fields. .
8. If you do not want to make the configuration visible for selection by end users immediately upon creation, click the Make Configuration Active button to turn it off. By default it is on.
   Tip: When this option is off, it is white. You can also view the tooltip to see the current setting.
9. Click Validate to test the connection.

   An invalid status will not prohibit use of the plugin if you later use the plugin with valid connection values, such as a valid user ID through Single Sign-On (SSO) or through a configuration override.

   Note: If you use SSO, be aware of the following:

   • The connection validation is attempted using the currently logged in SBM user. This may not be the user you want to use for the connection when you use the plugin.
   • Since the user ID used during configuration must be an SBM managed administrator, if you want to validate the connection using the user ID that you will use for SSO, you must make that user ID a managed administrator.