data manager administrator guide - infovistawebhelp.infovista.com/planet/62/content/pdfs/data... ·...

Planet 6.2

Data Manager Administrator Guide

Copyright © 2017

InfoVista S.A.S. All rights reserved.

Notice

This document contains confidential and proprietary information of InfoVista S.A.S. andmay not be copied, transmitted, stored in a retrieval system, or reproduced in any formator media, in whole or in part, without the prior written consent of InfoVista S.A.S.Information contained in this document supersedes that found in any previous manuals,guides, specifications data sheets, or other information that may have been provided ormade available to the user. This document is provided for informational purposes only, andInfoVista S.A.S. does not warrant or guarantee the accuracy, adequacy, quality, validity,completeness or suitability for any purpose the information contained in this document.INFOVISTA S.A.S. may update, improve, and enhance this document and the products towhich it relates at any time without prior notice to the user. INFOVISTA S.A.S. MAKES NOWARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OFMERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THISDOCUMENT OR THE INFORMATION CONTAINED HEREIN.

Trademark Acknowledgement

Planet is a trademark owned by InfoVista S.A.S. MapInfo Professional and the SpectrumSuite are registered trademarks of Pitney Bowes Software Inc. Map data copyrightOpenStreetMap contributors, CC BY-SA. RF-vu is a trademark owned by iBwave. Thisdocument may contain other trademarks, trade names, or service marks of otherorganizations, each of which is the property of its respective owner.

Last updated Friday, April 21, 2017

Contents Planet 6.2 1

Data Manager Administrator Guide 1Contents i

CHAPTER 1Introduction 1Features of Data Manager 2Understanding the Data Manager network configuration 3Centralize data 3Collaborate with others 3Manage access 3The Data Manager configuration 4Data Manager 5Data Manager Server 6Data Manager Server Console 6File Server folder 6

CHAPTER 2Installation 9Installing and configuring Data Manager Server 11System requirements for Data Manager Server 13Operating system 13Hardware and disk space 13Network access 13File Server folder requirements 14System platform compatibility 15Installing Data Manager Server and the Data Manager Server Console 16Migrating from previous versions 19Migrating projects in a multi-user environment 21Considerations when migrating projects 21Methods for migrating projects 22Workflow examples 23

CHAPTER 3Setup 27Managing Data Manager Servers 28

Starting and stopping Data Manager Servers 31Connecting to and disconnecting from Data Manager Servers 32Configuring and viewing logs 33Changing the location of the File Server folder 35Controlling permissions 37Defining Data Manager Server connection limits 40Backing up and restoring Data Manager projects and settings 42

CHAPTER 4Basic Usage 45Understanding permissions 46Project permissions 46Type permissions 47File permissions 48Controlling permissions 63Creating user and group accounts 66Importing Windows user accounts and groups 70Accepting and denying user connections 72Disconnecting Data Manager users 73Configuring project folders 74Configuring the import and export of network data with Xeda 77Mapping data 77Specifying shared custom data definitions 81Releasing locked project data 84

APPENDIX AImport/Export Command-Line Utility 85Using the IECON utility 86Syntax 87The IECON lexicon 102Parameters 103Optional Parameters 104

APPENDIX BData Manager Command-Line Utility 107Using the Data Manager Command-Line Utility 108

CONTENTS│DataManagerAdministratorGuide

CHAPTER1 Introduction

The Data Manager provides multi-user collaboration and centralizedproject management. It is a sophisticated document database systemfor project collaboration.

This chapter covers the following topics:

Features of Data Manager 2

Understanding the Data Manager network configuration 3

Centralize data 3

Collaborate with others 3

Manage access 3

The Data Manager configuration 4

Data Manager 5

Data Manager Server 6

Data Manager Server Console 6

File Server folder 6

Features of Data ManagerThe Data Manager enables you to store data centrally and manage projects moreefficiently. This greatly facilitates project collaboration and data sharing. Keyfeatures of the Data Manager are listed in the table below.

Feature Description

Data Centralization

n Data centralization of all required filesfor project creation enabling end-usersto easily re-create local Planet projects

n Ability to import up-to-date projectconfiguration data from the networkwhen using Xeda

n Management of severalprojects/markets using a single DataManager Server

n API for integration of third-partysystems with the Data Manager Server

Multi-User Collaboration

n Multi-user conflict resolutionn Data locking, enabling specific filesand/or records to be "checked out" byan end-user in order to avoid possiblemulti-user conflicts

n Data filtering, enabling large datasetsto be divided into smaller logicalsubsets

n Partial Get feature enables users tomodify and update specific sites basedon defined filters

n Multi-user change tracking

Permission Management

n Domain or login/password basedauthentication

n Advanced permission management(i.e., user groups and individual userpermissions)

n Per project data extensibility, allowingmanagement of additional fields inPlanet

n Per project user access permissions

IT and Administration

n Support for physical servers, virtualservers and cloud deployment

n 64-bit Windows server compatiblen Fully multi-threaded for large scaleimplementations (e.g., more than 500end-users)

DataManagerAdministratorGuide│2

Understanding the Data Manager network configurationThe Planet Data Manager feature extends the capabilities of Planet for multi-usercollaborative network planning and optimization work. With Data Manager, you canimplement workgroup best practices that ensure a higher level of quality in the workdone as errors are avoided. In addition:

n any number of users can work on a project simultaneously.n users can get up-to-date project data from Data Manager and then disconnectand continue working.

n project data can be held in a secure central location that is routinely backedup.

n a visual cue notifies users when project data on the server has changed sothat they can synchronize a local project with the updated project on theserver.

Centralize dataProjects are stored in a central location accessible to all users. Instead of arelational database, a document database is used whereby Data Manager storesinformation using a flat data structure, which simplifies data storage and improvesperformance. This means that a database software (SQL or Oracle) is no longerneeded. This makes Data Manager Server quick and easy to install and configure.

To work on a project, a Planet user retrieves a copy from the Data Manager so thathe or she can work on it locally on their workstation. Each user designs, analyzes,and optimizes their network design and once they are satisfied with the results,changes are uploaded to Data Manager.

Collaborate with othersUsing Data Manager, multiple Planet users can store and access common projectdata from a secure location.

Manage accessUsing the Data Manager Server Console, the Data Manager Administrator controlsproject access as well as file updates. The figure below illustrates how the DataManager solution could be implemented in the workplace. The diagram shows twoData Manager Server Consoles that are used to manage a Data Manager Server. RFEngineers from Regions 1 and 2, who are Planet users, access Data Manager fromwithin Planet to retrieve and store project data.

CHAPTER 1│DataManagerAdministratorGuide

Figure 1: Data Manager network configuration

The Data Manager configurationA Data Manager network configuration consists of:

n a Data Manager Server, which connects to a File Server foldern one or more Data Manager Server Consolesn Planet users

Planet users connect to Data Manager from within Planet and can add, update, orview project data depending on their assigned permissions. The figure belowillustrates a Data Manager network configuration. Each Planet user accesses theData Manager service and File Server service in order to work with data and projectfiles saved in the File Server folder.


Figure 2: Illustration of Data Manager implementation

Note: You can install multiple Data Manager Servers. Each will have its own FileServer folder.

Planet data management comprises the following software elements:

