You are on page 1of 40

Radioplan

Administration Guide

Version 3.12

www.actix.com
Documentation Version: Admin-v3.12, June 2009

Software Version: Actix Radioplan v3.12

The content of this manual is provided for information only, is subject to change without notice,
and should not be construed as a commitment by Actix. Actix assumes no responsibility or liability
for any errors or inaccuracies that appear in this documentation.

Copyright © 2001–2009 by Actix GmbH.

All rights reserved.

Trademark Notice
Radioplan is a registered trademark of Actix GmbH in the European Union.
Actix and the Actix logo are trademarks of Actix Ltd.
Microsoft, Windows, Windows NT, Windows XP, and Windows Vista are trademarks or registered
trademarks of the Microsoft Corporation. Panasonic is a registered trademark of Matsushita Electric
Industrial Co., Ltd.All other product or brand names are trademarks or registered trademarks of
their respective holders.

Contact:
Actix GmbH Actix Ltd
Altmarkt 10 200 Hammersmith Road
D-01067 Dresden Hammersmith
Germany London, W6 7DL
tel.: +49 (0) 351 404 29 – 0 United Kingdom
fax: +49 (0) 351 404 29 – 50 www.actix.com
e-mail: sales@actix.com
www.actix.com
Contents

1 INTRODUCTION ..........................................................................................5
1.1 ACTIX RADIOPLAN SYSTEM ARCHITECTURE ................................................................ 5
1.2 HARDWARE AND SYSTEM REQUIREMENTS .................................................................. 6

2 INSTALLING THE RADIOPLAN CLIENT APPLICATION ................................................7


2.1 INSTALLATION PACKAGE ...................................................................................... 7
2.1.1 Installation Options for the Installer.......................................................... 7
2.1.2 Installation Flags .................................................................................... 7
2.2 INSTALLATION OF RADIOPLAN AS A SINGLE DESKTOP APPLICATION ................................... 9
2.3 RADIOPLAN INSTALLATION UNDER CITRIX ............................................................... 12
2.4 FOLDER STRUCTURE OF THE RADIOPLAN CLIENT APPLICATION ....................................... 12
2.5 PERSISTENT AND TEMPORARY FILE STORAGE MECHANISMS ........................................... 14
2.5.1 BinDataDir – Folder to Store Large Binary Files per Project ........................ 14
2.5.2 TempDataDir – Folder to Store Temporary Files ....................................... 15
2.5.3 WINESHome – Folder to Store User Settings and Logs .............................. 16
2.6 RADIOPLAN WINES.EXE COMMAND LINE OPTIONS ................................................... 16
2.7 PREREQUISITES FOR USING AN ORACLE DATABASE SERVER .......................................... 16

3 DONGLE SUPPORT AND LICENSE MANAGEMENT .................................................. 19


3.1 MANUAL INSTALLATION OF THE USB DRIVER FOR HARDWARE DONGLES ........................... 19
3.2 REMOTE USB DONGLE UPDATE PROCEDURE ............................................................ 20
3.3 FLOATING NETWORK LICENSE MANAGER SETUP AND ADMINISTRATION ............................. 21
3.4 WEB FRONT-END FOR FLOATING NETWORK LICENSE MANAGER ...................................... 24
3.5 CONFIGURATION OF CLIENT APPLICATION SETTINGS TO CONNECT TO A FLOATING
NETWORK LICENSE SERVER ............................................................................... 25

4 CONFIGURATION AND CUSTOMIZATION ............................................................ 27


4.1 CONFIGURATION FOLDER STRUCTURE .................................................................... 27
4.2 GENERAL CONFIGURATION OPTIONS – WINES.INI ................................................... 29
4.3 USER RIGHTS MANAGEMENT – UMRIGHTS.INI AND UMREQUIREMENTS.INI ...................... 34
4.4 SIMULATION CONFIGURATION ............................................................................. 35
4.5 OPTIMIZATION ENGINE CONFIGURATION................................................................. 35
4.6 CUSTOMIZATION OF PLUGINS.............................................................................. 35
4.7 CUSTOMIZATION OF LEGEND PRESETS AND THE USER WORKSPACE ................................. 36

5 REFERENCES ........................................................................................... 39
www.actix.com
Actix Radioplan Administration Guide Introduction 5

1 Introduction
Actix Radioplan is an application that has been designed as an extendible system that can
be installed in single desktop computers or in central server environments including Citrix.
The application is a client-server application where the user client is a thick client Windows
application and the backend is an SQL database. While for single desktop applications or
smaller workgroups a simple MDB file is sufficient, for central server deployments an
Oracle database can be used.
This document provides the necessary detailed information how to setup, configure,
customize the client application and how to configure the SQL database. It is also
described how a central network license server can be configured and how a USB hardware
dongle that is used for license protection can be upgraded remotely.

1.1 Actix Radioplan System Architecture


Actix Radioplan is a component-oriented system. Its core is a thick-client Windows
application that interfaces with a backend SQL database, a shared file system to store
large binary data, certain functional modules that extend the platform with simulation and
optimization capabilities, various plug-ins implemented as DLLs that provide interfaces to
external 3rd party applications and file formats, and customer-specific extensions such as
automated reporting and result analysis.

Measurement
Measurement
Planning
Planning Tool
Tool Result
Result Analysis
Analysis
Data
Data Import
Import
Adapters
Adapters Plugins
Plugins
Plugins
Plugins

Automatic
Automatic Cell
Cell Planning
Planning (ACP)
(ACP)
Measurement
Measurement Module
Module

Actix
Actix Radioplan
Radioplan Autom.
Autom. Neighbor
Neighbor List
List Plg.
Plg. (ANP)
(ANP)
Simulation
Simulation Module
Module
Parameter
Parameter Opt.
Opt. Module
Module

Desktop or Application Server

Shared Oracle 10g Floating


Floating License
License
File Database Manager
Manager
System Server

File Server Database Server License Server

Fig. 1-1 Actix Radioplan System Architecture

Fig. 1-1 shows the system architecture for a fully utilized installation. The Radioplan client
application including various modules, planning tool adapters, measurement data import
plug-ins, and result analysis plug-ins is installed on a Windows desktop client or on a
Windows application server (e.g. Citrix & Windows Server 2003).
On single desktop installations, the SQL database and the shared file system are hosted on
the application server. Thus, neither shared file server nor a central Oracle database is
required.

www.actix.com
Actix Radioplan Administration Guide Introduction 6

The application is protected with a USB hardware dongle. For the license management
three options are available:

For a stand-alone desktop application, the USB dongle can be connected to the
desktop where the application is installed and no further setup of a license server
is required.

For installations in central application server environments, i.e. Citrix, where users
connect to the system remotely a floating license manager is required that is
installed on a central license server. All users can share a pool of available floating
network licenses.

It is also possible to install a floating license manager on a central server where


Radioplan applications installed on single desktop machines share a pool of floating
network licenses.
Details how to setup a floating license manager and how to configure the client
applications to connect to the central floating license manager are described in Chapter 3.

1.2 Hardware and System Requirements


The Radioplan client application is a native Windows 32 bits application. The following
operating systems are supported:

Windows XP 32 bits SP1 or higher

Windows XP 64 bits

Windows Vista 32 or 64 bits all versions

Windows Server 2003 32 bits

Windows Server 2003 64 bits

Citrix MetaFrame v3 or higher in combination with the supported Windows Server


systems, a Citrix client v9.0 or higher is recommended
The following hardware is required to run the system with reasonable performance:

