TEMS Discovery Enterprise - Device Module

System Configuration

NT13-26614, 0.1, 11/4/2013 1

© Ascom. All rights reserved.
TEMS is a trademark of Ascom. All other trademarks are the property of their respective holders.

2 NT13-26614, 0.1, 11/4/2013

 Contents

1 Overview 5

2 System Requirements 6
2.1 Software Requirements .................................................................................................... 6
2.2 Hardware Requirements ................................................................................................... 6
2.2.1 Small Size Server .......................................................................................................... 6
2.2.2 Mid Size Server ............................................................................................................. 6
2.2.3 Large Server.................................................................................................................. 6
2.2.4 Typical Hardware .......................................................................................................... 7
2.2.5 Disk Drive configuration ................................................................................................. 7

3 SQL Server Installation 8

3.1 Prerequisite ....................................................................................................................... 8
3.2 Installation ......................................................................................................................... 8
3.2.1 SQL Server 2008 R2 Enterprise 64 bits ......................................................................... 8
3.2.2 SQL Server 2012 Enterprise SP1 64 bits ..................................................................... 20

4 SQL Server Configuration 21

4.1 Logins ............................................................................................................................. 21
4.2 Memory configuration ..................................................................................................... 21
4.3 Default Database Location (Optional) ............................................................................. 22
4.4 TEMPDB Configuration................................................................................................... 23
4.5 SQL Server FILESTREAM configuration ........................................................................ 24

5 Microsoft SQL Server Analysis Services configuration 27

5.1 Prerequisite ..................................................................................................................... 27
5.2 Configuring HTTP Access (Only for client data access) ................................................. 27
5.2.1 Copy the MSMDPUMP.dll to a folder on the Web server ............................................. 27
5.2.2 Create an application pool ........................................................................................... 27
5.2.3 Create a virtual directory.............................................................................................. 30
5.2.4 Configure IIS authentication and add the extension ..................................................... 31
5.2.5 Edit the MSMDPUMP.INI file to set the target server ................................................... 34
5.3 URL for the HTTP Connection ........................................................................................ 35
5.4 Testing the Connection ................................................................................................... 35

6 Database Migration 36

7 TEMS Discovery Enterprise 38

7.1 Installation ....................................................................................................................... 38
7.2 Configuration................................................................................................................... 40
7.2.1 General Options .......................................................................................................... 40
7.2.2 Configure TEMS Discovery Enterprise temporary data processing folder. ................... 40
7.2.3 Configure Measurement Data Storage......................................................................... 41
7.2.4 Configure Statistics Database...................................................................................... 44

NT13-26614, 0.1, 11/4/2013 3

 7.2.5 Configure statistics database connection ..................................................................... 45
7.3 Archiving log file .............................................................................................................. 45
7.4 TA Database ................................................................................................................... 47
7.5 TMI Database.................................................................................................................. 48

8 Configuring TEMS Discovery Client 49

8.1 Connect to TEMS Discovery Enterprise configuration Database .................................... 49
8.2 Connect to Statistics Database ....................................................................................... 50
8.2.1 Configure statistics database connection ..................................................................... 52

4 NT13-26614, 0.1, 11/4/2013

 1 Overview
TEMS Discovery Enterprise is a multithreaded data analysis and network optimization tool.
TEMS Discovery Enterprise uses multiple threads in background to process log files and
user can select the number of threads to use from the TEMS Discovery configuration
options windows (see section 2). The processing capacity and the hardware requirement
depend on the number of threads configured to process measurement data. Each thread
usually runs on one core of the CPU. For a hyper threaded CPU one thread runs on a
hyper thread.
In addition to CPU needed for processing log files, TEMS Discovery Enterprise also needs
processor time for Microsoft SQL Server databases. Generally SQL Server takes 25%-40%
CPU time if SQL Server instance and TEMS Discovery Enterprise resides in the same
machine. To get a better performance it is advised to use a separate SQL Server machine
for TEMS Discovery Enterprise.

