Configuring a check for the uniqueness of product values

By default, IXIASOFT CCMS checks 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.

Note: This can be applied within a Hosted environment, but only within a test server.
For example, 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>
The name (specified in the <name> element) must always be unique within a deployment. You can configure the CCMS to check the uniqueness of any other element in the .product file.
You define the list of unique values in the releasemanagement.xml file, inside the <uniquekeys> element. For example, let's say that you also wanted the product code to be unique within a deployment. In this case, 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 a unique value:
  1. Open the TEXTML Administration perspective by clicking the TEXTML Administration shortcut on the tool bar. If the shortcut is not displayed, follow these steps:
    1. Select Window > Perspective > Open Perspective > Other
    2. Click TEXTML Administration.
    3. Click Open.
  2. In the TEXTML Administration view, double-click the server. If your server is not displayed in the view, you must add it to the view.
  3. When the Connect as dialog opens, type your username and password and click OK.
  4. Double-click the name of your Content Store to open a connection to it.
  5. In the repository's /system/conf collection, check out the releasemanagement.xml file and open it with a text editor.
  6. 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>
-->
  7. If necessary, uncomment the <uniquekeys> element.
  8. Add a <key> element for each product value that must be unique within a deployment.
  9. Save, close, and check in the releasemanagement.xml file.
  10. 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 IXIASOFT CCMS > Synchronize Configuration. Additionally, have an administrator refresh IXIASOFT CCMS Web so that users will see the change reflected there.