1GB or RAM for desktop installations, 2GB RAM for server installations

XGA graphics card (1024x768 pixels minimum) with 16 Million colors or higher

Pentium 4 class processor with 2GHz clock speed, Pentium M mobile processors
with 1.6GHz clockspeed are recommended, multi-core CPU systems (or hyper-
threading) can improve the allover system performance due to parallel processing
capabilities of the application.

At least 10 GB of available disk space on the drive where the shared file system
and the local database is installed.
For a deployment with an Oracle SQL database, it is required to use Oracle 10g R2. On the
application server, an Oracle client 10.2 or higher including SQLPlus and Oracle provider
for OLEDB is required.

www.actix.com
Actix Radioplan Administration Guide Installing the Radioplan Client Application 7

2 Installing the Radioplan Client Application


2.1 Installation Package
Radioplan is delivered as a single setup.exe Windows Installer executable. The file itself
contains the respective .MSI file. Latest versions can be downloaded from MyActix.com
support portal.
If an administrator needs to run the installation in silent mode, one can simply extract it by
running setup.exe with the following command line parameters:
setup.exe /S /v/qn
Following statement will further create a winesinstall.log:
setup.exe /S /v"/qn /log winesinstall.log"
Note: all parameters within the quotes are passed on to the MSI Windows Installer.

This section describes ways of influencing the Radioplan installer behavior by using flags.
To use these, you need to either pass the corresponding property or properties to msiexec
or use a transform file (MST) to set these when installing using a Citrix or other packager.
See details below.

2.1.1 Installation Options for the Installer


There are installations options available. How to pass them to the Windows Installer is
described in the following and the option flags you find in chapter 2.1.2.
When installing from setup.exe, use
setup.exe /v"PROPERTY=1"
where PROPERTY is the name of the considered property. To combine several properties,
just append them, separated by spaces, e.g.
setup.exe /v"RP_NO_CONFIG=1 RP_NO_MDB=1"

When installing from the MSI, use


msiexec /i "Actix Radioplan 3.9.1.msi" PROPERTY=1

When using a packaging system (like Citrix Installation Manager), you may need to create
a transform file (MST) using, e.g. Microsoft Orca or InstallShield.
Please also refer to the subsequent section „Radioplan Installation under Citrix‟.

2.1.2 Installation Flags

RP_NO_CONFIG
Defining this property using a value different from 0
results in the configuration tree not being installed.

www.actix.com
Actix Radioplan Administration Guide Installing the Radioplan Client Application 8

RP_NO_MDB
Defining this property using a value different from 0
results in the MDB not being installed.

RP_NO_LICREDIST
Defining this property using a value different from 0
results in the licensing redistributables not being installed.

RP_NO_DONGLEDRV
Defining this property using a value different from 0
results in the dongle drivers not being installed.

RP_NO_FORSK
Defining this property using a value different from 0
results in the Forsk Atoll integration not being installed.

RP_NO_AIRCOM
Defining this property using a value different from 0
results in the Aircom Asset integration not being installed.

RP_NO_WIND
RP_NO_PCTEL
RP_NO_PANASONIC
RP_NO_ANITE
RP_NO_ANDREW
RP_NO_COUEI
RP_NO_COMARCO
RP_NO_ANRITSU
RP_NO_AGILENT
Defining one or more of these properties using a value different from 0
results in the corresponding measurement import module(s) not being installed.

RP_WITH_AFP
Defining this property using a value different from 0
results in the AFP module being installed. Be sure that Radioplan is properly configured
when using this option.

www.actix.com
Actix Radioplan Administration Guide Installing the Radioplan Client Application 9

2.2 Installation of Radioplan as a Single Desktop Application


This section describes the normal installation procedure for Radioplan on a single
computer. If Radioplan shall be installed under Citrix please consider the additional
information in Section 2.3.
The software is installed comparable to any other Windows application. The InstallShield
installer software is used for the setup process.
From version 3.8 the installation directories where application and user data is installed
has been revised in order to be compliant with the newest Windows operating system
Vista. Therefore, side by side installations of various releases is supported now, and
previous installations of an older version will not be automatically removed anymore.
However, if an existing version is updated by a newer version (new build), the previous
installation is replaced by the latest one.

Important Notice for Hardware Dongle Usage

If the Radioplan installation is delivered with a hardware


dongle, make sure that any of the dongles is not inserted
before the entire installation procedure has been finished!
This will ensure that the USB port driver for the hardware
dongle is installed or updated correctly before the dongle is
inserted for the first time. If an USB dongle is inserted
during the installation process InstallShield may report an
error 1935. If that happens please unplug the USB dongle
and retry the installation.

The installation of the driver for the hardware dongle


requires administrator rights on the computer. Make sure
that you have those rights when Radioplan is installed with
hardware dongle support.

Radioplan Upgrade The InstallShield installer does not


remove any existing database nor binary data that is
stored in the shared. Thus, it is safe to execute the
installation process, since the data stored in the ~\db\
directory is not modified. When the updated Radioplan
application is started for the first time, it will securely
convert and update the data.

If a Radioplan of the same release version is already installed on this computer, a dialog
appears allows the user to

modify the current installation (for instance add/remove features)

repair the current installation

remove (uninstall) the current installation (but the local database and all files
stored in the ~\db\ directory are not removed).
If a newer release version is installed on a system where a previous build version of the
same release has already been installed, the InstallShield wizard informs the user that it is
performing an update of the existing installation.

www.actix.com
Actix Radioplan Administration Guide Installing the Radioplan Client Application 10

Please note that modules that require a COM registration


(e.g. the Atoll Synchronization Module, see also [R-ASM])
will always connect to the version that was installed last on
the system.

In the following, the steps required to accomplish a new installation are described. First,
the license agreement is shown. Please read it carefully to get familiar with the license
terms. If you do not accept it, you cannot install the software on your computer. To accept
the license conditions, select the radio button I accept the terms in the license agreement
and click Next.

Fig. 2-1 License agreement dialog

Following this agreement, one can select a target folder for the installation of the program
files.
In the next dialog, one can decide whether to install the complete software package or a
customized version. Using the latter option, the available features are shown in a
hierarchical structure. Some of the Radioplan core components are required and must be
installed. It is always possible to install additional features at a later time by running the
setup procedure again. For the features to be installed a custom setup directory can be
chosen using the Change… button.

www.actix.com
Actix Radioplan Administration Guide Installing the Radioplan Client Application 11

Fig. 2-2 Custom Setup dialog

Next, the setup procedure is ready to install. After confirmation, old Radioplan installations
will be uninstalled (if the directory has not been renamed, see note above), and the
selected features are installed.
Furthermore, various Windows system components will be updated if required. Radioplan
does require the Microsoft Data Access Components (MDAC), the MSXML 2 library, and
Visual C++ runtime DLLs for Visual C++.NET 2005 SP1. Since the latest MDAC and MSXML
libraries are installed or updated with MS Windows service packs under Windows XP and
Windows Server 2003, typically only the Visual C++ runtime DLLs need to be updated by
the Installer according to the Windows standard procedures.
A new menu folder Actix  Radioplan <version> is created in the Windows start menu that
contain the icon to start Radioplan.

Java Runtime Installation: The WiNeS Network


Simulator requires a Java Runtime Environment, release
1.5 or higher. Since most of the computers have already
installed an up-to-date JDK or a JRE, the Java Runtime
Environment is NOT installed by InstallShield. If necessary,
it must be done separately.