NT13-26614, 0.1, 11/4/2013 5

 2 System Requirements
2.1 Software Requirements
 Microsoft Windows Server 2008 R2 64 bits or Microsoft Windows Server 2012 Standard
64 bits
 Microsoft SQL Server 2008 R2 Enterprise 64 Bits or Microsoft SQL Server 2012
Enterprise SP1 64 bits
 Microsoft SQL Server Analysis Services
 Web Server (IIS 7.0) (Optional)

2.2 Hardware Requirements

2.2.1 Small Size Server

 2x 6-core hyper threaded CPU of 2.5 GHz and above. This will provide 24 threads; use
12 threads for processing log files and leave other 12 threads for SQL Server.
 64 GB of RAM – configure 40 GB for SQL Server. Remaining 24 GB will be used by
TEMS Discovery and system.
 See section 2.2.5 for disk configuration.

2.2.2 Mid Size Server

 2x 8-core hyper threaded CPU of 2.5 GHz and above. This will provide 32 threads; use
16 threads for processing log files and leave other 16 threads for SQL Server.
 64 GB of RAM – configure 40 GB for SQL Server. Remaining 24 GB will be used by
TEMS Discovery and system.
 See section 2.2.5 for disk configuration.

2.2.3 Large Server

 4x 8-core hyper threaded CPU of 2.5 GHz and above. This will provide 64 threads; use
maximum 48 threads for processing log files and leave other 16 threads for SQL
Server.
 128 GB of RAM – configure 96 GB for SQL Server. Remaining 32 GB will be used by
TEMS Discovery and system.
 See section 2.2.5 for disk configuration.

6 NT13-26614, 0.1,11/4/2013
 2.2.4 Typical Hardware
Small Server Mid Server Large Server
Model HP ProLiant ML370 HP ProLiant DL560 Gen8 Server
G6
Processor 2x Six-Core Intel® 2x Intel® Xeon® E5- 4x Intel® Xeon® E5-4650
Xeon® Processors 4650 Processor Processor
X5650
RAM 64 GB – PC3L-10600R 64GB (8x8GB) Dual 128GB (16x8GB) Dual
8x8GB 2Rank Memory Rank x4 PC3-12800R Rank x4 PC3-12800R
Memory Memory
Storage Controller 1 Embedded P410i/ZM HP Embedded P420i Smart Array Controller
(SAS Array Controller)
Storage Controller 2 HP Smart Array P822/2GB FBWC Controller
Disk Enclosures D2700 Disk Enclosures
Disk 16 X 300 GB 15K SAS SSF
6 X 600 GB 10K SAS SSF

2.2.5 Disk Drive configuration

Here is an example of typical disk configuration of SQL Server machine.
o C: (OS & Software) ( RAID1) 2 X 300GB 15K 6G SAS SSF
o D: ( SQL TEMP, TD TEMP & SQL FILESTREAM) (RAID10) 10 X 300 GB 15K
SAS 6G SSF ( 1.5 TB RAW)
o E: (SQL Log) (RAID 10) 4 X 300GB 15K 6G SAS SSF ( 600 GB RAW)
o G: (Measurement Data) (RAID5) 6 X 600 GB 10K 6G (3.0 TB RAW)

Use appropriate number of disks for volume F and G based on the storage
requirements. Format drive D:, E: and G: as NFTS with 64 KB block size.

NT13-26614, 0.1, 11/4/2013 7

 3 SQL Server Installation
