17-10
XMS Configuration Guide
Propagating Assets to Other Xmedia Servers
Resolving Propagation Exceptions
Propagation exceptions are alerts raised on a recipient server when a problem occurs
during the propagation of assets. In most cases, these exceptions are triggered by a naming
conflict between the propagable category or assets on the propagation server and the
category on the recipient server.
In addition to alerting users of a problem, propagation exceptions allow assets and
categories to be propagated to a recipient server, despite name clashes, by temporarily
renaming the propagated asset or category. The exception produces a message which
identifies what conditions need to be fixed for the exception to be cleared (figure
17-8
). For
example, the offending asset on the recipient server may need to be renamed, deleted, or
moved so that the propagated asset can use its name and location. Once the user properly
fixes the problem, they can clear the exception by pressing the
C
LEAR
button.
Propagation exceptions always occur on a recipient server, never on the propagation
server. The propagation server is merely notified that an exception occurred on one of its
recipient servers. When an exception is raised, the
R
EFRESH
L
IST
button is highlighted on
the recipient server’s Xmedia Server Control Panel’s Propagation Exceptions page. Click
the
R
EFRESH
L
IST
button to update the Exception List with the most current exceptions.
The following sections describe each of the three (3) types of propagation exceptions, as
well as providing instructions for how to resolve and clear these exceptions.
•
“Information Propagation Exceptions” on page 17-11
•
“Category Propagation Exceptions” on page 17-11
•
“Categorisation Propagation Exceptions” on page 17-12
Figure 17-8. Propagations Exceptions alert users of problems that occurred during propagation
Propagation Exceptions
Exception message