The original JRE by Sun Microsystems is available on the


installation CD-ROM in the directory \jre\ as an additional
executable setup.

In order to uninstall the Radioplan software, to install any other feature, or to repair the
installation, just run the setup program again.
If an Radioplan installation with hardware dongle software protection is used, the
according driver has been installed silently during the installation process. The driver
installation does detect the correct operating system automatically and the respective USB
driver is installed. The USB driver supports Windows XP 32 and 64 bits, and Windows Vista
32 and 64 bits operating systems as well as Windows Server 2003 32 and 64 bits.
More information on the hardware dongle support and the usage of floating licenses in a
computer network can be found in Chapter 3.

www.actix.com
Actix Radioplan Administration Guide Installing the Radioplan Client Application 12

2.3 Radioplan Installation under Citrix


The installation of the application under Citrix is very similar to the procedure as described
in Section 2.2. However, under Citrix the user has to execute the setup.exe installer file
according to the following procedure:
It is recommended to login onto the respective server using a remote desktop connection.
In order to make sure that a connection to the console session is established, please use
the following statement to connect (the best way is to enter this command by Start-
>Run…):
mstsc /v:CitrixServerName /console.
Then login, open the control panel, select “Software”, select “Add/Remove programs” and
pick the setup.exe file and follow the Install Shield Wizard. Please take into account that
various local drives are mapped to alternative shares. Thus it might be necessary to
modify the installation directory where Radioplan shall be installed.
Note: Under Citrix the software cannot be installed by just clicking on the setup.exe file.
Citrix changes the mode internally from “User” to “Install” if you use the Add/Remove
programs icon which guarantees that necessary registry entries will be added to the “core”
Windows registry instead of to a shadow registry.

2.4 Folder Structure of the Radioplan Client Application


After Radioplan has been installed, the following folder structure is available and has to be
eventually customized, see also Chapter 4. From version 3.8 application files (executables,
DLL‟s) and application data (configuration settings, database and project files) are installed
into separate directories in order to be compliant with Windows Vista guidelines.
There are several directories where the setup installs files. Default locations are
summarized in the following table:

Table 2-1 Installation folders

Folder Description and Default Location


Installation or In this folder all executables and DLLs are installed. The default
Application folder location is:
%ApplicationPath% c:\program files\actix\radioplan\X.Y
X.Y are given by the major and dot release version of the
application, e.g. 3.12
Configuration or In this folder all configuration and customization files, local
Application data databases and project files are installed. The default location is:
folder
%APPDATA% c:\documents and settings\all users\
application data\actix\radioplan\X.Y (Windows XP)

c:\ProgramData\actix\radioplan\X.Y (Windows Vista)

X.Y are given by the major and dot release version of the
application, e.g. 3.12

www.actix.com
Actix Radioplan Administration Guide Installing the Radioplan Client Application 13

Folder Description and Default Location


User settings folder In this folder the application stores user specific settings such as
%WINESHOME% legend settings and workspace configurations. Also log files are
stored into this folder. The folder does not depend from the
installed version, i.e. all versions are using common user settings.
The default location is:

c:\documents and settings\user\


application data\actix\radioplan (Windows XP)

c:\users\user\AppData\actix\radioplan (Windows Vista)

The user represents the login name of the user.

The following table details which directories are created within the folders summarized
above:

Table 2-2 Installation sub-directories

Folder Content
%ApplicationPath%\ WiNeS.exe Radioplan application and certain DLLs
%ApplicationPath%\asm COM components specific to the Atoll
Synchronization Module, refer also to [R-ASM]
%APPDATA%\configuration All Radioplan specific configuration files. This is the
central directory where configuration files can be
edited for customization, see also Section 2.5.
%APPDATA%\db Default directory for a local repository: A
dbwines.mdb access file as well as large binary
project files are stored in this folder.
%ApplicationPath%\help Radioplan online help files
%ApplicationPath%\library The Radioplan library that contains pre-configured
settings for user equipment, mobility profiles,
service profiles, UE profiles, and monitoring settings
used by the simulator module.
%ApplicationPath%\licensing A folder that contains various utilities for license
management such as the remote update tool and
the floating license server for hardware dongles.
%ApplicationPath%\measurement The folder contains a data collection application for
the Panasonic UMTS scanner VS-2100A. This
application is installed for customers that use
Radioplan in conjunction with the UMTS scanner.
%ApplicationPath%\plugins A folder that contains subfolders for various
planning tool adapters, measurement data import
plugins, and result analysis plugins.

www.actix.com
Actix Radioplan Administration Guide Installing the Radioplan Client Application 14

2.5 Persistent and Temporary File Storage Mechanisms


Radioplan does store all of the project meta data in an SQL database. However, certain
files are stored in dedicated folders which can be configured in WINES.INI, refer also to
Section 4.1.

2.5.1 BinDataDir – Folder to Store Large Binary Files per Project


The BinDataDir folder does contain all large binary files that will not be stored within the
SQL database directly in order to improve the allover performance of the system. The
folder complements the SQL database, and therefore, the administrator has to make sure
that always the correct BinDataDir folder is configured in relation to the configured SQL
database.
The BinDataDir folder contains sub-folders where the folder name is the primary key of the
Radioplan project (Project ID). The Radioplan project ID can be viewed in the lower left
corner of the project settings dialog, e.g. 11:

Fig. 2-3. Project Settings Dialog

Within this project folder (e.g. BinDataDir\286) the following file types are stored (the file
name is given by the primary key of the related database object):

Table 2-3. Files stored in project folders in the BinDataDir shared directory

File Extension Description


*.pl Unmasked pathloss matrix
*.plinc Inclination matrix that complements the unmasked pathloss
matrix
*.pla Masked prediction for a given resolution – LowRes part of the
prediction matrix
*.plah Masked prediction for a given resolution – HighRes part of the
prediction matrix
*.trf Traffic matrix
*.rvn Revenue matrix

www.actix.com
Actix Radioplan Administration Guide Installing the Radioplan Client Application 15

File Extension Description


*.mor Clutter matrix
*.dem DEM matrix (also known as terrain height)
*.bin Binary results imported from drive test measurements or
simulations
*.binmeta Meta data for binary results, complements a binary results file
*.rd Road data, typically imported from vector data
*.go Vector overlay layers
*.lyr Raster layers (locked layers)
*.vis Cell visualization layers
*.area Area polygons
*.antenna Antenna pattern files
*.rep Reports
*.tmplt RNC templates

During the import of measurement results and simulation results, if the import process
was successful, in the BinDataDir folder temporary files are created that will be
automatically transferred into the respective project folder. If the import process is
interrupted by the user or an error occurs, the files will be automatically removed from the
BinDataDir folder.

These temporary files will always be created in this folder


independently of any setting of TempDataDir (see also
Section 2.5.2). Once the import has been completed the
files can then be simply moved to the project folder by the
operating system. In this way, the files do not need to be
copied from one storage unit to another one.

2.5.2 TempDataDir – Folder to Store Temporary Files


In order to speed up the processing of automatic optimization tasks, some pre-calculated
matrices need to be stored on a local temporary drive and will be deleted after the
optimization module is unloaded. The file name convention for temporary files created by
Radioplan is RP*.TMP. The TempDataDir can be configured in WINES.INI.
If the application terminates during the optimization processing, it is necessary to delete
the remaining temporary files from time to time. For that purpose a helper function is
available in Radioplan (Tools  Database  Delete Temporary Files) that can be used by
users with administrator rights (see Section 4.3).