3.1 Prerequisite
TEMS Discovery Enterprise uses SQL Server database for storing measurement data and
SQL Server Analysis Services for statistics data. SQL Server Database engine supports
Windows Authentication and SQL Server Authentication but SQL Server Analysis Services
only support Windows Authentication. It is recommended to use Windows Authentication
for TEMS Discovery Enterprise. TEMS Discovery Professional client can use SQL Server
Authentication for accessing data produced by TEMS Discovery Enterprise.
If TEMS Discovery Enterprise and SQL Server are installed in a single machine create a
local windows account and use this account as SQL Server administrator account. Also
use this account to process data in TEMS Discovery Enterprise.
If TEMS Discovery Enterprise and SQL Server are installed in two separate machines then
both the machines should part of the same domain. Create a domain account and use the
account as SQL Server administrator and as well as to process data in TEMS Discovery.

3.2 Installation

3.2.1 SQL Server 2008 R2 Enterprise 64 bits

1. Run SQL Server setup and click on the ‘Installation’ and select ‘New installation or add
features to an existing installation’.

2. Continue to follow on screen installation instruction and install all prerequisite and
required files. Once successful SQL Server 2008 R2 Setup will start. Click on the ‘New
installation or add shared features’ button.

8 NT13-26614, 0.1,11/4/2013
NT13-26614, 0.1, 11/4/2013 9
 3. Click next, enter product key and accept licensing agreement. Then go to ‘Setup Role’.
Select ‘SQL Server Feature Installation’.

10 NT13-26614, 0.1,11/4/2013
 4. Click next and go to ‘Feature Selection’ screen. Select ‘Database Engine Services’ and
‘Analysis Services’ and Management Tools.

NT13-26614, 0.1, 11/4/2013 11

 5. In the ‘Instance Configuration’ screen choose ‘Default instance’. If you choose named
instance, give a instance name.

12 NT13-26614, 0.1,11/4/2013
 6. Click next and go to ‘Server Configuration’ screen. Select an account to run SQL Server
services. Use your company’s security policy in selection account name. If the SQL
Server machine is only accessible within company’s intranet you may select ‘NT
AUTHORITY\SYSTEM account. This account has full access to all resources in the
local machine. If you use other account make sure this account has full access to all
database drives used by this instance of SQL Server.

NT13-26614, 0.1, 11/4/2013 13

 7. Click on the ‘Collation’ tab and make sure they are same a follows.

14 NT13-26614, 0.1,11/4/2013
 8. Click Next and Go to ‘Database Engine Configuration’ screen. Select ‘Mixed Mode’ and
provide a strong password for ‘sa’ account. Add the user created in section 3.1 as
administrator.

NT13-26614, 0.1, 11/4/2013 15

 9. Click on ‘Data Directories’ and use the drives created in section2.2.5 for various
database directories as follows.

16 NT13-26614, 0.1,11/4/2013
 10. Click on the ‘FILESTREAM’ tab and check all and also give a windows share name
(default same as SQL Server instance name).

NT13-26614, 0.1, 11/4/2013 17

 11. Click next and go to ‘Analysis Services Configuration’ page. Add the user created in
section 3.1 as administrative user.

18 NT13-26614, 0.1,11/4/2013
 12. Click on the ‘data Directories’ tab and provide appropriate folders for data, log, temp
and backup. Click next and complete the installation.

NT13-26614, 0.1, 11/4/2013 19

 3.2.2 SQL Server 2012 Enterprise SP1 64 bits
SQL Server 2012 installation procedure is similar to the installation procedures of SQL
Server 2008 R2 except step 6 described above in section 3.2.1.
SQL Server 2012 permits Windows virtual accounts to be used as service accounts. If
the instance name of the SQL Server is ‘SQL2012’ then virtual account name for SQL
Server Database Engine is ‘NT Service\MSSQL$SQL2012’ and for SQL Server
Analysis Services is ‘NT Service\MSOLAP$SQL2012’. Use virtual accounts to run all
SQL Server 2012 services.

20 NT13-26614, 0.1,11/4/2013
 4 SQL Server Configuration
