Page History

CardioLog provides advanced visitor segmentation capabilities by integrating both external and internal personal user data into reports.

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 designated web service which supplies the desired organizational structure of users and groups. 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 separate web service that supplies the user information.

Contents

• Retrieving Users and Groups From a Custom Source
• Creating the Custom User and Group Structure Web Service
• Retrieving User Information From a Custom Source
• Creating the Custom User Information Web Service
• Configuring Visitor Segmentation by Active Directory Attributes
• Configuring Visitor Segmentation by SharePoint User Profiles
• User Categories Updates

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:

1. Create the custom organization structure web service for your organization.
2. Verify that your custom organization structure web service returns a valid XML response, according to the XML schema,
3. Confirm the CardioLog Scheduling Service user account has sufficient read request permissions to access the web service.
4. From the navigation pane in CardioLog go to Administration and in System Configuration select Users and Groups Management.
5. Click on the desired database you would like to edit.
6. Enter the custom web service URL in the Web Service URL text box (acceptable file extensions: "aspx", "asmx", "xml").
7. Confirm all other details are accurate.
8. Click Save.
9. Perform IISRESET on the CardioLog application server.
10. After the next Active Directory update, your users and groups will be added to the relevant Users and Groups filter of each report.

...

The Users and Groups web service should be exposed by a web page which provides a XML string response according to the following 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.

 Sample Data:

...

In order to load additional user information from a web service, specify a web service from which the User Categories Updates service will extract the user data. This is done through the CardioLogAdministration user interface:

1. Create the custom user information web service for your organization.
2. 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.
3. In the navigation pane in CardioLog go to Administration > System Configuration > User Categories Updates.
4. Click Next.
5. Enter the web service URL in the Categories Web Service URL field (acceptable file extensions: "aspx", "asmx", "xml").
6. Click Save and restart the CardioLog Scheduling Service.
7. Perform IISRESET using the IIS Manager on the CardioLog application server.
8. 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.

...

The user information web service should be exposed by a web page which provides an XML string response, according to the following format: 

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.

Sample Data:

Anchor
active directory active directory

Configuring Visitor Segmentation by Active Directory Attributes

...