It is always safe to try to delete all temporary files that


comply with the naming convention, because Radioplan
does lock all opened files and therefore they cannot be
deleted by another process.

www.actix.com
Actix Radioplan Administration Guide Installing the Radioplan Client Application 16

2.5.3 WINESHome – Folder to Store User Settings and Logs


Radioplan automatically stores the user workspace settings and user legend settings in a
personal folder. The users can configure the look and feel of the application, since the
application tries to re-import the latest workspace settings during application startup. No
data is stored in the user‟s registry in order to avoid conflicts under Citrix where the user‟s
registry might be discarded after the session has been closed.
If the user activates an option to write all log messages, which are shown in the message
window, into files, then these log files are also stored in the personal folder as configured
by the WINESHome variable in WINES.INI. If a log file exceeds a file size of 1 MB, the file
is renamed by using the current date and time and a new file is opened. That mechanism
avoids that too large log files are generated.
Note: The current location of the WINESHome folder can be verified if the user presses the
“Explore Log Folder…” button available in the General Settings Dialog. For details see also
[R-UG].

2.6 Radioplan WINES.EXE Command Line Options


This Section describes all supported command line options for the Radioplan client
application. In order to register or unregister WINES.EXE, the following command line
arguments can be used:
WINES.EXE /register – registers Radioplan in the registry, which is used by the Atoll
Synchronization Module, see also [R-ASM]
WINES.EXE /unregister – unregisters Radioplan and removes any COM related entry from
the Windows registry.
It is possible to tell Radioplan which “configuration” folder shall be used to read the
installation-specific settings. This is helpful if the application shall be e.g. published under
Citrix but various default configuration settings shall be used by different user groups (e.g.
regional offices):
WINES.EXE /configdir=c:\configurationXYZ – tells Radioplan to read any settings from
the alternative configuration path c:\configurationXYZ. Both absolute and relative path
names are supported incl. UNC path naming conventions. Note that no blanks are
supported before and after the equal (“=”) character.
If Radioplan is executed without any command line parameter, the configuration is parsed
from the following locations:

Radioplan searches for an environment variable WINESCONFIG. If that


environment variable is defined, the configuration is parsed from the path as
specified by the environment variable. It is important to know that an absolute
path must be defined. Relative pathnames are not supported by this option.

If no environment variable is defined, the default configuration is parsed from


%APPDATA\configuration.

2.7 Prerequisites for Using an Oracle Database Server


Deployments with an Oracle SQL database must use Oracle 10g R2. On the application
server, an Oracle client 10.2 or higher including SQLPlus and Oracle provider for OLEDB is
required. It is also necessary to manually configure TNSNAMES.ORA on the application
server to configure a database connection. Furthermore, the ConnectionString in
WINES.INI has to be configured accordingly, see also Section 4.1.

www.actix.com
Actix Radioplan Administration Guide Installing the Radioplan Client Application 17

Under 64 bits Windows operating systems 32 bits applications are usually installed under
c:\program files (x86)\Actix\Radioplan. Due to a bug in the original Oracle client version
10.2 the application cannot connect to an Oracle database even if all settings (connect
string and settings in TNSNAMES.ORA) are configured in a correct manner. The reason is
the parenthesis in the path name.
There are two solutions to resolve this problem:

Upgrading the Oracle client with path 6 will resolve the problem

Install Radioplan into another directory that does not contain parenthesis.

www.actix.com
Actix Radioplan Administration Guide Installing the Radioplan Client Application 18

www.actix.com
Actix Radioplan Administration Guide Dongle Support and License Management 19

3 Dongle Support and License Management


3.1 Manual Installation of the USB Driver for Hardware Dongles
If a dedicated server, where Radioplan is not installed, is used as a floating license
manager, it is necessary to install or update the USB driver for the hardware dongle. The
reason is that the USB driver is a mandatory prerequisite for the floating license manager.
The Radioplan licensing system uses hardware dongles from Marx Software Security
(www.marx.com). The manufacturer provides an installer that automatically installs the
necessary drivers for the respective operating system. It is never required to reboot a
machine after a driver has been installed or updated.
On the CD-ROM or after installing Radioplan, a CBUSetup.exe installer is available in the
~\drivers\ directory. To manually install or update the driver execute the installer and just
select Install in the appearing dialog.

Note: Administrator rights are required to install or to


update the USB driver on the system.

In order to install or upgrade the driver silently, it is possible to use the following syntax:
cbusetup.exe /Q /CRYPTOKEN
The installer returns the following exit codes that might be helpful if the driver cannot be
installed and an error is shown:

Table 3-1. Exit codes of the USB dongle installer

Exit Code Description


0 No errors occurred.
-1 The installer could not detect your operating system.
-2 The user aborted the installation.
-3 Wrong version of the operating system.
-4 The setup had an internal error. Please, contact your distributor to
notify about this problem.
-5 The user has requested the installer to run in the "quiet" mode but
the device was set incorrectly. Run the installer with a help switch
(/? or /H) to see the command line syntax. The following
command line syntax is acceptable:
CBUSetup.exe /Q /CRYPTOKEN
-6 The user does not have enough rights if the installer is run under
Windows NT/XP. Contact your System Administrator.
-7 The installer could not perform a registration of the device
driver(s). Please, run the installer again, and if the problem
persists, contact your distributor.

www.actix.com
Actix Radioplan Administration Guide Dongle Support and License Management 20

3.2 Remote USB Dongle Update Procedure


Radioplan is protected by a hardware dongle and all the necessary license information is
retrieved from this USB hardware security device. When a customer licenses e.g.
additional software modules– also for a limited time period – these modules can be
activated remotely by reprogramming the hardware dongle. This section describes how the
license information can be updated at the end user‟s side without sending the USB dongle
to Actix.
First, the customer generates a transaction file for the currently connected hardware
dongle. This file must be sent to Actix, and in return, an activation file is submitted to the
end user. Using this activation file, the customer can update the respective hardware
dongle, as schematically depicted in Fig. 3-1.

Fig. 3-1. General procedure of the hardware key update process

The necessary steps for creating a transaction key and updating the hardware security
device using an activation code provided by Radioplan is described in detail in the
following.
The transaction necessary to start a license update can be generated with the utility
rupdate.exe. This application was installed together with Radioplan and can be found in
the %ApplicationPath%\licensing\RUpdate folder. The application window of the
Remote Update utility is shown in Fig. 3-2.

Fig. 3-2 Remote update utility used for hardware dongle reprogramming

www.actix.com
Actix Radioplan Administration Guide Dongle Support and License Management 21

A transaction key is created by executing the New Transaction button and is shown in the
upper field. This key can be exported to a file with the Export button. This transaction key
is also stored onto the hardware dongle. Thus, it is only possible to create a new
transaction key, if no transaction was initialized before or if the last transaction was
already completed. However, it is still possible to overwrite a previously created
transaction key which cancels the transaction started before. If an open transaction is
detected, a warning appears and the user has the choice to cancel this open transaction.
Then, please send the following information via email to support.dresden@actix.com or via
the portal www.myactix.com:

the serial number of the dongle (as found on the little badge attached on the
dongle) and

the transaction key file TrKey.rfp.


In return, the customer will receive a file that comprises the updated hardware dongle
information, namely an activation code (default: ActCode.rfp). This file must be imported
into the Remote Update utility by using the Import button. Finally, the update procedure
executed by pressing the Update button will reprogram your hardware dongle.
Note that only the hardware dongle can be updated that the transaction key was created
for. It is not possible to reprogram other hardware dongles using the submitted activation
code.