4.1 Logins
If virtual accounts are used for running SQL Server 2012 services, virtual account for
SQL Server Analysis Services should be added as SQL Server database login.
Start SQL Server Management Studio and connect to the Database Engine. Expand
‘Security’ from the left panel and right click on the ‘Logins’ that will display the context
menu. Click on ‘New Login…’ and enter ‘NT Service\MSOLAP$<sql_instanceName> as
login name (see the screen below). SQL Server Analysis Services uses this login to
connect to the SQL Server Database Engine.

4.2 Memory configuration

Restrict the SQL Server to use a fixed size of memory. Otherwise SQL Server will
consume all system memory available and deprive other processes. This will slow down
the system since system will be using virtual memory from page files.
Open Microsoft SQL Server Management Studio and right click on the SQL Server
instance and click Properties. Click the Memory tab and set the Maximum server
memory.

NT13-26614, 0.1, 11/4/2013 21

 4.3 Default Database Location (Optional)
Click the Database Settings and set the default Data and Log file location if you have not
already configured during installation.

22 NT13-26614, 0.1,11/4/2013
 4.4 TEMPDB Configuration
The tempdb system database is a global resource that is available to all users connected
to the instance of SQL Server and is used to hold temporary user objects that are explicitly
created, internal objects that are created by the SQL Server Database Engine etc.
The size and storage bandwidth of tempdb can affect the performance of a system. It is
always better to use a high IOPs storage for tempdb.
Create one tempdb file for each core of the system. If system has 4 processors and
each processor has 8 cores than create 32 tempdb files. In section 2.2.5 drive D: is
used for tempdb. 6 dives in RAID 0 configuration will provide 1080- 1200 IOPs. Use
the following command to add a file to tempdb from SQL Server Management Studio
(assume there is a folder ‘SQLServer2008’ under D: drive).
ALTER DATABASE [tempdb] ADD FILE (NAME = N'tempdev01', FILENAME =
N'D:\SQLServer2008\tempdev01.ndf', SIZE = 524288KB, FILEGROWTH = 5120KB)

Change the ‘Name’ and ‘FILENAME’ in the above command and repeat it for all of the
cores available in the system.

NT13-26614, 0.1, 11/4/2013 23

 4.5 SQL Server FILESTREAM configuration
If FILESTREAM is not configured during the installation of the SQL Server, use the
following steps to enable and configure SQL Server FILESTREAM.
1. On the Start menu, point to All Programs; point to Microsoft SQL Server 2008 R2 or to
Microsoft SQL Server 2012, point to Configuration Tools, and then click SQL Server
Configuration Manager.
2. In the list of services, right-click SQL Server Services, and then click Open.

3. In the SQL Server Configuration Manager snap-in, locate the instance of SQL Server on
which you want to enable FILESTREAM.
4. Right-click the instance and then click Properties.

24 NT13-26614, 0.1,11/4/2013
 5. In the SQL Server Properties dialog box, click the FILESTREAM tab.
6. Select the Enable FILESTREAM for Transact-SQL access check box.
7. If you want to read and write FILESTREAM data from Windows, click Enable
FILESTREAM for file I/O streaming access. Enter the name of the Windows share in
the Windows Share Name box.
8. If remote clients must access the FILESTREAM data that is stored on this share, select
allow remote clients to have streaming access to FILESTREAM data.

NT13-26614, 0.1, 11/4/2013 25

 9. Click Apply.
10. In SQL Server Management Studio, click New Query to display the Query Editor.
11. In Query Editor, enter the following Transact-SQL code:

EXEC sp_configure filestream_access_level, 2

RECONFIGURE

12. Click Execute.

13. Restart the SQL Server service.

26 NT13-26614, 0.1,11/4/2013
 5 Microsoft SQL Server Analysis Services
