Echelon i.LON SmartServer 2.0 - Manual (Page 18)

i.LON SmartServer 2.0 Programmer’s Reference 2-4
2.4.2 SOAP Response
xmlns:SOAP-ENV=http://schemas.xmlsoap.org/soap/envelope/
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
2005-02-02T11:30:15.220+01:00
030000066f02
172.25.143.222
80
2005-02-02T11:31:41Z
90
<MessageNameResponse xmlns="http://wsdl.echelon.com/web_services_ns/ilon100/v4.0/message/">
0
xsi:type=“type”>
networkName/channelName/deviceName/functionBlockName/pointName
<Parameter1>Parameter1ValueParameter1>
<Parameter2>Parameter2ValueParameter2>
...
xsi:type=“type” >
networkName/channelName/deviceName/functionBlockName/pointName1
<Parameter1>Parameter1ValueParameter1>
<Parameter2>Parameter2ValueParameter2>
...
...
MessageNameResponse>
2.5 SOAP Messages Formats
A SOAP message is sent to the SmartServer each time you invoke a SOAP function. The content of
the SOAP message and the affect it has on the SmartServer is based on the input you supply to the
function. Using the Set function for example, the SmartServer 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 item. The following sections go through each
part of the SOAP messages to describe the interface.
SOAP messages are XML documents that are transferred from one entity to another; therefore, the first
line in any SOAP message is always the XML version header. SOAP 1.1 and 1.2 both conform to
XML 1.0, so this line will not need to change if the SOAP version is updated.
For more information on the types referenced in this section, see the Version 4.0 XML schema type
(iLON100.xsd), which is installed in the L
ON W ORKS \iLon100\images\iLon100 4.0x\web\WSDL\v4.0
folder on your computer when you install the SmartServer software.
Note: All SOAP messages sent to and from the SmartServer must adhere to the UTF-8 encoding
standard. This is indicated by the
tag included in
each SOAP message, as shown in the following sections. However, this restriction is not enforced by
the SmartServer software. As a result, the SmartServer 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 SmartServer. 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.