Configure the uniqueness of product values

By default, IXIA CCMS confirms that product names are unique within a deployment, but you can configure it so that other values in the .product file are unique as well.

You can configure the CCMS to ensure the uniqueness of any element, other than the product name, in the .product file. The name, specified in the <name> element, must always be unique within a deployment. You define the list of unique values in the releasemanagement.xml file, inside the <uniquekeys> element.

Important: Make configuration changes in a test environment and confirm they work before copying them to a production environment.
Consider the following template file for a product:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE product PUBLIC "-//IXIA//DTD CMS Product//EN" "product.dtd">
<product id="id" base="">
	<name/>
	<productmeta>
		<code/>
		<description/>
		<aliases/>
		<productlines/>
		<components/>
	</productmeta>
	<relatedproducts/>
	<releases/>
</product>
Suppose you also wanted the product code to be unique within a deployment. To do so, you add the following <key> element to the releasemanagement.xml file. 
<uniquekeys>
   <key type="PRODUCT" index="index_name" xpath="xpath"/>
</uniquekeys>
where:
index_name

Is the name of the index defined for this field in the Index Definition document.
xpath Is the XPATH of the element that must be unique.
For example:
<uniquekeys>
   <key type="PRODUCT" index="code" xpath="//*[contains(@class, ' product/code ')]"/>
</uniquekeys>

To configure the uniqueness of product values:

  1. In the TEXTML Administration perspective, connect to your server.
  2. Locate the releasemanagement.xml file in the repository's /system/conf collection.
  3. Check out the file and open it for editing.
  4. Locate the <uniquekeys> element.
    In the initial configuration, this field is commented out. For example:
    <!-- index is name of index defined in system index -->
<!-- 
<uniquekeys>
   <key type="PRODUCT" index="code" xpath="//*[contains(@class, ' product/code ')]"/>
</uniquekeys>
-->
  5. If necessary, uncomment the <uniquekeys> element.
  6. Add a <key> element for each product value that must be unique within a deployment.
  7. Save, close, and check in the file.
  8. Inform users of the changes.
    The changes will be applied automatically once users close and then reopen their CCMS Desktop. Users can also apply the changes without restarting their CCMS Desktop by clicking IXIA CCMS > Synchronize Configuration. Additionally, refresh IXIA CCMS Web so that users will see the change reflected there.