
XMS Configuration Guide
17-15
Propagating Assets to Other Xmedia Servers
Distributed work order concepts and behaviors
There are a few concepts and behaviors that you need to be aware of regarding the creation
and use of distributed work orders in a hub and spoke propagation system:
•
Even though distributed work orders will exist on that spoke and on the hub, they can
only be created on a spoke server’s Xplorer, Xbuilder, or Xnews applications.
•
Work orders can be created on the hub, even if the hub server is setup for propagation.
The spoke servers, however, will be unaware of these work orders. The work orders
will be recognized as simple work orders (hub-only), not distributed work orders. As a
result, the work order will
not
be prefixed by a spoke ID.
•
Distributed work orders are always “pairwise” between a spoke and the hub. This
means that work orders cannot be distributed between two spokes, or between two
spokes and a hub.
•
The work order workflow on both servers (hub and spoke) must be identical (see
“Setting up a hub and spoke server for distributed work orders” on page 17-16
).
•
If a work order is created on the spoke, jobs cannot be added to the work order from
the hub. The hub is only able to fulfil the distributed work order jobs, not create them.
•
If a distributed work order's job undergoes a transition or is modified on a spoke, it will
also transition or be modified on the hub, and vice versa.
•
If an attachment is added to a distributed work order, it will be added on both servers.
•
An asset that is ingested into a distributed work order on the hub will be propagated to
the spoke’s placeholder, once the work order is finalized.
•
Placeholders are categorized on both the hub and spoke, unless the category does not
already exist on the hub. In such a case, a placeholder is still categorized on the spoke,
but it is
not
categorized on the hub. The placeholder category information on the hub
would simply display
I
MAGES
as the category.
•
If a category on the hub is set to automatically propagate to the spoke associated with
the distributed work order, editing the hub’s category by ingesting and/or categorizing
an asset, triggers a propagation to the spoke. This may result in the duplication of the
asset in different categories on the spoke (one replacing the placeholder, another being
the ingested asset). These assets will essentially be the same asset, only stored in two
different categories. As a result, changes to one of these assets are reflected in the
other. Therefore, it is advisable to ingest the asset into the same category as the
placeholder.