Echelon Enterprise Services 2.0 - Manual (Page 41)

Echelon Enterprise Services 2.0 User’s Guide 31
8. After the SmartServers have been upgraded, they are automatically rebooted. When a
SmartServer reboot has finished, STATUS_DONE is displayed in the Status box.
The total time of the upgrade and reboot is approximately 15–25 minutes depending on the
complexity of your network configuration.
Creating an i.LON Template
You can configure a network on a single SmartServer operating in LNS mode or Standalone mode,
make a template of that SmartServer’s configuration, and then deploy that template on multiple
SmartServers. This lets you create a “golden image” of one site and then replicate that image multiple
times on identical sites. For example, if you have several buildings that have the same physical
network, you can create an i.LON template for one building, and then deploy the template to
automatically configure and install the other buildings. If your site uses LNS network management
services, the i.LON template also includes an image of the LNS network database to which the
SmartServer is synchronized. When you deploy the i.LON template, an identical LNS network
database is created for each deployment site.
Specifically, you can logically add external devices and their data points to the development
SmartServer, configure the development SmartServer’s embedded applications (Alarm Generator,
Alarm Notifier, Data Logger, Scheduler, and so on), configure your custom FPM applications, and
create custom SmartServer Web pages. After you have finished configuring your development
SmartServer, you can create a template of it.
You can then deploy the template. When you deploy a template, the networks attached to the
deployment SmartServers will have the same configuration as the development network. This means
that the deployment SmartServers will have the same external devices, external data points,
SmartServer applications, FPM configuration, and custom SmartServer Web pages as the development
SmartServer.
You can also use templates to pre-configure the built-in applications on a single development
SmartServer and then deploy the template. A common use-case scenario is the configuration of
multiple SmartServers at one site. For example, on one development SmartServer, you can configure
one or more schedulers, data loggers, type translators, or other applications on the SmartServer’s