Echelon Enterprise Services 2.0 ReadMe

Release 4.04, August 2010

Copyright © 1998 – 2010 Echelon® Corporation
All Rights Reserved

1       Introduction

This document describes SmartServer 2.0 Enterprise Services (EES) Service Pack 1 (SP1), which is herein referred to as Echelon Enterprise Services 2.0 SP1 or EES 2.0 SP1. This document describes how to upgrade to EES 2.0 SP1, and the fixes includes in this release.  See Upgrading to EES 2.0 Release 4.04 for instructions on installing the service pack and verifying that it has been installed, and Changes in EES 2.0 Release 4.04 for details on what is fixed in this release.

Additional information and updates for EES 2.0, including service packs and critical updates, may be available at www.echelon.com/ilon.  The latest service packs and updates may not be included with your SmartServer.  See Echelon’s Knowledge Base at www.echelon.com/support for answers to frequently asked questions.

To provide full functionality, EES 2.0 SP1 and the SmartServer 2.0 SP1 software must be used with the latest Microsoft Internet Explorer 7 or newer, or Mozilla Firefox 3.0 or newer.  If you are using SmartServer 2.0 SP1 with an LNS® Server or the LonMaker® Integration Tool, you must be using the latest Echelon LNS Turbo and LonMaker service packs and updates.  The latest LNS and LonMaker service packs and updates at the time of the SmartServer 2.0 SP1 release are included with the LNS Server included with the i.LON LNS Server Editions, are included on the SmartServer 2.0 SP1 DVD, and are also available from www.echelon.com/downloads.

2       Contents

1        Introduction. 1

2        Contents. 1

3        Release Identification. 2

4        Upgrading to EES 2.0 Release 4.04. 2

5        Changes in EES 2.0 Release 4.04. 3

5.1         Rapid Deployment 3

5.2         Release 4.04 Update. 3

5.3         Fixes. 3

6        Known Problems and Workarounds. 3

6.1         Extra Tab in Firefox when Using a FB Plug-in. 4

6.2         LNS Proxy Disabled after EES 2.0 IP Address is Changed. 4

6.3         LonMaker Tool Failures with Many NVs. 4

6.4         Cannot Create and Deploy i.LON Templates via HTTPS. 4

6.5         Clear Browser Cache after Installation Upgrade. 4

7        Documentation. 4

7.1         Rapid SmartServer Deployment 4

7.2         Rapid Component Deployment 4

 

3       Release Identification

This document applies to Echelon Enterprise Services 2.0 with Service Pack 1 (Release 4.04).  To verify that you have this release on your computer, follow one of the following procedures:

·        For Windows 7 and Windows Vista, click the Start button, type Programs and Features in the Search box, press ENTER to open Programs and Features, and then click Echelon i.LON SmartServer 2.0 Enterprise Services.  If the Version column is not displayed, right click the list header, select More, and then select Version to add the Version column.  The version number of EES 2.0 with SP1 is 4.04.088.

·        For Windows XP, open Add or Remove Programs in Windows Control Panel, and then click Echelon i.LON SmartServer 2.0 Enterprise Services.  Click the Click Here for Support Information link.  The version number of EES 2.0 with SP1 is 4.04.088.

The following table summarizes the i.LON 100 e3 plus and SmartServer release history:

Name

Number

Date

i.LON 100 e3 plus

3.03

April 2008

i.LON 100 e3 plus SP1

3.04

December 2009

i.LON SmartServer

4.00.136

January 2008

i.LON SmartServer SR1

4.01.012

March 2008

i.LON SmartServer SR2 and SP2

4.02.055

October 2008

i.LON SmartServer 2.0

4.03.123

October 2009

i.LON SmartServer 2.0 SP 1

4.04.088

August 2010

4       Upgrading to EES 2.0 Release 4.04

You can upgrade EES 2.0 Release 4.03 to Release 4.04 by installing SmartServer 2.0 Enterprise Services SP1. SmartServer 2.0 SP1 is available as a free download at www.echelon.com/ilon.  To upgrade a Release 4.03 installation to Release 4.04, follow these steps:

