XMS Configuration Guide
17-11
Propagating Assets to Other Xmedia Servers
Information Propagation Exceptions
Information Propagation Exceptions identify that a problem has occurred during the
propagation process, but the problem was resolved without any immediate user
intervention required to proceed.
An Information Propagation Exception is raised when:
•
a name clash between two categories (with the same category ID) prompts the
automatic renaming and/or moving of a recipient server’s category
•
a propagated asset has been uncategorized by a non-propagation user session
•
a propagated asset has been deleted by a user
•
a propagated asset has been updated by a user session
Since Information propagation exceptions are resolved without any need for user
intervention, they can easily be cleared from the Exception List using the
C
LEAR
button.
Category Propagation Exceptions
Category Propagation Exceptions identify that a name clash has occurred between the
propagated category on the propagation server and an existing category on the recipient
server. In such a case, the categories would have different internal IDs, despite having the
same name. As a result of the naming conflict, the existing category on the recipient server
cannot be moved or renamed automatically, like it would have been for an Information
Exception. The Category Exception still allows the category to be propagated, but the
propagation category is given a temporary name on the recipient server until the name
clash is resolved (figure
17-9
). The propagated category is easily identifiable by its
temporary name, which always ends with
_Propag
.
Figure 17-9. A category is added to the recipient server using a temporary name
The Category Propagation Exception’s message suggests how to appropriately resolve the
name clash. For example,
“T
O
CLEAR
THE
EXCEPTION
,
MAKE
IT
POSSIBLE
FOR
CATEGORY
Image\Apples_Propag
TO
BE
RENAMED
TO
Apples
.”
Figure
17-10
demonstrates that any attempt to clear the exception will be rejected until the
name conflict is resolved. Therefore to resolve the conflict, it is suggested that the category
Apples
be renamed, moved, or deleted, and then clear the Category Exception. Clearing
the Category Exception triggers the system to automatically rename the
Apples_Propag
category to
Apples
.
Figure 17-10. The category name conflict must be resolved before the exception can be cleared