Database Logs ..........................20 Setting up HTTP access to the CUBE ................21 Installing IIS ............................ 21 Copying the pump binaries ......................21 Creating an IIS application pool ..................... 21 Setting up handler mappings......................22 Name extension ..........................23 TANDBERG Analytics Extension Admin guide...
Page 3
Setting the target Analysis Services server ..................25 Creating a domain service account and giving it read access to the cube ........25 Verifying that the connection works ....................25 References and related documents ..................27 Licenses ..........................28 EULA ...........................32 TANDBERG Analytics Extension Admin guide...
Introduction Document Revision History Rev 02 August 2010: Release of version 1.1 Rev 01 May 2010: Release of the Analysis Extension 1.0 TANDBERG Analytics Extension Admin guide...
Introduction This document describes the TANDBERG Analytics Extension. The TANDBERG Analytics Extension is an online analytical processing (OLAP) system for the TANDBERG Management Suite (TMS) and provides advanced reporting functionality on your video network. It integrates with Business Intelligence (BI) applications, custom built applications, and other applications capable connecting to an OLAP cube such as Microsoft Excel.
OLAP compatible clients to access a known and supported list of information about the usage of your visual communications network without disrupting ongoing operations. The Analytics Extension component is installed on an existing TANDBERG Management Suite Server and creates and maintains new information stores. The new information stores enhance the type of data available for TMS customers, and provides a standardized, supported way of accessing reporting data made available through the Analytics Extension.
The following table and illustration explain the various elements involved with the TANDBERG Analytics Extension and how they relate to each other. TMS Web Server – The Windows installation that hosts the TMS web application.
Windows Domain accounts (with reader role permissions). Add http pump ref The data warehouse CUBE connects to the data warehouse database using a data source defined configured to use the DWH service user credentials. TANDBERG Analytics Extension Admin guide...
It only needs SQL login access to the TMS and the db_datareader role on the TMS database. If the account password changes, the installation must be reconfigured. See the Analytics Extension Reconfiguration section for more information. TANDBERG Analytics Extension Admin guide...
4. Go to the Membership subpage. Click Add… to enter users or groups (Figure 1). To grant read access to domain members, use the Everyone group. Use the Authenticated Users group to exclude guest accounts and anonymous users. Figure 1: Managing user rights for accessing the cube TANDBERG Analytics Extension Admin guide...
2. Right-click the instance name in Object Explorer and then click Properties. 3. In the Select a Page pane, click Security. 4. Click Add to add one or more Windows users or groups to the server role. TANDBERG Analytics Extension Admin guide...
This panel shows the status and log details for past runs of the ETL job and can be used to verify the job is running, or help diagnose why the data warehouse databases are not updating. TANDBERG Analytics Extension Admin guide...
Page 13
Run ETL Job Now – Clicking this will manually initiate an immediate ETL job. Note this task may take a significant amount of time to complete. Note: This window does not automatically refresh. Click the Refresh button to refresh the list with the latest information. TANDBERG Analytics Extension Admin guide...
SQL Administrator manually and then use the reconfigure wizard to update your software. Note: TANDBERG recommends that the reconfiguration wizard not be used to replace the source database with an entirely different TMS database. The reconfiguration wizard is useful in cases where the underlying data is either the same, or a logical continuation of the current database (such as the current database with more data).
Cannot insert the value NULL into column „PeakActualVideoCalls‟ This bug only occurs in Analytics extension version 1.0, and is fixed for version 1.1. A patch for version 1.0 exists. Customers encountering this problem can contact TANDBERG Support to obtain the patch. TANDBERG Analytics Extension Admin guide...
3. In the Import Data window that follows, click Properties… 4. Go to the “Definition” tab (Figure 6). 5. Append the text string in the “connection string” field with “;password=<your password>”. Note the semicolon in front. TANDBERG Analytics Extension Admin guide...
After creating a connection, the error message XML for Analysis parser: The LocaleIdentifier property is not overwritable and cannot be assigned a new value may appear when you try to utilize the connection in a pivot table or chart. This issue only TANDBERG Analytics Extension Admin guide...
Page 18
2. Locate the <odc:ConnectionString> element, and append “;Locale Identifier=1033” (note the semicolon) to the end of the element‟s content (Figure 8). Click Save. 3. The connection is now updated and ready for use. Figure 7: Opening the connection for editing TANDBERG Analytics Extension Admin guide...
<Installation Dir>\TANDBERG\Analytics Extension\ReportingService\Logs <Installation Dir>\TANDBERG\Analytics Extension \AdminWeb\App_Data\Logs These files are plain text but are low level and intended for debugging purposes by TANDBERG personal. Database Logs The data warehouse itself also keeps logs useful for troubleshooting; these entries are stored in the database itself in the table‟s orc.ExecutionEventLog.
3. In the “Connections” tree view that opens, right-click Application Pools and choose “Add Application Pool…” 4. Give the new application pool a suitable name (for example “Analytics-pump”), and set Managed pipeline mode to Classic (Figure 9). TANDBERG Analytics Extension Admin guide...
3. Click Edit Feature Permissions… in the Actions list to the far right. 4. Make sure that both Read and Script are selected. Click OK. 5. Click Add Script Map… in the Actions list. A new dialog window now opens (Figure 11). TANDBERG Analytics Extension Admin guide...
2. Click the ISAPI and CGI Restrictions icon from the IIS group (Figure 12). Figure 12 3. A list of extensions appears. Find the extension you just created, select it, and click Edit…. 4. Give the extension a descriptive name (Figure 13), and click OK. TANDBERG Analytics Extension Admin guide...
1. Open the Internet Information Services (IIS) Manager tree view and select the Analytics-pump node 2. Click Default Document. 3. Click Add… in the Actions list. 4. In the dialog box, type msmdpump.dll and click OK. TANDBERG Analytics Extension Admin guide...
This account will be used by all clients that access the HTTP pump. TANDBERG recommends setting up this account so that users are not allowed to change its password. Verifying that the connection works The HTTP pump is now set up and ready to use.
Page 26
Setting up HTTP access to the CUBE When the connection has been created, it can be used in pivot tables and pivot charts just like any other connection to Analysis Services. Figure 16 TANDBERG Analytics Extension Admin guide...
The following table lists documents and websites referenced in this document. All TANDBERG documentation can be found on the TANDBERG website. For advice from the technical support team on all TANDBERG products, see the TANDBERG Knowledge Base. Name Document reference...
Page 29
· publish the software for others to copy; · rent, lease or lend the software; or TANDBERG Analytics Extension Admin guide...
Page 30
(including code) on third party Internet sites, or third party programs; and · claims for breach of contract, breach of warranty, guarantee or condition, strict liability, negligence, or other tort to the extent permitted by applicable law. TANDBERG Analytics Extension Admin guide...
Page 31
It also applies even if Microsoft knew or should have known about the possibility of the damages. The above limitation or exclusion may not apply to you because your country may not allow the exclusion or limitation of incidental, consequential or other damages. TANDBERG Analytics Extension Admin guide...
(COLLECTIVELY, "LICENSEE") TO THIS AGREEMENT. IF YOU DO NOT AGREE TO ALL OF THE TERMS OF THIS AGREEMENT, THEN TANDBERG IS UNWILLING TO LICENSE THE SOFTWARE TO YOU AND (A) DO NOT DOWNLOAD, INSTALL OR USE THE SOFTWARE, AND (B) YOU MAY RETURN THE SOFTWARE AND ALL RELATED DOCUMENTATION (“DOCUMENTATION”) FOR A FULL REFUND.
Page 33
LIMITED WARRANTY. Except as may be required by law in the particular country where the Product is being used, TANDBERG warrants that, for a period of three (3) months from the date of shipment by TANDBERG ("Warranty Period"), the Software will operate substantially in accordance with the Documentation.
Page 34
PROCUREMENT OF SUBSTITUTE GOODS, LOSS OF PROFITS, OR THE LIKE), EVEN IF THE PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. TANDBERG’s MAXIMUM LIABILITY TO LICENSEE FOR DAMAGES ARISING OUT OF OR RELATING TO THE SOFTWARE, WHETHER BASED IN CONTRACT, TORT...
Page 35
EULA TANDBERG‟s licensors are third-party beneficiaries of this License and the provisions hereof are made expressly for the benefit of, and are enforceable by, TANDBERG‟ licensors and their licensors. FOR U.S. GOVERNMENT END USERS. The Software and Documentation are “commercial items” as defined in FAR §2.101, consisting of “commercial computer software”...
Page 36
Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental. TANDBERG Analytics Extension Admin guide...
Need help?
Do you have a question about the ANALYTICS EXTENSION and is the answer not in the manual?
Questions and answers