1.     Mount the image as a virtual DVD using virtual DVD software such as CloneDrive or MagicDisc.  If the SmartServer 2.0 SP1 setup application does not launch immediately, open the setup.exe file on the root directory of the Echelon i.LON SmartServer 2.0 SP1 DVD.  The SmartServer 2.0 Service Pack 1 setup application main menu appears. 

2.     Click Install Products.  The Install Products dialog appears.

3.     Click Echelon i.LON SmartServer 2.0 Enterprise Services SP1The Echelon i.LON SmartServer 2.0 Enterprise Services SP1 installer appears.

4.     Follow the steps of the installation wizard.  The installation will automatically upgrade the existing Echelon SmartServer 2.0 Enterprise Services Release 4.03 installation on your computer to Echelon SmartServer 2.0 Enterprise Services Release 4.04.

5       Changes in EES 2.0 Release 4.04

5.1      Rapid Deployment

The EES 2.0 AdminServer no longer stores the standard SmartServer firmware files in the template when you create an i.LON template.  This significantly reduces the time required to create and deploy i.LON templates.  See 7.1 Rapid SmartServer Deployment for documentation.

The EES 2.0 AdminServer can now be used to create and deploy components to up to 100 SmartServers at a time.  A component is any collection of files that you want to deploy to one or more SmartServers from an AdminServer.  For example, a component may consist of an FPM app, resource files, XIF files, and custom Web pages that you want to deploy to one or many SmartServers.  See 7.2 Rapid Component Deployment for documentation. (57345)

5.2      Release 4.04 Update

The EES 2.0 AdminServer can now update a Release 4.03 SmartServer 2.0 to Release 4.04 (SmartServer 2.0 with SP1).  See the ReadMe document for SmartServer 2.0 SP1 for a description of the changes in Release 4.04. (56858)

5.3      Fixes

The following table summarizes problems fixed in this release.  The EPR column lists Echelon internal problem tracking numbers.

EPR

Description

54842

An i.LON template that included an LNS network database contained the entire LonWorks/Types folder.

56433

When deploying an i.LON template that contains a capitalized license folder (“License”), the AdminServer overwrites the license files on the target SmartServers.

56549

The EES Administration Service Web interface sometimes failed with Firefox 3.6.

56818

If you install EES 2.0 on a computer that does already have the Java Developer’s Kit (JDK) installed on it, the Tomcat Server used by EES 2.0 does not run.

6       Known Problems and Workarounds

This section describes known limitations and problems for this release.  Numbers in parentheses at the end of the descriptions are Echelon's internal problem tracking IDs.

6.1      Extra Tab in Firefox when Using a FB Plug-in 

When you configure a functional block in the LNS tree using a plug-in, an additional tab opens if you are using FireFox.  Workaround: Close the extra tab.  (53410)

6.2      LNS Proxy Disabled after EES 2.0 IP Address is Changed

If you change the IP address of the computer running EES 2.0, the LNS Proxy Web service is disabled.  Workaround: Restart EES 2.0 using the tray tool.  (54447)

6.3      LonMaker Tool Failures with Many NVs

The LonMaker tool may fail when you create many network variables in LNS mode.  Workaround: Install LNS Turbo Service Pack 7 or newer on the computer with the LNS Proxy Web service. (56401)

6.4      Cannot Create and Deploy i.LON Templates via HTTPS

Creating or deploying an i.LON template fails if the deployment or target SmartServer uses HTTPS and their SSL certificates have not already been accepted.  Workaround: Restart EES 2.0 using the tray tool.  (54782)

6.5      Clear Browser Cache after Installation

After upgrading previous Echelon Enterprise Services installation some Admin Service Web User Interface Elements might be unavailable in the browser window.  Workaround: Clear the browser cache manually.  (57576)

7       Documentation

This section describes updates to the documentation.

7.1      Rapid SmartServer Deployment

You can use the EES 2.0 AdminServer to create and deploy i.LON templates, which are templates containing all the configuration data for a SmartServer.  You can use i.LON templates for SmartServers that have been configured in LNS mode or Standalone mode.  If you create an i.LON template for LNS mode, the template also includes a copy of the LNS network database for the SmartServer.