configuration
Microsoft SQL Server Analysis Services requires clients to be authenticated by the
Microsoft Windows operating system in order to establish a connection with the service. It
is possible to disable the security feature of Analysis Services but it is not recommended.
If it is not possible to use Windows Integrated authentication mechanism for client
computers that are not in the same domain of Analysis Services server computer, Analysis
Services allows HTTP or HTTPs access of Analysis Services data on Internet Information
Services 7.0 using basic authentication. The follow sections explain how to configure
HTTP access for Analysis Services on Windows Server 2008 R2.
Configure HTTP data access only if client computers are not in the same domain of SQL
Server machine.

5.1 Prerequisite
The following services should be installed on Windows Server 2008 R2 before enabling HTTP
access to Analysis Services.
 Microsoft SQL Server 2008 R2
 Microsoft SQL Server Analysis Services
 Web Server (IIS) with following Role Services
o Common HTTP features
o Application Development
o Security
o Management Tools

Note: IIS Server and Microsoft SQL Server Analysis Services machine should be in domain.

5.2 Configuring HTTP Access (Only for client data access)

5.2.1 Copy the MSMDPUMP.dll to a folder on the Web server

The drive must be formatted for the NTFS file system. The path to the folder that you create
must not contain any spaces.
1. On the web server, create the following folder: <drive>:\inetpub\wwwroot\OLAP

2. Copy the contents of the ISAPI folder on the Analysis Services computer to the
\inetpub\wwwroot\OLAP folder you just created.

The ISAPI folder can be found at <drive>:\Program Files\Microsoft SQL

Server\<instance>\OLAP\bin\isapi (e.g. C:\Program Files\Microsoft SQL
Server\MSAS10_50.MSSQLSERVER\OLAP\bin\isapi) . It contains the following files
and folder: MSMDPUMP.DLL, MSMDPUMP.INI, and a Resources folder that contain
language resource files.

5.2.2 Create an application pool

1. Start IIS Manager. Click Start, point to Run, and then type Inetmgr.

NT13-26614, 0.1, 11/4/2013 27

 2. Right-click Application Pools and then click Add Application Pool. Create an application
pool named OLAP, using .NET Framework v2.0.50727, with Managed pipeline mode
set to Classic.

3. By default, IIS creates application pools using Network Service as the security identity.
To change the identity of the application pool you just created, right-click OLAP, and
then select Advanced Settings.

28 NT13-26614, 0.1,11/4/2013
 4. In Identity, Select ApplicationPoolIdentity.
5. By default, on a 64-bit operating system, IIS sets the Enable 32-bit Applications
property to false. If you copied msmdpump.dll from a 64-bit installation of Analysis
Services, this is the correct setting for the MSMDPUMP extension on a 64-bit IIS server.
If you copied the MSMDPUMP binaries from a 32-bit installation, set it to true. Check
this property now to ensure it is set correctly.

NT13-26614, 0.1, 11/4/2013 29

 5.2.3 Create a virtual directory

1. In IIS Manager, open Sites, right-click Default Web Site (or whatever web site you are
using to access the Analysis Services), and then click Add Virtual Directory.
2. In Alias, type OLAP.
3. In Physical Path, click the browse button and navigate to C:\inetpub\wwwroot\OLAP.
Click OK.

4. Right-click the OLAP virtual directory you just created, and then click Convert to
Application.
5. In the Add Application dialog box, next to Application Pool, click Select and then choose
the OLAP application pool that you created in the previous section.
6. Click OK twice to accept the changes, and to convert the application.

30 NT13-26614, 0.1,11/4/2013
 5.2.4 Configure IIS authentication and add the extension

1. In IIS Manager, open Sites, open Default Web Site, and then select the OLAP virtual
directory.
2. Double-click Authentication in the IIS section of the main page.

3. Enable Basic Authentication.

NT13-26614, 0.1, 11/4/2013 31

 4. Disable Anonymous Authentication. If you enable Anonymous Authentication, IIS will
always use it first, even if you enable other authentication methods.
5. Click the OLAP virtual directory to open the main page. Double-click Handler Mappings.

