Adding Plugins

You will need to add a default plugin to Release Control only if the plugin has somehow been removed from your system or if you have installed a new version of the plugin. If you have just installed a non-default or custom plugin, you will need to add it.

If the plugin (or version of the plugin) you want to use is already added, continue with Adding or Updating Configurations.

To add a plugin to Release Control:

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

   http://serverName/workcenter/tmtrack.dll?shell=swc&StdPage&template=rlm%2fprovideradmin

   Tip: The link for your installation is in SBM Configurator. Just select the Release Control tab and click the link.

2. At the top of the page, click the Add Plugin link.

3. Enter the required fields for the plugin.

   Note: The XML Context File field references an XML file included in the plugin, and the name in this field must exactly match the referenced file name.

   You do not need to enter the path; the XML file is in the provider jar file previously installed into the application server.

   Atlassian JIRA Software:

   • Name: Atlassian JIRA Software Provider
   • Description: The Atlassian JIRA Software RLC provider implements the request provider type for the Atlassian JIRA Software integration.
   • XML Context File: serena-provider-jira-1_0.xml

   CA Nolio:

   • Name: CA Nolio Provider
   • Description: The CA Nolio RLC provider implements the execution provider type for the CA Nolio integration.
   • XML Context File: serena-provider-nolio-1_0.xml

   ChangeMan ZMF*:

   • Name: ChangeMan ZMF Provider
   • Description: The Serena ChangeMan ZMF RLC provider implements execution and deployment unit provider types for the ChangeMan ZMF integration.
   • XML Context File: serena-provider-zmf-1_0.xml

   Dimensions CM*:

   • Name: Dimensions CM Provider
   • Description: The Serena Dimensions CM RLC provider implements execution, deployment unit, and request provider types for the Dimensions CM integration, where requests are associated with release package requests and baselines are associated with deployment units.
   • XML Context File: serena-provider-dim-1_0.xml

     ------------------

   • Name: Dimensions CM Request Provider
   • Description: The Serena Dimensions CM Request RLC provider implements execution and deployment unit provider types for the Dimensions CM integration, where requests are associated with deployment units.
   • XML Context File: serena-provider-dimrequest-1_0.xml

   Jenkins:

   • Name: Jenkins Provider
   • Description: The Jenkins RLC provider implements the execution provider type for the Jenkins integration.
   • XML Context File: serena-provider-jenkins-1_0.xml

   SBM*:

   • Name: SBM Provider
   • Description: The Serena Business Manager RLC provider implements execution and request provider types for the SBM integration.
   • XML Context File: serena-provider-sbm-1_0.xml

   SDA*:

   • Name: SDA Component Version Provider
   • Description: The Serena Deployment Automation RLC provider implements execution and deployment unit provider types for the SDA Component Version integration.
   • XML Context File: serena-provider-sdacomponentvers-1_0.xml

     ------------------

   • Name: SDA Snapshot Provider
   • Description: The Serena Deployment Automation RLC provider implements execution and deployment unit provider types for the SDA Snapshot integration.
   • XML Context File: serena-provider-sdasnapshot-1_0.xml

   ServiceNow:

   • Name: ServiceNow Provider
   • Description: The ServiceNow RLC provider implements execution and deployment unit provider types for the ServiceNow integration.
   • XML Context File: serena-provider-servicenow-1_0.xml
4. Click Add Plugin.
   Tip: If the Add Plugin button remains grayed out, try clicking in the Description field after filling out the XML Context File field.

   If you receive an error that the plugin does not exist even though you have installed it, ensure that you restarted SBM Tomcat after copying the jar files to the server and that the XML file name is entered exactly as documented and has no extra blanks or hidden characters.

   Important: If you try to add a version of the plugin that isn't installed, the Add Plugin will fail. See Installing Plugins.

   * Default plugin