TEMS Discovery Enterprise - Device Module

System Configuration

NT13-26614, 1.0, 11/3/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, 1.0, 11/3/2013

 Contents

1 Overview 5

2 System Requirements 6
2.1 Software Requirements .................................................................................................... 6
2.1.1 Server Operating System .............................................................................................. 6
2.1.2 Client Operation System ................................................................................................ 6
2.1.3 SQL Server ................................................................................................................... 6
2.1.4 .NET Framework ........................................................................................................... 6
2.2 Hardware Requirements ................................................................................................... 6
2.2.1 Server Hardware ........................................................................................................... 6
2.2.2 Client Hardware ............................................................................................................. 7

3 SQL Server Installation 8

3.1 Prerequisite ....................................................................................................................... 8
3.2 Installation ......................................................................................................................... 8
3.2.1 SQL Server 2008 R2 64 bits .......................................................................................... 8
3.2.2 SQL Server 2012 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 Configure SQL Server Analysis Services 27

5.1 Configure Analysis Services Server Administrators ........................................................ 27
5.2 Grant read permission to cubes ...................................................................................... 28

6 Database Migration 31

7 TEMS Discovery Enterprise 33

7.1 Installation ....................................................................................................................... 33
7.2 Configuration................................................................................................................... 35
7.2.1 General Options .......................................................................................................... 35
7.2.2 Configure TEMS Discovery Enterprise temporary data processing folder. ................... 35
7.2.3 Configure Measurement Data Storage......................................................................... 36
7.2.4 Configure Statistics Database...................................................................................... 39
7.2.5 Configure statistics database connection ..................................................................... 40
7.3 Archiving log file .............................................................................................................. 40
7.4 TA Database ................................................................................................................... 42
7.5 TMI Database ................................................................................................................. 43

NT13-26614, 1.0, 11/3/2013 3

 8 Service Configuration 44

9 Configuring TEMS Discovery Client 45

9.1 Connect to TEMS Discovery Enterprise configuration Database .................................... 45
9.2 Connect to Statistics Database ....................................................................................... 46
9.2.1 Configure Statistics Database Connection ................................................................... 48

4 NT13-26614, 1.0, 11/3/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, 1.0, 11/3/2013 5

 2 System Requirements
2.1 Software Requirements

2.1.1 Server Operating System

 Microsoft Windows Server 2008 R2 64 bits
 Microsoft Windows Server 2012 Standard 64 bits

2.1.2 Client Operation System

 Windows 7 64 bits

2.1.3 SQL Server

 Microsoft SQL Server 2008 R2 Enterprise SP2 64 bits
 Microsoft SQL Server 2008 R2 Standard SP2 64 bits
 Microsoft SQL Server 2012 Enterprise SP2 64 bits
 Microsoft SQL Server 2012 Standard SP2 64 bits
 Microsoft SQL Server 2012 Business Intelligence SP2 64 bits
 Microsoft SQL Server Analysis Services

2.1.4 .NET Framework

 Microsoft .NET Framework 4.5.1

2.2 Hardware Requirements

2.2.1 Server Hardware

2.2.1.1 SQL Server

Small Server Mid Server Large Server
Model HP ProLiant DL380p Gen8
Processor 1 X Intel® Xeon® E5-2609 1 X Intel® Xeon® E5- 1 X Intel® Xeon® E5-2690
v2 2630 v2
RAM 4 X HP 16GB (1x16GB) Dual Rank x4 PC3-14900R 8 X HP 16GB (1x16GB) Dual
(DDR3-1866) Rank x4 PC3-14900R (DDR3-
1866)
Storage HP Embedded Smart Array P420i/1GB FBWC
Controller 1
Storage HP Smart Array P421/1GB FBWC 6Gb 2-ports Ext SAS Controller
Controller 2
Disk Enclosures D2700 Disk Enclosures
Disk 4 X 146 GB 6G 15K SAS SFF 8 X 600 GB 6G 10K SAS SFF
2 X 300 GB 6G 15K SAS SFF 2 X 300 GB 6G 15K SAS SFF
4 X 300 GB 6G 10K SAS SFF 4 X 300 GB 6G 10K SAS SFF
8 X 600 GB 6G 10K SAS SFF 8 X 600 GB 6G 10K SAS SFF

