Grass Valley GV STRATUS Installation v.3.1 - Manual (Page 173)

application has its own XML file in which information is stored. You can keep the applications in
synch by using an orderly task flow as you configure the K2 SAN.
When doing initial installation and configuration tasks, you can export/import system information
from one application’s XML file to the other application’s XML file. You can also merge from
K2Config into an existing SiteConfig system description. These export/import/merge features support
a one-time process in which a system as described in the XML file of one application is imported
into the XML file in the other application. The target XML must not already contain the system
being imported.
When you change a setting in one application, it is not automatically updated directly in the other
application. The applications do not communicate dynamically with one another. However, both
applications can read settings as currently configured on the actual physical device and update their
XML file accordingly. This is the method you must use to keep the applications in synch.
When you change a setting that is managed by both applications, you should change it first in
SiteConfig, as a general rule. This application gives you the best context for the system as a whole
and provides features to identify and verify changes. Once the change is implemented on the actual
physical device, you must then open the relevant page in the K2Config application. This causes the
K2Config application to refresh its settings from the device and write the change to its XML file.
It also allows you to verify your change within the context of the K2Config application.
The following table summarizes operations that involve interaction between SiteConfig and K2Config.
Additional information Task flow context and policies Operation
This operation creates a K2 SAN in
K2Config with SiteConfig defined
devices. Uses the site name to check
if the K2 SAN already exists. The
operation will not import if the K2
SAN exists with the same name. The
operation can import all sites which
are K2 SANs from a single system
description file in a single import step. Use this operation for initial install/commission
(greenfield) sites. First define the site topology
using SiteConfig and complete network
configuration and software deployment. Then
import the SiteConfig system description into
K2Config and complete the K2 SAN
configuration. Import SiteConfig system
description file into
K2Config
This operation creates a SiteConfig site
with K2Config defined devices. The
operation removes all other sites. Use this operation when you're running
SiteConfig for the first time at a site with
existing K2 SANs that have already been
configured with K2Config. This allows you to
seed the SiteConfig system description with
device information that is already in the
K2Config XML file. After you have done this
operation for the first time, do not do it again. Import K2Config XML
into SiteConfig
This operation creates a SiteConfig site
with K2Config defined devices but
leaves existing sites as is. Use this operation when you've already defined
some sites using SiteConfig and you later want
to bring in another K2Config defined K2 SAN
that doesn't exist in SiteConfig. Do not merge
a K2Config XML that you've already merged.
If you do so, it is likely that SiteConfig will
create a new site with the same devices. Merge K2Config XML
into SiteConfig system
description
2013 12 19 GV STRATUS Installation and Service Manual 173
Understanding system concepts