Page History
...
- Verify that your system meets the software and hardware requirements.
- Install the Required Web Server (IIS) Role Services on your web server.
- Deploy the CardioLog Analytics SharePoint feature for usage tracking, or add the tracking code to a common page component of your choice (for example - master pages, page toolbars, Web Parts, headers or footers).
- Create a new EventCollector web application on your web server. For the new web application:
- Create a dedicated application pool with ASP.NET version 4.0 and Integrated managed pipeline mode.
- The application pool should run with a local administrator account.
- Grant the application pool account the "db_owner" role on the CardioLog database.
- Set the web application authentication method to Anonymous access (disable Windows Authentication).
- Grant Full Control permissions for the IIS_IUSRS group on the EventCollector folder
- Copy the files from the CardioLog server [CardioLog Installation Directory]\EventCollector to the new directory.
- Copy the files from the CardioLog server [CardioLog Installation Directory]\Setup Files\SLPS to the new directory under \EventCollector\bin folder.
- Execute the following command on your web server: Slps.Runtime.Configuration /Install (execute it from this location - \EventCollector\bin)
- Contact us to receive the required licenses for the web server (product edition and engagement package) and apply it using the License Admin tool (execute it from this location - \EventCollector\bin\Microsoft.Licensing.LicAdmin.exe).
- Create a new CardioLogAgent web application on the web server. For the new web application:
- Create a dedicated application pool with ASP.NET version to 4.0 and Integrated managed pipeline mode.
- The application pool should run with a local administrator account.
- Set the web application authentication method to Windows Authentication (disable Anonymous access).
- Grant Full Control permissions for the IIS_IUSRS group on the CardioLogAgent folder
Copy the files from the CardioLog server [CardioLog Installation Directory]\CardioLogAgent to the new directory.
Edit the following keys in the CardioLogAgent\web.config file, located in the <appSettings> section and enter the NLB FQDN, where [domain name] is the NLB FQDN for the web applications.
Info icon false <add key="EventCollectorPath" value="http[s]://[domain name]/EventCollector/monitor.aspx" />
<add key="CardioLogAgentRoot" value="http[s]://[domain name]"/>
Note: When the EventCollector and CardioLogAgent web applications are installed on your SharePoint WFEs under each SharePoint web application _layouts folder, edit the following keys in the CardioLogAgent\web.config file, located in the <appSettings> section, where [domain name] is the SharePoint web application FQDN.Info icon false <add key="EventCollectorPath" value="http[s]://[domain name]/_layouts/EventCollector/monitor.aspx" />
<add key="CardioLogAgentRoot" value="/_layouts"/>Edit the following URLs in the Java Script tracking code:
Info icon false http[s]://[domain name]/CardioLogAgent/getCAData.aspx?r='+Math.random();
http[s]://[domain name]/CardioLogAgent/ca.aspx?u='+document.location.href;
http[s]://[domain name]/CardioLogAgent/AgentEmbed.aspx?env=[SharePoint version]';
[domain name] - the NLB FQDN for the web application.
[SharePoint version] - MOSS2007, SP2010, SP2013, SP2016 or SPOnline
If the CardioLog Analytics SharePoint feature for usage tracking is deployed, edit the URLs in the following location:
C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\LAYOUTS\CardioLogAgent\CardioLogAgent.jsIf the Java Script tracking code is embedded within a common page component on your SharePoint WFEs, edit the URLs in there.
- In the CardioLog database, edit the URL column 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]')
where name = 'EventCollector'
[Old URL] - http[s]://CardioLog-machine-name:port
[New URL] - http[s]://[domain name]
...