n Data Manager (installed on the each user's workstation as part of Planet)n Data Manager Server (installed as a two services on the server)n Data Manager Server Console (installed on the network)n File Server Folder

Data ManagerFor Planet users who will be working with Data Manager, it is installed as part ofPlanet and is accessed from the Data tab. Using Data Manager, multiple Planet userscan perform the following tasks:


n update their Planet projects with changes made by other usersn lock or unlock project data (locking prevents other users from modifying thedata in Data Manager)

n submit modified project data to Data Managern filter the data shown in the Data Manager tree view to display only a subsetn view details of individual project items, the lock status of items, and the dateand time of the last update

n compare the values in the Planet project currently open and the values storedin Data Manager

Data Manager ServerThe Data Manager Server, which consists of the Data Manager Server service, linksPlanet users and the File Server folder. Planet users connect to a Data ManagerServer and can add, update, or view project data depending on their assignedpermissions.

Data Manager Server ConsoleUsing the Data Manager Console, the Data Manager Administrator can managemultiple Data Manager Servers from a central location. Using the Console, theAdministrator can perform tasks such as

n adding, modifying, and deleting users and groupsn defining project and user permissionsn creating folders for Planet users to store project datan defining connection limitsn monitoring servers

You can install Data Manager Server Console on the same computer as a DataManager Server or on its own.

File Server folderWithin the File Server folder, data files and project files are stored. The File Serverfolder can be on a local drive (e.g., c:\FileServerFolderLocal) or on a network (e.g.,\\131.104.156.200\FileServerFolder). Mapped drives cannot be used.

Best Practice: For the best performance, configure the File Server folder to beon the local drive where the Data Manager Server is installed.

Data files stored in the File Server folder include:

n the project (.planet) filen data (.datx) files

Project files stored in the File Server folder include:

n grid files (.grd files and associated .tab files)n workspace files (.wor files)n analysis files (.grd and .grc files and associated .tab files)


n .xml filesn antenna files (.paf and pafx files)n curve files (.curve files)n link budget files (.dpl files)n propagation model files (.pmf files)n project files (.planet files)n attachments (any files in the Attachments folder)n other settings files (such as color or class profiles)


CHAPTER2 Installation

You can use Planet in a standalone mode where a single user installsthe software with no connection to a data store or links to a network.This allows the most freedom to the end user and is suitable forindependent projects where multi-user collaboration is not necessary.

If you are working in a multi-user environment, typically multipleinstallations of the Planet application are installed on clientworkstations, similar to the standalone mode; however, the embeddedData Manager application is used for multi-user collaboration. The DataManager Server is installed and connected to in order to centrally storeand synchronize data from the workstations.


Installing and configuring Data Manager Server 11

System requirements for Data Manager Server 13

Operating system 13

Hardware and disk space 13

Network access 13

File Server folder requirements 14

System platform compatibility 15

Installing Data Manager Server and the Data ManagerServer Console 16

Migrating from previous versions 19

Migrating projects in a multi-user environment 21

Considerations when migrating projects 21

Methods for migrating projects 22

Workflow examples 23


Installing and configuring Data Manager ServerThe Data Manager Server simple install enables you to quickly set up a multi-userenvironment for network planners and designers who use Planet by following these7 steps. Note that a database software (SQL or Oracle) is no longer needed.

STEP 1

Contact your regional Customer Support Center to obtain the password required todownload the software. Ensure you have a valid Product Identification (PID)number.

STEP 2Verify the system requirements.

See "System requirements".

STEP 3Download the software from the InfoVista web site.

STEP 4Create a File Server folder for data file and project file storage.

See "File Server folder requirements".

STEP 5Step through the pages of the Installation Wizard to install the Data ManagerServer and the Data Manager Server Console.

See “Installing Data Manager Server and the Data Manager Server Console”.


http://www.infovista.com/

STEP 6Configure the Data Manager Server Console.

See “Managing Data Manager Servers”.

STEP 7Define user, group, and project permissions.

See "Understanding permissions", "Creating user and group accounts", and"Working with project folders"


System requirements for Data Manager ServerThis section describes system requirements for Data Manager Server, including theserver operating system, hardware and disk space, network access, and file serverfolder requirements.

Data Manager Server runs on the Microsoft .NET framework (version 4.6.1). If youdo not have this software installed on your computer, you must download and installit from the Microsoft web site.

Operating systemYou can install Data Manager Server on any of the following 64-bit operatingsystems:

n Windows Server 2008, 2012, 2016n Windows Vistan Window 7n Windows 8.1n Windows 10

See "System platform compatibility".

Note: It is recommended that you set the system locale to “English (UnitedStates)”.

Warning: Some Automatic Updates can cause the computer to reboot, whichmay interrupt operations in Data Manager Server. It is recommended that youmodify the Automatic Updates settings so that they are not done automatically.

Hardware and disk spaceHardware and disk space requirements will vary considerably depending on thenumber of Planet users and projects and the types of data being stored.

Note: For specific system requirements, contact Customer Support.

Network accessTo store Planet project data, each Data Manager Server requires network access toa File Server folder (although the file server folder can also be created on a localdrive). Each Data Manager Server Console requires network access to the DataManager Servers that you want to manage.

If you are using a firewall, you must do one of the following:


http://www.infovista.com/services/customer-support/wireless-products

n Turn the firewall software off.n In your firewall software, define DataManagerServer.exe as a trustedapplication.

n In your firewall software, open the port through which Data Manager Servercommunicates with the network. By default, this is 7878.

See your firewall software documentation for details.

File Server folder requirementsTo configure Data Manager Server, you must have access to a designated FileServer folder on the local drive (e.g., c:\FileServerFolder\Local) or on the network(e.g., \\131.104.156.200\FileServerFolder). Mapped drives cannot be used. WhenData Manager users check in or submit Planet project data, Data Manager Servercreates a folder structure for storing the project files. Project folders are identifiedwith a unique number.

Warning: If the File Server folder and the Data Manager Server are on differentcomputers, you must ensure that the Data Manager Server is assigned an accountand password that are valid on the computer on which the File Server folder islocated.


System platform compatibilityThe tables below detail the compatibility of Planet with various system platforms.

Table 1Windows workstation compatibility

Platform Planet 6.2

Windows Vista Professional 64-bits* √

Windows 7 Professional 64-bits √

Windows 8.1 Professional 64-bits √

Windows 10 Professional √

*partially tested

Table 2Windows server compatibility

Platform Planet 6.2

Windows Server 2003 and 2003 R2 64-bits √

Windows Server 2008 64-bits √

Windows Server 2008 R2 64-bits √


Windows Server 2012 R2 64-bits √



Installing Data Manager Server and the Data Manager ServerConsoleYou can install multiple Data Manager Servers and Data Manager Server Consoles inyour network, but only one of each on any one computer. In order to configure useraccess to Data Manager Servers, you must install at least one Data Manager ServerConsole in your network.

Note: Data Manager Server 6.1 can be installed alongside any other version ofData Manager Server (e.g., Data Manager Server 6.1 and Data Manager Server5.8 can be installed on the same computer). Each Data Manager Server must beconfigured to use its own File Server folder.

Warning: The version of Data Manager Server software that you install mustmatch the version of Planet that the Data Manager users have installed. Forexample, Data Manager Server 6.1 must be used with Planet 6.1.

Warning: Before you begin this procedure, ensure that you are the only user onthe computer and that Planet is not open.

Procedure1. Navigate to the Planet Product Downloads page at http://www.infovista.com.2. On the Product Downloads page, enter the Product ID number indicated in the

email or letter sent to you, and click Submit. Type the product password youreceived from your Customer Support Center in the box beside the version ofPlanet that you want to download and click Submit. Type the product passwordyou received from your Customer Support Center in the box beside theversion of Planet that you want to download and click Submit. Read thedownload instructions and, in the Data Manager Server Installation Files table,click the folder icon in the Single column, and download the program file to atemporary folder on your computer.

3. Double-click the Data Manager Server.exe file.

The Install Wizard opens.

4. On the Welcome page of the Installation Wizard, click Next.5. Read the license agreement and, if you accept the terms of the agreement,

click Yes.6. On the Select Features page, do the following:

n If you want to install Data Manager Server, enable the Data ManagerServer check box.

n If you want to install Data Manager Server Console, enable the DataManager Server Console check box.


http://www.infovista.com/services/customer-support/wireless-products

By default, both options are enabled.

6. In the Destination Folder section, accept the default location, or click Browse,choose the folder in which you want to install the software, and then click OK.

The name of the destination folder must not contain a closing parenthesis.

7. Click Next.

The software is installed. The Adobe Reader software is required to view thePDF versions of the documentation installed with the product.

8. On the Install Complete page, if you want to view the Release Note, enable theYes, I Want to View the Release Note File check box.

9. Click Finish

The Data Manager Configuration Wizard opens if this is the first time you haveinstalled Data Manager Server; otherwise, the Data Manager ConfigurationEditor opens where you can verify the connection parameters.

10. In the Data Manager Configuration Wizard, specify the path to an empty FileServer folder.

11. Do one of the following:n If you are moving from an existing Data Manager installation, enable theMigrate an Existing Data Store check box.

n If you want to create a new data store, clear the check box.12. Click Next.13. Verify the communication ports and click Next.14. Define a user name and password for the Data Manager Administrator.


This user name and password is required whenever a new server is added tothe Data Manager Server Console.

15. Click Finish.16. In the Windows Services, start the Mentum Data Manager service.17. From the Start menu, select Data Manager Server Console.


Migrating from previous versionsConfiguration information (such as the data store name, location, user profiledefinitions, ports in use, etc.) is saved in the ConfigurationSettings.xml file (e.g.,ConfigurationSettings6.1.0.xml). By default, this file is saved in the\ProgramData\Mentum\Data Manager 6.x folder (for Windows 7).

This file contains connection details and credentials. Part of the migration processrequires that you select the configuration settings file for the existing data store (bethat a relational database or document database).

Procedure1. Do one of the following:

n If you are installing Data Manager Server for the first time, in the DataManager Configuration Wizard, follow the prompts to configure the DataManager Server. The Wizard opens when there is noConfigurationSettings6.xml file.

n If you are upgrading to the latest version, in the Data ManagerConfiguration Editor, verify the connection settings. The Editor openswhen there is an existing ConfigurationSettings6.xml file.

2. Specify the File Server folder.

The File Server folder can be a local folder (e.g., c:\FileServerFolderLocal) ora folder on a network (e.g., \\131.104.156.200\fileserver). Mapped drives arenot supported.

3. In either the Wizard or the Editor, do one of the following:n To migrate an existing data store, enable the Migrate an Existing DataStore check box.

n To use a new data store, clear the Migrate an Existing Data Store checkbox.

4. Review default communication ports.5. On the Administrator Login page, specify a user name and password for the

Data Manager Administrator login.6. Click Finish.

If you are migrating an existing data store, the Data Manager Migrator opens.


7. Click the Browse (...) button next to Source Configuration File, and browse tothe ConfigurationSettings.xml file.

8. Do one of the following:n To migrate project data, enable the Migrate Project Data check box.n To migrate Data Manager settings only (e.g., projects, users,permissions, etc), clear the Migrate Project Data check box.

9. Click Finish.


Migrating projects in a multi-user environmentIf you are self-reliant and not working in a collaborative multi-user environmentthen project migration from a previous Planet version is done automatically usingthe Planet Migrator. If, however, you are working in a multi-user environment andusing the Data Manager, it is important to coordinate project migration efforts inorder to ensure that project integrity is maintained. There are, however, manydifferent approaches that you can take. This topic details some of the things toconsider in order to complete a successful migration.

Warning: Ensure a server backup of all projects is made prior to projectmigration. See “Data Manager Backup/Restore Wizard”.

Warning: It is very important the engineers synchronize local and Data Managerprojects prior to the migration.

Considerations when migrating projectsWhen determining the best project migration strategy to use, consider:

n the number of Data Manager serversn the number of Data Manager usersn the number of projects to migrate


Methods for migrating projectsHow projects are migrated in a multi-user environment depends on your work environment and practices. At a very high level, here aresome of the ways that projects can be migrated.

Role Option 1 Option 2 Option 3 Option 4

Administrator Migrates the existing datastore and Data ManagerServer settings using theData ManagerConfiguration tool.

Migrates the existing datastore and Data ManagerServer settings using theData ManagerConfiguration tool.

Creates a new data storeand new Data ManagerServer settings. Re-creates Data Managerfolders and re-configuresusers and permissionsusing the Data ManagerConsole.

Creates a new data storeand migrates serversettings. Data Managersettings are migrated usingthe Data ManagerConfiguration tool.

Engineers Delete their local projectsand then do a fresh Getdownloading a copy of themigrated projects fromData Manager.

Migrate their local projectsby opening them in thelatest version of Planet.They then connect to DataManager and resolve anyconflicts that exist.

Migrate their local projectsby opening them in thelatest version of Planet andthen check the newlymigrated projects into thenew data store using DataManager.

Migrate their local projectsby opening them in thelatest version of Planet andthen check the newlymigrated projects into thenew data store using DataManager.

Option 1 Option 2 Option 3 Option 4

Workflow examplesProject migration options are illustrated in the workflow examples below.

Option 1

Step 1 All engineers connect to the Data Managerand synchronize project data in order toensure that projects stored in DataManager are up-to-date.

Step 2 All engineers log out of and disconnectfrom the Data Manager server.

Step 3 The Data Manager Administrator upgradesthe Data Manager Server and migratesproject data and Data Manager Serversettings. The Data Manager Administratorenables the Migrate an Existing Data Storecheck box in the Configuration tool andmigrates Data Manager settings.

See“Migratingfrompreviousversions”

Step 4 Each engineer installs the latest version ofPlanet.

Step 5 Engineers ensure there are no files withintheir local Planet project that they want tokeep and then delete the local version ofthe project.

Step 6 Each engineer connects to the DataManager and performs a Get on the Planetproject to download a copy from theserver.


Option 2


Step 2 The Data Manager Administrator upgradesthe Data Manager Server and migratesproject data and Data Manager Serversettings. The Data Manager Administratorenables the Migrate an Existing Data Storecheck box in the Configuration tool andmigrates Data Manager settings.


Step 3 Each engineer installs the latest version ofPlanet and then opens and migrates eachproject.

Step 4 Each engineer connects to the DataManager and synchronizes the localproject with the server version stored inData Manager resolving any conflicts thatmay exist.


Option 3

Step 1 All engineers connect to the Data Managerand synchronize project data in order toensure that local projects are up-to-date.


Step 3 The Data Manager Administrator creates anew data store and re-configures theusers, projects, and permissions using theData Manager Server Console.

See“InstallingDataManagerServerand theDataManagerServerConsole”

Step 4 The Data Manager Administrator upgradesData Manager ensuring the MigrateExisting Settings check box in theConfiguration tool is cleared.

Step 5 Each engineer installs the latest version ofPlanet and then opens and submits theproject to Data Manager.


Option 4

Step 1 All engineers connect to the Data Managerand synchronize project data in order toensure that local projects are up-to-date.


Step 3 The Data Manager Administrator creates anew data store.

Step 4 The Data Manager Administrator upgradesData Manager and migrates existing DataManager Server settings ensuring that theMigrate Existing Settings check box in theConfiguration tool is selected.


Step 5 Each engineer installs the latest version ofPlanet and then opens and submits theproject to the Data Manager.


CHAPTER3 Setup

It is important to manage Data Manager Servers effectively in order toensure Planet users have access to the data they need to completetasks successfully.


Managing Data Manager Servers 28

Starting and stopping Data Manager Servers 31

Connecting to and disconnecting from Data ManagerServers 32

Configuring and viewing logs 33

Changing the location of the File Server folder 35

Controlling permissions 37

Defining Data Manager Server connection limits 40

Backing up and restoring Data Manager projects andsettings 42

Managing Data Manager ServersThe Data Manager Server Console enables you to manage multiple Data ManagerServers from a central location. You can add any number of Data Manager Serversto the tree view of the Data Manager Server Console. The figure below shows anexample of the Data Manager Server Console. While there is only one Data Managerserver in this example, you could organize the servers such that the Console is usedto manage two Data Manager Servers: Region 1 Server and Region 2 Server. Addinga Data Manager Server means that the server is registered with the Data ManagerServer Console and is available in the tree view. To perform any managementfunctions on the server, you must connect to it after you add it.

In a network where multiple administrators may be accessing a common set of DataManager Servers simultaneously, messages are displayed in the Log window toindicate when an administrator has logged on or off. If there is a Data ManagerServer installed on the same server as the Data Manager Server Console, it is addedto the tree view by default. You can delete it from the tree view if you do not want tomanage it using the local Data Manager Server Console or you can define thesettings so that it is not added to the tree view automatically.

Figure 1: Data Manager Server Console example

Your network can contain multiple Data Manager Server Consoles, but only one percomputer. Configured servers are automatically added to the tree view; however, if


this is not the case verify that the Log On account used for the Data Manager Serverservice has full security permissions for the Data Store folders.

Procedures

To start the Data Manager Server ConsoleAfter the Data Manager Server has been installed, change the Log On settings for theData Manager Server service to use an account that has the appropriate securitypermissions.

1. On the Windows desktop, right-click My Computer and choose Manage.2. In the Computer Management dialog box, expand Services and Applications,

and select Services.3. Right-click on the Data Manager Server service and choose Properties.4. In the Data Manager Server Properties dialog box, on the General tab, click

Stop to stop the Data Manager Server service.5. On the Log On tab, enable the This Account option, define an account that has

the appropriate security permissions, and click Apply (see the image below).In most cases, a qualified Windows domain username is required, i.e.,[email protected].

6. On the General tab, click Start to restart the Data Manager Server service.7. Open the Data Manager Server Console again.

To add Data Manager ServersAdding a Data Manager Server to the Data Manager Server Console does not changethe status of the Data Manager Server (started or stopped) on the host server. Youview the status of the Data Manager Server on the host server using the Servicesoption of the Windows Administrative Tools.

1. Choose Start > All Programs > Data Manager Server > Data Manager ServerConsole.

The Data Manager Server Console opens. The first time you start the DataManager Server Console, if you have a Data Manager Server installed on thesame machine, it is automatically added to the tree view. You can change thesettings so that the local Data Manager Server is not automatically added tothe tree view.

2. To add another Data Manager Server to the Console, in the tree view, right-click Console Root and choose Add Server.

3. In the Server Registration dialog box, define the server configurationparameters.

This name is used only in the tree view of the Data Manager Server Console toidentify the Data Manager Server.


To edit a Data Manager Server definition1. In the tree view of the Data Manager Server Console, choose Console Root.2. In the right-hand panel, right-click the Data Manager Server for which you

want to edit server details, and choose Modify Server.3. In the Server Registration dialog box, change server details as required, and

click OK.

To delete Data Manager ServersDeleting a Data Manager Server from the Data Manager Server Console does notchange the status of the Data Manager Server on the host server.

1. In the tree view of the Data Manager Server Console, choose Console Root.2. In the right-hand panel, right-click the Data Manager Server that you want to

delete, and choose Delete Server.3. In the confirmation dialog box, click Yes.


Starting and stopping Data Manager ServersYou start and stop a Data Manager Server using the Services option of the WindowsAdministrative Tools on the server on which the Data Manager Server is installed.

Procedures

To stop and start a Data Manager Server1. Choose Start > Control Panel > Administrative Tools > Services.2. Do one of the following:

n To stop Data Manager Server, right-click Data Manager Server andchoose Stop.

n To start Data Manager Server, right-click Data Manager Server andchoose Start.

Tip: You can also start and stop Data Manager Server by right-clicking DataManager Server and choosing Properties. Then, on the General tab, click Stop orStart.

To define Data Manager Server startup settingsYou use the Services option of the Windows Administrative Tools to configure DataManager Server to start automatically or manually when the server starts up.

1. On the server on which the Data Manager Server is installed, choose Start >Control Panel > Administrative Tools > Services.

2. Right-click Data Manager Server and choose Properties.3. In the Data Manager Server Properties dialog box, choose one of the following

from the Startup Type list:n Automaticn Manualn Disabled

4. If the file server folder is installed on a different computer than the DataManager Server, click the Log On tab and ensure that the selected Log On Asaccount has read, write, and modify access to the file server folder.

5. Click OK.


Connecting to and disconnecting from Data Manager ServersYou manage Data Manager servers using the Data Manager Server Console. It isfrom the Console that you manage users, groups, and projects and configure use.Disconnecting from a Data Manager Server means that you cannot manage it usingthe Data Manager Server Console.

Neither connecting to nor disconnecting from a Data Manager Server changes itsstatus (started or stopped) on the host server. If the Data Manager Server is startedon the host server, Planet users will be able to connect to it.

Warning: You can only connect to a Data Manager Server that has been started.

Procedures

To connect to a Data Manager Servern In the tree view of the Data Manager Server Console, right-click the DataManager Server to which you want to connect and choose Connect.

To disconnect from a Data Manager Servern In the tree view of the Data Manager Server Console, right-click the DataManager Server from which you want to disconnect and choose Disconnect.


Configuring and viewing logsData Manager Server keeps a log of the events that occur during user connections.Each event is described in a log message that includes the time of the event, thetype of event, and a description of the event. You can set a limit to the number of logmessages displayed in the Log window, and then specify whether to clear the logmessages from the Log window or save them to a text (.txt) file after the limit hasbeen reached.

The following icons are used in the Log window to indicate the status of an event:

Successful event

Event warning

Event error

Procedures

To set log options1. In the tree view of the Data Manager Server Console, expand Console Root,

choose the Data Manager Server for which you want to set log options, andthen choose Tools > Options.

2. In the Options dialog box, click the Log tab.3. In the When Log Reaches box, type the number of log messages at which you

want to clear the Log window, or accept the default, and then choose one ofthe following actions to take when the log reaches this limit:

n Clear—The Log panel is cleared without saving the log messages.n Save to the File—The log messages in the Log panel are saved in thelocation that you specify. To specify a location, click Browse (...), and inthe Save As dialog box, navigate to the folder where you want to savethe file, type a file name, and click Save. The file will be created whenthe limit is reached.

4. Click OK.

To view log messages1. In the tree view of the Data Manager Server Console, expand Console Root.2. Expand the Data Manager Server for which you want to view log messages,

and choose Log.


Note: You can clear the log messages or save them to a file at any time by right-clicking in the right-hand panel and choosing the appropriate command.

Tip: You can also view Data Manager log messages in the Event Viewer in theWindows Administrative Tools. To access the Event Viewer, choose Start >Control Panel > Administrative Tools > Event Viewer. Data Manager log messagesappear under the System Log node in the tree view.


Changing the location of the File Server folderThe location of the File Server folder is defined during the initial configuration ofData Manager Server; however, you can change the location of this folder ifrequired. To enable Data Manager users to access existing project data, you mustcopy the contents of the File Server folder to the new location.

Tip: You can also change the File Server location by stopping the Data Managerservice and modifying the ConfigurationSettings<version>.xml file located in theProgramData\Mentum\Data Manager 6.x folder.

Procedure1. In the tree view of the Data Manager Server Console, expand Console Root,

expand the Data Manager Server for which you want to change the File Serverfolder location, expand Services, and choose File Server.

2. Do one of the following:


n Type the local path or full network path of the file server folder in theData Store Folder box.

n Click the Browse (...) button, navigate to the new folder location, andclick OK.

3. Click Apply.


Controlling permissionsAs the Data Manager Administrator, you determine which actions a user can performby creating group accounts through which you control permissions (i.e., you grant orrestrict access to data). Permission settings determine whether a Data Manageruser can modify data and submit changes to Data Manager. This is done from theSecurity panel of the Data Manager Console by right-clicking Groups and choosingAdd. For each group, you can define specific access permissions and assign selectusers to each group.

Figure 1: Permission control

There are two types of permissions and they can be set on a project-by-projectbasis:

n Type Permissions—refer to those permissions related to categories ofinformation stored in the database such as environments, flags, groups, etc.

n File Permissions—refer to those permissions related to the specific file typesstored in the file server folder such as analysis layers, frequency plans, etc.


Depending on the permission controls defined, permissions are evaluated in Planetand an error issued when permission is denied or permissions are validated when aData Manager user attempts to submit changes to the Data Manager.

Example

In this example, the Data Manager Administrator enabled the Type Permissionscheck box and then cleared the Network Settings check box for the LTE project forthe group to which the user is a member. This means that when the user attempts tomodify network settings in Planet, an error message displays indicating permissionis denied.

If the Type Permissions check box had been cleared, the user would have been ableto edit network settings in Planet but would see an error when submitting networksetting changes to Data Manager.

Procedures

To specify permission control for a group account1. Choose Start > Data Manager Console.2. In the tree view, expand the Security node.3. Right-click Groups and choose Add.


4. In the Group dialog box, on the General tab, specify a name for the group andselect users to add to it.

5. Click the Project Permissions tab, select a project in the tree view, and choosethe appropriate access (i.e., No Access, Read Only, Read and Write, or FullAccess).

6. Click the Type Permissions tab and, for each project, clear the check box nextto project items to which access is denied.

7. Click the File Permissions tab and, for each project, clear the check box nextto those file types to which access is denied.

8. Click OK.

To enable permission validation in Planet1. In the Data Manager Server Console, in the tree view, select the Data

Manager Server for which you want to define administrative options.2. Choose Tools > Options.3. In the Options dialog box, click the Permissions tab to set permission controls:

n Enable the check box next to Type Permissions to put into effect the typepermissions you defined for the user or group. When you enable thischeck box, permissions are verified in Planet. When you clear this checkbox, permissions are verified when the project is submitted to DataManager.

n Enable the check box next to File Permissions to put into effect the filepermissions you defined for the user or group. When you enable thischeck box, permissions are verified in Planet. When you clear this checkbox, permissions are verified when the project is submitted to DataManager.

4. Click the Server tab to define server options (such as server port, number ofconnections, transaction timeout, etc.).

Note: Both the Server and Log tabs are displayed when you have selected a DataManager Server in the Data Manager Console tree view. If no server is selected,only the Log tab displays.

Warning: Only file permissions related to antenna and propagation models areverified in Planet. This means, for example, that if you enable File Permissions inthe Options dialog box and clear the check box next to LTE FDD Analyses, whenthe Planet user deletes the analysis no error message is displayed in Planet.


Defining Data Manager Server connection limitsWhen a Data Manager user accesses project data, the data is loaded into memory onthe server where the Data Manager Server is installed. If you have a large numberof users, you can conserve memory resources by limiting the number of userconnections and setting a time limit for inactivity. If a user does not perform anyactions on project data for the specified period of time, the project is removed frommemory. The next time the user performs an action, the project is reloaded intomemory.

Note: In Data Manager memory, only network data is kept in the Cache. Layers,antenna patterns, propagation models, etc. are not. As a result, the size inmemory is proportional to the .planet.datx file size as seen in the project folder(e.g., for 300 000 sectors, Data Manager can use up to 4 GB of RAM depending onhow many sectors are in the Data Manager).

Procedure1. In the tree view of the Data Manager Server Console, expand Console Root,

choose the Data Manager Server for which you want to configure connections,and then choose Tools > Options.

2. In the Options dialog box, click the Server tab.3. In the Port box, type the port number for Data Manager connections or accept

the default.

This is the port number that Planet users must type in the Port Number box inthe Data Manager Connection Settings dialog box.

4. In the Maximum Connections box, type the maximum number of simultaneoususers who can connect to the Data Manager Server.

5. In the Transaction Timeout Period box, type the maximum number of minutesthat the Data Manager Server will wait for communication from a client that ischecking in or submitting data before it disconnects the client.

6. If you want the Data Manager Server Console to connect automatically (i.e.without authentication) to a Data Manager Server on the same computer,enable the Permit Non-Authenticated Local Administrative Consoles checkbox.

Depending on your security policies, you may want to clear this check box toprevent the local Data Manager Server from being added without passwordauthentication. If you clear this check box, you can manually add a local DataManager Server to the Data Manager Server Console. See “To add a DataManager Server to the Console”.

7. In the Cache Settings section, define the following parameters:n Maximum Memory Use—define the percentage of physical RAM allocatedfor the Cache.


n Clean-up Interval—define the time period during which projects are keptin the Cache. Once this time period expires, projects are only removedfrom the Cache if the memory used and the physical memory availableare below the define percentage.

8. Click OK.

Tip: You can also click the Options button on the toolbar to open the Optionsdialog box.


Backing up and restoring Data Manager projects and settingsIt is important to back up Data Manager projects and settings on a regular basis toprevent data loss in the event of a system failure.

Data Manager backup files must be saved on the computer that the Data ManagerServer is installed or on a drive that can be accessed by the Data Manager Server.You can save backup configuration files to the folder of your choice.

Each time you use the Data Manager Backup/Restore Wizard to back up DataManager projects, you can save the wizard settings in a backup configuration file. Abackup configuration file stores the settings for each of the enabled categories(Projects, Custom User Data Fields, Users, Groups, and Data Manager Settings), aswell as the backup file name and location. After you have saved a backupconfiguration file, you can perform subsequent backups by simply loading thebackup configuration file and clicking Finish.

Saving a backup configuration file is not something that you need do each time youperform a backup. You might want to save a few different backup configuration filesfor various purposes: back up projects and settings, only back up project data, oronly back up settings.

Procedures

To back up Data Manager projects and settings1. Choose Start> All Programs > Data Manager Server > Data Manager Server

Console.

The Data Manager Server Console opens.

2. In the tree view, right-click the Data Manager Server that you want to backupand choose Backup/Restore.

The Data Manager Backup/Restore Wizard opens.

3. On the Welcome page, click Next.4. On the Choose the action to perform page, choose Backup.5. If you want to use the settings contained in a backup configuration file, do the

following:n Enable the Load Backup Configuration From A File check box and clickNext.

n Click Browse (...), navigate to the backup configuration file (.xml), andclick Open.

6. Each time you use the Data Manager Backup/Restore Wizard, you can save thewizard settings in a backup configuration file.

7. Click Next.8. On the Choose the type of data you want to back up page, enable the check

boxes beside the types of data you want to back up, and click Next.


n Projects—project data stored in Data Manager. Custom fields areautomatically backed up with projects to maintain a match betweencustom user data in projects and Data Manager Server custom fielddefinitions.

n Custom Fields—custom fields defined by the Data Manager administratorand used by Planet users to add custom user data to the sectors and sitesin a project.

n Users—definitions of Data Manager usersn Groups—definitions of Data Manager user groupsn Data Manager Settings—the pathname of the file server folder used tostore project data and the Planet data file categories available to users.

n If you chose Projects as a type of data to back up, on the Choose theProjects and Folders You Want to Back Up page, do the following:

n If you want your selections to apply to the top-level folder as well asthose folders contained within it, enable the Cascade Selection checkbox.

n Enable the check boxes beside each project folder that you want to backup.

n Click Next.9. On the Choose the backup action to perform page, choose one of the following

options, and click Next:n Backup Data and Save Configuration File—create a backup of the chosenData Manager data and save the backup options you have set using thewizard in a backup configuration file.

n Backup Data Only—create a backup of the chosen Data Manager data. Abackup configuration file is not created.

n Save Configuration File Only—save the settings you defined while usingthe wizard in a backup configuration file. Data Manager data is notbacked up.

n On the Choose the location to save backup files page, do the following,and click Next:

n If you chose to back up Data Manager data, click Browse (...) beside theBackup File box, navigate to the folder where you want to store thebackup file, type a name for the backup file (.dmbak), and click OK.

n If you chose to save a backup configuration file, click Browse (...) besidethe Backup Configuration File box, navigate to the folder where you wantto store the backup configuration file, type a name for the file, and clickSave.

10. Click Next and then click Finish.

The Backup/Restore Progress dialog box shows the progress of your backup.

11. When your backup is complete, click OK, and then click Close in theBackup/Restore Progress dialog box.


To restore Data Manager projects and settingsThe project folders to which you are restoring the projects must be empty.

1. Choose Start > All Programs > Data Manager Server > Data Manager ServerConsole.The Data Manager Server Console opens.

2. To restore Data Manager projects and settings to a Data Manager Server, inthe tree view, right-click the Data Manager Server to which you want torestore data, and choose Backup/Restore.

The Data Manager Backup/Restore Wizard opens.

3. On the Welcome page of the Data Manager Backup/Restore Wizard, click Next.4. On the Choose the Action to Perform page, choose the Restore option, and

click Next.5. On the Choose the Backup File You Want to Restore page, click Browse (...)

beside the Backup File box, navigate to the backup file (.dmbak) from whichto restore Data Manager data, and click OK.

6. Click Next.7. On the Choose the Type of Data You Want to Restore page, enable the check

boxes beside the types of data you want to restore, and click Next.

Only the check boxes for the types of data contained in the backup you choseto restore are available.

8. If you chose Projects as a type of data to restore, in the tree view on theChoose the Projects and Folders You Want to Restore page, enable the checkboxes beside the projects you want to restore, and then click Next.

9. If you want to restore all of the projects contained in a project folder, enablethe Cascade Selection check box, and then enable the check box beside theproject folder.

10. Click Finish.11. When your restore is complete, click OK, and then click Close in the

Backup/Restore Progress dialog box.


CHAPTER4 Basic Usage

Data management with the Planet Data Manager encompasses somebasic administrative tasks, which are covered in this chapter.


Understanding permissions 46

Project permissions 46

Type permissions 47

File permissions 48

Controlling permissions 63

Creating user and group accounts 66

Importing Windows user accounts and groups 70

Accepting and denying user connections 72

Disconnecting Data Manager users 73

Configuring project folders 74

Configuring the import and export of network data withXeda 77

Mapping data 77

Specifying shared custom data definitions 81

Releasing locked project data 84

Understanding permissionsAs the Data Manager Administrator, you create profiles for users that determinewhich projects they can access and the actions they are allowed to perform. You canalso release locked data if required. And you do this for each Data Manager Serverin your network.

You can set the following types of permissions for individual users or groups:

n Project permissionsn Type permissionsn File permissions

User and group permissions are cumulative. When you add a user to a group, theuser inherits all of the group permissions, but also retains any permissions that areassigned at the individual user level. For example, a user may not have access to acertain project at the group level, but can be assigned access to the project at theindividual user level.

Best Practice: To better manage users, create groups and assign users tovarious groups.

Note: If you make changes to user or group permissions when a user is logged onto a Data Manager Server, the changes will not take effect until the next time theuser logs on to the Data Manager Server.

Project permissionsProject permissions determine the type of access that is allowed. Permissions canbe assigned for each project folder in the Data Manager Server at the user andgroup level. The figure below shows the types of permissions available. Forexample, if a user is assigned read-only access to a folder, the user can get aproject, but not submit changes or check a project in initially.


Figure 1: Project Permissions tab. In this example, User A has full access to theOttawa project but no access to the Toronto project.

Type permissionsType permissions determine the types of project data that a user can add or update.The items in the type permissions list correspond to the project data that is stored inthe database, not the binary files that are stored in the file server folder.

You can set type permissions at the project level for each of the various project datatypes. Type permissions are organized in a tree view based on the following generalcategories:

n Environments—geodatan Flags—flag datan Groups—group datan Link Configurationsn Local Area Networksn Network Data—site datan Network Settings—network technologiesn Project Configuration—project settingsn Subscriber Settings—subscriber-related data, including subscriber types,services, equipment, and clutter types

Type permissions are assigned at the group level and, by default, the group is givenaccess to all project data categories.


Figure 2: Type Permissions tab for Group 1

File permissionsFile permissions determine the types of files that users can add or update. The itemsin the file permissions list correspond to the binary file types that are stored in thefile server folder, not the project data that is stored in the database.

You can set file permissions for each of the various file types. All users who are notpart of a group share the same file permissions based on the settings defined in theSaved File Categories list.

By default, the categories that you enable in the Saved File Categories list are alsoenabled in the File Permissions list when you create a new group.


Figure 3: Example Saved File Categories list

The table below lists the file categories in the Saved File Categories list. For eachcategory, the table identifies the applicable Planet folder and the associated filetypes. Files in all the file categories listed are stored both locally and in the DataManager. Categories highlighted with an asterisk are mandatory and not displayedin the Stored File Category list.

When you enable or clear check boxes, you are granting or denying permission tostore files in Data Manager.

Example: If you clear the check box next to traffic maps when an engineerperforms an initial check in of the project, the engineer will submit the files fromthe Planet project based on the stored file category status (i.e., enabled orcleared). So, in the above example, if you clear the Traffic Map file categorycheck box on the Stored File Categories panel, the traffic map files will not besubmitted to the Data Manager. When the engineer is synchronizing his localproject with the one in Data Manager, he will not retrieve the traffic maps fromthe Data Manager. In addition, the engineer will be unable to submit new trafficmaps to Data Manager.


Category Name Planet Folder Planet File Types orFile Name

Areas Areas

.tab

.grc

.xml

CDMA2000 Analysis CDMA2000_Analyses

.ini

.nas

.dat

.map

.tab

.grd

.grc

.id

.xml

.txt

CDMA2000 Monte CarloSimulations

CDMA2000_MCSimulations

.ini

.nas

.dat

.map

.tab

.grd

.grc

.id

.xml

.txt

.params

CDMA2000 Reports Reports\CDMA .wrp

File categories



Clutter Geodata\Clutter.grc

.tab

Clutter Height Geodata\Clutter Height.grd

.tab

Custom Geodata Geodata\Custom Data all file types in theGeodata folder

Drive Tests Drive Tests all file types in theDrive Tests folder

Drive Test Predictions SPT .spt

Entity Attachmentsall files typesattached to the site,sector, or antenna

Facets Geodata\Facets

.txt

.fct

.vis

FCC FCC Contours

.dat

.map

.tda

.tab

.id

.tin

FCC Settings Project folderFCC.set

FCC_Overrides.ini

Fixed Subscriber Tables Fixed Subscriber Tables.csv

.xml

FixedWiMAXFDD Analysis FixedWiMAXFDD_Analyses

.ini

.nasCHAPTER 4│DataManagerAdministratorGuide


.dat

.map

.tab

.grd

.grc

.id

.xml

.txt

.params

FixedWiMAXTDD Analysis FixedWiMAXTDD_Analyses

.ini

.nas

.dat

.map

.tab

.grd

.grc

.id

.xml

.txt

.params

Graphs Geodata\Graphs

.txt

.dat

.id

.map

.tab

GSM_Analyses GSM_Analyses .map



.tab

.grd

.grc

.id

.xml

.txt

.params

Heights Geodata\Heights.grd

.tab

Heterogeneous NetworkAnalyses HetNet_Analyses

.ini

.nas

.dat

.map

.tab

.grd

.grc

.id

.xml

.txt

iDEN_Analyses iDEN_Analyses

ini

.nas

.dat

.map

.tab

.grd

.grc

.id



.xml

.txt

.params

Import Export Settings Import Export Settings .xml

Interference Matrices InterferenceMatrix

.imx

.imh

.srv

ITCnet Capacity Plans .cap

ITCnet Slot Plans .slp

ITCnet Analyses ITCnet_Analyses

.ini

.nas

.dat

.map

.tab

.grd

.grc



.id

.xml

.txt

LTE Call Events Call Trace Data\LTE

.csv

.tab

.grd

.xml

LTE Analyses LTE_Analyses

.ini

.nas

.dat

.map

.tab

.grd

.grc

.id

.xml

.txt

LTE MonteCarlo Simulations LTEMC_Simulations

.ini

.nas

.dat

.map



.tab

.grd

.grc

.id

.xml .

params

.txt

LTE Frequency Plans FrequencyPlan .fpp

LTE FSS Gain Tables Curves\LTE FSS GainTables .xml

LTE PRACH Plans PrachPlan.rsp

.txt

LTE Subscribers Subscribers.csv

.xml

LTE Tracking Area Plans LTE Tracking Area Plans

Morphologies Geodata\Morphologies.txt

.sol

Neighbor Lists NeighborList.xml

.csv

Network Data Network_Data

.xls

.xlsx

.csv

.xml



Network PerformanceInspector

Network PerformanceInspector .xml

Optimization Profiles Optimization Profiles .xml

Optimizations Optimizations.rep

.xml

Performance Analyses PerformanceAnalyses.qos

.qss

Planet Local Area NetworkFiles Local Area Networks .mlan

PN Offset Plan Analyses PNOffsetPlanning

.grc

.grd

.tab

.ini

.AnalysisReport

PN Offset Plans PNOffsetPlanning.pno

.txt

Polygons Geodata\Polygon

.dat

.id

.map

.tab

Propagation Model Analysis Propagation_Model_Analyses .xml

Reports Reports .rep

Scanner Survey Data Scanner SurveyData\Data Files

.xml

.data



.mvs

Scanner Survey Templates Scanner SurveyData\Template Files

.xml

.ini

Scanner Surveys Scanner Survey

Scrambling Code Plans ScramblingCodePlanning .scp

Shared Project Attachments Attachmentsfiles of any type

Shared Report Templates Report Templates

Shared Sector Queries Sector Queries .xml

Shared Site Templates Site Templates .xls

Simulcast Analyses Simulcast_Analyses

.ini

.nas

.dat

.map

.tab

.grd

.grc

.id

.xml

.txt

Site Sets Site Sets.csv

.ini

SmallCellPlanning SmallCellPlanning .xml



Social Media Social Media

.grd

.tab

.xml

Statistics Analysis Setting Settings\LayerStatistics .set

TDMA Frequency Plans FrequencyPlan .fpl

TDMA_FDMA Reports Reports\TDMA_FDMA .wrp

TDMA/FDMA Analysis TDMA_FDMA Analyses

.ini

.nas

.dat

.map

.tab

.grd

.grc

.id

.xml

.txt

Traffic Maps TrafficMaps

.grd

.tab

.xml

WCDMA Analysis WCDMA_Analyses

.ini

.nas

.dat



.map

.tab

.grd

.grc

.id

.xml

.txt

WCDMA Call Events Call Trace Data\WCDMA

.csv

.tab

.grd

.xml

WCDMA MonteCarloSimulations WCDMAMC_Simulations

.ini

.nas

.dat

.map

.tab

.grd

.grc

.id

.xml

.params

.txt

WCDMA Reports Reports\WCDMA .wrp

Weighting GridsSocial Media

Call Trace Daata

.grd

.grc



.tab

Wi-Fi Analyses

.ini

.nas

.dat

.map

.tab

.grd

Wi-Fi Frequency Plans .fpp

WiMAX - PreQual Analyses PreQual_Analyses

.ini

.nas

.dat

.map

.tab

.grd

.grc

.id

.xml

.txt

WiMAX Analysis WiMAX_Analyses

.ini

.nas

.dat

.map

.tab

.grd



.grc

.id

.xml

.txt

WiMAX Frequency Plans FrequencyPlan .fpp

WiMAX MonteCarloSimulation WiMAXMC_Simulations

.ini

.nas

.dat

.map

.tab

.grd

.grc

.id

.xml

.params

.txt


Controlling permissionsAs the Data Manager Administrator, you determine which actions a user can performby creating group accounts through which you control permissions (i.e., you grant orrestrict access to data). Permission settings determine whether a Data Manageruser can modify data and submit changes to Data Manager. This is done from theSecurity panel of the Data Manager Console by right-clicking Groups and choosingAdd. For each group, you can define specific access permissions and assign selectusers to each group.

Figure 1: Permission control

There are two types of permissions and they can be set on a project-by-projectbasis:

n Type Permissions—refer to those permissions related to categories ofinformation stored in the database such as environments, flags, groups, etc.

n File Permissions—refer to those permissions related to the specific file typesstored in the file server folder such as analysis layers, frequency plans, etc.


Depending on the permission controls defined, permissions are evaluated in Planetand an error issued when permission is denied or permissions are validated when aData Manager user attempts to submit changes to the Data Manager.

Example

In this example, the Data Manager Administrator enabled the Type Permissionscheck box and then cleared the Network Settings check box for the LTE project forthe group to which the user is a member. This means that when the user attempts tomodify network settings in Planet, an error message displays indicating permissionis denied.

If the Type Permissions check box had been cleared, the user would have been ableto edit network settings in Planet but would see an error when submitting networksetting changes to Data Manager.

Procedures

To specify permission control for a group account1. Choose Start > Data Manager Console.2. In the tree view, expand the Security node.3. Right-click Groups and choose Add.


4. In the Group dialog box, on the General tab, specify a name for the group andselect users to add to it.

5. Click the Project Permissions tab, select a project in the tree view, and choosethe appropriate access (i.e., No Access, Read Only, Read and Write, or FullAccess).

6. Click the Type Permissions tab and, for each project, clear the check box nextto project items to which access is denied.

7. Click the File Permissions tab and, for each project, clear the check box nextto those file types to which access is denied.

8. Click OK.

To enable permission validation in Planet1. In the Data Manager Server Console, in the tree view, select the Data

Manager Server for which you want to define administrative options.2. Choose Tools > Options.3. In the Options dialog box, click the Permissions tab to set permission controls:

n Enable the check box next to Type Permissions to put into effect the typepermissions you defined for the user or group. When you enable thischeck box, permissions are verified in Planet. When you clear this checkbox, permissions are verified when the project is submitted to DataManager.

n Enable the check box next to File Permissions to put into effect the filepermissions you defined for the user or group. When you enable thischeck box, permissions are verified in Planet. When you clear this checkbox, permissions are verified when the project is submitted to DataManager.

4. Click the Server tab to define server options (such as server port, number ofconnections, transaction timeout, etc.).

Note: Both the Server and Log tabs are displayed when you have selected a DataManager Server in the Data Manager Console tree view. If no server is selected,only the Log tab displays.

Warning: Only file permissions related to antenna and propagation models areverified in Planet. This means, for example, that if you enable File Permissions inthe Options dialog box and clear the check box next to LTE FDD Analyses, whenthe Planet user deletes the analysis no error message is displayed in Planet.


Creating user and group accountsAs the Data Manager Administrator, you create profiles for users that determinewhich projects they can access and the groups to which they are a member. Youmust create user accounts to allow Data Manager users to log on to a Data ManagerServer. When you create a user account, you define the following settings on a per-user basis:

n Group membershipn Project permissions

Groups enable you to assign the same set of permissions to multiple users. Whenyou add a user to a group, the user inherits all permissions from the group. Usersadded to groups also keep any additional individual permissions they have.

Best Practice: To better manage users, create groups and assign users tovarious groups.

Note: To add a user account with Windows domain authentication (i.e., where thename and password for the user are the same as the Windows name andpassword for the user), you must use the Accounts Import Wizard to create theuser account. See “Importing Windows user accounts and groups”.

Procedures

To add a user account1. In the tree view of the Data Manager Server Console, expand Console Root,

expand the Data Manager Server that you want to modify, expand Security,right-click Users, and choose Add.

2. On the General tab, type the user name in the Name box.

User names are not case sensitive and can be up to 64 characters in length.

3. If you want to assign a password, in the Password box, type the userpassword, and then retype the password in the Confirm Password box.

Passwords are case sensitive and can be up to 24 characters in length.

4. If the folder has subfolders and you want to apply the same permissions to allsubfolders, enable the Cascade Permissions check box.

You can also choose the root Projects node and cascade permissions to allprojects.

5. To allow the user to submit changes even if this results in items locked byanother user being overwritten, enable the Super User check box.


6. On the Project Permissions tab, choose the folder for which you want to defineprivileges and then choose one of the following options:

n No Access—The user cannot get a project stored in the folder, submitchanges to a project stored in the folder, or initially check a project intothe folder.

n Read Only—The user can get the project stored in the folder, but cannotsubmit changes or initially check a project into the folder.

n Read and Write—The user can get the project stored in the folder andsubmit changes to it, but cannot initially check a project into the folder.

n Full Access—The user can initially check a project into this folder, get theproject stored in the folder, and submit changes to it.

By default, all folders are set to No Access.

7. Repeat Step 6 for each folder for which you want to define permissions.8. Click OK.

The user name appears in the Name list.

Note: To see which groups a user is a member of, click the Groups tab, and thendouble-click on a group name to edit the group in the Group dialog box.

Tip: You can edit a user account by right-clicking the user name in the Name listand choosing Edit or by double-clicking the user account name.

To add a group account1. In the tree view of the Data Manager Server Console, expand Console Root,

expand the Data Manager Server that you want to modify, expand Security,right-click Groups, and choose Add.

2. On the General tab, in the Name box, type a name for the group.3. To add users to the group, click Add.4. In the Add User(s) dialog box, choose one or more users to add to the group

and click OK.5. On the Project Permissions tab, choose the folder for which you want to define

privileges and then choose one of the following options:n No Access—The group of users cannot get a project stored in the folder,submit changes to a project stored in the folder, or initially check aproject into the folder.

n Read Only—The group of users can get the project stored in the folder,but cannot submit changes or initially check a project into the folder.

n Read and Write—The group of users can get the project stored in thefolder and submit changes to it, but cannot initially check a project intothe folder.


n Full Access—The group of users can initially check a project into thisfolder, get the project stored in the folder, and submit changes to it. Bydefault, all folders are set to No Access.

6. If the folder has subfolders and you want to apply the same permissions to allsubfolders, enable the Cascade Permissions check box.

7. Repeat Step 5 and Step 6 for each folder for which you want to definepermissions.

8. On the Type Permissions tab, clear the check boxes beside the project datatypes that you do not want the group to be able to add or update.

9. On the File Permissions tab, clear the check boxes beside the project file typesthat you do not want the group to be able to add or update.

10. Click OK.

The group name appears in the Name list.

Tip: You can edit a group account by right-clicking the user name in the Name listand choosing Edit or by double-clicking the user account name.

To add users to an existing group1. In the tree view of the Data Manager Server Console, expand Console Root,

expand the Data Manager Server that you want to modify, then expandSecurity, and choose Groups.

2. In the Name list, right-click the group to which you want to add users andchoose Edit.

3. On the General tab, click Add.4. In the Add User(s) dialog box, choose the users that you want to add to the

group and click OK.5. In the Group dialog box, click OK.

To remove users from a group1. In the tree view of the Data Manager Server Console, expand the Data

Manager Server that you want to modify, expand Security, and chooseGroups.

2. In the Name list, right-click the group from which you want to remove usersand choose Edit.

3. On the General tab, choose the user(s) you want to remove and click Remove.4. In the Group dialog box, click OK.

To delete user or group accountsDeleting a group does not delete the individual users who were part of the group.

1. In the tree view of the Data Manager Server Console, expand the DataManager Server that you want to modify, expand Security, and do one of thefollowing:


n If you want to delete one or more users, choose Users.n If you want to delete one or more groups, choose Groups.

2. In the Name list, choose the users or groups that you want to delete, right-click, and choose Delete.


Importing Windows user accounts and groupsYou can use the Accounts Import Wizard to import existing Windows user accountsand groups. The accounts and groups that you import are assigned the defaultproject, type, and file permissions. You may need to modify these permissions afteryou have imported the accounts and groups.

When you import user accounts and groups from Windows, the user name andpassword cannot be changed. Data Manager users can simply enable the UseWindows Domain Authentication check box in the Data Manager Connection Settingsdialog box, and do not need to enter a user name or password.

When you import a group, only individual users are imported. Sub-groups are notincluded in the import.

Procedure1. In the tree view of the Data Manager Server Console, expand the Data

Manager Server that you want to modify, right-click Security, and chooseAccounts Import Wizard.

The Accounts Import Wizard opens.

2. On the Welcome page, click Next.3. On the Authentication Mode page, do one of the following:

n To log on to the active directory for the network using the currentaccount, choose Using Current Credentials.

n To log on to the active directory for the network using a differentaccount, choose Using Alternate Credentials, then type the domain namein the Domain box, the account name in the Account Name box, and thepassword in the Password box.

4. On the Available Domains page, choose the domains from which you want toimport accounts.

5. Click Next.6. In the Type of Groups section, enable any of the following check boxes:

n Global—use this option when you want to import accounts from thedomain in which you reside but you want to assign permissions to anyavailable domain. This is the recommended option.

n Domain Local—use this option when you want to import accounts fromthe domain in which you reside and you only need to assign permissionswithin this domain. This is the least time intensive option but focusesonly on one domain.

n Universal—use this option when you want to import accounts from anyavailable domain regardless of the domain in which you reside. In thiscase, permissions can be assigned from any domain as well. This optionis the most time intensive of the three options and is not recommended.

7. From the list of Available Groups, choose the groups you want to import andclick Next.


8. In the Accounts Import Mode section, do one of the following:n To import only the individual user accounts from the server, chooseAccounts Only.

n To import the user accounts and groups from the server, chooseAccounts and Groups.

9. Click Next.10. Review the list of accounts and groups, if required, do any of the following:

n If you want to remove an account, choose the account and click Remove.n If you want to make a change to the group or groups that you chose,click Back.

11. When you are satisfied with the list of accounts, click Next.12. Click Finish and then, in the Data Manager Server dialog box, click OK.


Accepting and denying user connectionsYou can choose to have a Data Manager Server accept or deny user connectionsusing the Data Manager Server Console. Denying user connections preventsPlanet users from connecting to the Data Manager Server. The Data Manager Servercontinues to run. This enables you to configure a Data Manager Server without therisk of having users connect.

The following icons are used to indicate whether a Data Manager Server is acceptingconnections:

n The Data Manager Server is accepting connections.n The Data Manager Server is not accepting connections.

Procedures

To accept user connectionsn In the tree view of the Data Manager Server Console, choose the DataManager Server that you want to accept user connections and then choose File> Accept Client Connections.

To deny user connectionsn In the tree view of the Data Manager Server Console, choose the DataManager Server that you want to deny user connections and then choose File>Deny Client Connections.


Disconnecting Data Manager usersYou can view a list of Data Manager users who are currently connected to a DataManager Server. For each user, the user name, host, and login time are displayed.You can disconnect Data Manager users at any time.

Procedure1. In the tree view of the Data Manager Server Console, expand the Data

Manager Server that you want to modify and choose Connected Clients.

A list of connected clients is displayed.

2. Right-click the user you want to disconnect and choose Disconnect.3. In the confirmation dialog box, click Yes.


Configuring project foldersTo enable Planet users to add project data to a Data Manager Server, you mustcreate a project folder for each Planet project. Project folders are located in theProjects node of each Data Manager Server.

Planet users cannot add project folders. The project folder structure you createdepends how your organization conducts its network planning and optimizationactivities. The folder hierarchy is for display and organizational purposes only and isnot reflected in the database or file server folder.

In the example below, project folders are organized by region and planning activity.

Figure 1: Sample project folder structure

Each folder in Data Manager Server can contain a single project. You assign useraccess permissions for specific folders.

The folder icons in the projects tree view indicate whether or not a folder containsproject data. You can add project descriptions to help Data Manager users identifythe contents of a folder when browsing projects.

Empty folder

Folder containing project data

Top-level node (cannot contain a project)

Note: You can have only one top-level node in your folder hierarchy. Userscannot check projects into the top-level node.

Procedures

To add a project folder1. In the tree view of the Data Manager Server Console, expand Console Root,

then expand the Data Manager Server to which you want add a project and


choose Projects.2. Right-click in the right-hand panel and choose Add.3. On the General tab, type a name for the project folder in the Project Name box

and, optionally, a project description in the Project Description box.4. On the Site Custom Fields tab, enable the check boxes beside the custom

fields to make available to sites of the project stored in the project folder.5. On the Sector Custom Fields tab, enable the check boxes beside the custom

fields to make available to sectors of the project stored in the project folder.6. Click OK.

The project folder is added to the project tree view.

Tip: You can add a sub-folder by right-clicking an existing folder and choosingAdd.

To delete a project folderWhen you delete a project folder, the project data is removed from the databaseand file server folder.

Note: You can only delete project folders that do not contain subfolders.

1. In the tree view of the Data Manager Server Console, expand Console Root,then expand the Data Manager Server from which you want to delete a projectand choose Projects.

2. In the project tree view, right-click the folder that you want to delete andchoose Lock.

This prevents users from trying to modify the project while it is being deleted.

3. In the project tree view, right-click the folder that you want to delete andchoose Delete.

4. In the confirmation dialog box, click Yes.

The project folder is deleted from the project tree view and the data isremoved from the database and the file server folder.

To delete the contents of a project folderDeleting the contents of a project folder enables you to remove the contents of thefolder while leaving the folder permissions intact. You can then reuse the folder for aproject with the same or similar permissions without having to define all of thepermissions again.

1. In the tree view of the Data Manager Server Console, expand Console Root,then expand the Data Manager Server from which you want to delete foldercontents and choose Projects.

2. In the project tree view, right-click the folder that you want to empty andchoose Lock.


This prevents users from trying to modify the project while it is being deleted.

3. In the project tree view, right-click the folder that you want to empty andchoose Empty.


The contents of the project folder are deleted and the data is removed fromthe database and the file server folder.

To lock a project folderLocking a project folder means that Data Manager users cannot modify the project.Users still have read access to the project.

1. In the tree view of the Data Manager Server Console, expand Console Root,then expand the Data Manager Server that contains the folder that you want tolock and choose Projects.

2. In the project tree view, right-click the folder that you want to lock and chooseLock.

The lock icon appears on the folder to show that the folder is locked.

Note: You can unlock a folder by right-clicking it and choosing Lock again. As theAdministrator, you can unlock any or all projects from the Data Manager Console.You can also release locks for a specific user.

To close a projectWhen a Data Manager user accesses project data, the data is loaded into memory onthe server where the Data Manager Server is installed. You can free up servermemory by closing a project.

1. In the tree view of the Data Manager Server Console, expand Console Root,then expand the Data Manager Server that contains the project you want torelease from server memory and choose Projects.

2. In the project tree view, right-click the folder containing the project you wantto release from memory and choose Close Project.


Configuring the import and export of network data with XedaXeda enables engineers to view and extract data from multiple sources to betterunderstand complex network environments. Engineers can take advantage of thisfeature and import up-to-date configuration data into a Planet project stored in theData Manager in order to ensure the network model created in Planet is as close tothe real-world as possible.

Similarly, you can set up the automatic export of data to a Xeda (.Xif) file. Bycreating and pointing to a .bat or .exe file, you can perform post-processingoperations on the .xif file.

Note: The Sector Selection and the Parameter Selection apply to all projectsbeing updated.

Note: Importing data from Xeda is only available for LTE FDD, WCDMA, and GSM.

Note: The import and export of data with Xeda is only supported in the Enterpriseand Ultimate editions of Planet.

Warning: It is important to ensure that a backup of the Data Manager database iscreated regularly. Data imported from Xeda overwrites the parameters in thePlanet projects. Without a backup, there is no way to restore data once an importhas been done. See "Backing up and restoring Data Manager projects andsettings".

Mapping dataIn order to match up data stored in Xeda with data contained within a Planet project,the following parameters must exist in both Xeda and Planet.

For LTE

Parameter Location in Planet

MCC Site Editor (Base Station - General tab)

MNC Site Editor (Base Station - General tab)

Cell Name Site Editor (Sector- Configuration tab)

TAC Site Editor (Sector - Configuration tab)


http://www.infovista.com/products/xeda_network_configuration_management

For WCDMA




Cell Name Site Editor (Sector- Carrier tab)

RNC Site Editor (Sector - General tab)

For GSM




Cell Name Site Editor (Sector- General tab)

BSC Site Editor (Base Station - General tab)

Procedures

To set up the automatic update of data from Xeda1. Open the Data Manager Console.2. In the tree view, expand the Xeda Integration node, and choose Import From

Xeda.3. Do the following:

n On the Settings tab, specify the URL to the server where Xeda is installedand if you want to generate a report of parameter changes to the DataManager project, enable the Generate Reports check box and specify thelocation where the report is to be saved.

n On the Projects tab, enable the check boxes next to those projects youwant to update with data from Xeda.

n On the Schedule page, choose the update frequency using the optionsand check boxes available.

n On the Sector Selection tab, create a query to identify those sectors toinclude in the update process.

n On the Parameter Selection tab, clear the check boxes next to the tablesor columns you do not want to include in the update.


To set up the automatic creation of sites using data from Xeda1. Open the Data Manager Console.2. In the tree view, expand the Xeda Integration node, and choose Import From

Xeda.3. Do the following:

n On the Settings tab, specify the URL to the server where Xeda isinstalled.

n Enable the Create Sites check box.n On the Projects tab, enable the check boxes next to those projects youwant to update with data from Xeda.

n On the Schedule page, choose the update frequency using the optionsand check boxes available.


n On the Parameter Selection tab, clear the check boxes next to the tablesor columns you do not want to include in the update.

Note: When you create new sites through an import of Xeda data, a defaultpropagation model and a default antenna model are assigned although they arenot saved as .pafx or .pmf files and are not meant for real-world networkmodeling. For this, you must obtain and tune propagation model files for theenvironments you are modeling and add and assign the antenna files being usedin the network.

Warning: In order to create sites, the project you are updating must store orshare a Height file through the Data Manager. If the file is shared, you mustdefine the full network path in the project settings, for example,\\server.company.com\geodata. Mapped drives cannot be used.

To set up the automatic export of data to a Xif file1. Open the Data Manager Console.2. In the tree view, expand the Xeda Integration node, and choose Export to Xif.3. Do the following:

n On the Settings tab, specify the export path and if you want to run postprocessing operations, define a path to the .bat or .exe file that containsthem.

n On the Projects tab, enable the check box next to the projects you wantto export.

n On the Schedule page, choose the export frequency using the options andcheck boxes available.



Note: DOS commands are not supported for post processing. Instead, define apath to a .bat or .exe file that contains the post-processing operations you want torun.


Specifying shared custom data definitionsAfter you define the custom data definitions in Data Manager Server and make thecustom fields available in the Planet project, a Planet user can add custom dataattributes to their project that can be shared through Data Manager. These customfields are displayed, and can be defined, on the user data tabs in the Site Editor andin the Site User Data dialog box.

Note: Sector and site custom data fields must have unique names.

Procedures

To add custom fields and define the data definition1. Ensure that there are no users connected to the Data Manager Server.

Because adding custom fields changes the underlying directory structure, youcannot do it while users are connected. Connected users are displayed on theConnected Clients panel.

2. In the tree view of the Data Manager Server Console, expand Console Root,expand the Data Manager Server to which you want add custom fields, expandCustom Fields, and do one of the following:

n To add custom fields for sectors, right-click Sector in the tree view andchoose Add.

n To add custom fields for sites, right-click Site in the tree view andchoose Add.

3. In the Add Fields dialog box, do the following for each custom data field youwant to add:

n In the Field Name column, type a name for the custom field.n From the list in the Data Type column, choose the type of data to bestored in the custom field. Press the F1 key for more information on thedata types.

4. Click OK.

To make custom fields available in a project1. In the tree view of the Data Manager Server Console, expand Console Root,

expand the Data Manager Server that contains the project in which you wantto make custom field available, expand Custom Fields, and do one of thefollowing:

n To make sector custom fields available in a project, right-click Sector inthe tree view and choose Edit Availability.

n To make site custom fields available in a project, right-click Site in thetree view and choose Edit Availability.


2. In the Custom Field Availability dialog box, do the following and click OK:n In the Project tree view, choose the project in which to make customfields available.

n In the Custom Fields list, enable the check boxes beside the customfields to make available in the chosen project.

n In the Custom Fields list, clear the check boxes beside the custom fieldsto omit from the chosen project.

To copy and paste custom fields from an Excel fileIf you have custom fields defined in a Microsoft® Excel (.xls) file, you can copy andpaste them into the Add Fields dialog box. You must ensure that the source data inthe Excel file contains valid data types. Press the F1 key in the Add Fields dialog boxfor information on valid data types.

If you already have custom fields defined, the fields that you copy and paste areadded to the existing fields. They do not overwrite the existing fields.

1. Ensure that there are no users connected to the Data Manager Server.

Because adding custom fields changes the underlying directory structure, youcannot do it while users are connected. Connected users are displayed on theConnected Clients panel.

2. In the tree view of the Data Manager Server Console, expand Console Root,expand the Data Manager Server to which you want add custom fields, expandCustom Fields, and do one of the following:

n To add custom fields for sectors, right-click Sector in the tree view andchoose Add.

n To add custom fields for sites, right-click Site in the tree view andchoose Add.

3. In Excel, copy the two columns that contain the custom field names and datatypes.

4. In the Add Fields dialog box, click the empty box immediately to the left of theField Name column header and then press Ctrl+V.

The text that you copied from the Excel file is pasted into the table in the AddFields dialog box.

5. Click OK.

To delete custom fields

Warning: When you delete a custom field from Data Manager, data stored in thecustom field is deleted from the projects in which the custom field was used tostore custom user data.

Ensure that there are no users connected to the Data Manager Server.


Because deleting custom fields changes the underlying directory structure, youcannot do it while users are connected. Connected users are displayed on theConnected Clients panel.

1. In the tree view of the Data Manager Server Console, expand Console Root,expand the Data Manager Server from which you want to delete custom fields,expand Custom Fields, and do one of the following:

n To delete custom fields from sites, click Site.n To delete custom fields from sectors, click Sector.

2. In the Field Name column of the Information pane, right-click the field thatyou want to delete, and choose Delete Field.



Releasing locked project dataIf a user has locked project data, the data cannot be modified by other users. At anytime, you (as the Data Manager Administrator) can release data locked by a user tomake it available to others. You can also transfer ownership of all locked projectdata to another Data Manager user. For more information on project folders, see"Configuring project folders".

You can also remove invalid locks. This can be useful for example, when the userwho originally put the lock on, no longer exists in the user database.

Warning: You can only transfer ownership of locked project data to another DataManager user if the user to whom you are transferring the locks has the sameData Manager permissions as the original owner.

Procedures

To release locks for a specific user1. In the tree view of the Data Manager Server Console, expand the Data

Manager Server, expand Security, and choose Users.2. In the Name list, right-click the user and choose Release Locks By This User.3. In the confirmation dialog box, click OK.

To transfer locks to another user1. In the tree view of the Data Manager Server Console, expand the Data

Manager Server, expand Security, and choose Users.2. In the Name list, right-click the user and choose Transfer Locks to Other User.3. In the confirmation dialog box, click OK.

To remove invalid locks1. In the tree view of the Data Manager Server Console, expand the Data

Manager Server, and choose Projects.2. Right-click the Projects node and choose Remove Invalid Locks in All Projects.3. In the confirmation dialog box, click OK.


APPENDIXA

Import/Export Command-Line Utility

Using the Import/Export command-line (iecon) utility, you can exportPlanet data to an Excel (.xls) file, a comma separated values (.csv)file,or a database. You can then make changes to the data and use theiecon utility again to import the data back into Planet or Data Manager.


Using the IECON utility 86

Syntax 87

The IECON lexicon 102

Parameters 103

Optional Parameters 104

Using the IECON utilityUsing the Import/Export command-line (iecon) utility, you can export Planet data toan Excel (.xls or .xlsx) file or a comma separated values (.csv) file. You can thenmake changes to the data and use the iecon utility again to import the data back intoPlanet or Data Manager.

This topic does not provide a comprehensive list of commands. See "TheIECON lexicon" for more information. The following conventions are used in theexamples provided to identify required and optional command options.

Text conventions

TextFormat Description

{ }

Braces are used to identify required options in syntaxdescriptions where there is more than one option. You mustchoose only one of the options. Do not type the braces whentyping the command.

For example:

If the command syntax is iecon {/i|/e}, you can type either iecon/i or iecon /e.

|

Vertical lines are used to separate options. Use only one of theoptions. Do not type the vertical line when typing the command.

For example:


[ ]

Square brackets are used to identify optional switches in syntaxdescriptions. Do not type the brackets when typing thecommand.

For example:

If the command syntax is iecon /i /pl /f:filepath [/t:”table list”], /t:”table list” is optional.

/x:value

Options indicated by /x:value require a value to be present. Ifthe value contains spaces or unusual characters, you mustenclose the value in quotation marks.

For example:

If the command syntax is /r:projectname, you must enter aproject name (e.g. /r:”New York/East”, where the project path is


TextFormat Description

in quotation marks because it contains a space.)

/x

Options indicated by /x require no value to be present.

For example:

The command /l requires lists the projects contained in DataManager or the sessions started by the current user.

SyntaxThe syntax for the iecon utility depends on what you want to do. The possiblescenarios are described in the following sections.

To list the projects in Data Manager

iecon /l [/dm] [/s:dmserver] {/u:dmusername /p:dmpassword|/dmis}

Where

/l is the list option.

/dmindicates that the items to be listed are the projects in DataManager. This option is not mandatory. If you do not enterit, /dm is assumed.

/s:dmserveris the Data Manager Server name. This option is notmandatory. If you do not enter a value, the Data ManagerServer on the local computer is used.

/u:dmusernameis a valid user ID defined on the Data Manager Server.

If Data Manager uses Windows domain authentication, donot use this option. Use the /dmis option only.

/p:dmpassword

is the password for the user ID. If no password is definedfor the user, you must still type /p:

If Data Manager uses Windows domain authentication, donot use this option. Use the /dmis parameter only.

/dmis

indicates that Data Manager uses Windows domainauthentication. If Data Manager uses Windows domainauthentication, use this option only. Do not use/u:dmusername and /p:dmpassword.

CHAPTER A│DataManagerAdministratorGuide

Examples

iecon /l /s:ott-1 /u:jdoe /p:passw@rd

In this example, the projects on server ott-1 would be listed, for example:New YorkNew York\CentralNew York\EastNew York\South

iecon /l /dmis

In this example, Windows domain authentication is used. All Planet projects on theData Manager Server on the local computer would be listed.

To list running Planet sessions

iecon /l /pl

Where

/l is the list parameter.

/pl

indicates that the items to be listed are the Planet sessions that werestarted by the current user. This option is used in a configuration withmultiple users and multiple Planet sessions on a single computer (forexample, a terminal server).

Example

iecon /l /plIn this example, all Planet sessions that were started by the current user on thelocal computer would be listed, for example:Available sessions:Session ID Project Name---------- ------------2881 New York2895New York\Central

To import data into Planet from an .xls or .csv file or export data from Planet toan .xls or .csv file.

Warning: You must always include the Summary worksheet (.csv file) in the dataimport and both the Summary.csv file and the schema.ini file must be in the samefolder.


Import syntax

iecon /i /pl /xeda [/id:session ID] [/ex|/csv] /f:filepath [/t:”table list”][/rg] [/rf] [/rs] [/rl] [/rn] [/rsu][/report]

Export syntax

iecon /e /pl [/id:session ID] [/ex|/csv] /f:filepath [/fs:”site and sectorlist”] [grp:"groupname, groupname"][/t:”table list”] [/c:”qualified columnlist”] [/op] [/ov] [/mu]

Where


Parameter Function

/i

imports data into the project currently open in Planetfrom the file indicated by the /f option.

If no project is open in Planet, an error message isdisplayed indicating that no project is loaded.

/e

exports data from the project currently open in Planetto the file indicated by the /f parameter.


/pl indicates that the destination of the import or thesource of the export is Planet.

/xeda imports data from Xeda.

/id:session ID

option used in a configuration with multiple users andmultiple Planet sessions on a single computer (forexample, a terminal server). This is the session ID ofthe project to import into or export from.

/ex|/csv

indicates that the source or destination file is an .xlsfile. When the source or destination file is a commaseparated values (.csv) file, you must use the/csv parameter.

/f:filepath

is the path to the .xls or .xlsx file to export to or toimport from. You can specify a new file or you canoverwrite an existing file. To overwrite an existing file,you must use the /ov parameter. You can also specify afolder with Excel files, CSV files, a Xif file, or a XedaURL.

/fs:”site andsector list”

option only available when exporting. It provides aquoted, comma-separated list of sites and sectors toexport. For sites, use the site name. For sectors, usethe site and sector names delimited by a colon. Forexample, to export Site_1 and the first sector of Site_2, you would type:fs:"Site_1, Site_2:1"

If the list contains only one item, you do not need toenclose the item in quotes.

/grp:”groupname, option only available when exporting. It filters sites


Parameter Function

groupname”based on group membership. For example, to exportall sites in group2 and group3, type:/grp:"group2, group3"

/t:”table list” By default, all tables are exported.

/rgoption only available when importing. Replaces allgroups with imported groups.

By default, groups are not replaced.

/rfoption only available when importing. Replaces all flagswith imported flags.

By default, flags are not replaced.

/rs

option only available when importing. Replaces all siteswith imported sites. This option includes the followingcommands (i.e., if you replace sites, you also implicitlyreplace the data included with the sites: exceptiondata, frequency plan data, link budget data, repeaters,and neighbor lists):

/rn

By default, sites are not replaced.

/rloption only available when importing. Replaces linkbudget data with imported link budget data.

By default, link budget data is not replaced.

/rnoption only available when importing. Replacesindividual neighbor lists with imported neighbor lists.

By default, neighbor lists are not replaced.

/rsuoption only available when importing. Replacessubscriber data with imported subscriber data.

By default, subscriber data is not replaced.

/c:”qualifiedcolumn list”

option only available when exporting from Planet to an.xls file. Option must include a quoted, comma-separated list of columns to export, and all requiredcolumns must be included (i.e., Site ID, Sector ID).The columns must be qualified by table names in theform:


Parameter Function

"tableName.columnName"

If you want to export all groups or all flags, you canuse a wildcard symbol(:). For example, to export allflags listed on the Sectors worksheet type/c:"Sectors.Flag:"

For all groups, type:/c:"Sectors.Group:"

By default, all columns are exported.

/opoption only available when exporting to an .xls file.Opens the file in Excel after exporting.

By default, the file is not opened in Excel.

/ov

option only available when exporting to an .xls file.Overwrites an existing .xls file.

By default the file is not overwritten. If the fileindicated by the /f parameter already exists and you donot use the /ov parameter, an error message isdisplayed.

/mu option only available when exporting. Overrides theproject settings and exports all values in metric.

/report create a report of the Xeda import process.

Examples

iecon /e /pl /id:2881 /ex /f:D:\Projects\Region1.xls

In this example, data from the project open in session 2881 of Planet would beexported to the file Region1.xls.

iecon /i /pl /ex /f:D:/Projects/Region1.xls /t:”Sectors”

In this example, data from the Sectors worksheet would be imported from theRegion1.xls file into the project open in Planet.


To import data into Data Manager from an .xls or .csv file or export data fromData Manager to an .xls or .csv fileYou must always include the Summary worksheet (.csv file) in the data import andboth the Summary.csv file and the schema.ini file must be in the same folder.

Import syntax

iecon /i /dm [/s:dmserver] [/port:portnumber] {/u:dmusername/p:dmpassword|/dmis} /r:projectname /ex|/csv/xif /f:filepath[/t:”table list”] [/rg] [/rf] [/rs] [/rhsn] [/rcc] [/rce] [/rca] [/rl][/rn] [/rsu] [/rcd] [/rsa] [/rnp] [/fcp]

Export syntax

iecon /e /dm [/s:dmserver] [/port:portnumber] {/u:dmusername/p:dmpassword|/dmis} /r:projectname /ex|/csv /xif /f:filepath[/fs:”site and sector list”] [/t:”table list”][/c:”qualified columnlist”] [/op] [/ov] [/mu]

Where


/i

imports data into the Data Manager Server (either theserver indicated by the /s option or the local computer ifthe /s option is not specified) from the file indicated bythe /f option.

/e

exports data from the Data Manager Server (either theserver indicated by the /s option or the local computer ifthe /s option is not specified) to the file indicated by the /foption.

/dm indicates that the destination of the import or the sourceof the export is a Data Manager Server.

/s:dmserveris the Data Manager Server name. If you do not enter avalue, the Data Manager Server on the local computer isused.

/port:portnumber

is the Data Manager port number through which DataManager will connect to the specified Data ManagerServer. If the port number is not specified, the defaultport (7878) will be used.

/u:dmusernameis a valid user ID defined on the Data Manager Server.


/p:dmpassword

is the password for the user ID. If no password is definedfor the user, you must still type /p:


/dmis

indicates that Data Manager uses Windows domainauthentication. If Data Manager uses Windows domainauthentication, use this option only. Do not use/u:dmusername and /p:dmpassword.

/r:projectname is the Data Manager project name.

/ex|/csv /xif/xeda

indicates that the source or destination file is an .xls or.xls file. When the source or destination file is a commaseparated values (.csv) file, you must use the/csv parameter. You can also import data from a Xif fileor from a Xeda URL.

/f:filepath

is the path to the .xls file to export to or to import from.You can specify a new file or you can overwrite anexisting file. To overwrite an existing file, you must usethe /ov option.


/fs:”site andsector list”

option only available when exporting. Provides a quoted,comma-separated list of sites and sectors to export. Forsites, use the site name. For sectors, use the site andsector names delimited by a colon. For example, toexport Site_1 and the first sector of Site_2, you wouldtype:/fs:”Site_1, Site_2:1”

If the list contains only one item, you do not need toenclose the item in quotes.

/t:”tablelist”

provides a quoted, comma-separated list of tables toimport or export.

By default, all tables are exported. For example, toexport the Sites, Sectors, and WiMAX_Sector_Settingstables, you would type:/t:”Sites, Sectors, WiMAX_TDD_Sector_Settings”

/rgoption only available when importing. Replaces all groupswith imported groups.

By default, groups are not replaced.

/rfoption only available when importing. Replaces all flagswith imported flags.

By default, flags are not replaced.

/rs

option only available when importing. Replaces all siteswith imported sites. This option includes the followingoptions (i.e., if you replace sites, you also implicitlyreplace the data included with the sites: exception data,frequency plan data, link budget data, repeaters, andneighbor lists):

/rl

/rn

By default, sites are not replaced.

/rhsn option only available when importing. Replaces HSNexceptions with the imported data.

/rcc option only available when importing. Replaces color codeexceptions with the imported data.

/rce option only available when importing. Replaces carrier


exceptions with the imported data.

/rca option only available when importing. Replaces carrierassignments with the imported data.

/rloption only available when importing. Replaces linkbudget data with imported link budget data.

By default, link budget data is not replaced.

/rnoption only available when importing. Replaces individualneighbor lists with imported neighbor lists.

By default, neighbor lists are not replaced.

/rsuoption only available when importing. Replacessubscriber data with imported subscriber data.

By default, subscriber data is not replaced.

/rcd option only available when importing. Replaces customdefinitions with the imported data.

/rca option only available when importing. Replaces drive testassignments with the imported data.

/rnp option only available when importing. Replaces NPMplatforms with the imported data.


/c:”qualifiedcolumn list”

option only available when exporting to an .xls file.Provides a quoted, comma-separated list of columns toexport. The columns must be qualified by table names inthe form:

"tableName.columnName"

If you want to export all groups or all flags, you can use awildcard symbol(:). For example, to export all flags listedon the Sectors worksheet type/c:"Sectors.Flag:"

For all groups, type:/c:"Sectors.Group:"

By default, all columns are exported.

/opoption only available when exporting to a. xls file. Opensthe file in Excel after exporting.

By default, the file is not opened in Excel.

/ov

option only available when exporting to an .xls file.Overwrites an existing .xls file.

By default the file is not overwritten. If the file indicatedby the /f parameter already exists and you do not use the/ov parameter, and error message is displayed.

/mu option only available when exporting. Overrides theproject settings and exports all values in metric.

Examples

iecon /e /dm /s:ott-1 /u:jdoe /p:passw@rd /r:”New York\EasternRegion” /ex/f:”D:\Projects\Project 1\Project1.xls”

In this example, Planet data would be exported from the EasternRegion projectstored on Data Manager Server ott-1 to the Project1.xls file located atD:\Projects\Project 1.

iecon /i /dm /s:ott-1 /dmis /r:”New York\EasternRegion” /ex/f:”D:\Projects\Project 1\Project1.xls” /t:”WiMAX_TDD_Sector_Settings”

In this example, Windows domain authentication is used. Planet data would beimported from the file Project1.xls to the EasternRegion project stored on Data


Manager Server ott-1. Only the WiMAX_TDD_Sector_Settings worksheet would beimported.

To attach files to a projectUse this procedure to attach files to a project in Data Manager. To list all the FileCategories available in Data Manger, use the following command: iecon /l /fcp/dmis.iecon" /i [/s:dmserver] /r:projectname /file /fcp:"Attachments\Shared"/f:filepath"

Where

/i

imports data into the project currently open in Planetfrom the file indicated by the /f option.


/s:dmserveris the Data Manager Server name. This option is notmandatory. If you do not enter a value, the Data ManagerServer on the local computer is used.

/r:projectname is the Data Manager project name.

/file indicates that the destination is Data Manager (i.e., youwant to submit the file to Data Manager).

/fcp is the destination folder within the project folder.

/f:filepath is the path to the file to attach.

Exampleiecon" /i /s:cag002 /r:"Projects\Ottawa" /file /fcp:"Attachments\Shared"/f:"C:\Projects\Ottawa\Model\ZTU_clutter.cpa"

In this example, the ZTU_clutter.cpa file would be automatically imported into theAttachments\Shared folder within the Ottawa project folder.

To attach files to a site, sector, or antennaUse this procedure to attach files to a site, sector, or antenna in Data Manager.There are two ways to attach files using IECON:

n By specifying a table which lists site, sector, antenna, and attachment path.n By specifying a single attachment to be added to a single entity on thecommand line


Note: No two sectors or antennas can have an attachment with the same filename.

To list all the File Categories available in Data Manger, use the following command:iecon /l /fcp /dmis.

Example 1

Example: iecon /i /dm /u:name /p:pwd /r:"Projects\Lte605" /file/attachToEntities /f:"D:\temp\attachments.csv"

The attachments.csv file would contain the following columns:

Site ID Sector ID Antenna ID FilepathSite_1 1 C:\AttachmentPic.jpgSite_1 2 C:\AntennaAttachment.gif

In this example, the AttachmentPic.jpg is added as an attachment to Site_1, sector 1while the AntennaAttachment.gif is added to Site_1, antenna 2.

Example 2

Example: iecon /i /dm /u:name /p:pwd /r:"Projects\Lte605" /file/fcp:"Attachments\Entity\Site_3\Antennas\1" /f:"D:\temp\attachment.gif"

In this example, attachment.gif is added as an attachment to Site_3, sector 1. Site_3 specifies the site name, Antennas specifies that the next identifier is for anantenna, and 1 specifies the index of the antenna. To attach a file to a sector, thecommand is:

Similarly, to add the attachment to site 3, sector 1, the command is:

iecon /i /dm /u:name /p:pwd /r:"Projects\Lte605" /file/fcp:"Attachments\Entity\Site_3\Sectors\1" /f:"D:\temp\attachment.gif"

Returns and errorsThe iecon utility returns one of the following values:

0 The command was successful.

1 The command was not successful.

All non-error messages are written to stdout and all error messages are written tostderr.


Sample usage scenarioThe following usage scenario outlines a typical set of tasks that a user wouldperform using the iecon utility and provides example commands that would be usedto complete the tasks.

Note: On Windows 7, the default folder is C:\Program Files\InfoVista\Planet 6.x.

In this example, a user wants to export a project stored on the Data Manager Servercagaxw008 to an .xls file, modify the Sectors table, and then import the project backinto the Data Manager Server.

1. User views a list of projects in Data Manager Server.Command: iecon /l /s:cagaxw008 /u:jdoe /p:passwordResult:

2. User exports project data from the New York project to an .xls file.Command: iecon /e /dm /s:ott-1 /u:jdoe /p:password /r:”Projects\New York”/ex /f:c:\projects\DM_New_York\NY.xls

Result:


3. User modifies two rows in the Sectors worksheet in the NY.xls file.4. User imports project data from the NY.xls file to the Data Manager Server.

Command: iecon /i /dm /s:cagaxw008 /u:jdoe /p:password /r:”Projects\NewYork” /ex /f:c:\Projects\DM_New_York\NY.xls /t:“Sectors”

Result:


The IECON lexiconUsing the Import/Export command-line (iecon) utility, you can export Planet data toan Excel (.xls or .xlsx) file or a comma separated values (.csv) file. You can thenmake changes to the data and use the iecon utility again to import the data back intoPlanet or Data Manager.

You can use the iecon utility from within a Command Prompt window or createscripts to automate iecon functions. For example, you can:

n list the projects in Data Manager.n list Planet sessions started by the current user (used in a configuration withmultiple users and multiple Planet sessions on a single computer).

n create a report file containing details about the Xeda import and update.n export data from Planet to a Microsoft Excel (.xls or .xlsx) file.n export data to a .xif file.n Import data from Xeda.n import data into Planet from an .xls or .xlsx file.n export data from Data Manager to an .xls or .xlsx file.n import data into Data Manager from an .xls file.n attach files to a project.

Tip: Use the /help command to view a complete list of available commands.

Syntaxiecon {/i|/e} /pl /f:filepath [/id:sessionid] [/t:"table list"]

iecon {/i|/e} /dm [/s:dmserver] [/dmis | /u:dmusername /p:dmpassword]

[/port:dmportnumber]

/r:projectname

/ex /f:filepath

[/t:"table list"]

iecon {/i|/e} /dm [/s:dmserver] [/dmis | /u:dmusername /p:dmpassword]


/r:projectname

[/t:"table list"]

iecon /l /pl

iecon /l /dm [/s:dmserver] [/dmis | /u:dmusername /p:dmpassword]


iecon /c [/s:dmserver] [/dmis | /u:dmusername /p:dmpassword]



[/fe:filterexpression]

/r:projectname

Parameters/i : Perform import.

/e : Perform export.

/l : Lists available Planet sessions (use with /pl), or

DataManager projects (use with /dm), or

DataManager stored file category's relative paths (use with /dm and /fcp).

/pl : Select Planet for the import/export/list.

/dm : Select DataManager for the import/export/list.

ExportingThe following parameters are required when exporting to an Excel file or commaseparated value files:

/f:filesystempath : Excel file (use with /ex) or

Xif file (use with /xif) or

Xeda server URL (use with /xeda) or

comma separated values folder (use with /csv) or the

file to submit into Data Manager (use with /fcp,

wildcards are supported).

ConnectingThe following parameters are required when connecting to Data Manager:

/s:dmserver : DataManager server, default is the local machine.

/dmis : Use integrated security to connect to datamanager.

/u:dmusername : DataManager username if not using integrated security.

/p:dmpassword : DataManager password if not using integrated security.

/port:dmportnumber : Data Manager Server port number.

/r:dmprojectname : DataManager project name.

/ex : Export/import via Excel.

/csv : Export/import via comma separated value files.


/xif : Export/import via tab separated value file.

/xeda : Import via Xeda web service.

/report:filepath : Create report in a XLS file while importing, use with /i opt

ion.

/file : Submit file(s) into the Data Manager, use with /i and /dm options.

Optional Parameters/t:"table list" : Quoted comma separate list of tables to export/import.

ConnectingThe following parameters can be used when connecting to Planet

/id:sessionid : Planet session identifier.

The following parameters can be used when importing

/rg : Replace group data with the imported data.

/rf : Replace flag data with the imported data.

/rs : Replace all site data with the imported data.

/rhsn : Replace HSN exceptions with the imported data.

/rcc : Replace color code exceptions with the imported data.

/rce : Replace carrier exceptions with the imported data.

/rca : Replace carrier assignments data with the imported data.

/rl : Replace link configuration data with the imported data.

/rn : Replace neighbor lists with the imported data.

/rsu : Replace subscriber data with the imported data.

/rcd : Replace custom definitions with the imported data.

/rsa : Replace drive test assignments with the imported data.

/rnp : Replace npm platforms with the imported data.

/fcp : File category's relative path (i.e, Antennas, Attachments\Shared\Links.

ExportingThe following parameters can be used when exporting.

/mu : Use metric units, ignore project settings for height and distance fields.

/fs:"site list" : Quoted comma separated list of sites to export.


/grp:"group list" : Quoted comma separated list of groups containingsites/sect

ors to export.

The following parameters can be used when exporting to excel.

/op : Opens the excel file after export.

/ov : Overwrite an existing Excel file if it already exists.

The following parameters can be used when exporting from Planet to Excel.

/c:"qualified column list" : Quoted comma separated list of columns.

The columns must be qualified by table names in the form"tableName.columnName" and all required columns must be included (i.e, SiteID,SectorID). For flag and group columns on the Sectors table, wildcards can be usedto specify all flag or all group columns (e.g. Sectors.Flag:, Sectors.Group:).

The following parameters can be used when exporting from Data Manager.

/fe:filterexpression : DataManager filter expression. See the examples below:

"Areas.<area_name>"

"Flags.<flag_name>.<flag_condition_name>"

"Groups.<group_name>"

"Technologies.<technology_name>"

/zip:filePath : Package the project from DataManager into the target zip file.


APPENDIXB

Data Manager Command-Line Utility

Using the Data Manager command-line utility, you can perform all thebasic administrative tasks that are available to you through the DataManager Console.


Using the Data Manager Command-Line Utility 108

Using the Data Manager Command-Line UtilityYou can use the Data Manager command-line utility from within a Command Promptwindow or create scripts to automate Data Manager Server administrative functions.The procedures in this appendix assume that you are familiar with the use ofcommands and switches within a Command Prompt window.

Some of the operations you can perform using the Data Manager command-lineutility include:

n back up Data Manager Servern configure groups.n configure project foldersn configure users

Text conventionsTable 1 lists the conventions used in this appendix to identify required and optionalcommand options.

Table 1 Text conventions


Text Format Description

{ }

Braces are used to identify required options in syntaxdescriptions where there is more than one option. You mustchoose only one of the options. Do not type the braces whentyping the command.

For example:


|

Vertical lines are used to separate options. Use only one of theoptions. Do not type the vertical line when typing the command.

For example:


[ ]

Square brackets are used to identify optional switches in syntaxdescriptions. Do not type the brackets when typing thecommand.

For example:

If the command syntax is iecon /i /pl /f:filepath [/t:”table list”], /t:”table list” is optional.

/x:value

Options indicated by /x:value require a value to be present. Ifthe value contains spaces or unusual characters, you mustenclose the value in quotation marks.

For example:

If the command syntax is /r:projectname, you must enter aproject name (e.g. /r:”New York/East”, where the project path isin quotation marks because it contains a space.)

/x

Options indicated by /x require no value to be present.

For example:

The command /l requires lists the projects contained in DataManager or the sessions started by the current user.

Syntax

The syntax for the Data Manager command-line utility depends on what you want todo.

CHAPTER B│DataManagerAdministratorGuide

The possible scenarios are described in the following sections.

Procedures

To run the Data Manager Server command-line utilityFrom a Windows Command Prompt, from the folder where theDataManagerCmd.exe is located (e.g., Program Files\InfoVista\Data ManagerServer 5), type:DataManagerCmd.exe /user=<value> /password=<value> /host=<value>/port=<value>

Where

/user is the user name with which you want to connect to DataManager Server.

/password is the password with which you want to connect to DataManager Server.

/host is the computer upon which Data Manager Server resides.

/port is the port number through which you want to connect toData Manager Server. The default port is 4321.

Example

Datamanagercmd.exe /host=TS03 /user=paolo

In this example, the user “Paolo” is connecting to TS03 using Windowsauthentication (hence, no password parameter need be specified)

To back up Data Manager Serverbackup /configfile=<value> [/backupfile=<value>]

Where

/configfile is the Data Manager Server configuration file.

/backupfileis an optional backup file location. If you do not specify alocation for the backup file, the location will be that specifiedin the configuration (.xml) file.

Example

n backup /configfile=//server01/DMS_config /backupfile=//server01/DMS_backup.dmbak

In this example, the server will be backed up to a DMS_backup.dmbak file onserver01.


In order to run the backup command, you must have already created a configurationfile.

To configure Data Manager groupsThe following commands are available to configure groups:

n group /view—lists the group names defined in Data Manager.n group /view [/name=<value>]—lists the properties for the specified group.n group /add [/name=<value>]—adds a new group with the specified name.n group /delete /name=<value>—deletes the specified group.n group /edit /name=<value> [/newname=<value>] [/project:<path>=none|read |write|all]—changes the specified group name and properties.

n group /adduser /name=<value> /username=<value>—adds the specifieduser to the group.

n group /deleteuser /name=<value> /username=<value>—deletes thespecified user from the group.

Where

/name is the group name./username is the name of the Data Manager user.

/project:<path> is the Data Manager project name and the path to theproject file.

Examples

/group /add /name=OttawaIn this example, a new group called “Ottawa” would be added to the Data ManagerServer project tree.

To configure Data Manager Server project foldersThe following commands are available to configure Data Manager Server projectfolders:

n project /view [/path=<value>]n project /add /path=<value> [/description=<value>]n project /delete /path=<value>n project /empty /path=<value>n project /edit /path=<value> [/newname=<value>] [/description=<value>]

Where

/path is the path to the project folder./description is the project description.

/project:<path> is the Data Manager project name and the path to theproject file.

CHAPTER B│DataManagerAdministratorGuide

Examples

/project /empty /path=DowntownIn this example, the contents in the project folder “Downtown” are deleted.

To configure Data Manager Server usersThe following commands are available to configure Data Manager Server users:

user /view [/name=<value>]

user /add /name=<value? [/userpassword=<value>] [/integrated=true|false]

user /delete /name=<value>

user /edit /name=<value> [/newname=<value>] [/userpassword=<value>][/integrated=true|false] [/project:<path>=none|read|write|all]

Where

/name is the user name./userpassword is the password for that user.

Examples

user /add /name=MarcoIn this example, a new user by the name of “Marco” is added to the tree view list.


data manager administrator guide - infovistawebhelp.infovista.com/planet/62/content/pdfs/data... ·...

Documents