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

i.LON SmartServer 2.0 Programmer’s Reference 1-3
introduced for the e2 release, and the version 3.0 namespace was introduced for the e3 release.
Support for the different namespaces as follows:
• i.LON 100 servers running the Release 1.0 software only support the version 1.0 namespace. This
means that a SmartServer running the Release 1.0 software can only respond to SOAP messages
from other SmartServers running the Release 1.0 software.
• i.LON 100 servers running the e2 software support the version 1.0 and 1.1 namespaces. This
means that an i.LON 100 server running the e2 software can respond to SOAP messages from
other i.LON 100 servers that are running the Release 1.0 or the e2 software.
• i.LON 100 servers running the e3 software support the version 1.1 and 3.0 namespaces. This
means that i.LON 100 servers running the e3 software can respond to SOAP messages sent from
other i.LON 100 servers that are running the e2 or e3 software.
• SmartServers running the SmartServer software support only the version 4.0 namespace. This
means that SmartServers running the SmartServer software can respond to SOAP messages sent
from other SmartServers. SmartServers running the SmartServer software cannot respond to
SOAP messages sent from i.LON 100 servers running the e3 software.
The following section, Version 4.0 SOAP Message Name Schema, describes the changes made to the
SOAP/XML interface between SOAP namespace versions ‘3.0’ and ‘4.0’ (i.e. between the e3 and
SmartServer releases).
Note: This manual often refers to the i.LON 100 and SmartServer releases by the version numbers
used in their SOAP namespace. For example, the SmartServer release is referred to by its software
version number, which is ‘4.0’, and the i.LON 100 e3 release is referred to as ‘3.0’. For more
information on the SOAP namespace, see Chapter 2 of this document.
1.4.1 Version 4.0 SOAP Message Name Schema
The SOAP/XML interface used for the SmartServer (version 4.0) uses a new message name schema.
It uses a common set of generic methods (List, Get, Set, Delete, Read, Write, Clear, and Invoke) for
retrieving and configuring the data of the various SmartServer applications. This section provides an
overview of the changes made to the SOAP message name schema from version 3.0.
1.4.1.1 Version 3.0 Message Name Schema
The message name schema used for version 3.0 was <Application>_<Message>_<Parameter>. The
Parameter was optional and normally not used. The Message was normally List, Get, Set or Delete.
The following provides examples of version 3.0 request messages:
TypeTranslator_List, TypeTranslator_Get_Rule, Read, DriverMOD_Set_Template
The response messages were identified by the message name plus the string <Response>.
The schema was: <Application>_<Message>_<Parameter>Response.
With the version 3.0 message name schema, there were numerous specialized SOAP messages and
SOAP structures, resulting in limited flexibility and intricate handling of a large number of Java or C#
proxy classes.
1.4.1.2 Version 4.0 Message Name Schema
Version 4.0 uses a single set of messages that are common to all applications. The messages for
retrieving and modifying configuration data consists of List, Get, Set, and Delete, and the messages for
retrieving and changing state information are Read and Write.