By default, IXIA CCMS confirms that product and library names are
unique within a content store, but you can configure it so that other values for products
and libraries are unique as well.
About this task
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.
Procedure
-
In the TEXTML Administration perspective, connect to your server.
-
Locate the releasemanagement.xml file in the repository's /system/conf collection.
-
Check out the file and open it for editing.
-
Locate the
<uniquekeys> element at the end of the
file:
<!-- index is name of index defined in system index -->
<!--
<uniquekeys>
<key type="PRODUCT" index="code" xpath="//*[contains(@class, ' product/code ')]"/>
</uniquekeys>
-->
-
If necessary, uncomment the
<uniquekeys> element.
-
Add a
<key> element for each product or library value
that must be unique within a content store.
In addition to the <code> element that is included by
default, you can also make the following elements unique:
| Element |
Class |
| description |
product/description |
| aliases |
product/aliases |
| productlines |
product/productlines |
| components |
product/components |
Tip: It's easiest to copy and paste an
existing <key> and edit it.
-
Save, close, and check in the file.
-
Inform users of the changes.
The changes are automatically applied
once users close and then reopen their CCMS Desktop.
Users can also apply the changes without restarting their CCMS Desktop by clicking . Additionally, refresh IXIA CCMS Web so that
users see the change reflected there.