32 NT13-26614, 0.1,11/4/2013
 6. Right-click anywhere on the page and then select Add Script Map. In the Add Script
Map dialog box, specify *.dll as the request path, specify
c:\inetpub\wwwroot\OLAP\msmdpump.dll as the executable, and type OLAP as the
name.

NT13-26614, 0.1, 11/4/2013 33

 7. Click Request Restrictions.
8. On the Verbs tab, verify that All verbs is selected. Click OK, and then click OK again to
finish adding the script mapping.

9. When prompted to allow the ISAPI extension, click Yes.

5.2.5 Edit the MSMDPUMP.INI file to set the target server

Open the msmdpump.ini file located in folder C:\inetpub\wwwroot\OLAP and take a look at the
contents of this file. It should look like the following:

<ConfigurationSettings>
<ServerName>localhost</ServerName>
<SessionTimeout>3600</SessionTimeout>
<ConnectionPoolSize>100</ConnectionPoolSize>
</ConfigurationSettings>

If the Analysis Services instance for which you are configuring HTTP access is located on the
local computer and installed as a default instance, there is no reason to change this setting.
Otherwise, you must specify the server name (for example,
<ServerName>TDSERVR01</ServerName>). For a server that is installed as a named

34 NT13-26614, 0.1,11/4/2013
 instance, be sure to append the instance name (for example, <ServerName>
TDSERVR01\AnalysisDataInstance</ServerName>).

By default, Analysis Services listens on TCP/IP port 2383. If you installed Analysis Services as
the default instance, you do not need to specify any port in <ServerName> because Analysis
Services knows how to listen on port 2383 automatically. However, you do need to allow
inbound connections to that port in Windows Firewall.

If you configured a named or default instance of Analysis Services to listen on a fixed port, you
must add the port number to the server name (for example, <ServerName>
TDSERVR01:55555</ServerName>) and you must allow inbound connections in Windows
Firewall to that port.

5.3 URL for the HTTP Connection

The connection string syntax for Analysis Services is the URL to the MSMDPUMP.dll file. If the
IP address of the computer is 123.456.789.012 and the web server is listening on the default
HTTP port, the URL is http:// 123.456.789.012/OLAP/msmdpump.dll. If web server is listening
on any other fixed port like 8080, the URL is http://
123.456.789.012:8080/OLAP/msmdpump.dll.

5.4 Testing the Connection

You can test the connection using Excel.
1. Open Excel and go to Data tab.
2. Click From Other Sources, and then choose From Analysis Services. In Server name,
enter the HTTP URL http:// 123.456.789.012:8080/OLAP/msmdpump.dll and provide a
windows account and password.

NT13-26614, 0.1, 11/4/2013 35

 6 Database Migration
TEMS Discovery Enterprise 10.0.2 database structures are different from its previous
versions. If you are currently running TEMS Discovery Enterprise 4.x.x or TEMS Discovery
Enterprise 10.0.1 you must run database migration utility before starting TEMS Discovery
Enterprise 10.0.2.
Database migration is separate standalone utility and is available in the installation CD.

1. SQL Server – provide the SQL Server connection information. Only Windows
Integrated authentication is supported for database migration.
2. Master Database – TEMS Discovery master database names will be
automatically populated. Select a master database if you have more than one.

Database path, transaction log path, FILESTREAM path will be automatically

populated. If you move the databases in a separate drive provide the new path
names.

36 NT13-26614, 0.1,11/4/2013
 Database migration utility will create a new database for each of the projects
present in the master database. So make sure there is enough free space available
to duplicate the largest database.

NT13-26614, 0.1, 11/4/2013 37

 7 TEMS Discovery Enterprise
7.1 Installation
The following two installation options are supported for the current release (10.0.2) of
TEMS Discovery Enterprise.
1. TEMS Discovery Enterprise server and user machines are in same network.

Domain Controller
TEMS Discovery Enterprise

