Professional Documents
Culture Documents
Administration Guide
Version 3.12
www.actix.com
Documentation Version: Admin-v3.12, June 2009
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.
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
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.
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
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.
Windows XP 64 bits
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
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.
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‟.
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
If a Radioplan of the same release version is already installed on this computer, a dialog
appears allows the user to
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
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.
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
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.
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
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
The following table details which directories are created within the folders summarized
above:
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
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
www.actix.com
Actix Radioplan Administration Guide Installing the Radioplan Client Application 15
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.
www.actix.com
Actix Radioplan Administration Guide Installing the Radioplan Client Application 16
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
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:
www.actix.com
Actix Radioplan Administration Guide Dongle Support and License Management 20
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
www.actix.com
Actix Radioplan Administration Guide Dongle Support and License Management 22
Select the option “Run as Service” and press the Start button to restart the server
as a service.
www.actix.com
Actix Radioplan Administration Guide Dongle Support and License Management 23
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 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.
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.
username: admin
password: cbnetserver
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
www.actix.com
Actix Radioplan Administration Guide Dongle Support and License Management 26
www.actix.com
Actix Radioplan Administration Guide Configuration and Customization 27
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.
www.actix.com
Actix Radioplan Administration Guide Configuration and Customization 28
www.actix.com
Actix Radioplan Administration Guide Configuration and Customization 29
Location where user workspace and legend settings shall be stored and
automatically reloaded upon application startup (“WINESHome”),
www.actix.com
Actix Radioplan Administration Guide Configuration and Customization 30
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.
www.actix.com
Actix Radioplan Administration Guide Configuration and Customization 35
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:
Admin Users can access ALL projects irrespectively of the project‟s owner settings.
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\
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);
Table 4-5 Order of legend preset and workspace import on start of Radioplan
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-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