Versions Compared

Old Version 1

changes.mady.by.user Sigalit Hassid

Saved on

compared with

New Version 2

changes.mady.by.user Sigalit Hassid

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Anchor
custom tree adaptor
custom tree adaptor
Custom Tree Adaptor - Monitoring Non-SharePoint Websites

CardioLog Analytics uses a logical tree to represent the hierarchical structure of the monitored website. Whenever a usage event is sent to CardioLog it maps to the relevant item in the website hierarchy. This allows CardioLog to create reports for any level of the website hierarchy.

The Portal Tree Updates service component is responsible for retrieving the hierarchical data from your website. If you wish to retrieve the structure of a non-SharePoint website, you can specify an external web service to provide the hierarchical (logical) structure of your website.

 In order to monitor a non-SharePoint web site you need to do the following:

  • Install the Tracking Agent, which monitors visitor behavior for non-SharePoint web sites. The tracking code is added to a common page component, like master pages.
  • Configure the Website tree adaptor to a create tree structure automatically by crawling the website pages, or develop a Custom Tree Web Service that will return a logical tree structure that represents the hierarchy of your website.

Anchor
tracking agent
tracking agent
Install the Tracking Agent

Note: The Tracking Agent installation does NOT require reboot or downtime. 

If the Tracking Agent web application, named CardioLogAgent and installed on your CardioLog application server, is inaccessible from the website server install the CardioLogAgent web application on the web site server. You can verify if CardioLogAgent is accessible by opening http://[web site root]/CardioLogAgent/ca.aspx

  1. Create a CardioLogAgent folder on the web site machine.
  2. Copy the installation files into the new folder from [CardioLog Installation Folder]\CardioLogAgent\. 
  3. Open IIS Manager on the web site machine, create a new virtual directory named CardioLogAgent under the website, which points to the copied CardioLogAgent folder.
  4. Set the following properties for the new virtual directory: "ASP.NET 2.0, Integrated Windows Authentication" and then verify that the folder permissions allow "Everyone" read access.
  5. Verify that you can open http://[web site root]/CardioLogAgent/ca.aspx (Enter your website server name)

  6. Open the copied CardioLogAgent directory, open the web.config file and edit the following key, located in the <appSettings> section:

    Info
    iconfalse

    <add key="CardioLogAgentRoot" value="http://[web site root]/"/>

  7. Copy the tracking code from Administration > System Configuration > Usage Tracking Code > Select Non-SharePoint Website.

    Image Added 
    System Configuration - Usage Tracking Code 
     
  8. Edit the all URLs contained in the tracking code that redirect to the CardioLog application server, to redirect to the web site root URL.
  9. Either add the edited tracking code into every page you want to track immediately after the opening <head> tag, or you can also use a common JavaScript file. Alternatively you can add it to a non-JavaScript common page component. In this case you need to add the opening and closing <script> tags. If you add the code to a master page, insert it before the closing </head> tag, and use opening and closing <script> tags.
  10. Verify event collection by clicking Ctrl+F12 and wait for several seconds. The tracking agent console should pop-up, displaying the ID number for the most recent monitored action (event). To close the console, press Ctrl+F12.

Anchor
custom tree
custom tree
Develop the Custom Tree Web Service

Using the Custom Tree Adaptor you can specify a web service which provides the hierarchical (logical) structure of your website.
In order to load your custom hierarchical structure to CardioLog from which the CardioLog Portal Tree Updates service component will obtain it, perform the following steps:

  1. Develop the custom tree web service for your web site.
  2. Verify that the custom tree 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. From the navigation pane in CardioLog go to Administration > System Configuration > Custom Tree Adaptor > Click Add.

    Image Added
    System Configuration - Custom Tree Adaptor
     
  4. Enter the name of your website in the Name textbox
  5. Enter the custom tree web service URL in the Website URL textbox (Acceptable file extensions are "aspx", "asmx" or "xml").
  6. Enter the custom tree web service method name in the Web Method Name textbox (in case of using "asmx").
  7. Click Save and restart the CardioLog Scheduling Service.
  8. After the next run of Portal Tree Updates, the tree structure will be displayed in the Analysis Center (Object Explorer) and will be available for reports that allow content drilldown. 