6 NT13-26614, 1.0,11/3/2013
 2.2.1.2 SQL Server 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 SFF
o F: (SQL Log & Temp) (RAID 10) (4-8) X 146 15K 6G SAS SFF (292-584 GB
RAW)
o G: (Log file archive) (RAID 5) 4X 600 GB 10K 6G SAS SFF (1.8 TB RAW)
o H: (Measurement Data) (RAID5) 4 X 600 GB 10K 6G SFF (1.8 TB RAW)
o I: (Statistics) ( RAID 10) 4 X 300 GB 10k 6G SFF ( 900 GB RAW)

Use appropriate number of disks for volume G, H, and I based on the storage
requirements. Format drive F, H and I as NTFS with 64 KB block size.

Format C and G drive as NTFS with 16KB block size.

2.2.1.3 TEMS Discovery Server

Small Server Mid Server Large Server

Model HP ProLiant DL380p HP ProLiant DL380p HP ProLiant DL380p
Gen8 Gen8 Gen8
Processor 2 x Intel® Xeon® E5- 2 X Intel® Xeon® 2 X Intel® Xeon® E5-
2630v2 E5-2650 v2 2697v2
RAM 2 X HP 16GB (1x16GB) 4 X HP 16GB 4 X HP 16GB (1x16GB)
Dual Rank x4 PC3- (1x16GB) Dual Rank Dual Rank x4 PC3-
14900R (DDR3-1866) x4 PC3-14900R 14900R (DDR3-1866)
(DDR3-1866)
Storage HP Embedded Smart Array P420i/1GB FBWC
Controller 1
Disk 4 X 146 GB 6G 15K SAS SFF 8 X 146 GB 6G 15K SAS
2 X 300 GB 6G 15K SAS SFF SFF
2 X 300 GB 6G 15K SAS
SFF

2.2.1.4 TEMS Discovery 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 SFF
o E: (TD TEMP & User data) (RAID10) (4-8) X 146 GB 15K SAS 6G SFF (292-
584 GB RAW)

Format C and E drive as NTFS with 16KB block size.

2.2.2 Client Hardware

Laptop or Desktop with Intel® Core™ i7 based processor with at least 2 cores having 2.5 GHz
or above frequency. 8 GB RAM minimum.

NT13-26614, 1.0, 11/3/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 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, 1.0,11/3/2013
NT13-26614, 1.0, 11/3/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, 1.0,11/3/2013
 4. Click next and go to ‘Feature Selection’ screen. Select ‘Database Engine Services’ and
‘Analysis Services’ and Management Tools.

NT13-26614, 1.0, 11/3/2013 11

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

12 NT13-26614, 1.0,11/3/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, 1.0, 11/3/2013 13

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

14 NT13-26614, 1.0,11/3/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, 1.0, 11/3/2013 15

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

16 NT13-26614, 1.0,11/3/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, 1.0, 11/3/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, 1.0,11/3/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, 1.0, 11/3/2013 19

 3.2.2 SQL Server 2012 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, 1.0,11/3/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, 1.0, 11/3/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, 1.0,11/3/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.1.4 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 F: drive).
