Versions Compared

Old Version 6

changes.mady.by.user Sigalit Hassid

Saved on

compared with

New Version Current

changes.mady.by.user Paul Berkowitz

Saved on

Key

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

CardioLog Analytics uses a logical tree to represent the hierarchical structure of the your 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 item at any level of the website hierarchy.

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

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

...

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

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

  1. Create a CardioLogAgent folder on the web site machineprimary website server.
  2. Copy the installation files into the new folder from [CardioLog Installation Folder]\CardioLogAgent\. 
  3. Open IIS Manager on the web site website 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 aspx (Edit the root name to reflect 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 > Under Administration in the Navigation Pane go to System Configuration > Usage Tracking Code > Select Non-SharePoint Website.
  8. Copy the tracking code provided in the text box.

     
    System Configuration - Usage Tracking Code 
     
  9. Edit the all URLs contained in the tracking code that redirect to the CardioLog application server, to redirect to the web site to your website root URL.
  10. Either add Include the edited tracking code into every page you want to track immediately by:
    • Adding it after the opening <head> tag
    , or you can also use a
    • on each relevant page
    • Use a common JavaScript file
    .
    • that will load on every page within your website 
    • 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.
  11. 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 again.

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 so the CardioLog Portal Tree Updates service component will obtain may catalog 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 in the top right corner.


    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 When using "asmx").
  7. Click Save and restart the CardioLog Scheduling Service by selecting it under Administration and clicking Restart Service in the top right corner..
  8. After the next run of scheduled Portal Tree UpdatesUpdate, the tree structure will be displayed in the Analysis Center (Object Explorer) and will be available for reports that allow content drilldown. 

...

The Custom Tree web service should be exposed by published on 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>

...

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>