TD Client1 TD Client2 TD Client3 TD Client4

TEMS Discovery Enterprise server and TEMS Discovery Client users are part of same domain. TEMS
Discovery Client is installed in user’s computer and uses Windows Integrated authentication to
connect TEMS Discovery Enterprise Databases.

38 NT13-26614, 0.1,11/4/2013
 2. TEMS Discovery Enterprise server and user machines are in separate networks.

Domain Controller

TEMS Discovery Enterprise Server

Application Server for TEMS Discovery Clients (multi users)
RDC

Server network

User1
User2 User3 User4

Client network

TEMS Discovery Enterprise server and TEMS Discovery users are in separate network. TEMS Discovery Client is installed in Application Server
and TEMS Discovery users remote desktop to Application Server to access TEMS Discovery Client. TEMS Discovery Client instances in
Application Server use Windows Integrated authentication to access TEMS Discovery Enterprise Databases.

NT13-26614, 0.1, 11/4/2013 39

 7.2 Configuration
Open the TEMS Discovery Enterprise configuration window.
1. Start TEMS Discovery Enterprise
2. Click on Configurations and Options.

7.2.1 General Options

7.2.2 Configure TEMS Discovery Enterprise temporary data

processing folder.
Create the following folders in the D: drive configured in section 2.2.5.
I. TD\SystemData (share as \\ServerName\SystemData) – TEMS Discovery
system configuration data and error log message files are stored there.
II. TD\Temp – Temporary local folder.

Click General Options

1. System Data (Local): use ‘D: \TD\SystemData’ folder for this field and share this
folder with ‘Everyone’ with read\write access. This folder is accessed by TEMS
Discovery Clients to access system settings.
2. Temp file folder (Local): use ‘D: \TD\Temp’ folder for this field. This is a local private
folder.
3. Enter ‘Max. Number of Import threads’ based on the hardware purchased.

40 NT13-26614, 0.1,11/4/2013
 7.2.3 Configure Measurement Data Storage
1. Click Measurement Data Storage from the left side of the screen.

2. Click on Use MS SQL Server for data storage.

3. Select or enter a SQL Server instance name to use. If the instance name is default
instance enter only the server name otherwise enter server name and instance name
as SERVERNAME\\INSTANCENAME
4. Only ‘Integrated Windows authentication’ is supported for TEMS Discovery
Enterprise.
5. Enter TEMS Discovery Enterprise configuration database name. If you are upgrading
an existing installation, select the old TEMS Discovery Enterprise configuration
database.

NT13-26614, 0.1, 11/4/2013 41

 6. Configure the folders for creating Measurement Database primary data file (Rows
Data), Database transaction log file (Log) and file stream database path (to store
Layer3 messages).
7. Use G: drive for ‘Rows Data’, E: drive for ‘Logs’ and D: drive for ‘FileStream’.
8. Click Use followings folder(s).
9. Click Add Folder to select the folders.

42 NT13-26614, 0.1,11/4/2013
 The following steps are needed only if SQL Server is installed in a separate machine.
Click on the ‘Paths for database data’ tab of the ‘Measurement Data Storage’ screen.

Create the following folders in D: Drive

I. TD\UserData_db (share as \\ServerName\UserData_db) – TEMS Discovery
intermediate file are stored there.
II. TD\BulkFile ( share as \\ServerName\BulkFile) – temporary files for SQL
Server bulk insert are created there.

Make the above folder Windows sharable to ‘Everyone’ with read\write access.
For the ‘Data folder (Local):’ field select ‘D: \TD\UserData_db’.
For ‘Temp file folder for SQL Bulk Insert:’ field select ‘D: \TD\BulkFile’. If SQL Server is
in a remote machine, select ‘\\ServerName\BulkFile’ network path.

NT13-26614, 0.1, 11/4/2013 43

 7.2.4 Configure Statistics Database
