ATOLL ADMINISTRATION COURSE
ATOLL ADMINISTRATION COURSE
Training Programme
1. Installation Procedures
2. Atoll Environment
3. Multi-User Environment Configuration
4. Database Management
5. Atoll Management Console (AMC)
6. Macros/Add-ins
© Forsk 2011 Slide 2 of 168 Confidential – Do not share without prior permission
1. Installation Procedures
Atoll
Distributed calculation server
Fixed licence solution
Floating licence solution
License Key Management
Oracle
Server for pathloss matrices and geo data
© Forsk 2011 Confidential – Do not share without prior permission
Slide 3 of 168
Atoll Installation
Hardware specifications for standalone configuration
Hardware specifications for server configuration
Atoll installation procedure
Application isolation
© Forsk 2011 Slide 4 of 168 Confidential – Do not share without prior permission
Hardware Specifications for Standalone Configuration
Standalone configuration: Atoll installed on each individual user computer
© Forsk 2011 Slide 5 of 168 Confidential – Do not share without prior permission
CPU Dual Core Processor or better
Memory 1GB minimum – 2GB+ recommended (according to size of project,
calculations)
Disk 10 GB free on disk recommended (or more according to the used
geographic database and local path loss matrices)
Operating System Microsoft® Windows® XP professional SP3 (32-bit and 64-bit)
or Vista/Seven (32-bit or 64-bit)
Software Environment Microsoft® Office 2003 or later
Workstation Requirements
Hardware Specifications for Server Configuration
Server configuration: Atoll installed on servers (Citrix, Terminal Services)
© Forsk 2011 Slide 6 of 168 Confidential – Do not share without prior permission
CPU Intel or AMD Dual/Quad/Hexa processor supported – 2.26+ GHz
Dimensioning recommendations:
1 core for 1 to 1.5 users (i.e. 2 cores for 2 to 3 users)
Memory 1 GB+ RAM recommended per user, or more according to the size of
project and the calculations performed
Minimum 4 GB
Operating System
Microsoft® Windows® 2003/2008 Server (32 or 64-bits)
Software Environment Microsoft® Office 2003 or later
Server Requirements
Hardware Specification for Server Configuration
Citrix requirements
Server side:
• MetaFrame (XenApp) presentation server 4.0 or later must be installed with Microsoft Windows Server
2003/2008
• Publication of Atoll required in order for all the users to have access to it
Server side:
• Citrix client 9.0 or later have to be installed
Terminal Services requirements
Sufficient number of licenses (CAL) available
© Forsk 2011 Slide 7 of 168 Confidential – Do not share without prior permission
Atoll Installation Procedure (1/5)
Download latest version from Forsk‟s support website by logging using the user name
and password provided by Forsk (www.Forsk.com)
Administrator rights required on the computer where Atoll is installed
UAC must be disabled on Vista/Seven/Server 2003/Server 2008 for installation
© Forsk 2011 Slide 8 of 168 Confidential – Do not share without prior permission
Atoll Installation Procedure (2/5)
Run As Administrator for Vista/Seven/Server 2008
Atoll setup wizard
© Forsk 2011 Slide 9 of 168 Confidential – Do not share without prior permission
Define installation directory for Atoll
Atoll Installation Procedure (3/5)
© Forsk 2011 Slide 10 of 168 Confidential – Do not share without prior permission
Different path can
be defined
Default directory is last
directory in which it was
installed or C:\Program
Files\Forsk\Atoll
Atoll Installation Procedure (4/5)
Atoll setup wizard
What is installed
Full installation:
• Atoll application
• Atoll calculation server
• Dongle driver for fixed license
• Atoll Management Console
• Add-ins (Google Earth Export, Best Signal Export)
© Forsk 2011 Slide 11 of 168 Confidential – Do not share without prior permission
Atoll Installation Procedure (5/5)
Custom: any combination of available components
Compact: Atoll only
© Forsk 2011 Slide 12 of 168 Confidential – Do not share without prior permission
Application Isolation
Application Isolation allows for multiple versions of Atoll to be installed and run on the
same machine at the same time
Relies on Microsoft COM+ technology
Atoll shared libraries (Fskgis, Fskppag, …) need to be registered
Registration is automatic as you install Atoll and overrides previously registered libraries
Registered libraries which do not match the version of Atoll may lead to software malfunction
You can force the registration to happen by using the Microsoft Windows regsvr32.exe utility
Click on Help→About Atoll in Atoll to get a list of
the registered libraries as well as their version
© Forsk 2011 Slide 13 of 168 Confidential – Do not share without prior permission
Distributed Calculation
Overview
Requirements
Principles
Installation of distributed computing server application
Distributed calculation service management
Setting distributed calculation servers
© Forsk 2011 Slide 14 of 168 Confidential – Do not share without prior permission
Distributed Calculation Overview
Overview
Enables to use multiple computers to calculate propagation path loss matrices
Distributed calculation service is ideally suited for memory intensive processes (no GUI)
A computer on which the distributed calculation service is installed and running is called a
Distributed Calculation Server (DCS)
Service is capable of managing up to 8 threads to perform calculations (4 by default)
Atoll supports a maximum of 64 parallel threads
© Forsk 2011 Slide 15 of 168 Confidential – Do not share without prior permission
Distributed Calculation Requirements
Installation requirements
Atoll must be installed on each workstation or server where distributed calculation server will
be installed
User account with administrator rights on the computer and sufficient rights (Read) to access
the geographic data folder
• Distributed calculations does not work with embedded geo data files
Calculation server must have an available licence: one token used by the DCS
Same subnet for the servers required to be detected automatically
© Forsk 2011 Slide 16 of 168 Confidential – Do not share without prior permission
Distributed Calculation Principles
Principles
Distributed calculation service uses the Windows named pipes to exchange data with Atoll
sessions requesting calculations
Automatic failover: in case of DCS failure or network disruption, calculations are performed
locally, using one thread only (to avoid memory saturation)
Calculations process
• User‟s workstation sends the request for calculating path loss matrices to distributed calculation
servers
• Distributed calculation servers calculate the path loss matrices and send the results directly to the
storage location (the file server where path loss matrices are stored)
© Forsk 2011 Slide 17 of 168 Confidential – Do not share without prior permission
1 Atoll DCS Request for
calculation
Result sent to
requester 2
…
Calculations performed using
parameters sent by the
requester and geo data
Distributed Calculation Installation
Installation of distributed calculation server application
Calculation server application (Atoll Server) included in the Atoll setup
Distributed calculation server application can be installed on any workstation or server where
Atoll is installed
© Forsk 2011 Slide 18 of 168 Confidential – Do not share without prior permission
To install this
application, tick the
"Atoll calculation
server" check box
Distributed Calculation Installation
Atoll setup procedure installs the service with the „localsystem‟ account (default account
for a service)
This account has full administrator permissions on the local machine, but no permissions at all on
the network
The service should run under a domain account (the logon must be
'domain_name\user_name' in the properties of the service)
© Forsk 2011 Slide 19 of 168 Confidential – Do not share without prior permission
Use a domain
account which has
the necessary
privileges to access
the geographic data
Distributed Calculation Installation
Distributed calculation server is installed as a service on workstations (or servers)
Up to 10 instances of the DCS can run on the same machine
Service available to other machines running Atoll as long as the DCS is running and
the service has not been manually stopped by the administrator of the computer
Manage the “Atoll Server” service properties
Control Panel -> Administrative Tools -> Services or type Services.msc in Run command
© Forsk 2011 Slide 20 of 168 Confidential – Do not share without prior permission
Access Atoll Server
properties in Windows
Services
Distributed Calculation Settings
Setting distributed calculation servers
(Tools→Distributed Calculation…)
© Forsk 2011 Slide 21 of 168 Confidential – Do not share without prior permission
Press “detect” to
search the subnet and
display all potential
calculation servers you
can use
Press “all” to scan all
potential calculation
servers on the subnet
when starting
calculations
Distributed Calculation Settings
Settings:
Atoll.ini stores the global settings of the DCS: [RemoteCalculation] section
• NumberOfThreadsPathloss=8 → 8 threads will be used
• When Atoll.ini modified, the service shall be restarted
• All the parameters are described in the Administrator Manual
Use the server name, not the IP address: Server1NameN
• Server1: Hostname of the computer
• NameN: Refers to a number from 0 to 9, i.e. instance number of the DCS
© Forsk 2011 Slide 22 of 168 Confidential – Do not share without prior permission
Two servers available for
calculations
Distributed Calculation Settings
If the account used by the DCS needs to be modified, it can be done via the Windows
Services:
Open the Windows Services (Control Panel → Administrative Tools → Services)
In the Log on tab of the Properties, it is possible to specify the account to be used (service
must be restarted)
© Forsk 2011 Slide 23 of 168 Confidential – Do not share without prior permission
Fixed Licence Solution
Fixed licence overview
Installation requirements
Installation procedure
© Forsk 2011 Slide 24 of 168 Confidential – Do not share without prior permission
Fixed Licence Overview and Requirements
Fixed licence overview
A NethaspTM key : hardware key to be plugged on the workstation
Key is programmed with one license token only and a set of modules (GSM, UMTS, LTE, etc)
Installation requirements
Operating system: Windows XP or later - Cannot be used on Server-type OS
Administrator rights required and UAC disabled
Available USB port to plug in the Nethasp hardware key
© Forsk 2011 Slide 25 of 168 Confidential – Do not share without prior permission
Fixed Licence Installation
Installation wizard
Part of the Atoll installation
Unplug the hardware key
During Atoll installation, tick the check-box “Driver for Fixed License Keys”
Restart the computer
Plug in the hardware key
© Forsk 2011 Slide 26 of 168 Confidential – Do not share without prior permission
To be checked
Floating Licence Solution
Floating licence overview
Licence server requirements
What is installed on server
Standalone workstations configuration
Server-client configuration
Installation procedure
© Forsk 2011 Slide 27 of 168 Confidential – Do not share without prior permission
Floating Licence Overview and Requirements
Floating licence overview
A NethaspTM key is used as floating hardware key on the server
Keys may be programmed with a variable number of license tokens
One workstation consumes one license token even if more than one Atoll session are running
Licence server requirements
Operating system: Microsoft Windows XP or 2003 server or later
Available USB port to plug in the Nethasp hardware key
Firewall network requirements
Firewall port 475 opened using UDP or TCP protocols (licence server behind firewall)
Automatically done during the installation of the License Manager and the drivers
© Forsk 2011 Slide 28 of 168 Confidential – Do not share without prior permission
What is Installed on Server
Hasp device driver
NethaspTM licence manager (installed as a service)
Automatic registration
Started automatically with the machine (no login required)
NethaspTM key
Nhsrv.ini file (optional – list of potential client addresses)
NethaspTM monitor to check the number of tokens consumed (optional)
NethaspTM software is available at www.Aladdin.com [HASP4 section]
© Forsk 2011 Slide 29 of 168 Confidential – Do not share without prior permission
Floating Licence Configurations
Standalone workstations configuration
Nethasp.ini file to store information about the network and location of license server
• To be placed in the Atoll Installation directory
• Server IP addresses (or host names in the network) in case of large server networks
Server-client configuration
Same as for the standalone configuration
Licenses consumptions rules still apply
Nhsrv.ini:
Specify the list of users server by the NetHASP Server
To be placed in the %systemroot% folder
© Forsk 2011 Slide 30 of 168 Confidential – Do not share without prior permission
Floating Licence Installation
Installation Wizard (1/2)
© Forsk 2011 Slide 31 of 168 Confidential – Do not share without prior permission
Floating Licence Installation
Installation Wizard (2/2)
© Forsk 2011 Slide 32 of 168 Confidential – Do not share without prior permission
License Key Management
Floating license keys monitoring
Key content
© Forsk 2011 Slide 33 of 168 Confidential – Do not share without prior permission
Floating License - HASP Monitor
Utility to identify the number of licenses used
Aladdin Monitor can be downloaded from www.Aladdin.com
© Forsk 2011 Slide 34 of 168 Confidential – Do not share without prior permission
Information about the key:
- Number of users
- IP addresses
List of floating license keys available
License Key content (fixed/floating)
Lic.exe (in Atoll installation directory)
Automatically installed with Atoll
Tool which enables to:
• Check the key number
• Program the dongle with licence files sent by FORSK
• List all available modules and their total number of tokens
© Forsk 2011 Slide 35 of 168 Confidential – Do not share without prior permission
List of keys found
Reference, type and
location
List/Number of modules
available
Maintenance and remaining days
Re-programming of the key
Oracle Database Settings for Atoll
Oracle server installation
Installation on PC client
© Forsk 2011 Slide 36 of 168 Confidential – Do not share without prior permission
Oracle Server Installation
Version requirements
Recommended version: Oracle 9i, 10g or 11g
32 and 64-bit version supported on the server side
Basic installation is sufficient
Empty “General Purpose” database with the name "ATOLLDB" and the specific SID
"ATOLLDB"
No need for Java, development tools or web servers…
Several tablespaces can be created for each project
Atoll main (e.g. ATOLLTS)
Atoll temp (e.g. TMPATOLLTS)
Atoll indexes (e.g. ATOLLINDEX)
© Forsk 2011 Slide 37 of 168 Confidential – Do not share without prior permission
Installation on PC Client (1/2)
Oracle client installation
Basic client can be installed
• Same release as the server
• 32-bit client shall be installed, as Atoll is a 32-bit application
Only Oracle runtimes are necessary
SQL*Plus, Enterprise Manager Console or TOAD must be installed for administration
purposes
The database location must be added to the TNSNAMES.ORA file
• Resides in the ORACLE_HOME\Network\Admin folder
© Forsk 2011 Slide 38 of 168 Confidential – Do not share without prior permission
Installation on PC Client (2/2)
Connecting to an Oracle database
Several databases can be accessed from a client, using the server identification (IP address
+ port + SID)
The accessible databases are listed in the file „TNSNAMES.ORA‟
© Forsk 2011 Slide 39 of 168 Confidential – Do not share without prior permission
<Server1> Host=Atoll1 (192.168.1.1)
Port=1521
Service_Name=ATOLLDB
<Server1> Host=Atoll1 (192.168.1.1)
Port=1521
Service_Name=ATOLLDB
<Server2> Host=Atoll2 (192.168.1.2)
Port=1521
Service_Name=PRODDB
<Server2> Host=Atoll2 (192.168.1.2)
Port=1521
Service_Name=PRODDB
<Server2> Host=Atoll2 (192.168.1.2)
Port=1521
Service_Name=TESTDB
<Server2> Host=Atoll2 (192.168.1.2)
Port=1521
Service_Name=TESTDB
Tnsnames.ora may point to
different databases
Instance 1 Instance 2 Instance 3
Server for Pathloss and Geo Data
Principles
Requirements
© Forsk 2011 Slide 40 of 168 Confidential – Do not share without prior permission
Principles and Requirements
Principles
Geographic data and shared path loss matrices should be stored on file servers
Requirements
Required disk space should be calculated according to the size of geographic data files and
path loss matrix files
• Path loss matrices size can be assessed via the number of transmitters, radius and resolution (main
and extended if any)
Shared path loss results and geo data should be accessible to Atoll through a fast network
connection, e.g. 1+ Gbps
A bandwidth of 30 Mbps is recommended per user to perform calculations between the Citrix
servers and the file servers
© Forsk 2011 Slide 41 of 168 Confidential – Do not share without prior permission
Training Programme
1. Installation Procedures
2. Atoll Environment
3. Multi-User Configuration
4. Database Management
5. Atoll Management Console (AMC)
6. Macros/Add-ins
© Forsk 2011 Slide 42 of 168 Confidential – Do not share without prior permission
2. Atoll Environment
ATL file content
Atoll general concepts
Sharing configurations
Master Atoll document creation
Path loss matrices settings
Atoll administration files
© Forsk 2011 Slide 43 of 168 Confidential – Do not share without prior permission
ATL File Content
Possibility to save a complete project within the ATL file
Radio data (Sites, Transmitters, Antennas, …)
Geographic data (DTM, Clutter, Maps, …)
Network parameters (Coordinate system, Units)
Path Loss calculation results
Prediction results
Measurements
Simulations
Multi-RAT documents can contain any one, any two or all three technologies: GSM,
UMTS and LTE
ATL file is single-user only
Possibility to externalize the path losses, geo data, etc.
© Forsk 2011 Slide 44 of 168 Confidential – Do not share without prior permission
Atoll General Concepts
Working systems
Stand-alone ATL file
• ATL file stored and used on local computer
Multi-user environment
• ATL files are linked to a central database (Access, Oracle,…)
Refresh
Archive
User 1
User 2
User i
Database
© Forsk 2011 Slide 45 of 168 Confidential – Do not share without prior permission
ATL
ATL
ATL
ATL
Process Setting-up Multi-user Environments
A multi-user environment is where a set of users work simultaneously on given parts
of a single large network stored in a database
Process of setting up such environments
1. Create the master Atoll document encompassing the entire network to populate the database
2. Set up the master database, via an export of the aforementioned master Atoll document
3. Create configuration files (containing path to the geo data, folder configuration, etc)
4. Calculate path losses matrices over the entire network stored on a shared directory
5. Create user Atoll documents (performed by final users) connected to the database
© Forsk 2011 Slide 46 of 168 Confidential – Do not share without prior permission
Storing Data
Storage in database (all projects)
All radio data (Sites, Transmitters, Antennas…)
Network parameters (Used technology, global parameters, frequency bands)
Default units (internal and projection systems, Rx and Tx)
Used coordinate system (internal and projection) parameters
Site lists management (site list names and site list contents)
Neighbours (internal and external)
Microwave links
Propagation models and their settings
© Forsk 2011 Slide 47 of 168 Confidential – Do not share without prior permission
Sharing Configurations
Two levels for sharing data
Limited sharing: mdb template
• No need for database server (only Microsoft Access)
• Document basic structure required to start a project (GSM, UMTS, LTE, etc...)
• Possibility to share the initial state and default values
• Templates are located in <Atoll software>\templates directory
• New templates can be easily added to that directory, and will be picked up by Atoll automatically
Full sharing
• Database (units, systems, radio data, etc...)
• User configuration files (geo data, studies, folder configurations, computation zone, macros)
• External folder containing path loss matrices + Calculation results export (matrices or plots)
Full sharing is referred to as multi-user environments
© Forsk 2011 Slide 48 of 168 Confidential – Do not share without prior permission
Master Atoll Document Creation
Principles of master ATL file in Atoll
Encompasses the entire network
• All the radio network data
• All the geographic data corresponding to the entire network set on server
Used to fill in the database with the radio data to be shared between all users
How to create a master ATL file
Selecting template
Defining coordinates system and units
Importing or creating the radio network data
Importing geo data (used for configuration file)
Setting up path loss matrices location
All the custom fields should be properly defined before exporting to the database
If added after the export, it must be done by altering the database directly, not through Atoll
• Modifying the database structure in this way will enable all the users to access the modified project with
the new custom fields when they open a new document from the database or refresh an existing one
© Forsk 2011 Slide 49 of 168 Confidential – Do not share without prior permission
Selecting Template
Procedure to create the master ATL file in Atoll
Create a new ATL file
© Forsk 2011 Slide 50 of 168 Confidential – Do not share without prior permission
Defining Coordinates System and Units
Setting the coordinate systems and units
© Forsk 2011 Slide 51 of 168 Confidential – Do not share without prior permission
Access to
coordinates
catalogues
Display system
definition
Projection system
definition
All Units parameters
definition
Degree
decimal
formats
Defining Coordinates Systems
Definition of coordinates systems
Projection system
• Cartographic coordinates (metres, miles, ...)
• Representation of geographic raster maps
Display system
• Cartographic or geographic (deg min sec, …) coordinates
• Used on labels, rulers and for data exchange
• Database reference coordinate system is the display coordinate system defined in Atoll at the time of
the initial project export to the database
Once exported in the database, the coordinates system cannot be changed
Slide 52 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Defining Units
Definition of unit systems (display only)
Distance: m, km, miles
Height and offset: m, feet
Selection of default radio units
Radiated Power: EIRP or ERP
Antenna gain: dBi or dBd
Transmission: dBm, Watts, KWatts
Reception: dBm, dBµV, dBµV/m
Selection of temperature units
°Celsius, °Fahrenheit
Slide 53 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Importing or Creating the Radio Network Data (1/4)
The radio data in Atoll comprises everything related to network parameters
For any technology
Antenna
• Physical equipment used by transmitters
Site
• Geographical location on which can be installed transmitters
Transmitter
• Radio interface built on a site using antenna(s) and optionally equipment such as TMA or feeder
(sector)
Repeater
• Device which can amplify a received signal
• Modelling of impact on the additional coverage provided to transmitters
Remote antenna
• Shifted antenna using the resources of a donor transmitter
Slide 54 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Importing or Creating the Radio Network Data (2/4)
For GSM documents
Subcell
• Set of TRXs of a same type in a transmitter
• (Tx – TRX type) pair
• BCCH, TCH, TCH inner
TRX
• Frequency list
For UMTS, CDMA, WiMAX, LTE and TD-SCDMA documents
Cell
• Specifications of a carrier in a transmitter
• (Tx - carrier) pair
Slide 55 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Importing or Creating the Radio Network Data (3/4)
Sites creation using generic import in Sites, Transmitters (and Cells in 3G) tables
Source
• From any ASCII text file
• From any table exported using the generic export feature within Atoll
Destination
• New records
• Update of existing records
Requirements
Respect the following order
• 2G : 1)Sites → 2)Transmitters
• 3G, 4G and WiMAX : 1)Sites → 2)Transmitters → 3)Cells
Slide 56 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Importing or Creating the Radio Network Data (4/4)
Sites creation using copy/paste in Sites, Transmitters (and Cells in 3G)
From an .xls file to the Atoll document
From an Atoll document to another one
Requirements
Respect the following order
• 2G : 1)Sites → 2)Transmitters
• 3G, 4G and WiMAX : 1)Sites → 2)Transmitters → 3)Cells
Ensure that tables match together
• Between the tables in Excel and in Atoll
• Between the tables in the Atoll documents
XML import
Import all the radio data from one Atoll document to another one
Checks the data integrity after importing
Slide 57 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Importing Geo Data (1/3)
Atoll supports several geo data types
Propagation calculation
• DTM
• Clutter classes
• Clutter heights
Dimensioning
• Traffic
Statistics and prediction plot reports
• Population
• “Generic” maps other than DTM, clutter or traffic (Revenue, subscriber maps)
Microwave link analysis
• Rain map
Only for display
• Scanned maps
• Vector data (Roads, railways, regions…)
Slide 58 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Importing Geo Data (2/3)
Import the geographic data into the ATL file
Slide 59 of 168 Confidential – Do not share without prior permission
Altitudes, Clutter
Heights, … can be
imported
Import of image or
scan
© Forsk 2011
Importing Geo Data (3/3)
Maps can be either embedded into the document or not
Embedding the map into the project is useful for
Data access speed
Make portable projects
Not embedded
Location path is saved in the ATL file
Limits the ATL file size
Permits file sharing on data server
Is required for distributed path loss calculation
Slide 60 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Path Loss Matrices Settings
Overview
Path loss matrices storage
Calculating path loss matrices
Contents of .losses folder
Managing shared path loss matrices folder
Slide 61 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Path Loss Matrices Settings (1/4)
Overview
Possibility to calculate two path loss matrices per transmitter (and repeater)
• A main matrix over a near radius computed with a high resolution and a propagation model
• An optional extended matrix over a far radius computed with a low resolution and another propagation
model
Path loss matrices storage
Embedded in ATL document (not recommended)
Externalised in .losses folder
Possibility to share the externalised .losses folder between users
One public path loss matrix folder for all the users (referred to as public result storage)
Calculation administrator
Slide 62 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Path Loss Matrices Settings (2/4)
Storing master ATL path loss matrices in an external folder
This folder is the private path loss matrices folder of the master ATL file
Serves as shared path loss matrices folder for all the other user projects
Create a private path loss matrices folder on file server
Slide 63 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Path Loss Matrices Settings (3/4)
Calculating path loss matrices
Perform the entire path loss matrix calculation for the master ATL file
Explorer window → Transmitters folder → Calculate Path Loss Matrices
Slide 64 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Path Loss Matrices Settings (4/4)
Contents of .losses folder
1 .Los (binary file) per transmitter or repeater (low and high resolution)
1.Dbf file
• Validity information on each matrix
1 folder for extended matrices
• Lowres
Shared path loss matrices folder management
Administrators: Read & Write
Users: Read Only
Slide 65 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Shared Matrices/Geo Data Settings
Recommendation on defining paths to linked files
Recommended method of defining paths to geographic data or path loss files is the universal
naming convention (UNC)
Example:
• Absolute path: C:\Program Files\Forsk\Geo Data\...
• Relative path: \Program Files\Forsk\Geo Data\...
• UNC path: \\Computer\C\Program Files\Forsk\Geo Data\...
UNC allows for preserving links to external data when working in a multi-server
environment or when moving ATL files to a different workstation
Slide 66 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Atoll Administration Files
User configuration file (.cfg)
Parameters and settings not stored in the database
Atoll initialisation file (.ini)
Is used to inform Atoll of the preferred settings to be used during Atoll sessions.
It can be used to adjust the behaviour and algorithms used in Atoll.
Study file (.xml)
Describes prediction studies with customized settings (default name : studies.xml)
Slide 67 of 168 Confidential – Do not share without prior permission
© Forsk 2011
User Configuration File (1/5)
User configuration content (.cfg) (1/2)
Geographic dataset
• Paths of geographic maps
• Settings (clutter class parameters, colours, visibility flag…)
Computation and focus zones
Folder configuration
• Grouping, sorting, filtering options
• Display settings
Prediction configuration
• Study list
• Definition and settings for each study
Slide 68 of 168 Confidential – Do not share without prior permission
© Forsk 2011
User Configuration File (2/5)
User configuration content (2/2)
Automatic neighbour allocation parameters
AFP configuration (available in GSM documents only)
• Calculation options selected when starting an AFP session
• Calculation parameters used for interference histograms
Scrambling Code (UMTS) or PN offset (CDMA) automatic allocation parameters
Paths of files containing macros
Slide 69 of 168 Confidential – Do not share without prior permission
© Forsk 2011
User Configuration File (3/5)
Exporting user configurations to user configuration files
Slide 70 of 168 Confidential – Do not share without prior permission
© Forsk 2011
User Configuration File (4/5)
User configuration files can be created for different groups of users
Loading automatically user configuration files
Use “C:\Program Files\Forsk\Atoll\Atoll.exe -cfg <configuration_file>” as the application path
for Atoll‟s desktop shortcut
Name the user configuration file to be loaded automatically "Atoll.cfg" and place it in the Atoll
installation directory
Importing user configurations
Reset existing geo data
Reset existing studies
Slide 71 of 168 Confidential – Do not share without prior permission
© Forsk 2011
User Configuration File (5/5)
Importing user configurations files
Slide 72 of 168 Confidential – Do not share without prior permission
Import .cfg/.geo in ATL
Create .cfg/.geo
© Forsk 2011
Atoll Initialisation File (1/3)
Atoll.ini is an ASCII text file to inform Atoll of the preferred settings to be used
Loading Atoll initialisation file
Place the Atoll.ini file in the Atoll installation directory
Declare the .ini file to be loaded in command line
Slide 73 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Atoll Initialisation File (2/3)
Some of the options available in Atoll.ini file
License management options
Blocking access to certain modules
• [Licence]
Measures = 0
Mw = 0
Database options
Setting an automatic database integrity check at open or refresh
• [Database]
Integritychecker = 1
Distributed calculation server options
Setting the distributed calculation server priority
• [Remotecalculation]
Atollsvrpriority = -1, 0, 1 or 2
Slide 74 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Atoll Initialisation File (3/3)
Parallel calculations
Setting number of threads used for calculation
• [Remotecalculation]
NumberOfThreadsPathloss = 1, 2, ..., or 8
• Maximum number of threads that can be used for path loss calculations (4 by default)
NumberOfThreadsSimulation = 1, 2, ..., or 8
• Maximum number of threads that can be used for Monte-Carlo simulation calculations (4 by
default)
Other options are available and described in the Administrator Manual
Slide 75 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Xml Studies File (1/2)
XML file used to share customized coverage prediction studies
The interest of .xml study file is to have specific list of customized studies for a particular type
of user
Contains descriptions of coverage prediction studies
General parameters (name of study template, comments, group, sort, and filter criteria)
Study conditions (study criterion, lower and upper thresholds, servers to be studied, margin,
carrier, etc)
Display settings (display type, visibility scale, add to legend option, tips text, transparency
level, etc…)
Use of XML studies file
Imported directly in Atoll
Saved in installation directory
Slide 76 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Xml Studies File (2/2)
Creating xml file
xml import
User-
defined
studies
xml import
Slide 77 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Training Programme
1. Installation Procedures
2. Atoll Environment
3. Multi-User Environment Configuration
4. Database Management
5. Atoll Management Console (AMC)
6. Macros/Add-ins
Slide 78 of 168 Confidential – Do not share without prior permission
© Forsk 2011
3. Multi-user Environment Configuration
Components of multi-environments
Multi-user environment overview
Interaction with databases
Shared matrices management
ATL files upgrade
Exchanges between existing database and Atoll
Conflict management between users
Audit tool to check the consistency of the tables
Database upgrades
Slide 79 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Components of Multi-environments
Slide 80 of 168 Confidential – Do not share without prior permission
Master Calculation Document
This document is used by the calculation
script to update the shared path losses
daily. It comprises the entire network for
the technology.
Shared Data
Radio data is stored in the database.
Path Loss Matrices and Geo Data can be
shared between all users via a file server.
User Documents
Contain all or part of the data stored in the
database.
© Forsk 2011
…
Shared Pathloss
Matrices
Radio Network
Database
Geographic Data
Master Atoll
Document
User Document 1 User Document N
Multi-user Environment Overview
Study list and
definition
Macros
Computation
zone
Folder
configurations
Geo data path and
description
Refresh
Archive
User configuration
Export
Import
Slide 81 of 168 Confidential – Do not share without prior permission
Atoll
Database
User Rights
Atoll tables
(Sites,
Transmitters,
Neighbors,
…)
Public
Shared
Matrices
User 1
ATL
User 2
ATL
…
Radio data Pre-calculations Geo data and studies
© Forsk 2011
Exchanges between existing database and Atoll (1/9)
Connection to the database
Open from an existing database
Write in the database
Archive
Read from the database
Refresh
Slide 82 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Opening new project from
the database
Write/Read to/from the
database
Exchanges between existing database and Atoll (2/9)
ATL document creation from a centralised database
Requirement
• Existing database initially created with Atoll
Procedure
• Command “From an Existing Database…” in the File►New menu
Slide 83 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Exchanges between existing database and Atoll (3/9)
Procedure
Select project
Slide 84 of 168 Confidential – Do not share without prior permission
Select the sites to load according to any defined Sites Lists.
Allows to reduce unnecessary data retrieved from the database
Project selection
If some fields have been grouped in custom field
groups, it is possible to select one or several groups
in order not to load all the possible customs fields
and save some memory.
Not loading Neighbours tables will limit the
document file size and then improve loading
times.
© Forsk 2011
Exchanges between existing database and Atoll (4/9)
Memorization of the link
Modifications in the ATL file are not reported in real time in the database (and vice
versa): use of Archive and Refresh functions to write/read to/from the database
Slide 85 of 168 Confidential – Do not share without prior permission
Refresh
Archive
ATL file Database
© Forsk 2011
Exchanges between existing database and Atoll (5/9)
To update each personal ATL according to the modified database (other users)
Refresh command
Slide 86 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Exchanges between existing database and Atoll (6/9)
Options of Refresh from the database dialogue
Archive your changes in the database
• Archive changes in database instead of refreshing from database
• Atoll opens the archive assistant dialogue
Refresh unmodified data only:
• Keep the current modifications in ATL document
• Load the data from the database that does not impact these modifications
Cancel your changes and reload database
• Performs a complete refresh by overwriting any changes made in the ATL document
Slide 87 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Exchanges between existing database and Atoll (7/9)
To update the database after modifying an ATL document
Archive command (according to rights as defined by database administrator)
Slide 88 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Exchanges between existing database and Atoll (8/9)
Archive dialogue lists all the modified tables and the number of modifications in each
table in parentheses
Modifications can be of three types
Updated: value of a field modified in the ATL file
Deleted: record completely deleted from a table
Inserted: new record added to a table
Slide 89 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Exchanges between existing database and Atoll (9/9)
Select a table in the left pane
Pending changes pane lists all the modifications in that table
Conflict management between users
Automatic detection of conflicts
Resolving database conflicts
Slide 90 of 168 Confidential – Do not share without prior permission
Archive all the changes made in
the Atoll document to the database
Archive only the selected pending
changes in the pending changes
pane
© Forsk 2011
Conflict Management Between Users (1/3)
Automatic detection of conflicts
Conflicts occur when
Different users have modified the same record
A user has modified a record which has been deleted by another
Slide 91 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Conflict Management Between Users (2/3)
Resolving database conflicts
Resolving a conflict on a modified record
Resolving a conflict on a deleted record
Slide 92 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Conflict Management Between Users (3/3)
Resolving all the conflicts simultaneously
Accept all the modifications made by other users in the database and update document with
values from the database
Overwrite the modifications made by other users in the database with the values from
document
Slide 93 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Database Consistency (1/2)
Audit tool
Check data consistency between the different Atoll tables (Sites, Transmitters, etc.)
Can be used with Atoll documents linked to a master database or Atoll documents created
from a master database then disconnected
Slide 94 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Database Consistency (2/2)
Research of integrity problems
List of all the objects with non existing references
• e.g. Transmitter equipped with a non existing antenna
• e.g. Transmitter without a reference site
Solutions to remove integrity problems
• In the ATL document : possibility to globally delete all the objects
• In the database : delete corrupted records in the ATL file, then archive changes to the database
Research of undefined record
List of sites without transmitters, transmitters without subcells/ TRXs in GSM/TDMA
documents, transmitters without cells in UMTS, is95-CDMA, CDMA2000 documents and
transmitters/cells without neighbours etc.
Research of duplicated records
List of objects that have the same identifier
• e.g. Sites with the same name
Microwave data check
Verify the consistency and validity of some data of Microwave link networks
Slide 95 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Pathloss Management
Path loss results folders overview
Path loss matrices update
Path loss result management
Slide 96 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Path Loss Results Folders Overview
Shared path loss folder: used to store all the pathlosses at a central location, rather
than storing them locally on each user‟s computer (may require large disk space)
Slide 97 of 168 Confidential – Do not share without prior permission
User 1 User i
…
- Shared pathloss folder stored in a
central location (file server)
- Pathlosses will be recalculated
daily (via a script)
© Forsk 2011
Path Loss Results Folders Overview
Private external path loss matrices folder of master calculation ATL document serves
as shared path loss matrices folder for all the other users projects
Administrators: Read & Write
Users: Read Only
Slide 98 of 168 Confidential – Do not share without prior permission
Directory containing
pre-calculated public
matrices shared by
users and populated
by a calculation script
© Forsk 2011
Users store their ATL associated path loss matrices in their private path loss matrices
folder
Path Loss Results Folders Overview
Slide 99 of 168 Confidential – Do not share without prior permission
Externalised matrices
(any location)
Embedded into the
ATL project
© Forsk 2011
Path Loss Results Folders Overview
If some parameters are modified in a user‟s local Atoll document
Atoll automatically detects which matrices have been invalidated
Only the path loss matrices related to the modified transmitters will be recalculated
• Recalculated matrices are stored in the private folder associated with the ATL file/ embedded in the file
itself
Slide 100 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Path Loss Matrices Update
Access to shared matrices folder from user‟s ATL file:
Use shared
Private
matrices
Valid?
Calculate
Use them
Shared
matrices
Valid?
Exist in
private
folder
Delete it
(in Atoll.ini:
FullResyncPrivShared=1)
Slide 101 of 168 Confidential – Do not share without prior permission
YES
NO
YES
NO
© Forsk 2011
Path Loss Matrices Update
In multi-user environments, a script is in charge of calculating the invalid path loss matrices
daily
BAT file is used to call the VBS script UpdateSharedPathloss.vbs for multiple projects
This file contains as many lines as existing technologies in the database (i.e. GSM, UMTS, etc)
• Cscript.exe \\Server\Atoll\AtollData\AtollPathlossData\AtollPathlossUpdate\UpdateSharedPathloss.vbs GSM
• Cscript.exe \\Server\Atoll\AtollData\AtollPathlossData\AtollPathlossUpdate\UpdateSharedPathloss.vbs UMTS
• …
VBS file (UpdateSharedPathloss.vbs)
Runs the calculations according to the technologies listed in the BAT file
• If multiple projects of the same technology in the DB, the VBS script will run for every project
Reads a three tab-delimited file (same as GeoSelector.dat) to open the ATL file and the associated
configuration file (with path to geo data)
BAT file scheduled through the Windows Task scheduler
Slide 102 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Path Loss Matrices Update
VBS script updates shared path loss matrices automatically
Generate or update path loss matrices, based on synchronised database
Script execution
• Start an Atoll session (start)
• Open the calculation administrator‟s Atoll document (open)
• Refresh from the database (refresh)
• Calculate path loss matrices (calculate)
• Close the Atoll session (exit)
Slide 103 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Path Loss Matrices Update
Slide 104 of 168 Confidential – Do not share without prior permission
Archive
Archive
Refresh of
calculation ATL files
Scheduled on a daily basis
Calculate invalid pathloss matrices
Store them in the shared pathloss directory
User 1
User i
…
Final users Calculation script
Refresh
Refresh
Example of scenario below
Shared directory used by the
final users
© Forsk 2011
Path Loss Matrices Update
Requirements for a transmitter or repeater to be taken into account in calculations
Active
Non-Filtered (transmitter or site folder)
Calculate path loss matrices from transmitters folder (Administrator)
Computation zone does not influence the transmitters calculation, and path loss matrices size
Calculate path loss matrices from prediction folder (Common End User)
Calculation area intersecting the rectangle including the computation zone
Slide 105 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Path Loss Matrices Update
Calculation ATL refreshed from the database
Administrator or script updates the shared path loss matrices only when they are not
being accessed by other users
Slide 106 of 168 Confidential – Do not share without prior permission
Useful feature for the administrator:
For setting up the shared path loss matrices folder
For keeping the shared path loss matrices up to date
Recalculate all the path loss
matrices, valid or invalid
© Forsk 2011
Path Loss Matrices Update
Updating path loss result (for end users)
Path loss matrices are calculated for all active transmitters and repeaters with calculation
areas intersecting the rectangle including the computation zone
If the path loss matrices are not valid, Atoll will automatically start recalculating them the next
time they are used
Deletes all the path loss matrices even if they
are existing and valid and recalculates them
Computes the unlocked prediction studies
Use this feature if geographic data has
changed
Slide 107 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Path Loss Result Management
Path loss result management
Validity checking
– Detection of invalid matrices
– Automatic detection for radio data and
calculation area modifications
– No detection for geo data
modifications
Matrix size
and path
checking
Possibility to freeze
existing matrices
Matrix export (ASCII or
binary format)
Path loss matrix
settings
Tools to determine the
number of transmitters to
re-compute matrices and
invalidity causes
Possibility to display all or
invalid matrices only
Slide 108 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Databases Upgrade
Databases upgrade overview
Database automatic migration using AMC
Database manual migration procedure
Upgrading disconnected ATL documents
Upgrading ATL documents connected to a database
Slide 109 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Databases Upgrade Overview
Ensure compatibility between version N and N+1, but not (N+i) with i>1
Atoll versions upgrade:
Build upgrade: Only bug corrections / No database structure changes
Minor version: Bug corrections and new features / No database structure changes
Major version: Database structure changes, bug corrections and new features
Database structures are only modified between two major versions
Databases are referred to as 2.8 and 3.1 database
Atoll documents are referred to as 2.8.3 and 3.1.0 documents
It is necessary that the databases be up to date and compatible with the version used
Slide 110 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Database Automatic Migration Using AMC
It is highly recommended to use AMC to perform databases upgrades
Automatically recognize obsolete fields and deletes them from database tables
Wizard first upgrades the schema of tables
New tables, fields, triggers are added
User customizations (custom fields, labels, groups) are preserved
Upgrade database which was neither created nor already upgraded (at least once)
using the AMC
Need to upgrade a newly created schema with the AMC to enable optimizations for the
selected database type (SQL server, Oracle,…) and activate optional features (History
Management, User Management).
Slide 111 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Database Manual Migration Procedure
Database manual migration procedure
Can create a database with new version structure using the contents of a disconnected
previous version document
• e.g.: create a new 3.1 database using the contents of a disconnected 2.8.X document
• File > database > export to export the project from previous version to database from the new version
• Perform the corresponding changes in the database in line with the new Atoll version structure
Changes in the data structure are listed in the administration guide
Slide 112 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Upgrading ATL Documents (1/2)
Upgrading disconnected documents
Atoll automatically upgrades disconnected documents from version N to N+1
Save the document (using either “Save" or “Save as…") in the new version
Upgrading ATL documents connected to an upgraded database
Slide 113 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Upgrading ATL Documents (2/2)
Upgrading ATL documents connected to a non-upgraded Database
Document must be disconnected
Slide 114 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Training Programme
1. Installation Procedures
2. Atoll Environment
3. Multi-User Environment Configuration
4. Database Management
5. Atoll Management Console (AMC)
6. Macros/Add-ins
Slide 115 of 168 Confidential – Do not share without prior permission
© Forsk 2011
4. Database Management
Oracle terminology
Oracle SQL Administrative tool
Master Database Creation
Modifying the Atoll data structure
Sharing Sites table
Slide 116 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Oracle Terminology
User:
Someone who can connect to a database and may own objects (e.g. tables)
Schema:
Objects owned by one user and one user only (1 to 1 relationship)
Schema ≈ User
Tablespace:
Logical storage unit in the database. Stores the tables, indexes, etc.
Trigger:
SQL procedure fired when a specific action happens: update, insert, delete, …
Privilege:
Right to execute an SQL statement or access another user‟s objects (tables, etc)
Role:
Set of privileges that can be granted to another user or role
Slide 117 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Oracle SQL Administrative tool
Administrative tool to interact with the Oracle database:
SQL Plus
TOAD
Enterprise Manager (or web interface)
SQL Developer
…
Possibility to check the tables, views, triggers, indexes, etc
A DBA account (=Administrator account) is usually required in case SQL scripts have to
be run
Slide 118 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Oracle SQL Administrative tool
Oracle SQL administrative tool (Enterprise Manager, SQL Plus, TOAD) can be used
to assign privileges and roles to users
It is needed to be connected as DBA/owner of a table to grant a privilege on this table
“With Grant option” allows the grantee to grant the object privileges to other users and
roles
AMC enables to easily assign privileges to users without using Oracle interface
Slide 119 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Oracle SQL Administrative tool
Enterprise Manager: Easy-to-use interface to assign roles, privileges, etc
Slide 120 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Master Database Creation
Prerequisite to master database creation
Oracle has already been installed on the server and clients
An empty database where data will be stored has been created, with the name "ATOLLDB"
and the specific SID "ATOLLDB“
An entry has been added in the TNSNAMES.ORA file enabling communication with the Atoll
database
A dedicated tablespace has been created (usually one per project)
Empty user account in Oracle DB must be created before Atoll can export a project to the DB
• Following privileges granted to this user: CONNECT, RESOURCE, CREATE PROCEDURE, CREATE
SEQUENCE, CREATE TABLE, CREATE TRIGGER, CREATE VIEW, UNLIMITED TABLESPACE
Slide 121 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Filling an empty account in Oracle (1/3)
Create a new master database
Open Atoll project containing all the radio data
Check via Tools → Options that the coordinates are correct
Select File → Database → Export the Document to a New Database…
Slide 122 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Filling an empty account in Oracle (2/3)
Selection of the Oracle database
All the tables are exported to the database in the specified Oracle schema
Slide 123 of 168 Confidential – Do not share without prior permission
Name of the schema
Name of the Oracle
instance
© Forsk 2011
Filling an empty account in Oracle (3/3)
Once exported, it is recommended to upgrade the structure of the database with the
AMC
New triggers/fields added in the database
Enables the activation of Users Management/History Management
Mandatory to be able to upgrade to a new major version
Export is performed only once to fill in the database
User can retrieve this project using their Oracle account
Slide 124 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Modifying the Atoll data structure
Custom fields can be added/deleted to/from all Atoll tables
It is not possible to add a new field directly inside Atoll when connected to an Oracle
database
Custom fields are added/deleted to/from Atoll tables by altering the database structure
Use of SQL scripts or Oracle interface (Enterprise Manager or web management interface)
Once the database structure has been changed, the Atoll documents shall be refreshed
from the database (File→Database→Refresh from the Database) to be updated
Slide 125 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Modifying the Atoll data structure
Schema, table and column must be specified when adding custom fields
In case of addition of a custom field, the data type shall be as described below
Slide 126 of 168 Confidential – Do not share without prior permission
Atoll Oracle
Text (n characters) VARCHAR2(n)
Short Integer NUMBER(6,0)
Long Integer NUMBER(11,0)
Single/Double NUMBER
True/False NUMBER(1,0)
Date/Time DATE
Currency NUMBER(38,0)
© Forsk 2011
Modifying the Atoll data structure
Adding a new column
Alter table <SCHEMA>.<TABLE> ADD <COLUMN> <DATATYPE>;
Example:
• Schema: ATOLL_GSM
• Table: Sites
• Column: TestSite, 20-character text field
• SQL query: ALTER TABLE ATOLL_GSM.Sites ADD TestSite VARCHAR2(20);
• Schema: ATOLL_UMTS
• Table: Transmitters
• Column: Reference, Short Integer
• SQL Query: ALTER TABLE ATOLL_UMTS.Transmitters ADD Reference NUMBER(6,0);
Dropping a column
Alter table <SCHEMA>.<TABLE> DROP COLUMN <COLUMN>;
Example:
• Schema: ATOLL_GSM
• Table: Sites
• Column: City
• SQL query: ALTER TABLE ATOLL_GSM.Sites DROP COLUMN City;
Slide 127 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Modifying the Atoll data structure
Once custom fields have been added/deleted, it is required to update the structure of the
history tables (if History Management is enabled)
Performed via the AMC
Automatically upgrades the structure of the history tables
Via the “Manage Modifications History” menu of the corresponding schema:
Slide 128 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Sharing Sites Table (Optional)
Views instead of tables
ATOLL_GLOBAL.Sites = (ATOLL_GSM.Sites) U (ATOLL_UMTS.Sites)
(ATOLL_GSM.Sites = ATOLL_UMTS.Sites = Select * from ATOLL_GLOBAL.Sites)
Slide 129 of 168 Confidential – Do not share without prior permission
ATOLL_GLOBAL
Sites table
ATOLL_GSM
Sites view
Antennas table
…
ATOLL_UMTS
Sites view
Antennas table
…
ATOLLDB
© Forsk 2011
Training Programme
1. Installation Procedures
2. Atoll Environment
3. Multi-User Environment Configuration
4. Database Management
5. Atoll Management Console (AMC)
6. Macros/Add-ins
Slide 130 of 168 Confidential – Do not share without prior permission
© Forsk 2011
5. Atoll Management Console (AMC)
Overview
Installing the AMC
Running the AMC
Upgrading the database
User Rights Management
History Management
Slide 131 of 168 Confidential – Do not share without prior permission
© Forsk 2011
AMC Overview
Atoll Management Console provides the possibility of globally managing the database
with a dedicated interface
Easy upgrade of the database
User Rights Management (Oracle)
History Modifications Management (Oracle)
Atoll Management Console supports
Oracle
Microsoft SQL server
Microsoft Access
Slide 132 of 168 Confidential – Do not share without prior permission
© Forsk 2011
AMC Requirements
Installation requirements
Can be installed during Atoll installation
Administrator rights to the computer are necessary
UAC disabled, Run As Administrator on Vista/Seven OS
Installation procedure
Latest versions available on the Forsk‟s support website by logging on using the user name
and password provided by Forsk
Installed in the same directory as Atoll
Slide 133 of 168 Confidential – Do not share without prior permission
© Forsk 2011
AMC Installation
AMC installation wizard
Slide 134 of 168 Confidential – Do not share without prior permission
To be checked during Atoll
installation
AMC will be installed in the
same directory than Atoll
© Forsk 2011
Running the AMC
Two possibilities to run the AMC:
Open AtollMgmt.msc in the Atoll Installation Directory
Start → All Programs → Atoll → Atoll Management Console
Logging on to the AMC:
Must be
checked
Slide 135 of 168 Confidential – Do not share without prior permission
Enter DBA Credentials
© Forsk 2011
Upgrading the database
Overview
How to upgrade
Slide 136 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Overview
Database upgrade via the AMC:
Complex nature of the upgrade process if done manually rather than using the AMC
Adds new triggers/fields in the DB to be in line with the structure of the new Atoll version
• Mandatory to use the DB with the new version of Atoll
Once database has been filled in the first time, it must be upgraded to the current
version of Atoll used at the export:
Necessary to be able to upgrade from version N to version N+1 later
Slide 137 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Upgrading the database
Slide 138 of 168 Confidential – Do not share without prior permission
Right-click the project
Select Upgrade Database… Upgrading database for
the first time
Current version of the
database
Version of the upgraded
database
© Forsk 2011
Upgrading the database
Database upgraded with the AMC contains additional fields in table ATOLL_ADMIN
Used to improve the performance of the upgrade feature
An extra field called DB_RECORD_ID
Every table in the master database (except Coordsys and Units) contains this extra field
Purpose of this field is to store the record ID for each record in the table
Information in this field cannot be modified
Slide 139 of 168 Confidential – Do not share without prior permission
Field Type Description
NAME Text(50) Name of the database as provided by the user
DESCRIPTION Text(255) Description of the database as provided by the user
ATOLL_VERSION Text(10) Current version of Atoll
ATOLL_BUILD Integer Current build of Atoll
Added by the Atoll Management Console
ATOLL_DBTYPE Text(10) Type of Atoll database (i.e. Master or Project)
Added by the Atoll Management Console
ATOLL_TEMPLATE Text(50) Base Atoll template used to create the master database
Added by the Atoll Management Console
DBSCHEMA Memo Image of the schema of the original database
Added by the Atoll Management Console
© Forsk 2011
User Rights Management (Oracle)
Overview
Enabling User Rights Management
How to use
Slide 140 of 168 Confidential – Do not share without prior permission
© Forsk 2011
User Rights Management Overview
Atoll Management Console enables to:
Create, edit, delete, and deactivate user accounts
Set database access rights for each user
Set access rights to various objects in the Atoll interface for each user
• Radio data tables, properties dialogues, coverage prediction parameters, propagation models, etc.
Slide 141 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Enabling User Rights Management
Make the database compatible with the User Rights Management
Selection of the schema in the AMC
Manage Users…
GUIUSERRIGHTS table is added in DB
when enabling User Management
Slide 142 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Privileges for Users and Roles Defined with AMC (1/8)
GUIUsersRights table content
Each user‟s interface access rights are stored in a unique record
With the following syntax
RADIOPARAMS=X;CALCPARAMS=Y;PROPAGMODELS=Z;PASSWORD=T
Slide 143 of 168 Confidential – Do not share without prior permission
ATOLL_USER Rights in the database/Atoll interface
USER1 RADIOPARAMS=ALL;CALCPARAMS=ALL;PROPAGMODELS=ALL;
PASSWORD=STD
USER2 RADIOPARAMS=STD;CALCPARAMS=STD;PROPAGMODELS=STD;
PASSWORD=STD
USER3 RADIOPARAMS=NONE;CALCPARAMS=NONE;PROPAGMODELS=NONE;
PASSWORD=NONE
© Forsk 2011
Privileges for Users and Roles Defined with AMC (2/8)
RADIOPARAMS=X
Access to radio data
• Sites, Transmitters, Cells, Subcells, Repeaters, Remote antennas, Secondary antennas, Intra- and
Inter-technology neighbours …
Access to radio planning parameters
• Antennas patterns, frequency bands, frequency domain…
CALCPARAMS=Y
Access to all the coverage predictions and their parameters
PROPAGMODELS=Z
Access to propagation models and their properties
PASSWORD=T
Password confirmation when opening an ATL file connected to the database
Slide 144 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Create and Edit User Accounts
Privileges for Users and Roles Defined with AMC (3/8)
Modify the
user‟s
password
Enter a user
name and
password
Slide 145 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Privileges for Users and Roles Defined with AMC (4/8)
Database rights
No access
• User has no Read or Write access to the database
• Database is not visible to the user
• Not allowed to create an Atoll document based on this database
Read Only
• User has Read access to the database but not Write permission
• Allowed to create Atoll documents from the database
• Cannot archive in the database the modifications made from ATL file
Standard
• User has full Read access and Write access limited to standard radio tables of the database (sites,
transmitters, cells, neighbours, repeaters, secondary antennas)
Administrator
• User has Read and full Write access to all the tables of the database
Slide 146 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Privileges for Users and Roles Defined with AMC (5/8)
Access to radio data
Full (RADIOPARAMS = ALL)
• Read and Write access to all the data tables and related properties dialogues
Standard (RADIOPARAMS = STD)
• Full Read access and Write access limited to standard radio tables and related properties dialogues
(sites, transmitters, cells, neighbours, repeaters, secondary antennas)
• Read-only for other parameters such as antennas patterns…
Read Only (RADIOPARAMS = NONE)
• Read-only access to radio network data tables and related properties dialogues
• Not allowed to modify radio network data and parameters
Slide 147 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Privileges for Users and Roles Defined with AMC (6/8)
Access to Predictions
All (CALCPARAMS = ALL)
• Read and Write access to all the coverage predictions and their parameters
Standard (CALCPARAMS = STD)
• Access to customized coverage prediction studies list only
• Allowed to modify coverage conditions and display settings
Customized only (CALCPARAMS = NONE)
• Access to customized studies only
• Not allowed to modify coverage predictions and display settings
Slide 148 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Privileges for Users and Roles Defined with AMC (7/8)
Access to Propagation Models
Full (PROPAGMODELS = ALL)
• Read and Write access to all the propagation models and their parameters
Read Only (PROPAGMODELS = NONE)
• Read Access only to propagation models
Slide 149 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Privileges for Users and Roles Defined with AMC (8/8)
Password Confirmation
YES (PASSWORD = STD)
• Prompts for the password when opening a document connected to the database
NO (PASSWORD = NONE)
• Does not prompt for the password
Slide 150 of 168 Confidential – Do not share without prior permission
© Forsk 2011
History Management Overview
Atoll Management Console enables to
Track User‟s changes in the database
Purge History tables in the database
Slide 151 of 168 Confidential – Do not share without prior permission
© Forsk 2011
History Modifications
Enable Modifications History
Slide 152 of 168 Confidential – Do not share without prior permission
List of the History tables,
records and status
© Forsk 2011
Possibility to enable/disable, repair or purge the tables
History Modifications
Slide 153 of 168 Confidential – Do not share without prior permission
Enable/Disable the history
on the specified table If database modification structure or
upgrade, it is necessary to
install/repair the tables
Purge of the database to remove
all history before a specified date
© Forsk 2011
Training Programme
1. Installation Procedures
2. Atoll Environment
3. Multi-User Environment Configuration
4. Database Management
5. Atoll Management Console (AMC)
6. Macros/Add-ins
Slide 154 of 168 Confidential – Do not share without prior permission
© Forsk 2011
6. Macros/Add-ins
Add-ins and Macros Management
GeoSelector
History Module
Slide 155 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Add-ins and Macros Management
Description
Interface in Atoll
Slide 156 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Add-ins and Macros Management
Macros
VBS scripts
Shall be loaded into Atoll → Atoll.cfg to be used to load them automatically when opening
Atoll
Add-ins
C++ libraries
Registered on each machine
Available to all Atoll versions installed on the machine
Macros and Add-ins can be found on Forsk website (www.Forsk.com/support)
Slide 157 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Add-ins and Macros Management
Possibility to view installed Add-ins and Macros in Atoll
Tools→Add-ins and Macros…
Information about add-ins when clicking Infos…
Slide 158 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Geo Selector
Geo selector description
Geo selector requirements
Geo selector installation
Configuration of geo selector files
Slide 159 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Geo Selector Description
Description
Facilitates the loading of a project from the database
Oracle/SQL Server supported
Dedicated GUI
Loads a project from the database with generic or user account
Loads the configuration file associated to the project
Saves the project to a specific location (optional)
Slide 160 of 168 Confidential – Do not share without prior permission
Select the project to load
from the DB
Enter the login/password
or use the generic
Read/Only account
Indicate where to save
the file
© Forsk 2011
Geo Selector Installation
The Geoselector package contains
The Geoselector library file: Geoselector.dll
The Geoselector parameter file: Geoselector.ini
The Geoselector data file: Geoselector.dat
Installation of Geoselector.dll
Administrator privileges are required to copy and register the Geoselector library on the
computer
Thick-client environment: library must be installed on each user‟s computer
Thin-client environment: only one installation per server is required
Slide 161 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Configuration of Geo Selector Files
Geoselector.ini
Geoselector.ini file must be copied to the “%Program Files%\Forsk” directory (e.g.
C:\Program Files\Forsk)
Geoselector.ini contains all the parameters required by the Geoselector add-in
• [GLOBAL] : general information and parameters
• Datfile (required): location of Geoselector.dat
• [DATABASE] : database related parameters
• Provider parameter (required): type of database
- MSDAORA.1 (Oracle)
- SQLOLEDB.1 (Microsoft SQL server)
• Datasource (required): name of the database
• [FILE] : file name and location (optional)
Slide 162 of 168 Confidential – Do not share without prior permission
© Forsk 2011
Configuration of Geo Selector Files
Geoselector.dat
Used by GeoSelector.ini for the project selection and loading of associated configuration file
3-tab delimited file
Content of GeoSelector.dat:
Slide 163 of 168 Confidential – Do not share without prior permission
Title of the project Schema name;
Sites List
Path to the configuration file
ATOLL GSM ATOLL_GSM \\FileServer\AtollData\AtollGlobalConfiguration\ATOLL_GSM.cfg
ATOLL UMTS ATOLL_UMTS;Region1
\\FileServer\AtollData\AtollGlobalConfiguration\ATOLL_UMTS.cfg
…
© Forsk 2011
History Module
History Module Description
Installation
Interface
Confidential – Do not share without prior permission
Slide 164 of 168 © Forsk 2011
History Module Description
Description
Tracks changes committed by users to the database
Oracle supported: History must be enabled first via the AMC
Dedicated GUI to visualize items history
History available on the following tables:
• Sites
• Transmitters
• Neighbours
• External Neighbours
• Repeaters
• Secondary Antennas
• GSM Only: SubCells, TRXs
• WiMAX and UMTS only: Cells
• MW only: Links, Hubs, Point-MultiPoint, Multihops, Multihops Link
Slide 165 of 168 Confidential – Do not share without prior permission
© Forsk 2011
History Module Installation
The History Module package contains
The AHM library file: AHM.dll
Installation of AHM.dll
Administrator privileges are required to copy and register the AHM library on the computer
Thick-client environment: library must be installed on each user‟s computer
Thin-client environment: only one installation per server is required
Slide 166 of 168 Confidential – Do not share without prior permission
© Forsk 2011
History Module Interface
Dedicated AHM interface in Atoll
Slide 167 of 168 Confidential – Do not share without prior permission
Filtering by item, status,
date and user
Available options for
AHM
History grid
Dynamically-built table
© Forsk 2011
THANK YOU!