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 external sources (any human resource management system or even custom databases), using a designated web service which supplies the desired organizational structure of users and groups.
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 Add Source > Custom.
System Configuration - Users and Groups Management - Custom
- Enter a name for the custom users and groups source in the Title textbox
- Enter the custom users and groups web service URL in the Website URL textbox (Acceptable file extensions are "aspx", "asmx" or "xml").
- Select Is Web Service = Yes and enter the custom users and groups web service method name in the Web Method Name textbox (in case of using "asmx").
- Click Set and enter user credentials if required in order to access the web service.
- 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.
The Users and Groups web service should be exposed by a web page which provides a XML string response according to the following schema:
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.