3.3 Floating Network License Manager Setup and


Administration
An installation of a floating license manager is required if the application is installed on a
central application server and the users access the software via remote desktop or if
multiple users want to share a pool of floating licenses.
The machine where the floating license manager shall be activated must have at least one
USB port available, and a 32 bits Windows operating system is required.
Before the floating license manager is configured, the USB driver must be installed on the
machine, where the floating license manager is going to be activated. Please follow the
procedure as described in Section 3.1.
Then copy the CbNet Server directory from an existing Radioplan installation or from the
CD-ROM to any folder of the machine where the floating license manager shall be
activated.
Finally, execute the CbNetSrv.exe application from the ~\CbNet Server\ directory. Then
an icon is shown on the task bar – a double click on it opens a window showing the
current license log file. Additionally, the license server can be stopped and started again by
pressing the according button in this window.
It is possible to configure the license server as a service. The advantage is that the license
server would be automatically started after a reboot of the computer. You can configure
the license server as a service in the following way:

Double click the icon in the taskbar.

Stop the CbNet Server by pressing the Stop button.

www.actix.com
Actix Radioplan Administration Guide Dongle Support and License Management 22

Fig. 3-3. CBNet Server window in application mode

Select the option “Run as Service” and press the Start button to restart the server
as a service.

Fig. 3-4. Change CBNet Server to run as an NT service

Then the CbNet Server will run again.

www.actix.com
Actix Radioplan Administration Guide Dongle Support and License Management 23

Fig. 3-5. CBNet Server is running as an NT service

Note that whenever the dongle has been removed, the license server must be restarted
after the dongle was inserted again.
Along with the server application, a floating license administration tool AdminApp.exe is
provided in the %ApplicationPath%\licensing\CbNet Server\ directory. This tool can be
used to

administer the license server (restart, shut down);

administer the license usage (list all users, disconnect single users).
After starting the administration tool, the main window is shown (compare Fig. 3-6). First,
all license servers (typically only one) must be searched in the network by pressing the
Get/Update Servers button. All servers found are listed in the field to the right. Then the
license administrator can login to the currently selected server by pressing the other
button Login To Server. The administrator password is needed for this. A new window is
opened that allows all administrative actions to be done.

Fig. 3-6 Main license administration tool window

www.actix.com
Actix Radioplan Administration Guide Dongle Support and License Management 24

For administrative purposes, a web-based front-end is also available that offers the same
functionality as the license administration tool. It can be accessed by selecting the URL
“http://<LicenseServerName>:8765” in a normal web browser where
<LicenseServerName> is the hostname of the license server or, alternatively, its IP
address, and 8765 is the default TCP/IP port number. Read the
%ApplicationPath%\licensing\CbNet Server\server.htm file for more information on
the floating license administration.
If the hardware dongle is properly inserted into the license server and the license server
application is running, Radioplan can be used throughout the network utilizing the floating
licenses. The hardware dongle controls the number of concurrent instances of Radioplan
that are simultaneously running.

3.4 Web Front-end for Floating Network License Manager


The floating network license manager can be administrated via a web client. In order to
access a floating license manager that is installed and running, please enter the following
web address into a web browser:
http://<hostname>:8765
The computer‟s host name or the respective IP address has to be used as a <hostname>.
Port 8765 is the default port number.
Click on the link “Administration” and enter the following login:

username: admin

password: cbnetserver

Fig. 3-7. Web front-end of the floating license manager client

The web front-end delivers information about the connected clients, the type of the dongle,
server information, etc. The license server can be configured, restarted and shut down;
single users can be disconnected from the license server.
The server.htm file in the CbNet Server directory contains more detailed instructions on
the usage of the license server administration web front-end.

www.actix.com
Actix Radioplan Administration Guide Dongle Support and License Management 25

3.5 Configuration of Client Application Settings to Connect to a


Floating Network License Server
After an installation of the Radioplan client application the license settings are configured
to search for a locally connected USB dongle. In order to use a shared pool of floating
network licenses, the LICENSE.INI file needs to be configured.
All licensing related files are stored in the following folder:
%APPDATA%\configuration\license\license.ini
where %APPDATA% is a placeholder for the configuration data directory of Radioplan (i.e.
where all configuration settings ini files are located). However, it is possible to use an
alternative configuration folder location, please refer to Section 2.5 for details.
In order to change the connection to one or more floating license server(s), the following
changes are necessary (required changes are shown in red color):
[License]
; License = 0 : HW protection
; License = 2 : SW protection
License = 0
; Port = USB : for local USB key (default setting)
; Port = TCP_IP : for remote connection via TCP/IP
;Port = "USB"
Port = "TCP_IP"
; Server = USB : for local USB key (default setting)
; Server = CBNetServerDNSName : for remote connection (or IP address)
Server = "FloatingLicenseManagerComputerName1"
; AlternativeServerX = AlternaticeCBNetServerDNSName : for remote
connection (or IP address)
; Up to X=4 Alternative Servers can be defined here...
AlternativeServer1 = "FloatingLicenseManagerComputerName2"
;AlternativeServer2 = ""
Note that up to 5 floating license managers can be configured. IP addresses or hostnames
can be used as Server or AlternativeServer names. The Radioplan application queries the
Server name first. In case the server does not respond or the number of floating licenses
has been exceeded, the next server (AlternativeServer1..4) is queried.

The setup of multiple floating license managers enables


failover capabilities if one license manager is temporarily
unavailable.

www.actix.com
Actix Radioplan Administration Guide Dongle Support and License Management 26

www.actix.com
Actix Radioplan Administration Guide Configuration and Customization 27

4 Configuration and Customization


In order to integrate Radioplan into a central server environment various configuration and
customization options are available. The customization is generally done by the
modification of *.INI files. Since Radioplan (WiNeS) 3.7 all files available for customization
are stored in a central “configuration” folder. For options on how to execute Radioplan with
an alternative configuration folder please refer also to Section 2.5.

In previous versions of Radioplan (“WiNeS” up to version


3.6) the *.INI files were stored on a different location. In
WiNeS 3.7 the location has changed and all configuration
files are located in a central configuration folder.

The syntax of all *.INI files is compliant with the well known INI files from the Windows
operating system. Therefore, a semi-colon (;) can be used to declare a line as comment.

Radioplan supports UNC path names. Thus, any directory


can be specified in the *.INI files by
\\server\share\pathname. The requirement to use 3
backslashes instead of two in WiNeS 3.6 or previous
versions is not relevant anymore. However, Radioplan
automatically translates these pathnames in order to
ensure backward compatibility.

4.1 Configuration Folder Structure


The configuration folder and file structure has been re-organized in Radioplan (“WiNeS”)
3.7 and it is shown in the table below.

Table 4-1. Configuration folder and file structure

Folder and File(s) Description


\defaultparameters.ini File contains all parameters used by network
elements including data type and range checking
settings.
\monitoring.ini File contains monitoring settings used by the
simulation module.
\optimization.ini Default settings for the optimization module. When
a project is opened these settings are copied into
the project. The user can manually import and
export optimization settings to and from projects,
i.e. it is possible to reset the optimization settings
by manually re-loading this file.
\resultparameters.ini Results generated by the simulation module, see
[R-SIM]. In the file it is defined which parameter
relates to which category (shown as sub-folders in
the Results tab tree).

