Page History
...
- owner - item's owner/creator
- version - item version, for tracking updates
- created- the item's creation date
- modified - the item's most recent modification date
Info | ||||
---|---|---|---|---|
| ||||
<item> <url>http://www.intlock.com</url> <title>Intlock</title> <entitytype>5</entitytype> <owner>INTLOCK\James</owner> <version>1</version> <template>Website Folder</template> <created>01/01/2007 00:00:00</created> <modified>08/01/2007 10:37:35</modified> <items> <item> <url>http://www.intlock.com/en-us/</url> <title>Home</title> <entitytype>12</entitytype> <owner>INTLOCK\James</owner> <version>1</version> <template>Website Folder Page</template> <created>01/01/2007 00:00:00</created> <modified>08/01/2007 10:59:16</modified> <items /> </item> <item> <url>http://www.intlock.com/home.aspx</url> <title>Home</title> <entitytype>12</entitytype> <owner>INTLOCK\James</owner> <version>1</version> <template>Website Page</template> <created>01/01/2007 00:00:00</created> <modified>08/01/2007 10:59:16</modified> <items /> </item> </items> </item> |
Anchor | ||||
---|---|---|---|---|
|
CardioLog Analytics provides the ability to segment authenticated visitors by their user names and the groups they belong to. The organizational hierarchy of users and groups is monitored by the Active Directory Updates service, which retrieves the data directly from Active Directory by default.
The Active Directory Updates service can also retrieve the data from a custom source, using a a designated web service which which supplies the desired organizational structure of users and groups.
Anchor | ||||
---|---|---|---|---|
|
In order to load your user and group organization structure to CardioLog, you are required to specify a web service that the Active Directory Updates service will gather the organization's data from. This is done through the CardioLog Administration user interface:
- Develop the custom organization structure web service for your organization.
- Verify that your custom organization structure web service returns a valid XML response, according to the XML schema,
- Confirm the CardioLog Scheduling Service user account has sufficient read request permissions to access the web service.
- From the navigation pane in CardioLog go to Administration > System Configuration > Users and Groups Management.
- Click Click Add Source > Custom > Custom.
System Configuration - Users and Groups Management - Custom
- Enter the custom web service URL in the Web Service URL text box (acceptable file extensions: "aspx", "asmx", "xml").
- Confirm all other details are accurate.
- Click Save and restart the CardioLog Scheduling Service.
- After the next Active Directory update, your users and groups will be added to the relevant Users and Groups filter of each report.
Anchor | ||||
---|---|---|---|---|
|
The Users and Groups web service should be exposed by a web page which provides a XML string response according to the following schema:
Info | ||||
---|---|---|---|---|
| ||||
<?xmlversion="1.0"encoding="utf-8" ?> <xs:schema elementFormDefault="qualified" xmlns:mstns="http://tempuri.org/ADXmlSchema.xsd" xmlns:xs="http://www.w3.org/2001/XMLSchema"> <xs:element name="tree"> <xs:complexType> <xs:sequence> <xs:element name="users"> <xs:complexType> <xs:sequence> <xs:element maxOccurs="unbounded" name="user"> <xs:complexType> <xs:sequence> <xs:element name="accountName" type="xs:string" /> <xs:element name="displayName" type="xs:string" /> <xs:element name="userMail" type="xs:string" /> <xs:element name="memberOf" type="xs:string" /> </xs:sequence> </xs:complexType> </xs:element> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="groups"> <xs:complexType> <xs:sequence> <xs:element maxOccurs="unbounded" name="group"> <xs:complexType> <xs:sequence> <xs:element name="groupName" type="xs:string" /> </xs:sequence> </xs:complexType> </xs:element> </xs:sequence> </xs:complexType> </xs:element> </xs:sequence> </xs:complexType> </xs:element> </xs:schema> |
Field Definitions:
User accountName: the user account name (a unique user ID).
User displayName: the user display name.
User userMail: the user email address.
User memberOf: a semicolon separated list of group names associated with the user.
Info | ||||
---|---|---|---|---|
| ||||
<tree> <users> <user> <accountName>MyCompany\james</accountName> <displayName>James Wright</displayName> <userMail>james.wright@mycompany.com</userMail> <memberOf>Administrators;Marketing</memberOf> </user> <user> <accountName>MyCompany\dana</accountName> <displayName>Dana Cohen</displayName> <userMail>dana.cohen@mycompany.com</userMail> <memberOf>Sales</memberOf> </user> </users> </tree> |
Anchor | ||||
---|---|---|---|---|
|
CardioLog Analytics provides advanced visitor segmentation capabilities by integrating both external and internal personal user data into reports.
Retrieval of additional user information, such as department, gender, and other profile data is performed by the User Categories Updates service, which retrieves the data from Active Directory attributes or SharePoint User Profiles by default. The User Categories Updates service can also retrieve the data from a custom source, using a a designated web service that that supplies the user information.
Anchor | ||||
---|---|---|---|---|
|
- Create the custom user information web service for your organization.
- Verify that the custom user information web service returns a valid XML response, according to the XML schema, and that the CardioLog Scheduling Service user account has sufficient permissions to access (request) the web service.
- In the navigation pane in CardioLog go to Administration > System Configuration > User Category Management.
- Click Add Categories Source > Custom.
System Configuration - User Category Management - Custom
- Enter the web service URL in the URL field (acceptable file extensions: "aspx", "asmx", "xml").
- Click Save and restart the CardioLog Scheduling Service.
- After the next run of the User Categories Updates service, your user categories will be added to the Visitor Segments filter of each report, under User Categories.
Anchor | ||||
---|---|---|---|---|
|
The user information web service should be exposed by a web page which provides an XML string response, according to the following format:
Info | ||||
---|---|---|---|---|
| ||||
<?xml version="1.0" encoding="utf-8" ?> <xs:schema id="CategoryXmlSchema" elementFormDefault="qualified" xmlns:mstns="http://tempuri.org/CategoryXmlSchema.xsd" xmlns:xs="http://www.w3.org/2001/XMLSchema"> <xs:element name="tree"> <xs:complexType> <xs:sequence> <xs:element name="item" type="UserCategoryXmlNode" minOccurs="0" maxOccurs="unbounded" /> </xs:sequence> </xs:complexType> </xs:element> <xs:complexType name="UserCategoryXmlNode"> <xs:sequence> <xs:element name="userName" type="xs:string" /> <xs:element name="categories" minOccurs="0" maxOccurs="1"> <xs:complexType> <xs:sequence> <xs:element name="categoryValue" type="categoryNode" minOccurs="0" maxOccurs="unbounded" /> </xs:sequence> </xs:complexType> </xs:element> </xs:sequence> </xs:complexType> <xs:complexType name="categoryNode"> <xs:sequence> <xs:element name="categoryName" type="xs:string" minOccurs="1" maxOccurs="1" /> <xs:element name="categoryValue" type="xs:string" minOccurs="1" maxOccurs="1" /> </xs:sequence> </xs:complexType> </xs:schema> |
Field Definitions:
username: the user account name (should match the accountName field in the organization structure)
categoryName: the designated category name.
categoryValue: the assigned category value.
Info | ||||
---|---|---|---|---|
| ||||
<tree> <item> <userName>MyCompany\james</userName> <categories> <categoryValue> <categoryName>Region</categoryName> <categoryValue>West</categoryValue> </categoryValue> <categoryValue> <categoryName>Gender</categoryName> <categoryValue>Male</categoryValue> </categoryValue> </categories> </item> <item> <userName>MyCompany\taylor</userName> <categories> <categoryValue> <categoryName>Region</categoryName> <categoryValue>North</categoryValue> </categoryValue> <categoryValue> <categoryName>Gender</categoryName> <categoryValue>Female</categoryValue> </categoryValue> </categories> </item> </tree> |