The XML document that is produced by one iteration of the LDAP HWM listener is formed as follows:
<listenerName>
<row>
<attribute values="count of values" name="attribute name>
<value>data<value>*With no parsing of the attributes, the resulting document appears as:
<?xml version="1.0" encoding="UTF-8" ?>
<ibidca>
<row>
<attribute values="1" name="l">
<value>New York</value>
</attribute>
<attribute values="1" name="uSNCreated">
<value>159019</value>
</attribute>
<attribute values="1" name="distinguishedName">
<value>CN=Herz\,
Judy,OU=USERS,OU=EI,OU=IWAY,OU=COR,DC=ibi,DC=com</value>
</attribute>
<attribute values="1" name="postalCode">
<value>10121</value>
</attribute>
<attribute values="1" name="co">
<value>United States</value>
</attribute>
<attribute values="1" name="cn">
<value>Herz, Judy</value>
</attribute>
<attribute values="1" name="st">
<value>NY</value>
</attribute>
<attribute values="1" name="streetAddress">
<value>2 Penn Plaza</value>
</attribute>
</row>
</ibidca>If the base64 attribute is selected, each attribute value is checked as to whether it can be represented in the ISO-8859-1 character set. Those that cannot, are converted to base64:
<attribute values="1" name="objectGUID">
<value>base64(77+9Sinvv71nUk9P77+96LhG77+978+9JO+/vm==value>
</attribute>The parsing parameter causes the listener to attempt to break down the value of each attribute into token/value pairs:
<?xml version="1.0" encoding="UTF-8" ?>
<ibidca>
<row>
<attribute values="1" name="l">
<value>New York</value>
</attribute>
<attribute values="1" name="uSNCreated">
<value>159019</value>
</attribute>
<attribute values="1" name="distinguishedName">
<value>
<CN>Herz, Judy</CN>
<OU>USERS</OU>
<OU>EI</OU>
<OU>IWAY</OU>
<OU>COR</OU>
<DC>ibi</DC>
<DC>com</DC>
</value>
</attribute>
<attribute values="1" name="st">
<value>NY</value>
</attribute>
<attribute values="1" name="streetAddress">
<value>2 Penn Plaza</value>
</attribute>
</row>
</ibidca> Later, an option will allow selection of DSML or another standard.
| iWay Software |