Echelon Enterprise Services 2.0 - Manual (Page 59)

Echelon Enterprise Services 2.0 User’s Guide 49
6. You can expand the Projects, Backups, or Templates folder to see the imported file.
Note: If you import a project that has the same name as an existing project on your computer, the
import will fail.
Using the i.LON AdminServer Remotely
You can access the i.LON AdminServer from a remote EES 2.0 client (a computer that is different
than your LNS Server/EES 2.0 computer), and perform administrative tasks on the SmartServers in an
i.LON project just as if you were working on your local LNS Server/EES 2.0 computer.
To access the i.LON AdminServer from a remote EES 2.0 client, open a Web browser and enter the
following IPv4 address:
http://<LNS Server/EES 2.0 Computer IP Address>/EES/AdminService/v4.0/index.htm.
If your SmartServer is synchronized to an LNS network database, you must access the i.LON
AdminServer from the same LNS Server/EES 2.0 computer that contains the LNS network database.
If you access the i.LON AdminServer on a different LNS Server/EES 2.0 computer that does not
contain the LNS network database, the administrative tasks performed on the i.LON project that
contains the LNS network database will fail (for example, creating and deploying an i.LON template,
backing up and restoring an i.LON image, and so on). This is because the i.LON AdminServer will
not be able to locate the LNS network database.
Using Rapid Deployment
You can use i.LON AdminServer to automatically install single-channel LNS managed or standalone
networks containing up to approximately 20 devices. i.LON SmartServer 2.0 features a new device
discovery method for acquiring the Neuron IDs of the devices on the network. With the device
discovery method, the SmartServer searches the physical network for uncommissioned devices and
matches them based on program ID to the devices stored in a SmartServer or LNS network database.
The SmartServer then automatically installs the discovered devices.
Automatic network installation eliminates the cumbersome manual tasks associated with network
installation such as matching up device configurations in a network tool with the physical devices on
the network, and pressing service pins on the devices to commission them.
To install devices automatically, follow these steps:
1. Prepare the development computer and SmartServer for the network design and installation. To
do this, follow these steps:
a. Upload the resource files provided by the device manufacturer for the devices being installed
to the root/L ON W ORKS /types/user folder on the flash disk of the development SmartServer.
b. Upload the XIF files provided by the device manufacturer for the devices being installed to
the root/L ON W ORKS /import folder on the flash disk of the development SmartServer.
c. If you are using LNS network management services and you plan on using the development
as the network interface, configure the development SmartServer as an RNI on your
development computers using the L
ON W ORKS Interfaces Control Panel application. See
Configuring the SmartServer as a Remote Network Interface in Chapter 3 of the i.LON
SmartServer 2.0 User’s Guide for more information on how to do this.
d. If you are using LNS network management services, add an LNS Server to the LAN in the
SmartServer Web interface. To do this, right-click LAN icon at top of navigation pane, point
to Add Host, click Server. Click LNS Proxy option, and then enter IP address of system
computer running LNS Turbo Server 3.25 (or newer). See Using the LNS Proxy Web Service
in Chapter 3 of this document for more information on adding an LNS Server to the LAN.