How it Works
Tandberg
Loading...
ANALYTICS EXTENSION
User Manual
36 pgs1.32 Mb0

Tandberg ANALYTICS EXTENSION User Manual

Download
Page 1
TANDBERG Analytics
Extension
Administrator guide
D14668.01
September 2010
Page 2
Introduction
Contents
Contents............................................................................................................................... 2
Document Revision History ................................................................................................ 4
Introduction ......................................................................................................................... 5
New feature overview .............................................................................................................................. 5
Technical overview ............................................................................................................. 6
Analytics Extension components and roles ................................................................ ...... 7
Data warehouse server ........................................................................................................................... 8
Data warehouse database ............................................................................................................... 8
Data warehouse CUBE .................................................................................................................... 8
Data warehouse updates ................................................................................................................. 9
Service account permissions and uses ................................................................................................... 9
Data warehouse service user ........................................................................................................... 9
DWH TMS service user .................................................................................................................... 9
Adding and managing users .............................................................................................10
Analytics users ...................................................................................................................................... 10
Administrator roles ................................................................................................................................. 11
Analytics extension administrators ................................................................................................. 11
Analysis services server administrators ......................................................................................... 11
Web interface ......................................................................................................................12
Download excel sample files .......................................................................................................... 12
Log ETL jobs .................................................................................................................................. 12
Reconfiguring Analytics Extension ..................................................................................14
Troubleshooting .................................................................................................................15
Web site issues ..................................................................................................................................... 15
ETL job failures .............................................................................................................................. 15
Client Connectivity Issues ..................................................................................................................... 16
Microsoft Excel and Windows Authentication ................................................................................ 16
The LocaleIdentifier property.......................................................................................................... 17
Logs ....................................................................................................................................20
Application Logs ............................................................................................................................. 20
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
Page 3
Introduction
Choosing an authentication mode .................................................................................................. 24
Setting msmdpump.dll as the default document ............................................................................ 24
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
Page 4
Document Revision History
Rev 02
August 2010: Release of version 1.1
Rev 01
May 2010: Release of the Analysis Extension 1.0
Introduction
Page 5
Introduction
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.
The TANDBERG Analytics Extension API is described in a separate document, TANDBERG Analytics
Extension API Documentation.
This document, along with the installation guide, release notes, and other documentation can be found at the Support > Documentation section of http://www.tandberg.com.
New feature overview
Analytics Extension version 1.1 is a maintenance release, with additional Analytics Extension cube features, installer enhancements, and improved logging.
The main improvement to the cube is a new fact table; Fact MCU Utilization. This supersedes the old Fact MCU Load, which is no longer available. As a result, existing reports that use Fact MCU Load must be updated to use the new measures. Fact MCU Utilization basically the end user access to the same data as before, but with improved data quality. In addition, the new fact table contains aggregated data about MCU usage across the entire installation, and can filter results on arbitrary MCUs.
Two bracket dimensions have been introduced: Actual Duration Brackets and Actual System Count Brackets. Both apply to Fact Conference. Actual Duration Brackets shows the mode average (most common conference durations). Actual System Count breaks down conferences by the number of participants.
A new Persistent System dimension has been introduced. This dimension is a variant of the System dimension. Persistent System will always associate historical call data with the current system information. The Persistent System dimension has the exact same attributes and hierarchies as the System dimension. This means systems can be renamed without losing associated historical data.
The installer now creates logs automatically, and will expose the version number in the log files. Also, the installer will catch some common TMS and DWH SQL server configuration mistakes and warn the user accordingly.
The Microsoft Excel example reports have been updated and use more intuitive descriptions. The ETL job has been made more robust, and handles TMS database data mismatches that could make the
1.0 ETL job fail.
Page 6
Technical overview
33.3
333
%
33.3
333
%
33.3
333
%
TANDBERG
VCS
TANDBERG
Analytics
Extension
Business
Intelligence User
End-
Users
Visual Communications
Network
Administrators
TANDBERG
TMS
Technical overview
The sections provide technical explanations of how the Analytics Extension components are created and used in ongoing operations, to assist administrators understand system dependencies.
TANDBERG Analytics Extension brings business intelligence, customized reporting, and high performance data mining to TMS. Analysis and data from your visual communications network can be accessed via industry standard tools.
Analytics Extension makes the best use of Microsoft‟s powerful SQL Server Analysis Services to provide business knowledge and customized reporting on your TANDBERG TMS Server, and integration with Business Intelligence applications. Analytics Extension enables the use of standardized, 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.
TANDBERG Analytics Platform
Page 7
Analytics Extension components and roles
TMS Web Server – The Windows installation that hosts the TMS web application. The TMS Web Server also requires a TMS SQL Server, which may or may not be the same Windows Server.
TMS SQL Server – The Microsoft SQL Server hosting the TMS Database. In smaller installations, this server is typically hosted on the same physical server that the TMS Web Server is hosted on. In advanced installations, these tasks are usually different physical Windows Servers.
tmsng
TMS Database – The main database used by TMS itself. This database is hosted by the TMS SQL server role and the default name of the database is tmsng.
TMS SQL Login – The SQL Login used by the TMS Web Server to access the tmsng database. By default, this is the sa account of the TMS SQL server, but can be customized during TMS installation.
Data Warehouse Server – The Microsoft SQL Server that will be hosting the Analytics Databases and SQL Server Analysis Services. This server can be the same SQL server as the TMS SQL Server, but is recommended to be a separate SQL server. This Server installation must be operational before attempting to install the Analytics Extension.
tmsng_dwh
Data Warehouse Database – A new database created by the Analytics Extension which serves as the long-term data repository for the Analytics Extension. This database is hosted by the Data Warehouse Server
CUBE
Data Warehouse CUBE – A new specialized multi-dimensional database created by the Analytics Extension which contains the pre-computed data created by the Analytics Extension. This database is hosted by the SQL Server Analysis Services Instance running on the Data Warehouse Server.
DWH Service User – A Windows domain user account used by the Analytics Extension to log into the data warehouse Server for ongoing operations. This account will be given the necessary permissions by the Analytics Extension installer.
DWH TMS Service User – A SQL Login for the TMS SQL server used by the Analytics Extension to read data from the TMS Database. This account is a SQL Login, not a Windows Account and must have at least the db_datareader role. See Appendix 2: Creating User Accounts in Windows Server and Microsoft SQL Server in the Analytics Extension installation guide for information on how to set up such an account.
Analytics Extension components and roles
To plan a deployment of the Analytics Extension, it is important to understand the components and roles used in the solution so you can deploy the solution in the best possible way for your environment. The following table and illustration explain the various elements involved with the TANDBERG Analytics Extension and how they relate to each other.
Page 8
Analytics Extension components and roles
tmsng_dwh
CUBE
tmsng
TMS Web Server
TMS SQL Server
Data Warehouse
Server
TMS SQL
Login
Analytics User
VCS
OLE DB
Feedback
Figure 1 Illustration of Roles and Components
Data warehouse server
Analytics Extension comprises two major elements - the data warehouse database, and the data warehouse CUBE.
Data warehouse database
The data warehouse database is used for analysis and data mining, and contains information from the TMS database combined with data computations and analysis.
Using credentials specified by the installing user, the data warehouse database is created in a SQL server instance of the data warehouse server. The default database name is tmsng_dwh. The DWH (data warehouse) service user is defined as the owner of the database, and this service account is used by the Analytics Extension to log into the database for ongoing operations. Ordinary users of the Analytics Extension API do not connect to this database.
The data warehouse database accesses the TMS database through a linked server, created on the data warehouse server during installation. The linked server is created automatically using the TMS database location and DWH TMS service user credentials supplied during installation. The DWH TMS service user is an SQL login for the TMS SQL server. This account only needs db_datareader role to access the TMS database, and can reuse any existing login with sufficient SQL access permissions.
Data warehouse CUBE
The data warehouse CUBE is a specialized type of database used in analysis and data mining. Its main advantage is its ability to hold pre-computed aggregates of data across many different dimensions, allowing fast manipulation of queries. The data warehouse CUBE holds different data defined as „facts‟, each of which has different defined „dimensions‟, which can be used to manipulate the information stored in the different fact tables. Analytics Extension provides sets of facts and dimensions that can be used by programmers and analytics users.
The data warehouse CUBE is created during installation in the Analysis Services instance on the data warehouse server. The default name for the database is tmsng_dwhAsDb (its name format must always be <database>AsDb). The DWH service user is configured as the owner of the CUBE and the DWH service user credentials are used by Analytics Extension to connect to the cube for ongoing operations. Ordinary users of the Analytics Extension API connect to this CUBE using an OLAP client and their 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.
Page 9
Analytics Extension components and roles
Data warehouse updates
Data mining and long term analysis of information is done using historical data. The focus is on historical data, instead of real-time data. Because of this, the data warehouse contents are not recorded in real-time as in the traditional reporting information viewed via TMS. Instead the DWH data is refreshed daily by the Windows Service installed on the TMS web server by the Analytics Extension.
The Windows Service initiates two updates, the ETL Task and the CUBE refresh. The ETL (Extract, Transform, Load) task extracts from the TMS database all new (recorded since the last time the ETL task run) data updates values and computations stored in the data warehouse database. Because only new information is processed, the ETL task is extremely efficient. This task is initiated by the Analytics Extension‟s Windows Service connecting to the data warehouse server at a scheduled time using the supplied DWH service user credentials. The ETL job executes on the data warehouse server and uses the defined linked server to read information from the TMS database. There is no significant extra load placed the TMS web server. An administrator may also initiate the ETL job to run immediately via the Analytics Extension web interface in TMS.
The CUBE refresh is performed daily after the data warehouse database has been updated by the ETL task. To initiate this update, the Analytics Extension Windows Service on the TMS Web Server connects to the Analytics Service on the data warehouse server using the DWH service user credentials and tells the CUBE to refresh. The CUBE uses the connection properties defined in the CUBE‟s Data Source definition to connect to the data warehouse database.
Service account permissions and uses
Data warehouse service user
The data warehouse service user account is used by Analytics Extension to log into the data warehouse database and data warehouse CUBE. This user account must be a valid Windows Domain account. It does not need any pre-existing permissions. It is also used by the data warehouse CUBE to connect to the data warehouse database in the Database Engine instance.
If the account password changes the installation must be reconfigured. See the Analytics Extension
Reconfiguration section for more information.
DWH TMS service user
The TMS service user account is used by the data warehouse server to pull data from the TMS database. This account must have an SQL Login capable of connecting to the TMS database tmsng. 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.
Page 10
Adding and managing users
Adding and managing users
There are two classes of users for the Analytics Extension:
administrators who have access to diagnostic information and settings analytics users who are consumers of the Analytics Extension data output
SQL Server Analysis Services (SSAS) uses a strict security model and only Windows authentication is supported. Any user or client who wishes to be an administrator or analytics user must have a valid Windows Domain account the SSAS instance trusts. Some software clients allow a user to specify which account they will use to authenticate to SSAS; others only support Integrated Authentication where the credentials of your current user identity are used.
Analytics users
Users who wish to read data from the Analytics Extension must have access to the data warehouse CUBE hosted by the SQL Server Analysis Service (SSAS). An account with SSAS access does not necessarily have the right to read the data warehouse CUBE.
SSAS offers administrators a wide variety of permissions possibilities for users, but to ease configuration the data warehouse CUBE has a custom reader role defined during installation. Users who are members of this role will have access to read, but not modify any information in the data warehouse CUBE. Access to the information made available via the Analytics Extension should be granted by adding users to this reader role.
To add a new user to the reader role:
1. Open Management Studio, and connect to the relevant SSAS instance.
2. Locate Databases > tmsng_dwhAsDb > Roles.
3. Right-click Reader and select Properties.
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
Page 11
Adding and managing users
To remove a user from the reader role:
1. Open Management Studio, and connect to the relevant SSAS instance.
2. Locate Databases > tmsng_dwhAsDb > Roles.
3. Right-click Reader and select Properties.
4. Go to the Membership subpage. Select the user to remove and click Remove.
Administrator roles
Analytics extension administrators
To view the Analytics Extension web interface, you must be a member of a user group in TMS that has the Configuration > Read permission. To run the ETL job, the user must be a member of a user group in TMS that has the Configuration > Update permission.
Group membership and group permissions are managed in the User Administration pages of TMS, located at Administrative Tools > User Administration.
Analysis services server administrators
Access to the data warehouse CUBE and data exposed by the Analytics Extension is controlled via the SSAS administrator role. Administrative privileges for the Analysis Services instance are controlled by the server role in the Analysis Services server instance.
By default, local administrators of the Windows Server are members of the server role and have full access to all features and data in the server instance. Other users can be added to the server role to grant them administrator rights. To add another user to the server role:
1. In SQL Server Management Studio, connect to the instance of Analysis Services.
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.
Page 12
Web interface
Web interface
The Analytics Extension web interface is accessed via your existing TMS installation. This section provides further interface information.
Note: If the server name or address used in the URL to access TMS and the address in the Analytics Extension URL configured in Administrative Tools are different, you may be prompted with a username/password dialog when accessing the Analytics Extension.
Figure 2: The Analytics Extension web interface
Download excel sample files
Sample Excel workbooks are included with Analytics Extension. See the TANDBERG Analytics
Extension installation guide for more information on installing these example spreadsheets.
Log ETL jobs
The ETL job extracts information from the source TMS database and updates the data warehouse server databases. 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.
Page 13
Web interface
Job Status – Shows a checkmark if the job was complete, a red x if it failed, or a gear icon if it is
currently in progress.
Start Time – The start time of the job, in TMS Server time Batch Duration – How long the job has been running for or how long the job took to complete Batch Errors – If a job fails, diagnostic information is listed here. Click on the entry to expand the
box and see more information.
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.
Page 14
Reconfiguring Analytics Extension
Reconfiguring Analytics Extension
Analytics extension provides wizard to help you through reconfiguring your setup. Common causes for reconfiguration are to update a server address, an expired password, other account information, or your server configuration or your network changes.
The wizard allows you to update:
destination database server name or IP address user name and password for the data warehouse service account source TMS database server name or IP address
While the reconfiguration wizard allows you to update the server addresses used by the installation, it cannot move any databases or create new accounts. The wizard can only be used to update your installation with external changes. If you need to change which servers host the TMS or data warehouse databases, those changes must be made by the 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).
Reconfiguring Analytics Extension will temporarily halt other web services on the same IIS, as the World Wide Web Publishing Service will be stopped and restarted by the wizard. The expected downtime is a few seconds.
The reconfiguration wizard will summarize your proposed changes and wait for confirmation before making any changes.
1. Open the Start menu and select TANDBERG > Reconfigure TANDBERG Analytics Extension.
2. Follow the onscreen prompts.
Page 15
Troubleshooting
Troubleshooting
Web site issues
User does not have sufficient permissions in TMS to view this module
A bug in SQL server can produce this error even when permissions are set correctly. A failed login attempt results in the following message in the web application log file log-AdminWeb.txt:
System.Data.SqlClient.SqlException: Login failed for user '<domain/account>'. Reason: Server is in script upgrade mode. Only administrator can connect at this time.
This can occur after a fresh installation of Microsoft SQL Server or after installing a SQL server service pack. To resolve this issue reboot the server.
An error has occurred!
This generic error message asks you to look in the logs for further information. The most common cause is SQL connectivity problems. Look for an SQL Network Interfaces:
Error Locating Server/Instance Specified message in log-AdminWeb.txt. Refer to the Analytics Extension installation guide for information on troubleshooting connection
errors.
Figure 3: The generic “An error has occurred” message
ETL job failures
Cannot insert the value NULL into column…
For some video networks with high MCU activity, the ETL job may fail with an error message:
Cannot insert the value NULL into column „PeakAudioCallBitrate‟ Cannot insert the value NULL into column „PeakVideoCallBitrate‟ 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.
Page 16
Troubleshooting
Figure 4: The “Cannot insert the value NULL into column…” bug as seen in the “Log ETL jobs” panel.
Multiple “Error: Internal error: The operation terminated unsuccessfully.”
Getting multiple Error: Internal error: The operation terminated unsuccessfully. messages in the same ETL job indicates that there have been major changes in the TMS database since you last ran the job (Figure 5), and that the Analytics Extension is unable to extract data because of schema changes or changes in constraints.
These errors can occur if you have used the reconfiguration tool to replace the source database with an entirely different TMS database. As described in Analytics Extension Reconfiguration section, the wizard tool should not be used for such changes. To fix the problem, use the reconfiguration tool again to return the source database to the original TMS database.
Figure 5: Multiple “Error: Internal error: The operation terminated unsuccessfully.” messages from the same failed ETL job.
Client Connectivity Issues
Microsoft Excel and Windows Authentication
Initialization of the data source failed
When connecting to a data warehouse Cube in environments where Integrated Authentication is not available or fails, Excel will run into authentication problems. The user will not be warned about this when creating the connection to Analysis Services and the connection will apparently be created properly. However, later when the user tries to use the connection in a Pivot Table or Pivot Chart, the user will get an Initialization of the data source failed error.
A workaround to the problem is appending the connection string manually:
1. In Excel, go to Data > Existing Connection.
2. Select the relevant connection, and click Open.
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.
Page 17
Troubleshooting
Example: If the user account is named “peter.jones”, the connection string might look like this:
Provider=MSOLAP.3;Persist Security Info=True;User ID=REPORTING\peter.jones;Initial Catalog=tmsng_dwhAsDb;Data Source=analytics.reporting.tms.lab;MDX Compatibility=1;Safety Options=2;MDX Missing Member Mode=Error
If the password of the account is “ENGLAND66”, the modified string should look like this:
Provider=MSOLAP.3;Persist Security Info=True;User ID=REPORTING\peter.jones;Initial Catalog=tmsng_dwhAsDb;Data Source=analytics.reporting.tms.lab;MDX Compatibility=1;Safety Options=2;MDX Missing Member Mode=Error;password=ENGLAND66
Checking the “Save password” box will make the changes to the connection string persistent. However, note that the connection string is stored unencrypted in an XML file on the local disk.
Figure 6: Manually appending the connection string
The LocaleIdentifier property
XML for Analysis parser: The LocaleIdentifier property is not overwritable and cannot be assigned a new value
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
Page 18
Troubleshooting
applies to certain combinations of old versions of Excel and SSAS. The following Microsoft Connect page describes a workaround Error when creating an Excel Pivot Table from a SSAS project.
1. Right click the connection in the Select Data Source window and select Open with > Notepad (Figure 7) to edit the connection file as described in the Microsoft Connect page,.
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
Page 19
Troubleshooting
Figure 8: Appending the connection string
Page 20
Logs
Logs
If you experience difficulties with the TANDBERG Analytics Extension, technical support may ask you to supply log files along with a description of your issue. The follow sections outline the types of logs available. For information on installer logs see TANDBERG Analytics Extension Installation Guide
Application Logs
Problems with the Analytics Extension web interface or the Windows Service that initiates the update jobs are logged in files located on the web server where the Analytics Extension was installed. Logged events from the Analytics Extension web interface and the Analytics Extension Service are stored in the following locations:
<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. orc.ErrorEventLog. dwh.AppliedPatch, and dwh.InstallerEventLog. These logs may be browsed using any SQL tool. To save all the entries in these logs to a file:
1. Open Management Studio and connect to the database engine instance
2. Expand Databases, find your data warehouse database (tmsng_dwh by default)
3. Right-click on the database and select “New Query”.
4. Set the Results to save to a file. Right click in the Query Menu, and select Results to > Results
to File.
5. In the query window, type in the follow four commands SELECT * FROM orc.ExecutionEventLog;
SELECT * FROM orc.ErrorEventLog; SELECT * FROM dwh.AppliedPatch; SELECT * FROM dwh.InstallerEventLog;
6. Click the Execute button to run the query. You will be prompted for a file name to save the results to. This will be a CSV file of the output you can share with technical support if requested.
Page 21
Setting up HTTP access to the CUBE
Setting up HTTP access to the CUBE
This chapter describes how to configure a Windows 2008 Server running SQL Server 2008 so that users may connect to the Analytics Extension CUBE without providing AD credentials. This makes it easier to connect to the CUBE for clients residing in an AD domain beyond the data warehouse server, or clients outside your network.
This solution uses HTTP for data access, taking advantage of IIS 7 as a middleware component to enable access to the CUBE. A small IIS web application – commonly known as an “HTTP pump” – will be set up on the data warehouse Windows server (which may or may not be identical to the TMS server, depending on your setup). This application acts as a “pump” that receives requests, authenticates them, and creates a security context for the requests before forwarding them to Analysis Services. After Analysis Services has executed the request, the pump will in a similar fashion pass the response back to the client.
This approach may also be used in scenarios where IIS and Analysis Services run on different computers. However, Windows does not by default allow AD delegation (remote impersonation by a server of other clients). If using an IIS separate from the Analysis Services server, you must set up Kerberos authentication and configure the domain to allow delegation before proceeding.
Installing IIS
Make sure that IIS is installed on the Windows server you want to set the HTTP pump set up on, normally the data warehouse server.
1. Open Start > Administrative Tools > Server Manager
2. Check if Web Server IIS is mentioned on the Roles Summary pane. If IIS is not already installed, click Add Roles and follow the installation wizard.
IIS needs the ISAPI Extensions role service installed, as well as an Authentication component. This document assumes that Basic authentication is installed. However, this authentication method transmits passwords using an easily decrypted algorithm, and should not be used if you are sending sensitive data over the public internet (unless you are also using SSL). It should however, be sufficient for internal networks.
To check if these components are installed:
1. Use the tree view in Server Manager and go to the Roles node.
2. Open the Web Server (IIS) pane, and if ISAPI Extensions and Basic Authentication (or the authentication method of your choice) have their status set to Installed, it is not necessary to install them. If they are not installed, install them by clicking Add Role Services and follow the installation wizard.
Copying the pump binaries
You must now manually copy binary files from Analysis Services to the directory that you want to use as the basis for your HTTP pump web application.
In a default 32bit installation of SQL Server 2008, the required files are located in C:\Program Files\Microsoft SQL server\MSAS10.MSSQLSERVER\OLAP\bin\isapi. Copy all of the files and subdirectories of this folder to a subdirectory of C:\inetpub\wwwroot, for example to C:\inetpub\wwwroot\analytics-pump. Do not use a path that contains spaces.
Creating an IIS application pool
1. Open Server Manager
2. Locate the Server Manager > Roles > Web Server (IIS) > Internet Information Services (IIS) Manager node.
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).
Page 22
Setting up HTTP access to the CUBE
Figure 9 Locate Default Web Site in the tree view. Right-click Default Web Site, and choose Add
Application… (Figure 10Error! Reference source not found.).
1. Give the application an alias (for example “Analytics-pump”)
2. Click Select… and choose the application pool you created above
3. Set the Physical path field to the location of the pump binaries (for example C:\inetpub\wwwroot\analytics-pump, see above)
4. Click OK to close the Add Application dialog.
Figure 10
Setting up handler mappings
1. Open the Internet Information Services (IIS) Manager tree view, and select the newly created web application.
2. Select Handler Mappings from the menu.
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).
Page 23
Setting up HTTP access to the CUBE
6. In the Request path: filed, type *.dll
7. Click …, and locate the folder that you copied the binaries to. Select msmdpump.dll and click Open.
8. Give a suitable name in the Name: field, for example Analytics-pump.
9. Click OK. You are now asked if you want to allow this ISAPI extension. Click Yes.
Figure 11
Name extension
1. Go to the Internet Information Services (IIS) Manager tree view and select the server node.
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.
Page 24
Setting up HTTP access to the CUBE
Figure 13
Choosing an authentication mode
Select the Analytics-pump node from the tree view, and click Authentication. You will now get a list of all authentication methods installed on your IIS server.
1. Right-click Anonymous Authentication and click Disable.
2. Right-click Basic Authentication and click “Enable.
3. Right-click Basic Authentication and click “Edit…
4. An Edit Basic Authentication Settings window opens (Figure 14). Enter the Windows domain of the data warehouse server in both the Default domain and Realm fields. Click OK.
Figure 14
Setting msmdpump.dll as the default document
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.
Page 25
Setting up HTTP access to the CUBE
Setting the target Analysis Services server
1. Open the folder containing the binary files (C:\inetpub\wwwroot\analytics-pump, if you used the example values above).
2. Open the msmdpump.ini file in a text editor.
3. Locate the <ServerName>localhost</ServerName> line in the .ini file.
4. If you installed Analysis Services using the default instance, leave the setting unchanged. If you use a named instance of Analysis Services, change the setting accordingly. For example, if the instance is named “myinstance”, the line should be changed to <ServerName>localhost\myinstance</ServerName>.
5. If you installed the HTTP pump on another server than your data warehouse server, replace localhost with the data warehouse machine name.
Creating a domain service account and giving it read access to the cube
You will need to create a domain account that is allowed to read the cube. This may be any domain account, as long as it is member of the Reader role defined in the tmsng_dwhAsDB Analysis Services database. See the Analytics Extension Installation guide for instructions on adding accounts to this role.
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. You should verify your setup by connecting to it from a computer that is not in the same domain as the
data warehouse server. It is assumed in this section that you are using Microsoft Excel to test the connection, but any client that can connect to an OLAP cube may be used.
Open a new workbook, and create a new workbook connection to Microsoft SQL Server Analysis Services by going through Excel‟s Data Connection Wizard. See the TANDBERG Analytics Extension
Installation guide for a guide to creating connections.
In the step where you normally enter the server name, enter the url to the HTTP pump instead (Figure
15). For example, if your IIS resides on dwh.example.com, the full url to the HTTP pump will be
http://dwh.example.com/analytics-pump/ (note the trailing slash). Use the username and password of the service account you just created.
Figure 15
When saving the data connection file, make sure to select Save password in file (Figure 16).
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
Page 27
References and related documents
Name
Document reference
TANDBERG Analytics Extension Installation Guide
D14657
TANDBERG Analytics Extension API Documentation
D14701
References and related documents
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.
Page 28
Licenses
Licenses
TANDBERG Analytics Extension © NOTICE
TANDBERG Analytics Extension PRODUCT
Copyright © 2010 Tandberg Telecom AS. All right reserved.
TANDBERG® is a trademark belonging to Tandberg Telecom AS and Tandberg ASA.
This product has been developed using software that is protected under copyright and other laws. Such software can be used under the following terms and conditions:
Apache License, Version 2.0:
Software released under the Apache License, Version 2.0: log4net.
The license can be found at http://www.apache.org/licenses/LICENSE-2.0.html
Microsoft End-User License Agreement:
Software released under the Microsoft End-User License Agreement: MICROSOFT SQL SERVER 2008 ADOMD.NET.
MICROSOFT SOFTWARE LICENSE TERMS
MICROSOFT SQL SERVER 2008 ADOMD.NET
These license terms are an agreement between Microsoft Corporation (or based on where you live, one of its affiliates) and you. Please read them. They apply to the software named above, which includes the media on which you received it, if any. The terms also apply to any Microsoft
· updates,
· supplements,
· Internet-based services, and
· support services
for this software, unless other terms accompany those items. If so, those terms apply.
BY USING THE SOFTWARE, YOU ACCEPT THESE TERMS. IF YOU DO NOT ACCEPT THEM, DO NOT USE THE SOFTWARE.
If you comply with these license terms, you have the rights below.
Page 29
Licenses
1. INSTALLATION AND USE RIGHTS. You may install and use any number of copies
of the software on your devices for your use solely with Microsoft SQL Server 2008 software.
2. ADDITIONAL LICENSING REQUIREMENTS AND/OR USE RIGHTS.
a. Distributable Code. The software is “Distributable Code” that you are permitted to distribute in programs you develop if you comply with the terms below.
i. Right to Use and Distribute.
· Distributable Code. You may copy and distribute the object code form of the
Distributable Code. You may not modify the Distributable Code and your programs must include a complete copy of the Distributable Code, including set-up.
· Third Party Distribution. You may permit distributors of your programs to copy and
distribute the Distributable Code as part of those programs.
ii. Distribution Requirements. For any Distributable Code you distribute, you must
· add significant primary functionality to it in your programs;
· require distributors and external end users to agree to terms that protect it at least as
much as this agreement;
· display your valid copyright notice on your programs; and
· indemnify, defend, and hold harmless Microsoft from any claims, including
attorneys’ fees, related to the distribution or use of your programs.
iii. Distribution Restrictions. You may not
· alter any copyright, trademark or patent notice in the Distributable Code;
· use Microsoft’s trademarks in your programs’ names or in a way that suggests your
programs come from or are endorsed by Microsoft;
· distribute Distributable Code to run with a software program other than Microsoft
SQL Server 2008 software;
· include Distributable Code in malicious, deceptive or unlawful programs; or
· modify or distribute the source code of any Distributable Code so that any part of it
becomes subject to an Excluded License. An Excluded License is one that requires, as a condition of use, modification or distribution, that
· the code be disclosed or distributed in source code form; or
· others have the right to modify it.
3. Scope of License. The software is licensed, not sold. This agreement only gives you
some rights to use the software. Microsoft reserves all other rights. Unless applicable law gives you more rights despite this limitation, you may use the software only as expressly permitted in this agreement. In doing so, you must comply with any technical limitations in the software that only allow you to use it in certain ways. You may not
· work around any technical limitations in the software;
· reverse engineer, decompile or disassemble the software, except and only to the
extent that applicable law expressly permits, despite this limitation;
· make more copies of the software than specified in this agreement or allowed by
applicable law, despite this limitation;
· publish the software for others to copy;
· rent, lease or lend the software; or
Page 30
Licenses
· use the software for commercial software hosting services.
4. BACKUP COPY. You may make one backup copy of the software. You may use it
only to reinstall the software.
5. DOCUMENTATION. Any person that has valid access to your computer or internal
network may copy and use the documentation for your internal, reference purposes.
6. TRANSFER TO A THIRD PARTY. The first user of the software may transfer it and
this agreement directly to a third party. Before the transfer, that party must agree that this agreement applies to the transfer and use of the software. The first user must uninstall the software before transferring it separately from the device. The first user may not retain any copies.
7. Export Restrictions. The software is subject to United States export laws and
regulations. You must comply with all domestic and international export laws and regulations that apply to the software. These laws include restrictions on destinations, end users and end use. For additional information, see www.microsoft.com/exporting.
8. SUPPORT SERVICES. Because this software is “as is,” we may not provide support
services for it.
9. Entire Agreement. This agreement, and the terms for supplements, updates, Internet-
based services and support services that you use, are the entire agreement for the software and support services.
10. Applicable Law.
a. United States. If you acquired the software in the United States, Washington state law governs the interpretation of this agreement and applies to claims for breach of it, regardless of conflict of laws principles. The laws of the state where you live govern all other claims, including claims under state consumer protection laws, unfair competition laws, and in tort.
b. Outside the United States. If you acquired the software in any other country, the laws of that country apply.
11. Legal Effect. This agreement describes certain legal rights. You may have other rights
under the laws of your country. You may also have rights with respect to the party from whom you acquired the software. This agreement does not change your rights under the laws of your country if the laws of your country do not permit it to do so.
12. Disclaimer of Warranty. The software is licensed “as-is.” You bear the risk of using
it. Microsoft gives no express warranties, guarantees or conditions. You may have additional consumer rights under your local laws which this agreement cannot change. To the extent permitted under your local laws, Microsoft excludes the implied warranties of merchantability, fitness for a particular purpose and non-infringement.
13. Limitation on and Exclusion of Remedies and Damages. You can recover from
Microsoft and its suppliers only direct damages up to U.S. $5.00. You cannot recover any other damages, including consequential, lost profits, special, indirect or incidental damages.
This limitation applies to
· anything related to the software, services, content (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.
Page 31
Licenses
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.
Page 32
EULA
EULA
TANDBERG Analytics Extension EULA
TANDBERG Analytics Extension PRODUCT END USER LICENSE AGREEMENT
IMPORTANT: PLEASE READ THIS END USER LICENSE AGREEMENT CAREFULLY BEFORE USING THE TANDBERG Analytics Extension SOFTWARE
(the “SOFTWARE”) SUPPLIED BY TANDBERG AND/OR ITS AFFILIATES ("TANDBERG") AND ACCEPTING THIS LICENSE AGREEMENT.
TANDBERG IS WILLING TO LICENSE THE SOFTWARE TO YOU ONLY UPON THE CONDITION THAT YOU ACCEPT ALL OF THE TERMS CONTAINED IN THIS LICENSE AGREEMENT. BY ACCEPTING THIS LICENSE AGREEMENT, YOU ARE BINDING YOURSELF AND THE BUSINESS ENTITY THAT YOU REPRESENT (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.
LICENSE. TANDBERG, or its licensors, owns all intellectual property rights, including patent, copyright, trade secret, trademark and other proprietary rights, in and to the Software
and Documentation. Licensee’s rights are limited to those expressly granted in this
Agreement.
This Agreement hereby grants to Licensee a non-transferable and non-exclusive license to use, solely for Licensee’s communication purposes, the Documentation and object code version of the Software, for the particular number of user licenses ordered and paid for by the Licensee and identified in the Purchase Order or invoice for the Software, under the terms and conditions set forth herein.
Licensee may:
permit third party service providers to utilize the Software on Licensee’s behalf
within the scope of license granted herein, provided such third party service provider agrees to be bound by the terms and conditions of this Agreement;
make a copy of the Software for backup and/or archival purposes; and copy and use the Documentation as reasonably necessary in connection with
Licensee’s authorized use of the Software.
Page 33
EULA
Licensee may not:
modify, adapt, decompile, disassemble, or reverse engineer the Software, except to
the extent that the foregoing restriction is expressly prohibited by applicable law;
make unauthorized copies of the Software or the Documentation; or without the prior written consent of TANDBERG, transfer or assign Licensee’s rights
under this Agreement, including an assignment by operation of law.
Licensee acknowledges and agrees that:
Licensee will include on permitted copies of the Software and Documentation all
copyright, trademark and other proprietary rights notices included on the originals;
the Software and Documentation may contain valuable proprietary information and
trade secrets of TANDBERG and its licensors and the Licensee shall protect the secrecy of, and avoid disclosure and unauthorized use of, the Software and Documentation, using at least those measures that Licensee takes to protect its own confidential information, (provided, however, that confidential information does not include the Software in object code form or Documentation that TANDBERG provides to others without an obligation of confidentiality);
Licensee shall comply with all applicable export control laws and regulations with
respect to the Software and Documentation;
any violation or threatened violation of this Agreement may cause irreparable injury to
TANDBERG for which equitable relief may be appropriate, in addition to all legal remedies; and
upon violation of any of the provisions of this Agreement or the expiration of the term
of this License, Licensee’s rights to use the Software and Documentation shall automatically terminate and Licensee shall return to TANDBERG or destroy all copies of the Software and Documentation.
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. TANDBERG does not warrant that the
functions of the Software will meet Licensee’s requirements or that operation of the Software
will be uninterrupted or error free. Licensee must inform TANDBERG in writing during the Warranty Period if the Software does not operate as warranted and provide to TANDBERG such information and materials as TANDBERG may reasonably request to document and reproduce such problem and to verify whether any proposed solution corrects such problem. Following the receipt of such information and materials, if TANDBERG determines that the Software does not operate as warranted, then TANDBERG will at its election, either: (a) modify the Software so that it does operate as warranted; (b) replace the Software with other software offering substantially similar functionality; or, (c) if neither (a) nor (b) is commercially feasible, refund the amounts paid to TANDBERG for the Software.
EXCLUSIONS. TANDBERG will have no responsibility, warranty or other obligations whatsoever if Licensee: (a) uses the Software in a manner inconsistent with its intended purpose or the Documentation; (b) modifies the Software without TANDBERG’s authorization; or (c) causes a failure of the Software through accident, abuse or misapplication.
Page 34
EULA
NO OTHER WARRANTIES. TO THE FULLEST EXTENT ALLOWED BY LAW, THE WARRANTIES AND REMEDIES PROVIDED IN THE LIMITED WARRANTY SECTION ARE EXCLUSIVE AND IN LIEU OF ALL OTHER WARRANTIES, EXPRESS OR IMPLIED IN FACT OR BY OPERATION OF LAW, STATUTORY OR OTHERWISE, INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, ACCURACY OF INFORMATION GENERATED, SATISFACTORY QUALITY, AND NON­INFRINGEMENT, ALL OF WHICH ARE EXPRESSLY DISCLAIMED. THESE DISCLAIMERS OF WARRANTY CONSTITUTE AN ESSENTIAL PART OF THIS AGREEMENT.
LIMITATION OF LIABILITY. TO THE FULLEST EXTENT ALLOWED BY LAW, THE PARTIES EXCLUDE ANY LIABILITY, WHETHER BASED IN CONTRACT, TORT (INCLUDING NEGLIGENCE), OR ANY OTHER LEGAL THEORY, FOR INDIRECT, CONSEQUENTIAL, INCIDENTAL, SPECIAL OR PUNITIVE DAMAGES OF ANY KIND (INCLUDING DAMAGES FOR INTERRUPTION OF BUSINESS, 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 (INCLUDING NEGLIGENCE), OR ANY OTHER LEGAL THEORY, WILL NOT EXCEED THE AMOUNTS PAID BY LICENSEE FOR THE PARTICULAR SOFTWARE GIVING RISE TO THE CAUSE OF ACTION.
THE DISCLAIMERS AND LIMITATIONS OF LIABILITY ABOVE WILL NOT BE AFFECTED IF ANY REMEDY PROVIDED HEREIN FAILS OF ITS ESSENTIAL PURPOSE.
GENERAL PROVISIONS. This License represents the complete agreement concerning this license, supersedes all prior agreements, and may be amended only by a writing executed by duly authorized representatives of both parties. The provisions of any order document used by Licensee shall be of no effect (notwithstanding any provisions in such order document to the contrary), except for the number of users, pricing and ship-to information. Any terms in Licensee‟s order document which are inconsistent with the terms of this License are not accepted by TANDBERG and the terms of this License will prevail.
This License is governed by, and is to be interpreted in accordance with the laws of the State of New York, excluding its conflict of law rules to the contrary. The United Nations Convention on Contracts for the International Sale of Goods is expressly disclaimed. If any provision of this Agreement is held by a court of competent jurisdiction to be invalid under any applicable statute, rule or law, the parties agree that such invalidity shall not affect the validity of the remaining provisions of this License, and further agree to substitute for the invalid provision a valid provision which most closely approximates the intent and economic effect of the invalid provision.
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” and “commercial computer software documentation” as used in FAR §
12.212 and 48 C.F.R.§§ 227.7202, and the corresponding provisions in DFARs, and
are being licensed to the U.S. government as commercial items pursuant to this license agreement and in compliance with FAR and DFAR.
RESERVATION OF RIGHTS. All rights not expressly granted under this agreement are reserved by the owners of the Software and Documentation.
Page 36
EULA
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB‟s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1005R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. 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.
Loading...
Buy Points How it Works FAQ Contact Us Questions and Suggestions Privacy Policy Cookie Policy Terms of Use