Anchor
schema
schema
Custom Tree Web Service Schema

The Custom Tree web service should be exposed by a web page which provides an XML string response according to the following schema:

Info
iconfalse
titleXML Schema


<?xml version="1.0" encoding="utf-8" ?>

<xs:schema id="OMTreeXmlSchema" elementFormDefault="qualified"

xmlns:mstns="http://tempuri.org/OMTreeXmlSchema.xsd"

xmlns:xs="http://www.w3.org/2001/XMLSchema">

<xs:element name="tree">

<xs:complexType>

<xs:sequence>

<xs:element name="item" type="XmlNode" />

</xs:sequence>

</xs:complexType>

</xs:element>

<xs:complexType name="XmlNode">

<xs:all>

<xs:element name="url" type="xs:string" />

<xs:element name="title" type="xs:string" />

<xs:element name="entitytype" type="xs:string" minOccurs="0" maxOccurs="1" />

<xs:element name="owner" type="xs:string" minOccurs="0" maxOccurs="1" />

<xs:element name="version" type="xs:string" minOccurs="0" maxOccurs="1" />

<xs:element name="template" type="xs:string" minOccurs="0" maxOccurs="1" />

<xs:element name="created" type="xs:string" minOccurs="0" maxOccurs="1" />

<xs:element name="modified" type="xs:string" minOccurs="0" maxOccurs="1" />

<xs:element name="permissions" minOccurs="0" maxOccurs="1">

<xs:complexType>

<xs:sequence>

<xs:element name="user" type="UserNode" minOccurs="0" maxOccurs="unbounded"/>

<xs:element name="group" type="GroupNode" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

</xs:complexType>

</xs:element>

<xs:element name="items" minOccurs="0" maxOccurs="1">

<xs:complexType>

<xs:sequence>

<xs:element name="item" type="XmlNode" minOccurs="0" maxOccurs="unbounded" />

</xs:sequence>

</xs:complexType>

</xs:element>

</xs:all>

</xs:complexType>

<xs:complexType name="UserNode">

<xs:sequence>

<xs:element name="username" type="xs:string" minOccurs="1" maxOccurs="1"/>

<xs:element name="permission" type="PermissionEnum" minOccurs="1" maxOccurs="1"/>

</xs:sequence>

</xs:complexType>

<xs:complexType name="GroupNode">

<xs:sequence>

<xs:element name="groupname" type="xs:string" minOccurs="1" maxOccurs="1"/>

<xs:element name="permission" type="PermissionEnum" minOccurs="1" maxOccurs="1"/>

</xs:sequence>

</xs:complexType>

<xs:simpleType name="PermissionEnum">

<xs:restriction base="xs:string">

<xs:enumeration value="R"/>

<xs:enumeration value="W"/>

</xs:restriction>

</xs:simpleType>

</xs:schema>

Field Definitions:

  • item - any specific item in the custom tree hierarchy.
  • URL - the item's full URL path
  • title -  the item's title as you would like it to be displayed in CardioLog reports
  • entitytype - the item's content type
  • template - the item's content type template, for displaying related icons in the tree structure 

Examples:

Entity type 5 - Folder
Available templates: 
Website Folder - Website_Folder.gifImage Added

Entity type 12 - Page 
Available templates: 
Website Page - Website_Page.GIFImage Added 
Website Folder Page -  Website_Folder.gifImage Added
Website Document - Website_Document.gifImage Added
Website Media - Website_Media.gifImage Added
Website Other - Website_Other.GIFImage Added

You can also define your own custom content types in coordination with Intlock.

  • 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
iconfalse
titleSample Data

 

<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>