Skip Navigation
  1. BlackBerry Docs
  2. BlackBerry AtHoc
  3. 1.2
  4. User Sync Client
  5. Configure the data integration file
  6. Data processor configuration
  7. CSV data processor
  8. CSV data processor node descriptions

CSV data processor node descriptions

<IntegrationData>
: This is a root node of the output file. It has the following sub nodes:
<users>
: This node contains definitions for a user. Under this node is a <user> node which represents one users that needs to be synchronized.
<user>
: This node represents each node that will be synchronized. The following sub nodes can be present under the <user> node:
  • <login_id>
    : The XSLT must produce this mandatory node. The value of this node is a username of a user that will be matched against a username in the
    BlackBerry AtHoc
     system.
  • <lineage>
    : (Optional) This node represents a membership in an organizational hierarchy. This node must be present when assigning a user to an organization hierarchy. The value of this node is the path of the organization hierarchy.
    To import the organization hierarchy user attribute, the <hierarchy> section must be enabled (un-commented) under the <syncOperations> section in the AtHocDataIntegration.config file.
  • <displayName>
    : (Optional) When provided, the value is the display name of the user.
  • <firstName>
    : (Optional) When provided, the value is the first name of the user.
  • <lastName>
    : (Optional) When provided, the value is the last name of the user.
  • <enabled>
    : (Optional) Values are “Y” or “N”. “Y” means the user should be created as an enabled user. “N” means the user should be created as a disabled user.
  • <customFields>
    : (Optional) The sub nodes of this node represent each attribute to synchronize. The sub node should be in the following format:
    <field commonName="common name of attribute">Value of attribute</field>
    .
  • <devices>
    : (Optional) The sub nodes of this node represent each device to synchronize. The sub node should be in the following format:
    <device commonName="common name of device">value of device</device>
    .
  • <lists>
    : This node can contain one or more <list> sub nodes that represents a distribution list.
    <list>
    : Represents one list. CommonName is the commonName of a static distribution list in the
    BlackBerry AtHoc
     system. The value is either “Yes” or “No”. “Yes” means the user should be added as a member of this list. “No” means the user should be removed.
You can use XSLT to create customized lineage from LDAP attributes. In addition to mapping LDAP attributes to
BlackBerry AtHoc
 custom fields, you can translate LDAP attribute values into other values recognized by the
BlackBerry AtHoc
 software.