Instruction Manual
authenticate access to Web pages that send or receive multiple SOAP messages. If a SOAP 
message is sent to the i.LON 100 that does not contain the correct user name and password, 
it will be ignored. For instructions on using the i.LON Web Server Security and Parameters 
utility, see Chapter 13 of the i.LON 100 Internet Server User‘s Guide. 
To protect FTP access to the XML configuration files, the i.LON 100 requires a user name 
and password for every FTP session. This username and password default to “ilon”, and can 
be re-defined with the i.LON 100 Security Web Page. The i.LON 100 Internet Server User’s 
Guide describes how to use this page. 
2.3  Formats of SOAP Messages 
As described in Chapter 1, a SOAP message is sent to the i.LON 100 each time you invoke a 
SOAP function. The content of the SOAP message, and the effect it has on the i.LON 100, is 
based on the input you supply to the function. The i.LON 100 reads the contents of the 
message, and adjusts its operating parameters of its applications accordingly. It also returns 
a response message describing the status or configuration of the modified application. 
This section describes the basic format of the SOAP messages that are sent to the i.LON 100 
when you invoke any of the functions described in this manual. It also describes the formats 
of the response SOAP messages that are returned by these functions. 
NOTE: All SOAP messages sent to and from the i.LON 100 must adhere to the UTF-8 
encoding standard. This is indicated by the <?xml version="1.0" encoding="utf-8" ?> tag 
included in each SOAP messages, as shown in the following sections. However, this 
restriction is not enforced by the i.LON 100 software. As a result, the i.LON 100 will accept 
SOAP messages that do not adhere to the UTF-8 encoding standard without throwing an 
error, which may result in invalid configuration data being written to your i.LON 100. To 
avoid this, you should program your application to ensure that all SOAP messages adhere to 
the UTF-8 encoding standard. For more information on the UTF-8 encoding standard, see 
http://www.ietf.org/rfc/rfc3629.txt. 
2.3.1 Input Messages 
The following represents the basic format of the SOAP messages that are sent to the i.LON 
100 when you invoke any of the functions described in this manual. The sections following 
this sample describe each part of the SOAP message. 
<?xml version="1.0" encoding="UTF-8" standalone="no"?> 
<SOAP-ENV:Envelope 
 SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" 
 xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"> 
 <SOAP-ENV:Body> 
 <echelon:FunctionName 
 xmlns:echelon="http://wsdl.echelon.com/web_services_ns/ilon100/v1.1/message/"> 
 <Data> Data </Data> 
 </echelon:FunctionName> 
 </SOAP-ENV:Body> 
</SOAP-ENV:Envelope>
2.3.1.1 SOAP Envelope 
The SOAP envelope is the highest level of a SOAP message. The SOAP envelope for any 
message sent to the i.LON 100 must conform to the W3C SOAP 1.1 proposed Technical 
Recommendation: 
i.LON 100 Internet Server Program2-2  mer’s Reference 










