Versions Compared

Old Version 5

changes.mady.by.user Paul Berkowitz

Saved on

compared with

New Version 6

changes.mady.by.user Paul Berkowitz

Saved on

Key

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

...

  1. Export the CardioLog registry key to a *.reg file:
    • 32-bit machine  - HKEY_LOCAL_MACHINE\SOFTWARE\Intlock\CardioLog  
    • 64-bit machine  - HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Intlock\CardioLog
  2. Edit the CardioLog registry key (*.reg file):

    "DATABASEINSTANCE"="[database server name]"

    "TARGETDIR"="[CardioLog Installation Folder]"

      [database server name] - The database server name that currently hosts the CardioLog database.
      [CardioLog Installation Folder] - The name of the CardioLog installation folder that will contain the CardioLog application files on the new application server Edit the database server name to match the new server that now hosts the CardioLog application.

  3. Import the CardioLog registry key to the new server by copying the *.reg file to the new server and double clicking on it.
  4. Disable both CardioLog windows services, CardioLog Diagnostics Service and CardioLog Scheduling Service, on the old CardioLog application server.
  5. Run the CardioLog installer on the new server (contact us to receive it). Follow the Installation Wizard steps.
  6. Create a backup of the [CardioLog Installation Folder]\CardioLogScheduleServices\Settings.config on the new server.
  7. Copy the [CardioLog Installation Folder]\CardioLogScheduleServices\Settings.config from the old server to the new server and edit all instances of the CardioLog server name to match your system (http://[CardioLog server name:port]/) and the CardioLog Installation Folder path.
  8. In the CardioLog database, edit the URL and server name columns in the tab_management table by executing the following SQL script:

    Use CardioLog
    GO

    update tab_management set url = replace (url, '[Old URL]', '[New URL]'), servername = replace (servername , '[Old machine name]', '[New machine name]')

    For the respective fields, confirm that all names match your system:

    [Old URL] - http[s]://CardioLog-machine-name:port
    [New URL]     - http[s]://CardioLog-new-machine-name:port
    [Old machine name]     - CardioLog old machine name
    [New machine name]     - CardioLog new machine name

  9. If you have implemented the CardioLog Analytics SharePoint Feature on your Web Front Ends (WFEs), edit all instances of the CardioLog server name (eg., http://[CardioLog server name:port]/ ) in the /_layouts/CardioLogAgent/web.config file, located on the SharePoint WFEs respecitvely:

    For MOSS 2007 only:
    C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE\LAYOUTS\CardioLogAgent/web.config

    For SharePoint 2010, 2013 only:
    C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\LAYOUTS\CardioLogAgent/web.config

    Otherwise, edit the CardioLog Java Script tracking code embedded within a common Java Script file, located on your SharePoint WFEs. The code is located at the end of the file, between the comments: //Intlock tracking code start and  //Intlock tracking code end

    For MOSS 2007 only:
    C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE\LAYOUTS\1033\core.js

    For SharePoint 2010 only:
    C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\LAYOUTS\1033\init.js

    For SharePoint 2013 only:
    C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\TEMPLATE\LAYOUTS\init.js

...

  1. In the Administration pane, click System Configuration, and then select SharePoint Tree Adaptor.
  2. Select your SharePoint farm.
  3. In the SharePoint Tree Adaptor dialog, edit the following fields:
      -      
      • Database Server -
      the
      • The SharePoint database instance name.
      -      
      • SharePoint Configuration Database Name -
      the
      • The SharePoint configuration database name. eg. 
      Example:
      • "SharePoint_Config"
      -      
      • Authentication -
       database
      • Database authentication type
      (windows integrated
      • : Windows Integrated, or SQL
      authentication)
      • Authentication.
      -      
      • SharePoint TEMPLATE Directory - this is the full path for the SharePoint 'TEMPLATE' directory. eg. 
      Example: "
      • \\<sharepoint server name>\C$\Program Files\Common Files\Microsoft Shared\Web Server Extensions\XX\TEMPLATE\" (Where XX - 12 for MOSS 2007
      ,
      • ; 14
      for
      •  for SharePoint 2010
      , 15 for
      • ; 15 for SharePoint 2013)
    • Click Apply.
    • Select the web application/s you want applications you would like to monitor, then click Save.
    • After the next run of Portal Tree Updates, the updated tree structure will be displayed be available in the Analysis Center (and Object Explorer).


      System Configuration - SharePoint Tree Adaptor

In versions lower than 2.0.8.0, follow these steps:
  • If the SharePoint databases are moved to a new server, edit the SharePoint database connection string in the [CardioLog Installation Folder]\SP20XXTree\Web.config file  (Where XX
 -
  •  is 07 for MOSS 2007
,
  • ; 10 for SharePoint 2010
,
  • ; 13 for SharePoint 2013):

<connectionStrings>

<add name="configDB" connectionString="Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=[SharePoint Configuration Database Name];Data Source=

[SharePoint Database Server Name]" />

<add name="contentDB" connectionString="Integrated Security=SSPI;Persist Security Info=False;Initial Catalog={0};Data Source={1}" />

</connectionStrings>

           [SharePoint Configuration Database Name] - edit the Your SharePoint config configuration database name
           [SharePoint Database Server Name] - edit the SharePoint Your SharePoint database server name

  • If the SharePoint web application root URL was modified
and/
  • or the SharePoint web application is hosted on new WFE servers, edit the following keys in the [CardioLog Installation Folder]\SP20XXTree\Web.config file (Where XX
 -
  •  is 07
for
  •  for MOSS 2007
,
  • ; 10
for
  •  for SharePoint 2010
,
  • ; 13
for
  •  for SharePoint 2013)

<add key="includedWebApps" value="[SharePoint web application root URL]" />

<add key="SharePointTemplatePath" value="[SharePoint TEMPLATE path]" />

           [SharePoint web application root URL] - a A star '*' separated list of the monitored SharePoint web applications in the farm
           [SharePoint TEMPLATE path] - edit the SharePoint Your SharePoint TEMPLATE folder path, which should be: 
           \\SharePoint WFE server name\C$\Program Files\Common Files\Microsoft Shared\Web Server Extensions\XX\TEMPLATE\ (Where XX -  is 12 for MOSS 2007, ; 14 for SharePoint 2010 and ; 15 for SharePoint 2013) 

Anchor
configure collection
configure collection
Configure Event Collection

Install You may either install the CardioLog Analytics Tracking Agent Feature as detailed here OR add , or add the Tracking Agent JavaScript Code to each SharePoint WFE. The tracking code should be placed in a SharePoint common .js  js file.

In the Administration pane, click System Configuration , select and select Usage Tracking Code and then select your SharePoint version.