Echelon Enterprise Services 2.
Echelon, LON, LONWORKS, LonTalk, Neuron, LONMARK, 3120, 3150, LNS, LonMaker, and the Echelon logo are trademarks of Echelon Corporation registered in the United States and other countries. LonPoint and LonSupport are trademarks of Echelon Corporation. Other brand and product names are trademarks or registered trademarks of their respective holders.
Table of Contents Preface ..................................................................................................... v Purpose .......................................................................................................... vi Audience......................................................................................................... vi Hardware Requirements................................................................................. vi SmartServer 2.0 Upgrade Requirements ....
Using the LNS Proxy to Integrate the SmartServer with LNS Tools....... 63 Synchronizing the SmartServer........................................................ 63 Copying External Data Points to the SmartServer ........................... 73 Troubleshooting the LNS Proxy Web Service ...............................................
Preface Echelon Enterprise Services 2.0 includes the i.LON AdminServer and the LNS Proxy Web service. The i.LON AdminServer is a Web application that you can use to manage and deploy SmartServers. The LNS Proxy is a Web service enables the SmartServer to directly communicate with LNS Server computers. Echelon Enterprise Services 2.
Purpose This document describes how to use the i.LON AdminServer and LNS Proxy Web service included in Echelon Enterprise Services 2.0 (EES 2.0). Audience This guide is intended for system designers and integrators with an understanding of control networks. Hardware Requirements Requirements for the running the Echelon Enterprise Services 2.0 software are listed below: • Microsoft® Windows Vista® or Microsoft Windows® XP.
SmartServer 2.0 Upgrade Requirements You must have a SmartServer 2.0 license for each SmartServer 1.0 (a SmartServer running the Release 4, 4.01, or 4.02 firmware) or i.LON e3 plus Server to be upgraded to SmartServer 2.0 (a SmartServer running the Release 4.03 firmware). You can the use the new i.LON AdminServer Web application included with Echelon Enterprise Services 2.0 to automatically upgrade your SmartServers. For more information on using the i.
Content This guide includes the following content: • Introduction. Introduces EES 2.0, describes the i.LON AdminServer and LNS Proxy Web Service included with EES 2.0, and describes how to install the EES 2.0 software. • Using the i.LON AdminServer. Describes how to use the i.LON AdminServer to create an i.LON project, create and deploy i.LON templates, upgrade i.LON images, backup and restore i.LON images and LNS network databases, and export and import i.LON projects, templates, and backups.
If you need more information on how to use a particular dialog in the i.LON AdminServer or SmartServer Web interface, you can click the question mark icon (?) in the upper right-hand corner of the dialog to open a new window with context-sensitive help for that dialog. Viewing the EES 2.0 ReadMe The EES 2.0 ReadMe provides descriptions of known problems, if any, and their workarounds. To view the EES 2.0 ReadMe, click Start, point to Programs, point to Echelon i.LON SmartServer 2.
x Region Europe Languages Supported English German French Italian Contact Information Echelon Europe Ltd. Suite 12 Building 6 Croxley Green Business Park Hatters Lane Watford Hertfordshire WD18 8YH United Kingdom Phone: +44 (0)1923 430200 Fax: +44 (0)1923 430300 lonsupport@echelon.co.uk Japan Japanese Echelon Japan Holland Hills Mori Tower, 18F 5-11.2 Toranomon, Minato-ku Tokyo 105-0001 Japan Phone: +81.3-5733-3320 Fax: +81.3-5733-3321 lonsupport@echelon.co.
1 Introduction This chapter introduces EES 2.0, describes the i.LON AdminServer and LNS Proxy Web Service included with EES 2.0, and describes how to install and activate the EES 2.0 software. Echelon Enterprise Services 2.
Introduction Echelon Enterprise Services 2.0 includes the new i.LON AdminServer and the LNS Proxy Web service. The i.LON AdminServer is a new Web application that you can use to manage and deploy SmartServers. You can use the i.LON AdminServer to perform batch operations on your SmartServers. For example, you can backup or upgrade multiple SmartServers at the same time, or you can create a template of one SmartServer and deploy that template on multiple SmartServers simultaneously.
Each time the source data point in the Web connection is updated, the data log file is downloaded to the LonWorks\iLON\EnterpriseServices\repository\ees-lnsproxy\ReceivedFiles folder on your computer. You can manually update the source data point using the Show Value dialog, the Data Points: View Web page, a custom SmartServer Web page, or other method.
Note: When you save your device as a template, clear the Clear from Template check box in the Network Management property as described in step 6. This saves the network management commands you set in steps c-d in the device template. These network management commands will be executed when new devices created from the device template are instantiated. 2.
c. In the Name property, enter a descriptive name for the device. d. Expand the Template folder to show all the folders in the LonWorks\iLON\EnterpriseServices\repository\ees-lnsproxy\config\template folder on your computer. Expand the folder containing the template to be used to create the device and then click that template. e. Click OK to return to the SmartServer Web interface. f. Click Submit.
Installing and Activating EES 2.0 Software The following sections describe how to install and activate the EES 2.0 software. You can install Echelon Enterprise Services 2.0 (EES 2.0) over previous versions of the Echelon Enterprise Services provided in releases 4, 4.01, and 4.02 (EES 1.0). For the 4.03 release, EES 2.0 requires activation. To install and activate the EES 2.0 software, follow these steps: 1. Install the i.LON SmartServer 2.0 software. 2. Install LNS Turbo Edition (3.
3. Click Install Products. The Install Products dialog opens. 4. Click Echelon i.LON SmartServer 2.0 Enterprise Services. If EES 1.0 is installed on your computer, the following dialog opens prompting you to confirm that you want to upgrade to EES 2.0. Click Yes to upgrade. Echelon Enterprise Services 2.
8 5. The EES 2.0 software installer opens. 6. Read the information on the Welcome window and click Next. The License Agreement window appears.
7. Read the license agreement (you can read a printed version of the license agreement in Appendix E of the i.LON SmartServer 2.0 User’s Guide). If you agree with the terms, click Accept the Terms and then click Next. The Customer Information window appears. 8. Enter your name and company name in the appropriate fields. The name and company may be entered automatically based on the user currently logged on and whether other Echelon products are installed on your computer. Click Next.
10. A dialog opens prompting you to select whether existing EES 1.0 data files in the LonWorks\iLON\EnterpriseServices folder are to be preserved or deleted. Select Yes to preserve the EES 1.0 data files, or select No to remove all the EES 1.0 data files. 11. The Port Selection window opens. 12. Enter the port used by the LNS Proxy Web service to transmit and receive SOAP/HTTP requests. The default port is 80. You can verify that the selected port is available by clicking Check.
14. Enter a user name and password to be used for accessing the LNS Proxy Web service. The default user name and password are both ilon. You should change the default user name and password to protect your LNS network databases. You can do this in the EES tray tool icon that is installed on your computer by the Echelon Enterprise Services installer. See Checking LNS Proxy Web Service Access in Chapter 3 for more information on changing the user name and password. Click Next. The Setup Type window appears.
16. Click Install to begin the Echelon Enterprise Services installation. 17. After the Echelon Enterprise Services has been installed, the Tomcat 6 Server starts and an EES tray tool ( ) is added to the notification area of your desktop (see Using the Echelon Enterprise Services Tray Tool in Chapter 3 for more information). The LNS Proxy Web service is enabled and ready for setup on your SmartServer (see Setting Up the LNS Proxy Web Service in Chapter 3 for more information).
19. Click Finish. The Echelon Enterprise Services ReadMe file appears. When you finish reading the ReadMe file, close the window. 20. A dialog opens prompting you to reboot your computer now or later. Click No to reboot your computer later. You will reboot after installing LNS Server Service Pack 5 as described in the next section. Installing LNS Server Service Pack 5 You must install LNS Server Service Pack 5 on your LNS Server computer. LNS Server Service Pack 5 is required by EES 2.
5. Click Install to begin the LNS Server Service Pack 5 installation. 6. After LNS Server Service Pack 5 has been installed, a window appears stating that the installation has been completed successfully. 7. Click Finish. Installing NodeBuilder Resource Editor To use the new fast data log transfer feature, the device resource files for the subject data points must be installed on your LNS Server computer running EES 2.0.
LNS Server computer. If you send binary data logs from your SmartServer to be converted to .CSV format and the device resource files for the subject data points are not present, the conversion will fail. To install NodeBuilder Resource Editor 3.14.02 and LonMark Resource Files 3.13, click the Echelon i.LON SmartServer 2.0 button in the taskbar to return to the i.LON SmartServer 2.
The Setup – System Info Web page opens. The Ethernet MAC Address is the first property listed under the Ethernet header. 16 4. When you receive your EES Activation Key (an XML file named Echelon1EES.xml), browse to the LONWORKS\iLON\EnterpriseServices folder on your computer, create a new folder named license, and then copy the EES Activation Key to the license folder. 5. Restart EES 2.0. To do this, right-click the EES tray tool icon and then select Restart Service.
Echelon Enterprise Services 2.
18 Introduction
2 Using the i.LON AdminServer This chapter describes how to use the i.LON AdminServer to manage and deploy SmartServers. It describes how to automatically install single-channel LNS managed or standalone networks containing up to approximately 20 devices. Echelon Enterprise Services 2.
Introduction to the i.LON AdminServer You can use the i.LON AdminServer to create i.LON projects, export and import i.LON projects, create and deploy i.LON templates, upgrade i.LON images, or backup and restore i.LON images and LNS network databases. You can open the i.LON AdminServer on a local EES 2.0 client (an LNS Server computer running EES 2.0), or 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).
4. Select the language to be used for the i.LON AdminServer. The i.LON AdminServer includes English (the default), German, and French languages, but you can work with the i.LON AdminServer in any one-byte or two-byte character language by translating the .properties file in the LONWORKS\iLON\EnterpriseServices\Appserver\webapps\EES\AdminService\v4.0\nls\echelon folder on your computer. See the i.LON SmartServer 2.
7. The i.LON AdminServer – Welcome Web page opens. It may take 1–2 minutes for the i.LON AdminServer Web page to appear. 8. You can now create i.LON projects, upgrade SmartServers, create and deploy i.LON templates, back up and restore SmartServers, and copy i.LON projects, i.LON templates, and backups from one computer to another. This section describe how to perform the following tasks with the i.LON AdminServer: • • • • • • • • Create an i.LON project. Upgrade the SmartServer firmware. Create an i.
2. The Add Project dialog opens. Enter the name for your project. A project name can include up to 256 alphanumeric characters. It may not contain the *, ‘, “, /, <, or > characters. Click OK. 3. Click Submit. 4. Expand the Projects folder to display your new project. 5. Optionally, you can click your project to open the Project Web page. You can use this Web page to add a description for the project and change its icon in the navigation pane. 6.
b. The SOAP Settings dialog opens. c. Enter the following properties: Protocol 24 Select the protocol used by the i.LON AdminServer to connect to the SmartServer (HTTP or HTTPS). The selected protocol must be enabled in the Setup - Security Web page in the SmartServer Web interface; otherwise, the following error occurs when the i.LON AdminServer tries to access the SmartServer: ERROR: WebService reports: "Could not connect to i.
Username Enter the user name for logging in to your SmartServer via HTTP. The default user name is ilon. Password Enter the password for logging in to your SmartServer via HTTP. The default password is ilon. d. Click OK to add the SmartServer to the IP channel. e. If the hostname of the SmartServer you are adding is the same as one already in the project (the default hostname is “SmartServer”), the Enter Name dialog opens.
i. Enter the following information: SOAP Path Enter the path on the SmartServer to which SOAP messages should be transmitted. This is typically the location of the WSDL or ASMX file on the server where it receives SOAP messages. The default path is /WSDL/iLON100.WSDL (the default location of this file on a SmartServer). FTP Port Enter the port the SmartServer uses for FTP communication. The default value is 21. Telnet Port Enter the port the SmartServer uses for Telnet communication.
i. 8. Optionally, you can click a service (or right-click one and click Edit on the shortcut menu) to display additional information, such as the port and user name used by the service. Optionally, you can right-click the SmartServer and select the following options: • TCP/IP Settings. Opens the Setup - Local i.LON SmartServer Web page, where you can modify the SmartServer's TCP/IP Settings. • Security Settings.
28 Using the i.
Upgrading the SmartServer Firmware You can use the i.LON AdminServer to upgrade the firmware on SmartServers running the Release 4, 4.01, or 4.02 firmware (SmartServer 1.0) and i.LON e3 plus Servers to the Release 4.03 firmware (SmartServer 2.0). You can also use the i.LON AdminServer to upgrade your SmartServers later as SmartServer 2.0 service packs are made available. Notes: • To upgrade i.LON e3 plus Servers or SmartServers that have previously been downgraded to the i.
Alternatively, you can click the SmartServer image under the Upgrades icon and then click Install. 30 4. The Install Web page opens. Click a SmartServer within any project in the navigation pane to add it to the list of SmartServers to be upgraded. 5. The Install Web page displays the hostnames and IP addresses of the SmartServers to be upgraded, their current firmware version, and the firmware version to which they are to be upgraded. 6. Click Install to begin the upgrade process. 7.
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.
internal App device, create the template, and then copy the template to one or more development SmartServers that have been set to the factory default settings. After you reboot the deployment SmartServers, the embedded applications on the on the deployment SmartServers will have the same configuration (data points, presets, and so on) as those on the development SmartServer. To create a template, perform the following steps: 1.
network database>-- folder, and is named lns_db\--. If any other administrative task for a SmartServer in the selected project has not been completed or has failed, a dialog opens prompting to confirm that you want to create the template. Note: If the i.LON AdminServer reports “Backup/Restore Failed.
3. The Deploy Web page opens. 4. In the Target property, enter the name of the target. If you do not specify a name, the i.LON AdminServer appends an index to the project name. For example, if the project is named “myProject”, the default name of the Target is “myProject1”. If the i.LON template includes an LNS network database, the Target LNS Database property displays the name of the LNS network database that will be created when the i.LON template is deployed.
automatically, with no further user-interaction required. After the template is deployed and the target SmartServer is rebooted, the target SmartServer will automatically discover the physical devices on the network, match the devices with the devices in the SmartServer or LNS network database, and the commission the devices. This is the default.
8. Username Enter the user name for logging in to your SmartServer via HTTP. The default user name is ilon. Password Enter the password for logging in to your SmartServer via HTTP. The default password is ilon. Click Deploy to deploy the template. The time required to deploy the template may range between 20 to 30 minutes, depending on the size of the template. Note: You can view the status of the current deployment by entering the trace 2 command in the target SmartServer’s console application.
Manually create the LonMaker drawing for the target LNS network database following the next section, Manually Copying a LonMaker Drawing, and then click Close. This step is required because the LonMaker drawing cannot be created automatically. In this step, you use the LonMaker Design Manager to create the LonMaker drawing for the target LNS network database from a copy of the source LNS network database in the i.LON template 12.
15. A remote network interface (RNI) for each deployment SmartServer is automatically created in the LonWorks Interfaces Control Panel application if the i.LON template included an LNS network database. The name of the RNI is #EES#. 16. If you are a deploying an i.
network database is named QSR1, you would create the LonMaker drawing for the QSR1 database following these steps: 1. Stop the LNS Proxy Web service because it is currently accessing the target LNS network database. To do this, right-click the EES tray icon in the notification area, and then click Stop Service on the shortcut menu. 2. Open the LonMaker Design Manager. 3. In the Database Name property under Existing Network, select the deployed LNS network database.
7. The Network Wizard opens. In the Network Name property, enter the name of the deployed LNS network database. In this example, you would enter QSR1. 8. Click Next in the subsequent pages in the Network Wizard to accept the default settings and then click Finish in the Domain Definition window. 9. After the LonMaker drawing for the target LNS network database has been created, close it. 10. Repeat steps 3–9 for each SmartServer to which you are deploying the i.LON template. 11.
13. The deployment SmartServer is synchronized to the target LNS network. Notes: • You can view the status of the synchronization by entering the trace 2 command in the target SmartServer’s console application. For more information on the SmartServer console application, see Appendix B of the i.LON SmartServer 2.0 User’s Guide. • If you have modified the source LNS network database since you deployed the i.LON template, your LonMaker drawing will be created based on the updated LNS network database.
3. Click Create Drawing. 4. When you open the LonMaker drawing, a prompt may open informing that there is a NSS device (LNS server network service device) conflict. Click OK, and then follow the instructions in the Network Wizard to open the drawing. Make sure you select the #EES# as the network interface. After the drawing is opened, a prompt opens asking if you want to resynchronize the network.
2. The Create Backup Web page opens. All the SmartServers in the selected project are listed and will be backed up. If your SmartServer is synchronized with an LNS network database, that LNS network database is also listed and will be backed up. If you are accessing the i.LON AdminServer on an LNS Server/EES 2.0 computer that is different than the one that contains the LNS network database, the back up will fail. To create the backup, access the i.LON AdminServer on the LNS Server/EES 2.
• Delete Source Project. Deletes the selected i.LON projects from the navigation pane on the left side of the i.LON AdminServer Web interface. • Delete LNS Network Database(s). Permanently deletes the LNS network databases in the selected i.LON projects from the LNS Server. This option is useful if you are managing many LNS networks. Delete Network Interface(s). Deletes the temporary network interface used by the i.LON AdminServer to communicate the SmartServer and LNS Proxy Web service from the i.
Restoring a SmartServer You can use the i.LON AdminServer to restore a backup of a SmartServer image, and to restore the LNS network database to which the SmartServer is synchronized (if you are using LNS mode). To restore a SmartServer from a backup, follow these steps: 1. Under the Backups icon, right-click the appropriate backup folder and then click Restore on the shortcut menu. 2. The Restore dialog opens. Echelon Enterprise Services 2.
3. Click Restore. The time required to restore the backup depends on the size of the backup image. If any other administrative task for a SmartServer in the selected project has not been completed or has failed, a dialog opens prompting to confirm that you want to create the backup. Click OK. 4. The Progress box displays the status of the restore. 5. After a SmartServer has been restored, it is automatically rebooted. When a SmartServer reboot has finished, STATUS_DONE is displayed in its Status box.
2. The Export Web page opens. 3. Click Export to begin the export. The time required for the export depends on the size of the i.LON project, template, or backup. 4. The i.LON project, template, or backup is copied to an export file (.zip) that is named EXPORT--- and is stored in an ees-export folder with same name. The following table lists where the ees-export files are stored on your computer.
Export File Import Folder in LONWORKS Directory Project LONWORKS\iLON\EnterpriseServices\repository\ees-import\projects Template LONWORKS\iLON\EnterpriseServices\repository\ees-import\templates Backup LONWORKS\iLON\EnterpriseServices\repository\ees-import\backups For example, to import the example project exported in the previous section, you would copy the following ees-export file for the project: LONWORKS\iLON\EnterpriseServices\repository\ees-export\projects\EXPORT-MyProject-2009-0 8-04-18191441
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.
2. If you are using LNS network management services, design the network using the LNS tree, the LonMaker tool, or another LNS network tool following these steps (see step 3 if you are using standalone network management). These steps have been designed for newer SmartServer users, who may need instructions on creating an LNS managed network with the SmartServer. You can design your network without following these steps if you are a more experienced user.
If you are using the LonMaker tool, you can use the i.LON SmartServer Configuration Utility to open the SmartServer’s applications from the LonMaker drawing. To do this, right-click the functional block shape in the LonMaker drawing representing the SmartServer application to be configured, and then click Configure on the shortcut menu. For more information on opening SmartServer applications from a LonMaker drawing, see Opening SmartServer Applications with the LonMaker Tool in Chapter 12 of the i.
6. Verify that the devices on the onsite network are uncommissioned. 7. Use the i.LON AdminServer to deploy the SmartServer template you created in step 6 on the deployment SmartServer attached to the onsite network. See Deploying an i.LON Template earlier in this chapter for more information on how to do this. • If you are installing a network that has one device per XIF file, select Automatic in the Deployment Mode property. After the i.
10. Optionally, you can wink or test discovered devices. To do this, right-click anywhere in the device’s row and then click Wink or Query Status on the shortcut menu. For more information on using the SmartServer to wink and test devices, see Chapter 5 of the i.LON SmartServer 2.0 User’s Guide. 11. Optionally, you can remove devices that you do not want to be assigned Neuron IDs or you do want to be created. To do this, right-click anywhere in the device’s row and then click Delete on the shortcut menu.
54 Using the i.
3 Using the LNS Proxy Web Service This chapter introduces the LNS Proxy Web service that is used for communication between the SmartServer and LNS network databases. It explains how to use the EES tray tool. It describes how to use the LNS Proxy Web service as an LNS network tool, and how to use LNS Proxy Web service to integrate the SmartServer with LNS network tools. It describes how to troubleshoot the LNS Proxy Web service if a firewall is blocking access to it. Echelon Enterprise Services 2.
Introduction The LNS Proxy Web service enables the SmartServer to directly communicate with LNS network databases on LNS Server computers running LNS Turbo Server (version 3.25). This means that you can use the SmartServer as a powerful standalone LNS network management tool to design, install, monitor/control, and maintain LONWORKS networks, or you can integrate the SmartServer with the LonMaker tool or other LNS network tools and use the SmartServer to monitor and control the network.
Overall, you can add, delete, rename, and modify channels, devices, functional blocks, network variables, and LONWORKS connections in the LNS tree and see the changes in the LonMaker drawing—and vice-versa—without performing any additional steps. Using the Echelon Enterprise Services Tray Tool You can use the EES tray tool to configure and help troubleshoot the LNS Proxy Web service. An icon representing this tool is added to the notification area of your desktop when you install EES 2.0 on your computer.
2. The Opened Databases dialog opens. This dialog lists the name and network interface used (if any) for each LNS network database opened by the LNS Proxy Web service. 3. To close an LNS network database, click the database, and the click Close Database. 4. Click OK when you are done viewing and closing LNS network databases.
2. The Options dialog opens with the Connection tab selected. This dialog lists the Port Number on the LNS Server computer that the LNS Proxy Web service uses to transmit and receive SOAP/HTTP requests, and it lists the User Name and Password required to access the LNS Proxy Web service. These values are initially set in the Echelon Enterprises Services installer. 3. Click OK when you are done viewing and modifying the LNS Proxy Web service access properties. 4.
2. Click the Options tab. 3. Click Clear Cache. 4. Click OK. Using the LNS Proxy Web Service You can use the LNS Proxy Web service as a standalone LNS network management tool to design, install, and maintain LONWORKS networks. In this case, you use the LNS tree in the SmartServer Web interface to create, configure, bind, commission, and test the devices in your network.
2. Right-click the LAN icon or a dial-out connection icon, point to Add Host, and then click Server (LNS, Email, Time, IP-852, WebTarget) on the shortcut menu. Note: If IP-852 routing is licensed and enabled on the SmartServer and the IP-852 Configuration Server is installed on the LNS Server computer, click the IP-852 Configuration Server icon ( ), click LNS Proxy, and then skip to step 5 in order to configure the properties of the LNS Server. 3.
User Name Optionally, enter a user name to be used by the SmartServer for accessing the LNS Proxy Web service. The default user name is ilon. SOAP Password Optionally, you can click Change Password to change the password used by the SmartServer for accessing the LNS Proxy Web service. The default password is ilon. Format Values in WebBinder SOAP Messages Using Select how data point values are formatted in SOAP messages sent to this LNS Server via Web connections.
networks at the same time by creating a template of your LNS network database and deploying it on multiple SmartServers as described in Using Rapid Deployment in Chapter 2. After you install the network, you can maintain it by upgrading, replacing, decommissioning, and testing devices. See Maintaining LONWORKS networks in Chapter 5 of the i.LON SmartServer 2.0 User’s Guide for how to do this.
Automatically Synchronizing the SmartServer to an LNS Network Database You can synchronize the SmartServer to an LNS network database using LNS Auto mode. In LNS Auto mode, the SmartServer independently initiates communication with an LNS network database via the LNS Proxy Web service, and automatically sends network configuration changes made in the SmartServer tree to the LNS network database.
5. In the Network Management Service property, accept the default LNS Auto option. In this mode, the SmartServer independently initiates communication with the LNS Proxy Web service, and automatically sends network configuration changes made in the SmartServer tree to the LNS network database. You should select this mode as long as a firewall is not blocking the SmartServer’s access to the port on the LNS Server computer selected for the LNS Proxy Web service (port 80 by default).
9. In the LNS Network dialog, select the LNS network database to which the SmartServer is to be synchronized and then click Finish. 10. The Use LNS Network Interface property check box is selected and the network interface used for communication between the LNS Server and the network is specified automatically. Accept these defaults if the LNS Server is attached to the physical network and you want the SmartServer to communicate with the devices on the network through the selected network interface. 11.
12. Click Submit. If you selected LNS Auto in the Network Management Service property, the name of the network changes to the name of the LNS network database specified in step 11, the network icon changes to an LNS server icon, and the synchronization automatically begins. During the synchronization process, items in the SmartServer tree that are out of sync with the LNS network database are highlighted yellow.
a. Click Synchronize in the LNS Network property. The SmartServer Resync dialog opens. The Items to be Synced property lists the number of objects in the SmartServer tree that need to be synchronized with the LNS network database. b. In the SmartServer Resync dialog, click Start. The Items to be Synced counts down as the synchronization operation progresses. When the synchronization operation has been completed, this number should be 0.
When you manually synchronize the SmartServer to an LNS network database, the SmartServer Web interface requests a list of objects to be synced from the SmartServer via SOAP and forwards the objects returned by the SmartServer to the LNS Proxy Web service. The LNS Proxy Web service returns a set of synced objects to the SmartServer Web interface, which forwards these objects back to the SmartServer.
Alternatively, you can click Driver, click the network icon in the SmartServer tree to open the Setup – LON Network Driver Web page, and then click the Synchronize button in the LNS Network property. 2. 70 The SmartServer Resync dialog opens.
3. Set the following synchronization options: Synchronize All Internal SmartServer Items Synchronizes all internal items in the SmartServer’s internal database, including hidden items, with the LNS network database. Internal items include the following: • LONWORKS channels. • The SmartServer’s internal App device and its child functional blocks and data points. • The SmartServer’s internal IP-852 router. • FPM devices and their child functional blocks and data points.
functional blocks. • Addition or deletion of dynamic network variables on the SmartServer’s internal App device while it is uncommissioned. Note: Selecting this option may significantly increase the time required for the manual synchronization as all hidden internal items are synced. Synchronize All External Items Synchronizes all external items in the SmartServer’s internal database with the LNS network database. External items include the following: • LONWORKS channels.
automatically updates the LON driver properties of the selected items (for example, timing parameters of a channel, commission and application statuses of a device, format description of a data point) in the SmartServer’s internal database. To synchronize one item, right-click the item (channel, device, functional block, or data point) in the target SmartServer tree, and then click Synchronize with LNS in the shortcut menu to synchronize the item.
2. Verify that you have added an LNS Server (running LNS Turbo Server [version 3.25] or newer) to the LAN that contains the LNS network database in which the network variable or configuration property is stored. See Using the LNS Proxy Web Service earlier in this chapter for how to do this. 3. Verify that you have synchronized the target SmartServer with the LNS network database containing the external network variables or configuration property you are copying.
7. Click Submit. 8. You can now add the external data points to the SmartServer’s built-in application and to your custom SmartServer 2.0 Web pages. The following steps describe how to add external data points to the SmartServer’s built-in applications (see the i.LON Vision 2.0 User’s Guide for adding data points to your custom SmartServer 2.0 Web pages): a. Verify that you have created an instance of the functional block that represents the application to which data points are to be added. b.
1. Verify that the SmartServer and the LNS Proxy Web service are using the same HTTP port on the LNS Server computer for SOAP communication. To do this follow these steps: a. Open the Setup – LNS Server Web page. To do this, click the LNS server icon in the tree view on the left side of the SmartServer Web interface. a. The port used by the SmartServer to communicate with the LNS Proxy Web service is specified in the HTTP Port (Web Server / SOAP) property. The default port is 80. b.
www.echelon.