3. Click on the Statistics Database from the left side of Options window
4. Click Enable statistics database
5. For ‘Temp file folder for BulkInsert’ field provide network path for the ‘BulkFile’
(\\ServerName\BulkFile) folder created above if SQL Server is in a remote
machine.
6. Click Add button to enter Analysis Services database information.

44 NT13-26614, 0.1,11/4/2013
 7.2.5 Configure statistics database connection

1. Enter Analysis Services database server name or IP address

2. Select authentication type.
3. Enter or select a database name.
4. For ‘Database path:’ browse to the folder where you want to place Database
primary data file.
5. For ‘Database log path:’ browse to the folder where you want to place Database
transaction log file.

If SQL Server authentication is selected, perform the following steps.

6. Enter the HTTP URL for Analysis Services
7. Enter a Windows account and password. This user could be a local user in the
Analysis Services machine or domain user of the domain Analysis Services
machine belongs to.

7.3 Archiving log file

To archive all the log files processed in TEMS Discovery Enterprise, configure SQL
Server FILESTREAM database.

NT13-26614, 0.1, 11/4/2013 45

 Use the following steps only if archival of binary log files are needed for future use. Make
sure SQL Server FILESTREAM is enabled (see the section 4.5).

1. Click the ‘Log Files’ from ‘Option Category’ and check ‘Enable log file database’.
2. Click ‘Add’ to configure a log file FILESTREAM database.
3. In the ‘Add SQL Server’ window provide the SQL Server instance name, database
name, file path for Database primary data file and Database transaction log file.

46 NT13-26614, 0.1,11/4/2013
 7.4 TA Database
Provide connection information for TEMS Automatic measurement database to merge mobile
and TEMS Automatic Call Generator’s service quality data. MTU name, group name and serial
number also retrieve from this database.

NT13-26614, 0.1, 11/4/2013 47

 7.5 TMI Database
To import TMI drive test data into TEMS Discovery database provide connection to the SQL
Server instance of the TMI database.

48 NT13-26614, 0.1,11/4/2013
 8 Configuring TEMS Discovery Client
Follow the steps below to access TEMS Discovery Enterprise database using TEMS
Discovery Client.

8.1 Connect to TEMS Discovery Enterprise configuration

Database
1. Click Measurement Data Storage from the left side of the screen.

2. Click on Use MS SQL Server for data storage.

3. Select or enter a SQL Server instance name to use. If the instance name is default
instance enter only the server name otherwise enter server name and instance name
as SERVERNAME\\INSTANCENAME
4. Select TEMS Discovery Enterprise configuration database name.
5. Click on the ‘Paths for database data’ tab.

NT13-26614, 0.1, 11/4/2013 49

 For ‘Data folder (Local):’ select the default folder or browse to a folder of your choice.
The fields in the ‘Remote path settings if database server is in a remote server’ are important to
TEMS Discovery Client to access settings and data produced by TEMS Discovery Enterprise.
For ‘System data folder’ provide the network path name of the system data folder of TEMS
Discovery Enterprise server configured in section 7.2.1.
For ‘Data folder’ provide the network path name of the data folder of TEMS Discovery
Enterprise server configured in section 7.2.3.

8.2 Connect to Statistics Database

7. Click on the Statistics Database from the left side of Options window
8. Click Enable statistics database
9. Click Add button to enter Analysis Services database information.

50 NT13-26614, 0.1,11/4/2013
NT13-26614, 0.1, 11/4/2013 51
 8.2.1 Configure statistics database connection

8. Enter Analysis Services database server name or IP address

9. Select authentication type.
10. Select a database name.

If SQL Server authentication is selected, perform the following steps.

11. Enter the HTTP URL for Analysis Services
12. Enter a Windows account and password. This user could be a local user in the
Analysis Services machine or domain user of the domain Analysis Services
machine belongs to.

52 NT13-26614, 0.1,11/4/2013