www.actix.com
Actix Radioplan Administration Guide Configuration and Customization 28

Folder and File(s) Description


\resultparameters_ Results generated by the measurement data import
measurements.ini plugins. In the file it is defined which parameter
relates to which category (shown as sub-folders in
the Results tab tree).
\resultparameterstrans.ini File that contains information which parameter
names shall be translated into a newer naming
convention. In this way, it is avoided that old
parameter names are shown.
\UMRequirements.ini User management requirements that map a user
rights level to a feature in Radioplan, see also
Section 4.3.
\UMRights.ini User rights definitions that map a user rights level
to a user in Radioplan, see also Section 4.3.
\wines.ini Main Radioplan configuration settings file, see also
Section 4.2.
\winesafp.xml Default settings for the miniAFP module.
\winesinterferencematrix.ini Default settings for the creation of an interference
matrix.
\winesmeas.ini Default settings for the measurement module and
pathloss tuning, refer also to [R-Meas].
\winesremote.ini Default settings for remote simulations as used by
the simulation module, refer also to [R-SIM].
\legend.ini Default legend settings for “factory defaults” that
shall be available for all users. This file is not
installed by default, but it can be copied into the
configuration folder afterwards. Please refer to
Section 4.7 for further details.
\winesworkspace.ini Default workspace settings for “factory defaults”
that shall be available for all users. This file is not
installed by default, but it can be created by
Radioplan and can be copied into the configuration
folder afterwards. Please refer to Section 4.7 for
further details.
\coordinatesystems\wkt.ini Definition of all coordinate systems supported by
Radioplan. If a user-specific coordinate system shall
be added, a further WKT*.INI file can be copied into
that directory.
\license\license.ini License configuration settings file, see also Chapter
3.
\optimization\*.ini Folder for further (optional) optimization settings
templates. Such templates are .INI files and have
the same format as optimization.ini. They can be
simply copied into that directory by an
administrator and/or they will be automatically
generated if a user presses the “save” button in the
optimization wizard. The latter option is subject to
permissions which can be set in the user rights
settings.

www.actix.com
Actix Radioplan Administration Guide Configuration and Customization 29

Folder and File(s) Description


\plugins\importresults\*.ini Default configuration settings files for measurement
data plugins, see also [R-Meas]. Each *.INI file
relates to a plugin DLL stored in
%APPDATA%\plugins\importresults\.
\plugins\resultanalysis\*.ini Default configuration settings for result analysis
plugins. Each *.INI file relates to a plugin DLL
stored in %APPDATA%\plugins\resultanalysis\.
\plugins\rnpintegration\*.ini Default configuration settings for planning tool
adapters. Each *.INI file relates to a plugin DLL
stored in %APPDATA%\plugins\rnpintegration\.

4.2 General Configuration Options – WINES.INI


The WINES.INI file is used to configure the following general connectivity settings:

Location of the shared file system (“BinDataDir”),

Location where temporary files i.e. cached matrices shall be stored


(“TempDataDir”),

Location where user workspace and legend settings shall be stored and
automatically reloaded upon application startup (“WINESHome”),

Settings about user rights management and personal folders in Radioplan.


WINES.INI is stored in the configuration folder under configuration\wines.ini. For options
on how to customize the location of the configuration folder, refer to Section 2.5.
For all folders it is possible to use placeholders for various path settings. The following
placeholders will replace the variable with the respective path name:

If a %ApplicationPath% string is found in a path name, it is automatically


converted into the application path of the application including the trailing
backslash, e.g. C:\Program Files\Actix\Radioplan\<version>\ .

The %APPDATA% placeholder is automatically replaced by the path name as


defined in Section 2.4.

The %WINESHOME% placeholder is automatically replaced by the user‟s personal


data folder. The default setting is described in Section 2.4, however it can be
defined in WINES.INI or via an environment variable (see below).

The following table describes all options available in WINES.INI in detail:

www.actix.com
Actix Radioplan Administration Guide Configuration and Customization 30

Table 4-2. Available Parameters in WINES.INI

Parameter or Description
Section
[General]
This is the section where the type of the SQL database can be configured.
SQLProvider Database: The database settings are parsed from the [Database]
section. This option must be used if Radioplan shall connect to a
JET MDB database (dbwines.mdb per default). This is also the
default setting after a new installation of Radioplan.
Oracle: The database settings are parsed from the [Oracle]
section. This option must be used if Radioplan shall connect to a
central Oracle SQL server.
[Database]
This section contains options for a JET MDB database connection.
AskForMDBOnStart 0: Radioplan uses the connect string and the BinDataDir folder for
the shared file system. This is the default setting.
1: Radioplan asks the user during application startup for a *.MDB
file where the application shall connect to. If the user selects a
MDB file and confirms the dialog with OK, the BinDataDir
pathname is also set to the folder where the chosen MDB file is
located. All binary data is then read and stored into local sub-
folders under the folder where the MDB file is located.
ConfirmDatabase 1: In case the application has been updated and an older
Update database is found, the user has to confirm that the database
schema is updated to the latest version. If the user does not
confirm it, the application will be closed. Note that older versions
of Radioplan („WiNeS”) cannot access a database having a newer
schema, and a database update cannot be reverted. Please make
a copy of the original MDB file including subfolders if you want to
use the old database schema. This option is on by default.
0: The user does not have to confirm a database update and the
schema update is done immediately. It is not recommended to
use this option.
CursorLocation “Client”: The ADO cursor location is a client cursor. This is always
the recommended option for MDB files because of the better
performance and stability compared with server side cursors.
“Server”: The ADO cursor location is set to a server side cursor.
This option is not recommended.
ConnectionString This is the connect string for the MDB file. Radioplan uses the JET
OLEDB driver for Access 4.0, and the default string is
"Provider=Microsoft.Jet.OLEDB.4.0;Data
Source=%APPDATA%db\dbwines.mdb;Persist Security
Info=False". On local installations the DBWINES.MDB file is stored
in a sub-folder ~\db\ under the main application data installation
folder (=%APPDATA%\db). If the database shall be shared in a
workgroup, the dbwines.mdb file must be copied onto a shared
file server and the “Data Source” path name must be configured
accordingly. The %APPLICATIONPATH%, %APPDATA, and
%WINESHOME% placeholder are automatically replaced by the
respective folder names.

www.actix.com
Actix Radioplan Administration Guide Configuration and Customization 31