Starting with Release 4.04 (SmartServer 2.0 with SP1), i.LON templates do not include a copy of the standard SmartServer firmware files.  When you deploy an i.LON template, the AdminServer verifies that the SmartServer firmware on the target SmartServer is compatible with the template.  If you are deploying a template created with Release 4.04 (SmartServer 2.0 with SP1) to a SmartServer with Release 4.03 (SmartServer 2.0) or earlier, use the EES 2.0 AdminServer to upgrade the SmartServer firmware before deploying the i.LON template. 

See Upgrading the SmartServer Firmware, Creating an i.LON Template, and Deploying an i.LON Template in the Echelon Enterprise Services 2.0 User’s Guide for more details.

7.2      Rapid Component Deployment

You can use the EES 2.0 AdminServer can to create and deploy components to up to 100 SmartServers at a time.  A component is any collection of files that you want to deploy to one or more SmartServers from an AdminServer.  For example, a component may consist of an FPM app, resource files, XIF files, and custom Web pages that you want to deploy to one or many SmartServers.  Components are deployed without stopping or rebooting the running apps on the target SmartServer or SmartServers.  This allows you to deploy components to operational sites without disrupting the sites.  As a result, don’t use component deployment for deploying updates to SmartServer system files—use i.LON templates for deploying system files instead.  The AdminServer does reboot the target SmartServers when you use deploy an i.LON template.

To create a component, follow these steps:

1.     Create a folder in the LonWorks iLON\EnterpriseServices\repository\ees-import\component directory with the name of your component.  By default, the LonWorks directory is C:\LonWorks.  For example, to create a component called MyHomePage using the default LonWorks folder, create C:\LonWorks\iLON\EnterpriseServices\repository\ees-import\component\MyHomePage.

2.     Create a directory hierarchy within your component folder that matches the directory hierarchy to be deployed to the SmartServer and copy the files to be deployed to that hierarchy.  For example, to create a component that replaces the default SmartServer home page, create an iLON\EnterpriseServices\ees-import\component\MyHomePage\web directory and copy your custom index.html file to the web directory.

3.     Right-click the Component folder in the AdminServer navigation pane and then click Import on the shortcut menu.  The AdminServer imports the files in your component directory and creates your component from them.  The AdminServer also deletes your original files so be sure to keep a copy of your original files in case you need to modify your component.  The component is named with your component name followed by a timestamp.

To deploy the component to one or more SmartServers, follow these steps:

1.     Expand the Component folder in the AdminServer navigation pane.

2.     Right-click the component to be deployed, and then click Deploy.  A deployment page appears in the application pane. 

3.     Click any SmartServers in the navigation pane to add them to the deployment target list.  SmartServers appear under the LAN heading for your projects in the navigation pane.  You can select up to 100 SmartServers.

4.     Click the Deploy button to start the deployment.  All the files in the selected component will be deployed to all the selected SmartServers.  Deployment status is displayed under the Status heading in the application pane.

To delete a component, right-click the component in the navigation pane and then click Delete on the shortcut menu.

To export a component that you can import on another AdminServer, right-click the component in the navigation pane and then click Export on the shortcut menu.  This creates a component file in your iLON\EnterpriseServices\repository\ees-export\component directory that you can import on another AdminServer.  The component file name will be the name of your component followed by a time stamp, with a .zip extension.  Using the example from creating a component above, the path and filename would be the following (with a different timestamp):

C:\LonWorks\iLON\EnterpriseServices\repository\ees-export\component\MyHomePage-2010-07-06-170319556.zip

To import a component from another AdminServer, follow these steps:

1.     Copy the component file to your iLON\EnterpriseServices\repository\ees-import\component directory.

2.     Right-click the Components folder in the navigation pane, and then click Import on the shortcut menu. 

3.     Click the Import button.  The AdminSever imports the component and deletes the component file.

 

 

Echelon, LON, LonWorks, i.LON, LNS, and LonMaker are registered trademarks of Echelon Corporation in the U.S.  and other countries.