ALTER DATABASE [tempdb] ADD FILE (NAME = N'tempdev01', FILENAME =
N'F:\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, 1.0, 11/3/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, 1.0,11/3/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, 1.0, 11/3/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.

1. Right-click the OLAP virtual directory you just created, and then click Convert to
Application.
2. 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.
3. Click OK twice to accept the changes, and to convert the application.

26 NT13-26614, 1.0,11/3/2013
 5 Configure SQL Server Analysis Services
5.1 Configure Analysis Services Server Administrators
1. In SQL Server Management Studio, connect to the instance of Analysis Services, and
then right-click the instance name in Object Explorer and then click Properties.
2. Click Security in the Select a Page pane, and then click Add at the bottom of the page
to add one or more Windows users or groups to the server role.

At installation time, SQL Server Setup requires that you specify at least one user account as the
Analysis Services system administrator.

NT13-26614, 1.0, 11/3/2013 27

 5.2 Grant read permission to cubes
1. In SQL Server Management Studio, connect to Analysis Services.

2. Open the Databases folder in Object Explorer, and select a cube database.

3. Right-click Roles and choose New Role. Notice that roles are created at the database
level and apply to objects within it. You cannot share roles across databases.

28 NT13-26614, 1.0,11/3/2013
 4. In the General pane, enter a name, and optionally, a description. This pane also
contains several database permissions, such as Full Control, Process Database, and
Read Definition. None of these permissions are needed for querying a cube.
5. In the Membership pane, click Add to enter the Windows user or group accounts that
will be accessing the cube using this role. Analysis Services only supports Windows
security identities.

NT13-26614, 1.0, 11/3/2013 29

 6. In the Cubes pane, select a cube, and then click Read access. Read access is sufficient
for accessing cube data from client machines.

7. Click ‘OK’ to grant permission to the users.

30 NT13-26614, 1.0,11/3/2013
 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.

NT13-26614, 1.0, 11/3/2013 31

 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.

32 NT13-26614, 1.0,11/3/2013
 7 TEMS Discovery Enterprise
7.1 Installation
The following two installation options are supported for the current release (10.0.8) 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.

NT13-26614, 1.0, 11/3/2013 33

 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.

34 NT13-26614, 1.0,11/3/2013
 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 E: drive configured in section 2.2.1.4.
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 ‘E: \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 ‘E: \TD\Temp’ folder for this field. This is a local private
folder.

NT13-26614, 1.0, 11/3/2013 35

 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.

36 NT13-26614, 1.0,11/3/2013
 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 H: drive for ‘Rows Data’, F: drive for ‘Logs’.
8. Click Use followings folder(s).
9. Click Add Folder to select the folders.

NT13-26614, 1.0, 11/3/2013 37

 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 E: Drive TEMS Discovery Data Processing machine
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 ‘E: \TD\UserData_db’.
For ‘Temp file folder for SQL Bulk Insert:’ field select ‘E: \TD\BulkFile’. If SQL Server is
in a remote machine, select ‘\\ServerName\BulkFile’ network path.

38 NT13-26614, 1.0,11/3/2013
 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.

NT13-26614, 1.0, 11/3/2013 39

 7.2.5 Configure statistics database connection

1. Enter Analysis Services database server name or IP address

2. Select authentication type (currently only Integrated Windows authentication
supported).
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.

7.3 Archiving log file

To archive all the log files processed in TEMS Discovery Enterprise, configure SQL
Server FILESTREAM database.
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).

40 NT13-26614, 1.0,11/3/2013
 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.

NT13-26614, 1.0, 11/3/2013 41

 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.

42 NT13-26614, 1.0,11/3/2013
 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.

NT13-26614, 1.0, 11/3/2013 43

 8 Service Configuration
Service configuration window will be displayed automatically if services are not configured
correctly. Make sure all the servers has static IP address and all ports configured are open
through firewall. Also make sure you run TEMS Discovery as ‘Administrator’ before making
changes to this Window.

 Provide a user name and password to run the services

 Provide a HTTP port if you want to execute report on the Server Machine from the
TEMS Discovery Thick Client.
 Select ‘Database Management Service’ from the drop down list. Provide the IP address
of the Database Server Machine and also provide a port number to communicate with
the Database Management Service. ‘Import threads’ should be ‘0’ for this service.
 Select ‘Data Processor Service’ from the drop down list. Provide the IP address, port
number and number of concurrent data import threads (default is 50% of the total
threads available in the system and maximum is 40). Also make sure at least 20
consecutive ports from the ‘Data Processor Service’ port number are opened through
firewall.
 Click ‘Save’ so save the configuration.

44 NT13-26614, 1.0,11/3/2013
 9 Configuring TEMS Discovery Client
Follow the steps below to access TEMS Discovery Enterprise database using TEMS
Discovery Client.

9.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, 1.0, 11/3/2013 45

 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.

9.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.

46 NT13-26614, 1.0,11/3/2013
NT13-26614, 1.0, 11/3/2013 47
 9.2.1 Configure Statistics Database Connection

6. Enter Analysis Services database server name or IP address

7. Select authentication type (currently only Integrated Windows authentication is
supported).
8. Select a database name.

48 NT13-26614, 1.0,11/3/2013