Parameter or Description
Section
BinDataDir This is the folder where the binary files shall be stored. Radioplan
does not store all large binary files such as pathloss matrices,
clutter maps etc in the database itself. These files are stored in a
hierarchical folder structure grouped by Radioplan projects where
the main folder name is the primary key of the project. For MDB
connections it is recommended to store the binary files in the
same folder (i.e. in subfolders) of the directory where the
dbwines.mdb file is stored. The %APPLICATIONPATH%,
%APPDATA, and %WINESHOME% placeholder are automatically
replaced by the respective folder names.
AutoCompact JET MDB files cannot exceed a file size of 2GB. Radioplan
DatabaseThreshold automatically compresses an MDB file if the file size exceeds the
_MBytes given threshold and no other user is currently connected to the
database. The default value for this threshold is set to 1800
MBytes. If this feature shall be deactivated, please set the
threshold to a value of > 2048 MBytes.
MaxLocksPerFile Due to compatibility reasons with old Netware file servers JET only
locks a maximum of 9500 pages per default. This can lead to
errors if a larger portion of the database must be temporarily
locked. It is recommended to set this value to 60000 to avoid this
problem.
TransactionCommit In JET 3.5 Microsoft has introduced an asynchronous mode that
Mode shall increase the all over performance. However, to enforce an
immediate write of changes to the database the
TransactionCommitMode must be set to 1. This yields in a
significantly higher stability of the database connection in
environments where multiple users connect to the same database
concurrently.
LockDelay In case the database is locked, JET waits a certain period of time
until the next write attempt is executed. The default value is 64
ms, but it is recommended to set it to 250 ms for Radioplan. If
the parameter is configured, the parameter is automatically
adjusted by +/-20% of the given value in order to minimise dead
locks with other sessions using the same value.
LockRetry In case the database is locked, JET retries to write the data to the
database n times, where n is configurable by this parameter. The
default JET value is 14, but it is recommended to set it to 40 for
Radioplan. The database raises a concurrency error if the
database is locked for time period of LockDelay * LockRetry.
[Oracle]
This section contains options for an Oracle database connection.
CursorLocation “Server”: The ADO cursor location is set to a server side cursor.
This setting is the only supported option for Oracle connections.

www.actix.com
Actix Radioplan Administration Guide Configuration and Customization 32

Parameter or Description
Section
ConnectionString This is the connect string for the Oracle database connection.
Radioplan uses the Oracle OLEDB drivers, which must be installed
with the Oracle Client on the application server, see also Section
2.7. The default connect string is "Provider=OraOLEDB.Oracle;
Data Source=WINES; User Id=USERID; Password=PASSWORD".
It is necessary to replace the “WINES” placeholder by the
database name as configured in TNSNAMES.ORA, the USERID by
the user name and PASSWORD by the password that shall be
used to connect to the Oracle database.
BinDataDir The BinDataDir is used to tell Radioplan where the binary files
shall be stored on a central file server. Since Radioplan does not
store the large binary files within the Oracle database, this setting
is mandatory. The administrator has to make sure that the given
folder for the binary files is consistent with the Oracle database,
which Radioplan is connected to.
[WCC]
This section contains various options to configure the default behavior of the application.
UserManagement 1: User rights management is enabled. This is the default option.
By using this option users can only access their own projects.
Identity management is realized by the NT login name of the user.
0: User rights management is disabled. This option can be
temporarily activated if an administrator or a user shall get access
granted to project, which are not their own.
DefaultUserLevel Radioplan supports user rights level management where certain
functions can be enabled or disabled depending on a given user
rights level, see also Section 4.3. The default value is 3, but it is
recommended to set it to 1 in central server installations and only
grant super users a higher user rights level e.g. 3, and
administrators a user rights level of 5.
CreatePersonal 1: A personal folder is automatically created if it does not already
Folder exist and new or imported projects are automatically stored in this
folder. This is the recommended option, because it helps to
organize projects in an easy way if many users are sharing a
single database. Note that this project folder management is
managed by the SQL database and it does not have an effect on
the folder structure that is created in the BinDataDir.
0: No personal folder in the Radioplan project tree is automatically
created if a user imports a new project from a planning tool or
creates a new one in Radioplan.
LibDir This folder specifies a directory, where default user equipment,
service and mobility profiles are available. It is not recommended
to change the default settings of this folder
("%ApplicationPath%\library") unless the supplier of the software
has provided an alternative library within an integration project.

www.actix.com
Actix Radioplan Administration Guide Configuration and Customization 33

Parameter or Description
Section
WINESHome Certain user specific workspace and legend settings need to be
stored and reloaded from a personal directory.
By using the WINESHome parameter it is possible to define an
alternative personal folder, for instance a personal home directory
that is mounted via a shared network drive. For example, if drive
H:\ is mounted to the user‟s home directory, the WINESHome
parameter can be set to “H:\”.
See also sections 2.4 and 4.7.
TempDataDir Radioplan has to store certain temporary files in a directory, e.g.
while a network optimization task is performed. Per default the
%TEMP% directory is used, which is typically defined as
“c:\documents and settings\username\local settings\temp”.
However, it is recommended to configure this path to a folder
where at least 16 GBytes of free disk space are available on
central server installations. It is also highly recommended to use a
local disk drive for the storage of temporary files instead of a
shared network drive, because the performance of the system is
much better if temporary files are stored locally.
In case of a termination of the application some temp files may
still reside in the temp folder. It is recommended to automatically
cleanup this folder while the system is rebooted, or to use the
Radioplan function “Tools->Database->Delete Temporary Files”
(user requires user rights level 5!). Temp Files created by
Radioplan always begin with the prefix “RP”, e.g. RP1234.TMP.
EnableBmpMenus 1: Radioplan shows Bitmap Menus per default. This is the
recommended option.
0: Radioplan does not show any Bitmap Menus. The parameter
has been introduced for old NT 4.0 server systems where
problems were occurring under Citrix, but for Windows Server
2003 this issue is not happening anymore.
ImportAnalysis 0: Radioplan imports simulation results for the entire area and not
AreaResultsOnly restriction to the analysis area applies. This is the recommended
option.
1: Radioplan imports only simulation results for the area that is
given by the analysis area.
[WCCMultiLanguage]
This section can be used to define an alternative code page and an alternative default
font.
DefaultFont An alternative default font for the user front-end can be specified.
The default value is “Arial”.
DefaultCharSet An alternative default character set can be specified. The default
value is 0 (ANSI).
[Simulator]
This section defines some Simulator specific settings. It is only required to modify this
section if the simulation module is licensed.
ExecFile This is the command line that is used to launch the Java
simulator. The default setting is “java.exe -Xmx512m -jar
wines.jar". In some cases it is useful to configure the max. heap
size that the Java process can use, e.g. –Xmx1024m if one GB of
heap shall be allocatable.

www.actix.com
Actix Radioplan Administration Guide Configuration and Customization 34

Parameter or Description
Section
ExecDir This is the folder where the wines.jar file (the simulator) is
installed. The default setting is “%APPDATA%simulator".
DataDir This is the folder where the simulator reads the project data and
stores temporary results. The default setting is
"%APPDATA%simdata".
BackupDir If Backup=1 (see below) the application always performs a
backup of the latest project incl. results that are available into a
backup folder. The default setting is "%APPDATA%backup".
Backup 0: No backup of the latest project is performed. This is the default
value.
1: A backup into the BackupDir folder is performed before a new
simulation is started.
Priority This is the NT process priority level that defines with which
priority the Java process is started in relation to the priority level
of the Radioplan application. -1 means
PRIORITY_BELOW_NORMAL which is the recommended default
setting.
AutoImport 1: The results are automatically loaded into Radioplan after the
simulation has been finished or the Java process has been
terminated (e.g. user pressed the Stop button). This is the default
setting.
0: The simulation results will not be automatically loaded into
Radioplan.

4.3 User Rights Management – UMRights.INI and


UMRequirements.INI
User rights management is a powerful method to grant different groups of users access to
an advanced or a restricted set of functions available in Radioplan. The principle is that
every user or user group has a given user rights level configurable in UMRights.INI. The
minimum required user rights level that is required to access a certain function in
Radioplan can be configured in UMRequirements.INI. In general, a higher user rights level
always allows the user to access more functions available in Radioplan. Both UMRights.INI
and UMRequirements.INI are stored in the configuration folder under
~\configuration\*.INI.
The default user rights level for all users not explicitly configured in UMRights.INI can be
configured in WINES.INI, see also Section 4.1.
In the UMRights.INI file, there exist two types of options on how user-specific user rights
levels can be configured:
In Section [WCC] user login names can be added with a given user rights level, for example
userxyz=3. Radioplan will use the user rights level 3 then for the user userxyz.
In Section [WCCNTGroups] it is possible to grant a group of users a given user rights level
when NT security groups are used. A local user group can be added in this section, for
example, ntgroupxyz=3. A domain user group can be added as
domainntgroupxyz=domain\ntgroupxyz.
The user rights in UMRequirements.INI are pre-configured for 4 standard user levels:

