6.7

Table 6‑1. Conflict Types (Continued)
Conflict
Properties used to
compare Category
Objects Conflict Types
Conflicting
Properties Conflict Resolution Options
Controller, but with a
different privilege list, then
the privilege lists for both
roles are merged.
n
SKIP. Do nothing. The specific
role is skipped.
Tag Category
conflict: A
category name
must be unique in
a
Platform Services
Controller.
n
name: Name of the
category.
n
cardinality:
Cardinality of
Category, either
Single or Multiple.
n
associableEntityTy
pe: List of
vCenter Server object
that can be associated
with a tag from this
category. A value of
All indicates all
vCenter Server
objects.
Only one type of
conflict can be seen
while importing Tag
Categories,
CategoryName
conflict. This conflict
indicates that a
category with the
same name exists in
the target
Platform Services
Controller but with
different properties
(cardinality or
associableEntityT
ype).
Properties that
can be conflicting
for conflict type
CategoryName
can be at least
one of two types:
Cardinality or
AssociableType
s.
n
COPY. A copy of the conflicting
category is created in the
target
Platform Services Controller,
with –-copy appended to the
category name. The new
category is created with the
same property name as in the
source
Platform Services Controller.
All the tags that were present
under this category is imported
under the newly created
CategoryCopy.
Note
The default resolution option to
resolve CategoryName
conflicts is COPY.
n
MERGE. Conflicting properties
are merged with the category
that is already present in the
SSO. Properties are merged
as follows:
a Description. The
description that is already
present is used.
b Cardinality. Cardinality
cannot shrink. If there is a
cardinality conflict, the
cardinality is set to
multiple. It cannot be
reduced to single.
vCenter Server Installation and Setup
VMware, Inc. 153