www.actix.com
Actix Radioplan Administration Guide Configuration and Customization 35

Table 4-3 Available user levels

User Level User Class Description


1 Standard User The configuration dialogs are reduced to a minimum.
Quick and easy usage in daily work is ensured.
2 Advanced User Additional configuration options are offered that
enable a usage of Radioplan for advanced tasks.
3 Power User The entire complexity of the configuration dialogs is
available. The complete range of Radioplan‟s
capabilities can be exploited.
5 Admin User Admin users have some specific additional
permissions, see notes below

The user rights level=5 has a specific meaning in Radioplan. It is reserved for admin users,
and it grants such users the following additional privileges:

Delete Temporary files with the Radioplan function Tools->Database->Delete


Temporary Files…

The number of users currently connected to a floating network license manager is


shown in the About Dialog (Help  About Radioplan)

Admin Users can access ALL projects irrespectively of the project‟s owner settings.

4.4 Simulation Configuration


The WiNeS Network Simulator can be configured by several *.ini files. They are located in
the %APPDATA%\configuration directory. More details on the simulation configuration can
be found in [R-SIM].

4.5 Optimization Engine Configuration


The optimization engine of the Network Optimization Module takes a list of parameters,
whose default values can be specified in the optimization.ini file. It contains several
sections concerning pixel resolution settings, parameter ranges, and optimization
algorithm configuration. More information on the default configuration of the optimization
engine is given in [R-ACP].

4.6 Customization of Plugins


Radioplan supports various plugins that enhance the functionality of the application.
Various plugins are delivered with the application per default, but also customer specific
plugins are available for certain customers. In order to add a plugin to the system, the
administrator has to copy the DLL plugin file and (optionally) a *.INI file into the
installation.
The following table summarizes the locations where plugin DLLs and related INI files are
stored. For details about the contents in the configuration folder, refer to Section 2.4. For
options on how to configure a customized location for the configuration folder, see Section
2.6.

www.actix.com
Actix Radioplan Administration Guide Configuration and Customization 36

Table 4-4. Plugin types and storage locations for DLL and configuration settings files

Plugin Type Storage location for plugin and related INI file
Measurement Data Plugins (*.DLL files):
Import Plugins %ApplicationPath%\plugins\importresults\
Configuration settings (*.INI files):
%APPDATA%\configuration\plugins\importresults\
More information on these *.ini files is given in [R-Meas].
Result Analysis Plugins (*.DLL files):
Plugins %ApplicationPath%\plugins\resultanalysis\
Configuration settings (*.INI files):
%APPDATA%\configuration\plugins\resultanalysis\
Planning Tool Plugins (*.DLL files):
Adapters %ApplicationPath%\plugins\rnpintegration\
Configuration settings (*.INI files):
%APPDATA%\configuration\plugins\rnpintegration\

4.7 Customization of Legend Presets and the User Workspace


Radioplan supports the definition of default legends for surface plots as well as workspace
settings that shall be available for all users by default. Additionally, the users can adjust
their legend and workspace settings.
Legends can be graphically configured in Radioplan by the Legend Presets functions that
are available in the Customize Legend Colors dialog. This dialog can be opened by clicking
on a legend.
The workspace is the conglomeration of all properties that affect the appearance of the
graphical elements in the viewing area. In particular, it contains:

general surface plot settings as defined in Tools  General Settings,

display settings as defined in Tools  Display Settings, and

individual layer templates as defined in the Layer Settings and listed by selecting
as defined in Tools  User Settings  Manage Layer Templates… .
The legends that have been defined in the Radioplan application, can be exported into a
legend.ini file by the menu entry Tools  User Settings  Export Legend Presets… .
Likewise, the workspace settings as defined in the Radioplan application, can be exported
into a winesworkspace.ini file by the menu entry Tools  User Settings  Export
Workspace… .
Depending on where these *.ini files are stored, they constitute the installation defaults
or the user-specific settings, which may overwrite the defaults. The principles how these
*.ini files are loaded and automatically saved by the Radioplan application are described
in the following.
When Radioplan is shut down, all legend presets and workspace settings – including any
user specific adjustments – are automatically saved to a legend.ini file and a
winesworkspace.ini file in the applicable Radioplan user folder, which is:

www.actix.com
Actix Radioplan Administration Guide Configuration and Customization 37

the WINESHOME path defined in the wines.ini file, which is located in the Radioplan
configuration folder (refer to section 2.4);

if the WINESHOME path is not defined in the wines.ini file:


the WINESHOME path defined as Windows environment variable;

if no WINESHOME path is defined at all:


the
Documents and Settings\<username>\Application Data\Actix\Radioplan\
folder (see also section 2.4).
Accordingly, on start of Radioplan, the system tries to read legend presets and workspace
settings from legend.ini and winesworkspace.ini files, which may be located at one or
more different locations. The order of their consideration is specified in Table 4-5.

Table 4-5 Order of legend preset and workspace import on start of Radioplan

Order Checked Location Comment


1 the Radioplan A central definition is always loaded during
configuration folder Radioplan startup. If the *.ini files do not exist at
(see section 2.4) this location, Radioplan-internal factory defaults
apply.
This central definition can be overridden by
consecutively loaded files with user-specific
workspace settings.
2 WINESHOME path as defined In the wines.ini file, WINESHOME may define the
in the wines.ini file location of user-specific Radioplan settings.
If it is defined and the *.ini files are found there,
the central definition is overridden by that.
3 %WINESHOME%\ A Windows environment variable WINESHOME can be
created to define the location of user-specific
Radioplan settings.
If step 2 was not successful, but this variable is
defined and the *.ini files are found there, the
central definition is overridden by that.
4 Documents and Settings\ If neither step 2 nor 3 were successful, Radioplan
<username>\ tries to load the legend.ini and
Application Data\ winesworkspace.ini files from this location.
Actix\Radioplan\
This option might not work if Radioplan is run on a
remote server (e.g. Citrix server).

www.actix.com
Actix Radioplan Administration Guide Configuration and Customization 38

www.actix.com
Actix Radioplan Administration Guide References 39

5 References

[R-ACP] Actix Radioplan. Automatic Cell Planning (ACP) Guide. Version 3.12. Actix
GmbH, Dresden, Germany, 2009.

[R-ASM] Actix Radioplan. Atoll™ Synchronization Module (ASM) Guide. Version


3.12. Actix GmbH, Dresden, Germany, 2009.

[R-Meas] Actix Radioplan. Measurements Guide. Version 3.12. Actix GmbH,


Dresden, Germany, 2009.

[R-SIM] Actix Radioplan. WiNeS Simulation Module. Version 3.12. Actix GmbH,
Dresden, Germany, 2008.

[R-UG] Actix Radioplan. User Guide. Version 3.12. Actix GmbH, Dresden,
Germany, 2009.

www.actix.com
Actix Radioplan Administration Guide References 40

www.actix.com

You might also like