204.4128.29 - DmView-9.0 - Installation Manual

DMVIEW 9.
0
INSTALLATION MANUAL
204.4128.29 rev. 29 Jan/2015
204.4128.29 - DmView-9.0 - Installation Manual.doc - Page 1 of 94

WARRANTY
Quality Management System

certified by DQS in compliance with
ISO9001 Registration No. (287097 QM)
Although every precaution has been taken in the preparation of this document, the Company takes no
responsibility for possible errors or omissions, and it will accept no obligation for damages resulting from
the use of the information contained in this manual. The specifications provided in this manual are subject
to changes without notice, and they will not be recognized as any kind of contract.

CONTACT INFORMATION
To contact the technical support, send suggestions, new functionalities, speak with the sales department,
please use one of the telephone numbers and/or emails provided below:
•Support:
oE-mail: support@datacom.ind.br
oPhone number: +55 51 3933-3122
oFax: +55 51 3358-0101
•Suggestions:
oE-mail: contact.dmview@datacom.ind.br
•Sales
oE-mail: sales@datacom.ind.br
oPhone number: +55 51 3933-3000
oFax: +55 51 3933-3003
•Internet
o www.datacom.ind.br/en
•Address
oDATACOM
oRua América, 1000 – Eldorado do Sul, RS - Brazil
oZIP CODE: 92990-000

CONVENTIONS
In order to make the understanding easier, the following conventions have been adopted throughout this
manual:
hyperlink – Indicates an internet address or an email address.
Command or button – Whenever a software command, button or menu is mentioned, this indication
will be in italic.
#Terminal screen messages and commands are shown as unformatted text,
coming after a # (hash) key.
These notes explain further some detail presented in the text.
This formatting indicates that the text contained herein is very important and that there is risk of damage. It
should be carefully read and it may avoid major difficulties.

MANUALS
The DmView manuals were divided into 5 different parts aiming to better organize them. They are:
• 204.4127.28 - DmView – Web Portal Manual
• 204.4128.28 - DmView – Installation Manual
• 204.4129.28 - DmView – General Operation Manual
• 204.4130.28 - DmView – Ethernet Switches Management Manual
• 204.4131.28 - DmView – PDH-SDH Management Manual
• 184.0010.01 – DmView – DM4600 User Guide
After installing the DmView, you will find the manuals in folder \DmView\Enterprise\doc. If you need any of
these manuals separately, they may also be requested to the support area.

CONTENT
1. Introduction...........................................................................................................8
1.1. Introducing DmView.....................................................................................................8
1.2. DmView Versions..........................................................................................................9
2. Installation requirements.....................................................................................10
2.1. Software and hardware required by DmView.............................................................10
2.2. Complementary Software...........................................................................................11
2.3. Application Server - WildFly........................................................................................12
2.4. MongoDB....................................................................................................................12
2.5. Support to virtual environments.................................................................................12
2.6. Firewall Configuration.................................................................................................13
2.6.1. DmView environment sample drawing....................................................................................13
2.6.2. Application Server > Network Devices ....................................................................................13
2.6.3. Network Devices > Application Server.....................................................................................14
2.6.4. Application Server > Oracle Database/ Mongo Database........................................................14
2.6.5. Application Console > Application Server ...............................................................................14
2.6.6. Application Server > Application Console................................................................................16
2.6.7. Application Console > Network Devices...................................................................................16
2.6.8. Workstations > Application Console.........................................................................................16
2.7. Database.....................................................................................................................17
2.7.1. Oracle 11 Express Edition.........................................................................................................17
2.7.2. Oracle Standard/Enterprise Edition 11g...................................................................................17
2.8. Java (SUN JDK 1.7.0_80)..............................................................................................17
2.9. Minimal Video Resolution...........................................................................................18
3. Oracle Install........................................................................................................19
4. mongo database Install........................................................................................22
4.1. Installing MongoDB (Windows)...................................................................................22
4.2. Mongo Database Backup............................................................................................25
5. application Server - WildFly..................................................................................28
5.1. Application Server – Wildfly installation on Windows ................................................28
5.1.1. Requirements:..........................................................................................................................28
5.1.2. Installation:...............................................................................................................................28
5.2. Application Server - Wildfly Installation on Linux/Solaris............................................28
5.2.1. Requirements:..........................................................................................................................28
5.2.2. Installation:...............................................................................................................................29
5.3. Application Server - WildFly Configuration on Windows/Unix....................................29
5.4. Removing WildFly on Windows...................................................................................33
5.4.1. Removing WildFly from system................................................................................................33
5.5. Removing WildFly on Linux/Solaris.............................................................................33

5.5.1. Removing WildFly from system................................................................................................33
6. Dmview Install......................................................................................................35
6.1. Installing DmView (Windows).....................................................................................35
6.1.1. Enterprise Server......................................................................................................................37
6.1.2. Enterprise Console...................................................................................................................47
6.1.3. Poller Server.............................................................................................................................50
6.1.4. Web Server...............................................................................................................................53
6.1.5. Database Server.......................................................................................................................57
6.2. Installing DmView (Unix)............................................................................................61
6.2.1. Requirements...........................................................................................................................61
6.2.2. Installing MongoDB..................................................................................................................61
6.2.3. Installing Apllication Server – Wildfly.......................................................................................61
6.2.4. Installing DmView.....................................................................................................................61
6.3. Upgrading DmView (Windows/Unix)..........................................................................72
6.4. DmView Settings.........................................................................................................74
6.4.1. Directory Hierarchy..................................................................................................................74
Table 1: Directories Description........................................................................................74
6.4.2. About Window.........................................................................................................................74
6.4.3. DmView Licenses......................................................................................................................76
6.4.4. Nms.conf Files..........................................................................................................................78
6.4.5. Starting DmView Services (Windows Version).........................................................................82
6.4.6. Starting DmView Services (Unix Version).................................................................................82
6.4.7. Pseudo Service.........................................................................................................................83
7. Complementary Configurations............................................................................85
7.1. Adjusting the shrink script..........................................................................................85
7.1.1. Windows...................................................................................................................................85
7.1.2. Solaris/Linux.............................................................................................................................87
7.2. PCGAGETv1 & PCGAGETv2.........................................................................................88
7.2.1. Version 1...................................................................................................................................88
7.2.2. Version 2..................................................................................................................................89
7.3. Scheduled Polling........................................................................................................90
7.4. Configuring Distributed Poller.....................................................................................91

1.INTRODUCTION
1.1.Introducing DmView
DmView is an Integrated Network and Element Management System developed to supervise and
configure Datacom devices, making available functions for supervision, failure, configuration, performance,
inventory, and safety management. The system can either be integrated to other management platforms or
operate independently. It is also possible to use different management architectures, from the field
operation via notebook to a centralized project with redundant application servers and multiple terminal
servers for remote access.
The system allows the access to its functionalities through a user friendly and easy-to-use Graphic
Interface. It allows the simultaneous access of multiple users in distinct management stations, allowing
different operators to manage the same network of Datacom devices. The system users operate with
distinct access levels, and it is possible to restrict the operation by type of device or location. Among the
main DmView functionalities, we have:
• Viewing and monitoring of managed devices, their interfaces, and CPUs, allowing the
identification of the operating status and active alarms.
• Receiving and addressing the events generated by the devices with automatic notification of
failure occurrence and the option to perform a specific action when a certain event is received.
• Running diagnostic actions and viewing performance parameters and counters.
• Full configuration of Datacom devices, including identification and location data records.
• Programmable backup and rotation of managed element configuration storage.
• Tools used to locate devices and their interfaces, including localization by operating status,
location, customer, etc.
• Viewing of Datacom devices through topological maps, making it easier to create locations and
links.
• Tools used for the provision of point-to-point circuits between different elements, allowing the
creation, change and location of circuits in the network.
• Correlation of events by port and by customizable circuit.
• Audit logs for user actions.
• Reports via Web interface, which can be exported to the following formats HTML, PDF, XLS,
XLSX, and CSV, and be sent via email and added to Favorites.
• Support to redundant servers operating in cluster for high automatic availability.
• Support to different operating systems (Microsoft Windows and Linux CentOS) and database
(Oracle).

1.2.DmView Versions
The DmView is available in the following versions:
• Enterprise Server: Is the unrestricted version; It is the most complete DmView management
solution that can be provided, including all the available tools/options on the system.
• Enterprise Console: Install only the administration console; is used for communication between
console and server. This option applies for when there is a server and you want to administrate it
through others machines, so you install the console mode.
• Web Server: This option is only for web view, where it is possible generates reports with
information about devices, circuits, links, users, etc. This mode is intended for those customers
who preferred install in separated environments the Enterprise Server and the Web server or
didn’t choose the web package at the moment of Enterprise Server installation.
• Database Server: to configure just the user database install this version and you may choose
among the options: database creation (Create), tablespaces creation, administration users and
DmView database (Setup and Create) or the update of the existing database (Update).
All these versions are found in a single installer, simply select the desired option at installation as will be
shown in the following sections.

2.INSTALLATION REQUIREMENTS
This chapter will help you install the DmView in computers that use operating systems Linux CentOS,
Windows 7, Windows Server 2008 and Windows Server 2012.
There are six steps to be followed during the installation process, which will be detailed in the next
chapters:
• Software and minimum hardware configuration required by DmView;
• Complementary software;
• Application Server – WildFly;
• Installing DmView;
• DmView licenses;
• Configuring the nms.conf file;
• Starting DmView;
• Mongo DB;
After these steps are followed, DmView will be ready to be run in the computer where it has been installed.
2.1.Software and hardware required by DmView

This section contains information regarding the operating systems in which it is possible to use the
DmView, required software (Database and Java) and server hardware specification for different sizes of
networks.
About the operating systems, the DmView is approved in the following versions:
• Server:
o Windows Server 2008 64 bits;
o CentOS 6.5 64 bits;
• Console:
o Windows 7 64 bits;
o CentOS 6.5 64 bits*;
Database:
o Windows Server 2008/2012 64 bits;
o Oracle Linux Server 5.8 64 bits (Unbreakable).
* Xming is homologated as a remote access software via Windows to Linux console server.

The minimum hardware requirements for DmView usage are the following:
• Processor
◦ Intel Core I5 or higher;

• Memory:
◦ 8 GB RAM;
• HD:
◦ 200 GB;
The additional software programs required by DmView are listed below:
• Database
o Oracle Standard/Enterprise Edition 11g 64 bits (not included in DmView installation);
o Oracle Express Edition 11g. (XE) 64 bits (not included in DmView installation);
• Java
o SUN JDK 1.7.0_80 (from version 6.7 on Java already comes on-board in DmView
installation, therefore, a separate installation is not required);
• MongoDB
o MongoDB 3.0.5 (not included in DmView installation).
• WildFly
o WildFly 8.1.0.Final (not included in DmView installation).
According to the number of elements to be managed and the number of simultaneous accesses to the
software, there is a minimum hardware specification where DmView will be installed. This calculation is
done by analyzing the models of devices that will be managed, the number of accesses, the number of
devices, the desired conditions of availability/redundancy. Contact Datacom so an analysis of the entire
environment can be done and hardware can be specified to support it.
For installation on Windows 7 it is recommended to disable the user account control option. To do it,
simply access the:
Control panel → User Accounts → Change user account control settings.
Enable the ‘do not give notice’, and click on OK.
It is also recommended to run the installer with administration permissions. To do so, click with the right
hand button on the executable and select: “Run as administrator”.
2.2.Complementary Software
Apart from the software from the previous section, DmView requires others for the correct
installation/usage. They should be installed before installing the DmView:
• Microsoft SNMP Agent (This item is an option if the service used for the traps is the Java version);
• Web Browser;
• Microsoft Terminal Service/Remote Desktop (optional tool, useful to export DmView server
screens to desktops of operators).

2.2.1 Microsoft SNMP Agent
Windows SNMP service should be installed in the server before installing the DmView. To do so, please
follow the steps below:
1.Click on the Start Button in the taskbar and select Settings/Control Panel;
2.In the Control Panel, select Add/Remove Programs;
3.In Add/Remove Programs, select Add/Remove Windows Components;
4.In Windows Components, select Management and Monitoring Tools. Click on Details and select
Simple Network Management Protocol;
5.Click on the OK button;
6.When requested, insert the Windows installation CD and click on Ok;
7.For the next step, you just have to click on End in Windows Components.
2.2.2 Web Browser

A Web browser should be installed since the DmView reports are generated by it. See below a list of Web
browsers that can be used:
• Internet Explorer (7.0 or later);
o http://windows.microsoft.com/en-us/internet-explorer/download-ie
• Mozilla Firefox (3.5 or later).
o http://www.mozilla.org/en-US/firefox/new/
2.2.3 Microsoft Terminal Service/Remote Desktop (optional)
In the Windows XP/2003 version or later, the Remote Desktop comes already installed by default when
installing the operating system. In Windows XP only one user can connect to the computer remotely at a
time and Windows 2003 comes with a free license for 2 simultaneous users. In order to increase the
number of simultaneous accesses to the server, in Windows 2003 it is necessary to purchase licenses
from Microsoft.
2.3.Application Server - WildFly

WildFly is an open source application server based on JEE plataform and full deployed on Java
programing. As a result, it may be used in any Operational System that support the language referred,
however the system must be 64 bits.
2.4.MongoDB
MongoDB is a document database that provides high performance, high availability, and easy scalability.
2.5.Support to virtual environments
DmView is supported in virtual environments such as VMWare and VirtualBox, and the memory,
processing, and disk settings should be allocated to this virtual machine, as recommended by DATACOM
upon a previous analysis that will take into account the number of elements to be managed, the device
models, DmView additional options that will be installed/licensed, the number of simultaneous users, high
availability/redundancy, etc.

2.6.Firewall Configuration
For DmView to work, to have access to the devices, database, application servers, and terminal servers, it
is necessary to release Firewall ports. Look at the example in the figure below and the firewall ports that
must be released.
2.6.1.DmView environment sample drawing.
Figure 1.DmView enviroment
2.6.2.Application Server > Network Devices
Ports to open in FW3 as the sample drawing.

No. Port Number Protocol Protocol Family Purpose
1 22 SSH tcp Command line ac-
cess to device.
2 23 Telnet tcp Interactive text-ori-
ented communica-
tion facility.
3 161 SNMP (V1, V2, udp SNMP access.
V3)
4 443 HTTPS (Poller) tcp Monitor, configure
and maintain the
management
devices.
4 69 TFTP tcp Firmware update.
5 80 HTTP tcp Monitor, configure
and maintain the
management
devices.
6 5554 Poller (Datacom tcp Monitor, configure
protocol) and maintain the

management
devices.
2.6.3.Network Devices > Application Server

1 162 SNMP Traps udp SNMP Traps.
2.6.4.Application Server > Oracle Database/ Mongo Database

cess to system.
2 161 SNMP udp SNMP access.
3 443 HTTPS tcp Administration
Console (web in-
terface).
4 1521 Oracle Database tcp Default Oracle
Database connec-
tion port.
5 1514 TCP Syslog over tcp Analyzer access
SSL to traffic log.
6 4560 DBFW internal tcp Incoming syslog
protocol messages from
external web ap-
plication firewall.
7 4600:4680 DBFW internal tcp Incoming traffic
protocol captures from Re-
mote Monitor.
8 5514:5593 Syslog tcp Incoming WAF
(F5) violation
alerts.
9 27017 Mongo Database tcp Default Mongo
Database connec-
tion port.
2.6.5.Application Console > Application Server

1 20 FTP tcp DmView Web Por-
tal.
2 22 SSH tcp Troubleshooting
directly in network

device.
3 23 Telnet tcp Troubleshooting
directly in network
device.
5 80 HTTP tcp DmView Web Por-
tal.
6 81 HTTP tcp DmView Web Por-
tal.
7 8443 HTTPS tcp DmView Web Por-
tal.
8 8081 Wildfly tcp Covers the li-
cense, device
discovery,
EFM/Nx2M circuit
importation, in-
ventory and circuit
merge services.
9 9990 Wildfly tcp The 9990 port is
used to
access the admin-

istration console.
10 6002 Provisioning tcp Perform configura-
tions on equip-
ment and
automatic circuit
provisioning.
11 8082 Provisioning tcp Perform configura-
tions on equip-
ment and
automatic circuit
provisioning.
12 1099 JMX tcp Monitoring the ap-
plication memory
allocation, threads
usage, input and
output operations,
CPU consumption
and processing
time for requests.
13 5557 JMX tcp Monitoring the ap-
plication memory
allocation, threads
usage, input and
output operations,
CPU consumption
and processing
time for requests.

management
devices.
15 61616 JMS tcp ActiveMQ API
used by DmView
for exchange mes-
sages between
the server/con-
sole.
2.6.6.Application Server > Application Console

1 61616 JMS tcp ActiveMQ API
used by DmView
for exchange mes-
sages between
the server/con-
sole.
2.6.7.Application Console > Network Devices

cess to device.
2 23 Telnet tcp Interactive text-ori-
ented communica-
tion facility.
3 161 SNMP (V1, V2, udp SNMP access.
V3)
4 443 HTTPS (Poller) tcp Monitor, configure
and maintain the
management
devices.
5 80 HTTP tcp Monitor, configure
and maintain the
management
devices.
management
devices.
2.6.8.Workstations > Application Console

1 3389 RDP tcp Windows Remote
Desktop access.
2.7.Database
DmView supports the use of three databases: Oracle Standard/Enterprise 10g/11g and Oracle 10/11
Express Edition (XE). We will see in the next topics the recommended databases and how to install them.
2.7.1.Oracle 11 Express Edition

The Oracle 11 Express Edition is the Oracle database free version, and it can be installed in Linux or
Windows 64bits. This version has the following limits:
• 11GB limit for database;

• Limit of one processor in the machine (that is, if the server has two processors one of them will be
ignored by the database;
• Maximum of 1GB of RAM.
Request the Oracle Installation Guide in Windows or in Linux for Datacom (support@datacom.ind.br).
2.7.2.Oracle Standard/Enterprise Edition 11g
The Oracle Standard/Enterprise Edition 11g 64 bits database is recommended for high volumes of data,
which requires high processing and memory capacity or when redundancy and high environment
availability are required.
The Oracle Standard Edition is licensed by processor and does not have memory and disk limit. With
Oracle Standard Edition it is possible to create a RAC (Real Application Cluster) of up to two instances to
work with storage, thus creating a redundant and high availability environment. Another limitation of Oracle
Standard Edition license concerns the number of physical processors in the server, which should be a
maximum of 4 processors. For servers with more than 4 processors, the Enterprise license should be
purchased.
For environments with more than two RAC instances, it is necessary to have the Oracle Enterprise Edition
license, which also counts with other options such as the Dataguard, a disaster recovery tool used to make
online replication of different websites.
Request the Oracle Standard/Enterprise Installation Guide for Datacom (support@datacom.ind.br).
2.8.Java (SUN JDK 1.7.0_80)
One of the pre-requirements to install DmView on Windows is to use SUN JDK 1.7.0_80. Java already
comes in DmView installation; therefore, no further installation is required.
Check the installation directory. There should be a folder called jdk1.7.0_80.

Figure 2. Jdk1.7.0_80
If there is another Java version installed in the machine, it will be ignored by DmView, which uses Jdk
1.7.0_80.
2.9.Minimal Video Resolution

The DmView is designed to be used with a minimum video resolution of 1280x1024. If a lower resolution
will be used, for example, 800x600, some windows may not be displayed in accordance with expectations,
there may be cuts in the window or options that may not be accessed.

3.ORACLE INSTALL
This section describes the procedures for installing Oracle XE in Windows environment as well as the
initial settings that must be performed in the SGBD so that it is suitable for use as a database server for
system Manager. If you want to install the Oracle Standard, please contact the Datacom support.
The installation must be made with the local user server.
1.1.Installling and configuring Oracle XE

1.Run the Oracle XE installer (setup.exe) and wait while the installation files are unpacked.
2.Then in the Install Wizard welcome window click "Next" to start the procedure.
Figure 3.welcome window
3. In the License Agreement window, select “I accept the terms in the license agreement” and then click
Next.
4.In the Choose Destination Location window, either accept the default or click Browse to select a different
installation directory. (Do not select a directory that has spaces in its name.) Then click Next.

Figure 4.Choose destination location
5. In the Specify Database Passwords window, enter and confirm the password ‘nms’ to use for the SYS
and SYSTEM database accounts. Then click Next.
Figure 5.Specify database passwords
6. In the Summary window, review the installation settings, and if you are satisfied, click Install. Otherwise,
click Back and modify the settings as necessary.

Figure 6.Resume installation
7.In the InstallShield Wizard Complete window, click Finish.

4.MONGO DATABASE INSTALL
This chapter guides the steps to install MongoDB. It is recommended install on the same server as Oracle
database, and that the system has at least 3 GB free disk space.
4.1.Installing MongoDB (Windows)

Running the MongoDB installer (We are currently using version 3.0.5, current release), the screen will
display the "Welcome" page, click Next.
Figure 7. Welc
ome screen

Following the "MongoDB License Agreement" is displayed, click the checkbox to accept and click Next.
Figure 8. License Agreement
Click Complete to select the full installation of MongoDB.
Figure 9. Setup Type
To install in a different partition of C:\ you must choose the Custom option.

Click Install to start the installation process.
Figure 10. Install screen
Figure 11. Progress screen

At the end of the installation process, a message informing that the installation was successful, appears.
Click Finish to complete the MongoDB installation process.
Figure 12. Finish screen
4.2.Mongo Database Backup
To create backup of database in mongodb you should use mongodump command. This command will
dump all data of your server into dump directory. There are many options available by which you can limit
the amount of data or create backup of your remote server.
The command will connect to the server running at localhost machine at port 27017 and backup all server
data to /bin/dump/ directory. Access the C:\ProgramFiles\MongoDB\Server\3.0\bin directory and type the
following command:
>mongodump
Output of the command is shown below:

Figure 13.Output do comando ‘mongodump’
This command will backup only specified database at specified path. However, there are lists of available
options that can be used with the mongodump command.
Syntax Description Example
mongodump --host
This commmand will backup all data- mongodump --host localhost
HOST_NAME --port
bases of specified mongod instance. --port 27017
PORT_NUMBER
This command will backup all the data-

mongodump --dbpath DB_PATH bases located in a specific directory mon- mongodump --dbpath
--out BACKUP_DIRECTORY god, and save the result in another direct- /data/db/ --out /data/backup/
ory.
mongodump --collection COLLEC- This command will backup only specified mongodump --collection mycol
TION --db DB_NAME collection of specified database. --db test
To restore backup data mongodb's mongorestore command is used. This command restores all data from
the backup directory.
>mongorestore
Output of the command is shown below:

Figure 14.Output do comando ‘mongorestore’

5.APPLICATION SERVER - WILDFLY
5.1.Application Server – Wildfly installation on Windows
5.1.1.Requirements:
• Java JDK 7 installed on the system.
o In the Windows command prompt, run “java –version” to get the version currently used;
o Command return example: java version "1.7.0_80";
o If your version is lower than 1.7, or the command does not return anything, install a new
version of java on the machine;
o The Installer is always available on the Oracle website. Choose the version for Windows
x64:
 http://www.oracle.com/technetwork/java/javase/downloads/java-archive-
downloads-javase7-521261.html#jdk-7u80-oth-JPR
o At the end of the installation, open a new cmd window and run "java -version" to confirm
the installation.
• Create a system environment variable (“Control Panel → System → System Advanced

Configuration → Advanced → Environment Variables”)
o Name: JAVA_HOME
o Value: directory where Java was installed (ex.: C:\Program Files\Java\jdk1.7.0_80)
• wildfly-8.1.0.Final.zip file (Get this file with the Datacom support).
5.1.2.Installation:
The Application Server - WildFly must be installed before installing DmView and is recommended to do on
the same machine where the DmView will be installed.
The WildFly may be installed in a simplified way, just unzipping the file at C:\
5.2.Application Server - Wildfly Installation on Linux/Solaris
5.2.1.Requirements:
• Create a system environment variable (ex.: export JAVA_HOME=/usr/lib/jvm/jdk1.7.0)
o Name: JAVA_HOME
o Value: directory where Java was installed (ex.: /usr/lib/jvm/jdk1.7.0)
• wildfly-8.1.0.Final.zip file (Get this file with the Datacom support).

5.2.2.Installation:
The Application Server - WildFly must be installed before installing DmView and is recommended to do on
the same machine where the DmView will be installed. Wildfly may be installed in a simplified way, just
unzipping the file at /opt (command: “unzip wildfly-8.1.0.Final.zip”).
5.3.Application Server - WildFly Configuration on Windows/Unix

This configuration is perfomed by DmView installer automatically. Only follow these steps in case you
already previously installed wildfly and you want to do your configuration manually.
1- Access the address http://localhost:9990/ and enter with the user/pass: admin/nms;
2- Click on menu “Configuration (1) > Datasources (2)” and after on “Add (3)”, as the image below:
Figure 15.JDBC Datasources.
3- Add the Datasources:

a. Importation:
- Name: importation-ds
- JNDI: java:/jdbc/importation-ds
- Driver: oracle
- Connection URL: connection String to the database. If Oracle is XE and is in the same
machine of WildFly: jdbc:oracle:thin:@localhost:1521:XE. If Oracle is standard and is in
the same machine of WildFly: jdbc:oracle:thin:@localhost:1521:datacom. If Oracle is in
another machine you need to change the “localhost” by your IP.
- Username: Username used by your DmView to connect to the database, the default is
“nms”;
- Password: Password used by your DmView to connect to the database, the default is
“nms”;
- Security Domain: Don’t need to be filled, can stay empty.
b. Inventory:
- Name: inventory-ds
- JNDI: java:/jdbc/inventory-ds
- Driver: oracle

“nms”;
“nms”;
c. Profiles:
- Name: profiles-ds
- JNDI: java:/jdbc/profiles-ds
- Driver: oracle
“nms”;
“nms”;
d. Nes:
- Name: nes-ds
- JNDI: java:/jdbc/nes-ds
- Driver: oracle
“nms”;
“nms”;
.
e. Status:
- Name: status-ds
- JNDI: java:/jdbc/status-ds
- Driver: oracle
“nms”;
“nms”;

4- After the addition of all Datasources, they should be disable, as the figure below:
Figure 16.JDBC Datasources-Disabled.
5- Select each one of the Datasources added and click on “Enable”, all Datasources must be
activated:
Figure 17.JDBC Datasources-Enabled.
6- Click on “Runtime”, “Manage Deployments”, “Add”:
Figure 18.Add Deployments.

7- Choose the “.ear” file located in “C:\Program Files\DmView\application-server\deployments”
(Windows) or “/opt/DmView/ application-server/deployments” (Unix) and click on “Next” and after
on “Save”.
Figure 19.Deployment Selection.
Figure 20.Verify Deployment Names.
8- Select the Deployment was created and click on “En/Disable” to activate. In the end of the
processing, the deployment should appear Enabled.

Figure 21.Ativando o Deployment.
Figure 22.Deployment ativado.
9- Done! Now the DmView services may be started with success.
5.4.Removing WildFly on Windows

To perform the update of WildFly, it must first be removed according to the steps below.
5.4.1.Removing WildFly from system
1. Stop “NMS Application Server” service;
2. Browse the “C:\wildfly-8.1.0.Final” folder;
3. Run “uninstall-service.bat” to remove the service;
4. Remove “C:\wildfly-8.1.0.Final” folder;
5.5.Removing WildFly on Linux/Solaris

To perform the update of WildFly, it must first be removed according to the steps below.
5.5.1.Removing WildFly from system

The WildFly Application Server may be uninstalled by simply deleting the WildFly Application Server's
installation directory. You will also need to remove the JBOSS_HOME environment variables if it exists in
bashrc or user profile.
Stop the service with:
• /etc/init.d/nms.as stop
Remove the service from the system:

• rm /etc/init.d/nms.as
Remove directory (usually located in /opt):
• rm -r /opt/wildfly-8.1.0.Final
Remove the JBOSS_HOME environment variable from bashrc/bash_profile located in the user home
directory (if any, the variable must be filed within one of these files):
• vi .bashrc
• vi .bash_profile
Apply the changes in the file system:
• source .bashrc
• source .bash_profile

6.DMVIEW INSTALL
6.1.Installing DmView (Windows)

The software can be made available through a link for download or can be provided on CD ROM by
Datacom. To start the installation process, you just have to double click on the installation file.
Figure 23. Installation File
The installation file has its name comprised of the product code “010.0001.83”, the “DmView-Enterprise-
9.0.0-0”, the operation system supported by installation file “windows” and the build or creation date of this
installer “20151215172549”.
The installation checks will be made for the Java and Microsoft SNMP Agent, since, as said in sections 2.1
and 2.2 of this manual, they are pre-requirements for the DmView installation. If any software program
required is not installed, or if it is installed with another version than the specified, the DmView installation
will be stopped.
After reading the license term, the path where the Management Software is installed must be specified.
Then, it will be provided the types of installation, Enterprise Server, Enterprise Console and Database
Server. Each type will be explained next.
The selection of this option must be based on the function that the station where DmView is being installed
will run Application Server, Application Console or Database Server only.

Figure 24.Selection of type of installation
Enterprise Server: Server mode, allows the administration console installation, all services necessary for
the DmView operation, web reports portal and the database creation.
Enterprise Console: DmView Administration Console. This is used when there is a server and you want
to manage it from other machines, so if you install DmView in console mode. This option is not installed
any service in the operating system, only the login.
Poller Server: Poller server creates another poller service instance in a different machine.
Web server: DmView Reports Portal, it must be selected to install. This installer option may be posterior
installed on another server.
Database Server: It must be selected to configure/create the database which will be used by DmView.
Oracle must be previously installed. This installer option may be posterior executed on another server.

6.1.1.Enterprise Server
After selecting the Enterprise Server install type and click next, the following options will be displayed.
Click next to install all the options.
1.1.1.1.Modules
After selecting the install type Enterprise Server and click "next", the options in the figure below will be
displayed. Click "next" to install all the options. If you want to install the database on another server, clear
the "Database Server" now and install then the other server with the database only through the "Database
Server" option.
Figure 25.Packages to be installed configuration.

1.1.1.2.Database Type
Currently, DmView only supports the Oracle database (11g XE, STD or ENT), so click next to confirm the
database. The database may have been previously installed to the installation of DmView.
Figure 26. Selecting the database type.

1.1.1.3.Application Server Parameters
Application Server - WildFly now used by DmView to support new features such as Add / Delete Multiple
Devices, IPSAN circuits Import, License Server, etc. In the future, some old features will also be migrated
to this new platform.
Figure 27.Application Server configuration.
AS Home: It must be filled with the path to the directory where the Application Server – WildFly was
installed. By default, the folder is usually located directory “C:\wildfly-8.1.0.Final”. If there is a previously
configured WildFly installation it is possible to reset the password of the default user "Admin" to its default
value "nms" by selecting the "Yes" button. If it is not necessary to reconfigure the user's password, select
"No".
AS Port: This field comes filled with the Wildfly default port, 8081. In case the user already has another
service in this port, this is the moment to change to another value. When the type of installation is ‘Update’
it will be filled here with the actual port in use by wildfly.

1.1.1.4.Database Parameters
The Oracle database must be installed before you begin installing DmView because the configuration
window "Database Parameters" is displayed during installation, if the "Database Server" module has been
selected. By setting the "Database Parameters", you can create the tablespaces and the DmView schema
in Oracle (Setup and Create), create only the DmView schema in Oracle (Create) or upgrade from an old
version of schema DmView Oracle (Update). The options "Create", "Setup and Create" and "Update" can
only be performed when the installer is running on the server itself (localhost) that is installed Oracle.
Figure 28.Database parameters configuration.
Create: Creates a dmview schema and import an empty database on local Oracle Database. It is
necessary that Oracle has already been installed and system tablespaces created. "Setup and Create"
must be already been run before. It must be run locally on the server running the Oracle.
Setup and Create: Creates the DmView system tablespaces, configure the system parameters, creates
the DmView schema and imports a DmView empty database (without data). In case this option be chosen,
in the next screen it will be presented the directory where is the “Table space folder”, which comes with
“C:\oraclexe\app\oracle\oradata\xe” by default, the Oracle 11 tablespace folder directory. It must be run
locally on the server running the Oracle.
Update: It updates a DmView schema on installed Oracle local machine. It is necessary that Oracle has
already been installed and system tablespaces created. "Setup and Create" must be already been run
before. It must be run locally on the server running the Oracle.
Database URL: Must be filled with the oracle database connection string. Must be always localhost
because this option can only be executed locally.
Schema: Username that you want to create the database schema.
Database password: Password that will be attributed to database schema user used on DmView.
Retype password: Repeat the password to confirm.

We recommend that the options of creating and updating of the database to run locally on the
server that has the database installed.
Figure 29.Database operation confirmation
A confirmation message informing that the operation in the database will be irreversibly appears. If you are
not sure, perform a database backup before proceeding. After be sure the operation can be done, click
"Next".

1.1.1.5.Mongo Database Parameters
The Mongo Database must be installed before you begin installing DmView because the configuration
window "Mongo Database Parameters" is displayed if, and only if, during installation "Database Server"
module has been selected. By configuring the "Mongo Database Parameters" you can indicate to DmView
where your configuration files are.
Figure 30.Mongo database parameters configuration
Mongo Database Folder: directory where the Mongo Database was installed. By default, this field is
already prefilled with the default directory, but the installation was carried out in this field other directory
should be changed (Select is always the full path to the bin directory of MongoDB installation).
Hostname: The server IP where MongoDB has been set (default localhost).
Port: The default port 27017 is used by MongoDB. It can be changed by the user in the mongo.conf
configuration file located in the "conf" folder DmView installation.
Schema: The user configured MongoDB database. By default comes filled with the value "nms". It can be
changed by the user in the mongo.conf configuration file located in the "conf" folder DmView installation.
Database Password: MongoDB database user password. By default comes filled with the value "nms". It
can be changed by user in the mongo.conf configuration file located in the "conf" folder DmView
installation.
Retype Password: MongoDB database user password confirmation. By default comes filled with the
value "nms". It can be changed by the user in the mongo.conf configuration file located in the "conf" folder
DmView installation.

1.1.1.6.Setup Shortcuts
Configuration DmView shortcuts. They can be created for all users or only to the user who is performing
the installation.
Figure 31.Shortcuts selection.

1.1.1.7.Summary
Summary of the options selected for installation.
Figure 32.Installation summary.

1.1.1.8.Copying, Processing e Finishing
Display the installation progress, detailing packages and operations that are being made during
installation.
Figure 33.Copying the installation files.

Figure 34.Processing all the information selected by the user.
Figure 35.Installation completed successfully.

6.1.2.Enterprise Console
Console: Installs only the management console and service used for the communication between the
console and server. Used when there is a server and someone wants to manage it through other
machines. Then DmView is installed in console mode in these other machines.
Figure 36.Selecting the Console mode option.

1.1.1.9.Modules
The "Install Type" "Enterprise Console", all modules to be installed are of system and binding.
Figure 37.Selecting the packages to be installed.
Currently, DmView only supports the Oracle database (11g XE, STD or ENT), so select next to confirm the
database. The database may have been previously installed to the DmView Enterprise Server installation
as it will use the same database server that was configured in the DmView Enterprise Server installation.

Figure 38.Database Type.
1.1.1.11.Select Servers
In this part of the installation, must be configured the parameters for the console connection to the DmView
application server (Nms Services), database server (Database URL), web report server (Web Server URL)
and Application Server - WildFly (AS Address).
Figure 39.Server information configuration.

Database URL: Must be filled with the oracle database connection string used by Enterprise Server.
NMS Services: It must be filled with the DmView server IP which you want to connect.
Web Server: Must be filled with the access address to DmView report portal. If the server was installed
with all options, the Web Server IP is the same of NMS Service.
AS Address: Must be filled with the access address to Application Server. By default the port is 8081.
From this point on, the installation proceeds like the Enterprise Server mode.
6.1.3.Poller Server
Poller: Installs only a Poller Instance. Choose this option if you already have DmView installed and want a
new instance running in another machine.
Figure 40.Selecting the Poller Server mode option.

1.1.1.12.Modules
The "Install Type" "Poller Server", all modules to be installed are of system and binding.
Figure 41.Selecting the packages to be installed.

Figure 42.Database Type.
In this part of the installation, must be configured the parameters for the console connection to the DmView
application server (Nms Services), database server (Database URL), web report server (Web Server URL)
and Application Server - WildFly (AS Address).

Figure 43.Server information configuration.
because this option can only be locally executed.
NMS Services: It must be filled with the DmView server IP which you want to connect.
AS Address: Must be filled with the access address to Application Server. By default the port is 8081.
6.1.4.Web Server
This option is only for web view, where it is possible generates reports with information about devices,
circuits, links, users, etc. This mode is intended for those customers who preferred install in separated
environments the Enterprise Server and the Web server or didn’t choose the web package at the moment
of Enterprise Server installation.

Figure 44.Selecting the Web Server mode.
1.1.1.15.Modules
The "Install Type" "Web Server", all modules to be installed are of system and binding.
Figure 45.Choice of packages to be installed

Figure 46.Database Type

In this part of the installation, must be configured the parameters for the Web Server connection to the
DmView application server (Nms Services), database server (Database URL) and server Application
Server - WildFly (AS Address).
Figure 47.Server configuration
At the moment of this installation is important that the data will be specified at database are according to
the information where is installed the Enterprise server. The IP application server DmView and Application
Server - WildFly are specified in Nms Services and AS Address fields respectively.

6.1.5.Database Server
This mode is just for user database configuration, and may be the database creation (Create), tablespaces
creation, administration users and dmview database (setup and create) or the update of the existing
database (update). In this option Database Server, the DmView won’t be installed.
Important to note that when there is already a database and the user options for Create or Setup and
Create mode, to have one more database in system, the new database credentials must be different from
the old to not delete existing information.
Figure 48.Selecting the Database Server option.

1.1.1.18.Modules
The "Install Type" "Database Server", all modules to be installed are of system and binding.
Figure 49.Choice of packages to be installed

Figure 50.Database Type
1.1.1.20.Database Parameters
The Oracle database must be installed before you begin installing DmView because the configuration
window "Database Parameters" is displayed during the installation of "install type" "Database Server". By
setting the "Database Parameters", you can create the tablespaces and the DmView schema in Oracle
(Setup and Create), create only the DmView schema in Oracle (Create) or upgrade from an old version of
schema DmView Oracle (Update). We recommend the "Create" option, "Setup and Create" and "Update"
to run locally on the server itself (localhost) that is installed Oracle.

Figure 51.Configuring the database and credentials installation options.
Create: Creates a dmview schema and import an empty database on local Oracle Database. It is
necessary that Oracle has already been installed and system tablespaces created. "Setup and Create"
must be already been run before.
Setup and Create: Creates the DmView system tablespaces, configure the system parameters, creates
the DmView schema and imports a DmView empty database (without data). In case this option be chosen,
in the next screen it will be presented the directory where is the “Table space folder”, which comes with
“C:\oraclexe\app\oracle\oradata\xe” by default, the Oracle 11 tablespace folder directory.
Update: when you select the Update mode, the database connection address (Database URL), Schema
and database password must be according to base data which you wish to do update. When you select
this option, the configured database schema will be updated to the version of the new installer.
because this option may only be locally executed.
OBS: We recommend that the options of creating and updating of the database to run locally on
the server that has the database installed.

6.2.Installing DmView (Unix)
Will be installed Linux CentOS 6.
6.2.1.Requirements
• To run DmView installation, use Java 7 for running the installer.
• MongoDB zip archive;
• Application Server – Wildfly zip archive.
6.2.2.Installing MongoDB
This installation is made via a zip file that contains all the content for MongoDB configuration. Follow these
steps:
• From the terminal (console), extract the contents of the zip file from the command:
◦ tar -zxvf mongodb-linux-x86_64-3.0.5.tgz
• Copy the extracted folder to the directory where the MongoDB will run, and set execute
permissions on the folder:
◦ mkdir -p /opt/mongodb
◦ cp -R -n mongodb-linux-x86_64-3.0.5/ /opt/mongodb
• Ensure that the binary files of bin folder are present in the PATH environment variable. To keep
the variable constantly updated, it is recommended to add the following line in the system file
“.bashrc":
◦ export PATH=<mongodb-install-directory>/bin:$PATH
• Before starting MongoDB for the first time, create a directory to be used for writing the MongoDB
process. By default, the directory used by the process is /data/db.
◦ mkdir -p /data/db
• Ensure that the user who is performing the MongoDB configuration has read and write
permissions to the directory.
• Check MongoDB startup process by running the command:
◦ mongod
6.2.3.Installing Apllication Server – Wildfly
This installation is made via a zip file that contains all the content for the Application Server – Wildfly
configuration. Follow these steps:
• From the terminal (console), extract the contents of the zip file from the command:
◦ unzip wildfly-8.1.0.Final.zip
• Copy the extracted folder to the directory where the Application Server - Wildfly will run, and set
execute permissions on the folder:
◦ mkdir -p /opt/wildfly-8.1.0.Final
◦ cp -R -n wildfly-8.1.0.Final/ /opt/wildfly-8.1.0.Final
◦ chmod -R +x /opt/wildfly-8.1.0.Final
Done. The other settings are made by DmView installer, so follow to the next section.
6.2.4.Installing DmView
Copy the installation DmView file (example: 010.0001.83-DmView-9.0.0-0-linux-20151016130459.jar) to

some directory and run the command: " 010.0001.83-DmView-9.0.0-0-linux-20151016130459.jar -console
" to start the installation (without graphical environment), as shown below:
Figure 52.DmView Instalation file

Type “1” to continue.

Figure 53.Running DmView installer
The DmView license agreement will appear, press "Enter" to continue until the end of the contract.
Figure 54.License Contract – 1

Type “1” to accept the license agreement.
Figure 55.License Contract - 2
The directory where DmView will be installed are displayed, press "Enter" to keep the suggested directory
or enter the path to the desired directory, then type "1" to continue.
Figure 56.DmView installation directory
The first option type Enterprise Server will be presented, type "Y" to accept or "N" to move to next option.
The other installation types are: Enterprise Console, Web Server and Database Server, type "1" to accept.
• Enterprise Server: server mode allows the installation of the management console, all
necessary services for DmView operation, web portal reports and database creation.
• Enterprise Console: This is the DmView console installation for consoles machine or user
desktop. When the Enterprise Server option is selected, the console is installed automatically.

• Database Server: Must be selected to configure/create the database that will be used by
DmView. Oracle must have been previously installed. Can be installed later on another server.
• Web Server: DmView Portal reports should be selected if you want to install it. Can be installed
later on another server.
• Poller Server: If you have already installed DmView and would like to have one more instance
installed on another machine, it should select this option.
Figure 57.DmView installation options – 1
After accepting the Enterprise Server mode, the modules database server, web server and application
server will be available for selection and installation. Enter "Y" for each module and type "1" to continue.
Figure 58.DmView installation

options – 2
Enter "Y" to accept the Web Server module installation.
Figure 59.Database type selection
Enter "Y" to accept the Database Server module installation.

Enter "Y" to accept the Database Server module installation, and then press 1 to continue.
Message will be displayed to select the database type being used. The only available option should be
"Oracle". Enter 0 to continue.

the Application Server configuration will be displayed. First indicate the address where the Application
Server is installed, by default the value comes to "/opt/wildfly-8.1.0.Final" folder. If there is a previously
configured WildFly installation it is possible to reset the password for the default user "Admin" to its default
value "nms" by typing 1 for "Yes". If it is not necessary to reconfigure the user's password, type 0 for "No".
Select database target parameter:
1. Create - If there are already tablespaces created, ie, a DmView database previously existed on this
Oracle server.
2. Setup and Create - Being made a new installation of DmView and on this server has never existed a
DmView database. Tablespaces used by DmView will be created automatically.
3. Update - An upgrade of a DmView database that already exists.
Choose one of the options above, according to your need and type the corresponding number: "0", "1" or
"2".
Figure 63.Database creation mode
The default connection URL of the database will be displayed "jdbc:oracle:thin:localhost:1521:xe” type
"Enter" to accept, or enter the URL of the desired bank. Remember to enter the database instance
correctly, it can be xe (when Oracle XE) or the name of the Oracle instance configured (ex: datacom) if
Standard or Enterprise. Note: For "Create" or "Setup and Create" target, the database server must
necessarily be localhost.

Figure 64.Database URL
The default Oracle Schema name will appear as "nms", type "Enter" to accept or enter the name if you
want to change the schema name. Enter and repeat the password to be used. Type "1" to continue.
The Oracle 11g XE tablespace folder will be displayed as the default value, type "Enter" to accept or enter
the correct path. Oracle XE 11, for example, has a different default folder, as shown in the screen example
above (/u01/app/oracle/oradata/xe). Type "1" to continue.
The message "This operation may cause irreversible data loss appears. Proceed anyway?" will be shown,
due to an operation being done in the database that can overwrite existing data. If the settings have been
made correctly, enter "0" then "1" to continue.
Figure 65.Database’s user and tablespace folder
The Mongo Database must be installed before you begin installing DmView because the configuration
window "Mongo Database Parameters" is displayed during installation if the "Database Server" module
was selected. By configuring the "Mongo Database Parameters" you indicate to the DmView where to find
its configuration files.

Figure 66.Database’s user and tablespace folder
Hostname: The server IP where MongoDB has been set (default localhost).
Port: Default port 27017 used by MongoDB. It can be changed by the user in the mongo.conf
configuration file located in the "conf" folder of DmView installation.
Schema: The user configured MongoDB database. By default comes filled with the value "nms". It can be
changed by the user in the mongo.conf configuration file located in the "conf" folder of DmView installation.
Database Password: The password database user configured MongoDB. By default comes filled with the
of DmView installation.
Retype Password: MongoDB database user password confirmation set. By default comes filled with the
of DmView installation.
Type 1 after finishing the Mongo setup to begin the installation of DmView. The installation process will
start, showing the log of each operation being performed.
Figure 67.Installing DmView – 1




Figure 74.Installing DmView - 7
After the installation, the message "BUILD SUCCESSFUL" should appear indicating that the installation
was completed successfully.
After the start of the Wildfly service, DmView services can be started. To do this, run the command:
"/etc/init.d/nms.allservices start".
Figure 75.Starting Dmview Services
DmView services will be started:
Figure 76.DmView services being started
After DmView services start, the user login can be opened:

Figure 77.Opening Dmview Login

6.3.Upgrading DmView (Windows/Unix)
1.1.2.Upgrading DmView
In case user wants to do an upgrade version, he must run the installer in the same way that he did in the
previous installations. In order to it works correctly, all services must be stopped, including Application
Server (Wildfly). The user must follow the steps according the previous sections and choose the
installation folder which DmView is installed. In this moment, the installer will recognize the installed
version and will inform the user that an upgrade will be made, as the figure shows below.
Figure 78.Upgrade Version
After clicking next, proceed as in the previous installations, the screens are the same. Remember that the
Application Server - Wildfly is also upgraded.
To database, three options will be available: “Create”, “Setup and Create” and “Update”. Choose
“Update” option to do not loose your data.

Figure 79.Upgrade Version - database
If the database is installed on another machine, we recommend that the installer to run locally so that
updating the database is made, that is, do not update the base carried out using a "Database URL" from a
remote server.

6.4.DmView Settings
6.4.1.Directory Hierarchy
DmView is comprised of the following directory hierarchy:
Directory Description
/activemq Binaries and message server settings.
/apacheds Binaries and NTP server settings.
It contains the nms-ear.ear file for the WildFly

/application-server
/backup DmView Database backups and event export files.
/bin Application binaries and scripts that interact with binaries.
/conf Logs and services configurations.
/data Directory where lies the nmspatch (file used to create and setup
DmView database)
/doc Documentation.
/ha H.A. configuration scripts and files.
/jdk_1.7.0_80 Java used by DmView.
/lib Libraries used by DmView.
/log DmView log files.
/temp Temp filed created by DmView.
/tomcat Web server used to make reports available.
/trapd Configuration Files of DmView Traps receiver service
/uninstall Files required to uninstall an application.
/utils Useful support programs such as Squirrel;
/xml-rpc Library for xml-rpc
Table 1: Directories Description.
6.4.2.About Window
The About window in the DmView can be accessed in two different ways:
1- Without logging in to DmView, access: Start:Programs:DmView:DmView-Enterprise:DmView About.
2- After logging in to DmView, access: Help:About.

Figure 80. About.
The About window shows system information such as the operating system version that is installed, the
Java version, the installation directory of DmView, and the process number.
In Version we have the information regarding the DmView version that is being used, as well as SW-
Version, Build-On, Database Version, and License (Demo or Enterprise).
The Managed Devices box shows the number of devices that are added to DmView and the maximum
number of devices that the license provided supports.
The Save Info and Feature Details buttons are used in the DmView licensing and will be presented as
follows.
The Contact tab shows the contacts for suggestions, support, and sales.

Figure 81.Contact.
6.4.3.DmView Licenses
After installation, DmView is made available with a license for up to 15 network elements and 5 remote
accesses through DmView Console. The Provisioning functionality is not available.
For the consoles to be used, the license is not required.
To manage the Provisioning functionality in DmView, increase the number of elements to be managed and
increase the number of remote accesses, a license should be generated for this purpose. To do so, the
following steps are required:
• Save the file containing the license data and send it to DATACOM.
• Import the file made available by DATACOM.
The number of elements to be managed, the number of remote accesses, and the Provisioning function-
ality should be previously negotiated with DATACOM Sales Department.

1.Save the file with license data
Click on Start:Programs:Enterprise:DmView About. Open the About window in DmView.
In the About window, you should click on Save Info, which will generate a file containing the
information previously selected.
The generated file should be sent to DATACOM so as the license is released.
2.Importing the file made available by DATACOM
DATACOM should provide the license file, which should be saved in \DmView\Enterprise\, with
the license.dat name.
Then you just have to check the number of elements that can be managed through
Startr:Programs:DmView:Enterprise:DmView About in the Managed Devices section, and the
licensed functionalities through Feature Details, as shown below:
Figure 82. Features available
Provisioning: Allows creating SDH/PDH and Metro Ethernet circuits.

DM881: Allows the addition, management, and configuration of DM881 devices.
DM4000: Allows the addition, management, and configuration of DM4000 line switches.
High Availability: Allows the use of high availability resources from DmView.
MX960: Allows the addition, management, and configuration of Juniper MX960 devices.
MPLS: Allows the use of MPLS in Ethernet Switch devices.
DM4650: Allows editing, managing, and configuration of DM4650 devices.
DM4680: Allows editing, managing, and configuration of DM4680 devices.
DM23X1: Allows editing, managing, and configuration of DM23X1 devices.
Obs.: A specific license is not required to DM4100 line devices, the default license is enough.

6.4.4.Nms.conf Files
DmView has a file called nms.conf where we can specify some important software parameters. This file
can be found in \DmView\Enterprise\.
This file will show the file structure, the parameters that can be configured and its possible values.
The beginning of the file is comprised of the General section, as we see below:
#General
Version=Enterprise-9.0.0-0
LicenseType=Enterprise-Server
•Version: this is an informative parameter, containing the DmView version.
•LicenseType: this specifies whether the application is the DmView or Console server [enterprise-
server / enterprise-console].
The next section is Server NMS.
#Server NMS
Server=localhost
nms.jmx.poller.port=6001
nms.jmx.provisioning.port=6002
provisioning.port=8082
provisioning.timeout=600000
service.xmlrpc.port=8081
service.xmlrpc.ssl.port=8444
service.xmlrpc.ssl.timeout=600000
nms.poller.distributed.enabled=false
nms.window.singleInstance.enabled=true
nms.poller.scheduled.enabled=true
nms.poller.scheduled.cron.expression=0 */6 * * *
•Server: Name or IP of the DmView application server

•nms.jmx,poller,port: Poller service port DmView uses to communicate with the equipment.
•nms.jmx.provisioning: Provisioning service port DmView uses to communicate with the equipment.
•provisioning.port: Port used by the provisioning service.
•provisioning.timeout: Provisioning service timeout.
•service.xmlrpc.port: Port used by XMLRPC service.
•service.xmlrpc.ssl.port: Port used by XMLRPC service.
•nms.poller.distributed.enabled: Configuration to enable distributed poller. For more information on
this feature, please contact support before activating.
•nms.window.singleInstance.enabled: Setting to prevent more than one bayface window is opened
by the same equipment.
•nms.poller.scheduled.enabled: Setting to enable / disable the scheduled polling
•nms.poller.scheduled.cron.expression: Configuration of distributed polling scheduling. For more
detailed information, please go to the section 7.3.
Trap/Event Configuration Section:
#Trap/Event Configuration
UseTrapd=NMSTrapD
TrapdPluginPort=5561
nms.jmx.trapd.port=6003
nms.event.store.interval=1
• UseTrapd: Indicates which traps service will be used by DmView. NMSTrapD is the java service
NMS TrapD.

• TrapdPluginPort: Port where the traps processor hear the interceptor traps in Java. The port used
by default is "5561".
• nms.jmx.trapd.port: Port used by Trapd service.
• nms.event.store.interval: Time in seconds used for recording of events in the database.
#Server Database
DatabaseType=oracle
JdbcUrl=jdbc:oracle:thin:@localhost:1521:xe
•DatabaseType: SGBD used [oracle/firebird];
•JdbcUrl: URL that describes the location of the database to be used. If the database were Oracle the
value would be:
oJdbcUrl=jdbc:oracle:thin:@localhost:1521:datacom;
#Fault Systems
KeepAlive=disable
IntegratedFaultSystems=
KeepAliveRate=20
•KeepAlive: This enables an internal service that sends a trap to the upper level fault system every
“KeepAliveRate” seconds informing which DmView services are operating correctly. Use it together
with “KeepAliveRate” [disable/enable].
•IntegratedFaultSystems: Name(s) or IP(s) and TCP port of high level fault systems to where DmView
should send the traps received [e.g.: 192.168.0.1|162|192.168.1|162]
•KeepAliveRate: Time in seconds between each DmView sent trap informing its correct operation.
Use it together with “KeepAlive”.
Web Section
#Web
ServerWWW=https://localhost:8443/nms/
•Server WWW: Base https address for the NMS Apache Tomcat service.
User preferences Section:
# time unit: hours 32

user.preferences.cache.expire=720

Database configuration parameters and its connections pool:
# Legacy database related configuration

##
# DBMS pool type possible values (c3p0,none)
database.DbmsPoolType=c3p0
database.DbmsPoolOnGuiEnabled=false
database.enableUniqueConnectionOnAutoProv=true
database.enableUniqueConnectionOnLogin=true
database.enableUniqueConnectionOnWeb=true
database.monitor.limits.maxPreparedStatementBatching=500000
##
# <> C3P0 Connection pool configuration <>
##
database.pool.c3p0.acquireIncrement=5
database.pool.c3p0.acquireRetryAttempts=9
# in milliseconds
database.pool.c3p0.acquireRetryDelay=5000
# in milliseconds
database.pool.c3p0.checkoutTimeout=0
# in seconds
database.pool.c3p0.idleConnectionTestPeriod=1800
database.pool.c3p0.minPoolSize=15
database.pool.c3p0.initialPoolSize=15
database.pool.c3p0.maxPoolSize=150
database.pool.c3p0.maxIdleTime=0
database.pool.c3p0.checkoutTimeout=0
database.pool.c3p0.maxStatementsPerConnection=0
database.pool.c3p0.statementCacheNumDeferredCloseThreads=0
database.pool.c3p0.numHelperThreads=3
# Enable database connection leak handling/detection
# in seconds
database.pool.c3p0.unreturnedConnectionTimeout=0
# enable to debug abandoned open connections
database.pool.c3p0.debugUnreturnedConnectionStackTraces=false
##
Then, the section referring to provisioning and Nx2M/EFM circuit importation services (change these
values only if you have knowledge of these features, otherwise contact our support).
##
# Provisioning database related configuration
##
provisioning.db.driver.class=oracle.jdbc.driver.OracleDriver
provisioning.db.url=${JdbcUrl}
##
# Connection pool configuration properties.
##
provisioning.db.pool.acquire.increment=5
provisioning.db.pool.acquire.retry.attempts=9
provisioning.db.pool.acquire.retry.delay=2000
provisioning.db.pool.checkout.timeout=0
provisioning.db.pool.idle.connection.test.period=60
provisioning.db.pool.min.pool.size=2
provisioning.db.pool.max.pool.size=20
provisioning.db.pool.max.idle.time=120
provisioning.db.pool.num.helper.threads=3

Section Application Server Configuration:
# Application Server Configuration

##
nms.as.base.url=http://localhost:8081
##
# Importation
##
importation.uri=${nms.as.base.url}/importation
provisioning.uri=http://localhost:8082/service
nms.discovery.url=${nms.as.base.url}/discovery
nms.inventory.url=${nms.as.base.url}/inventory
license.uri=${nms.as.base.url}/license
merge.uri=${nms.as.base.url}/merge
nms.profiles.uri=${nms.as.base.url}/profiles
nms.nes.uri=${nms.as.base.url}/nes
nms.status.uri=${nms.as.base.url}/status
•nms.as.base.url: Application Server - WildFly URL. If it has been installed on another port or on
another server, this parameter should be modified.
•importation.uri: URL used to contact the importation deployment of WildFly.
•provisioning.uri: URL used to contact the provisioning service. By default it must contain the
DmView server IP and port 8082.
•nms.discovery.url: URL used to contact the discovery deployment of WildFly.
•license.uri: URL used to contact the license deployment of WildFly.
•merge.uri: URL used to contact the merge deployment of WildFly.
•nms.profiles.uri: URL used to contact the profiles deployment of WildFly.
•nms.nes.uri: URL used to contact nes deployment of WildFly.
•nms.status.uri: URL used to contact satus deployment of WildFly.
##
# LDAP Conf
##
ldap.enable=true
In case of LDAP be enabled, the ladp.conf file must be also modified, according to the fields below,
defining the LDAP server configuration. You can find this file at DmView/conf folder.
##
# LDAP Conf
##
url="LDAP server URL"
userDn="Folder path containing the Dn user"
password="Dn userpass"
identifierAttribute="user unic Id Identification Atribute"
Section NES Device Cache configuration
##
#NES Device Cache configuration
##
nes.device.cache.expire.time=6
nes.device.cache.expire.unit=HOURS
nes.device.cache.size=200

Section Status Device Cache configuration
##
# Status Device Cache configuration
##
status.device.cache.expire.time=6
status.device.cache.expire.unit=HOURS
status.device.cache.size=200
NOTE: The default browser configuration, which opens DmView web reports, should be done by editing
file getWin32Browser.bat located in \bin do DmView folder.
Simply add the installation path of the desired browser as follows:
echo off
echo %ProgramFiles%/Internet Explorer/iexplore
6.4.5.Starting DmView Services (Windows Version)

After installed and configured, according to the previous sections, you simply have to start DmView
through Start:Programs:DmView:Enterprise:Start Services.
The services installed by DmView are the following:
• NMS Apache DS: When started it makes the machine an NTP server to be configured in the
devices. Simply add in the device configuration the IP of DmView server as being an NTP server.
• NMS Apache Tomcat: this is the Web Server used to make an interface between the user’s Web
browser and DmView, so as the reports can be generated.
• NMS Event and NMS External Trapd for Win32: services used to receive traps from elements.
• NMS JMS: DmView message server.
• NMS DCB: configuration backup service.
• NMS Poller: service responsible for the polling in the device.
• NMS Probe: service that makes the collection of performance data from the devices.
• NMS Provisioning: service responsible for the automatic provisioning of circuits.
• NMS TrapD: Service used to receive traps. The option for using the NMS External Trapd for
Win32 or the NMS Trap should be configured in the nms.conf.
• NMS XML-RPC: this service allows the integration of other systems with DmView through the
interface of commands and XML-RPC protocol.
• NMS Guardian: service that implements the H.A. in DmView.
Note: The “NMS Application Server” (Service used by WildFly) must be manually started through
the Windows Services window and before the DmView services. See more details in the 4 section.
6.4.6.Starting DmView Services (Unix Version)

To work with services it is necessary to be logged in as a root user. All DmView services are accessed
through the command line:
• /etc/init.d/nms.<service> <command>
in which:

• <service> can be replaced with: rmi, jms, poller, event, trapd, web, probe, dcb, xmlrpc.
• <command> can be replaced with: start, stop, and status* (*the latter is not available in all
services).
To start the rmi service as root, you should type:
• /etc/init.d/nms.rmi start
It’s important to emphasize that it is NEVER necessary to put an “&” at the end of the command since the
prompt is released as soon as the service goes up.
Note:
6.4.7.Pseudo Service
A pseudo service was created (as this is a service that takes care of other services) called nms.allservices,
whose objective is to start and stop the most commonly used services in the operators. It can also be used
to inform the running status of all DmView services.
Today the most common services are:
• JMS.
• Poller.
• Events.
• Provisioning
• Traps.
• Web.
To start the most common services:
• /etc/init.d/nms.allservices start
To stop the most common services:
• /etc/init.d/nms.allservices stop
To obtain the status of ALL services:
• /etc/init.d/nms.allservices status

7.COMPLEMENTARY CONFIGURATIONS
7.1.Adjusting the shrink script

If your database is Oracle XE, it’s interesting once in a while data is shrunk, because its storage capacity
is limited to only 4Gb, and after a while the occupation rate tends to increase significantly. To do so, simply
use the script ‘shrink_xe.bat’ (usually found in “C:\Program Files\DmView\bin”), which can be scheduled to
be run in Windows task scheduler, or by crontab, if the system is linux or solaris.
7.1.1.Windows
Access the Windows task scheduler in Start → Accessories → System Tools → Task Scheduler. Create a
new task, and give it a name.
Figure 83. Creating a task
Access the “Triggers” tab and set the date and time for the task to be run. In the figure below, the script is
scheduled to be run every Monday at 11 p.m.

Figure 84. Triggers tab
Access the Actions tab, click on the New button, and add the shrink_xe.bat file that was previously
commended in the beginning of this section.
Figure 85. Actions tab
After selecting the file, click on the OK button to end the scheduling. To check the final result in the task
scheduler main window, it is possible to see the scheduling in the schedulers library.

Figure 86. Final Result
7.1.2.Solaris/Linux
To set the shrink script in solaris/unix systems, we recommend you use crontab. Crontab is divided into
four different types of runners, where the following is determined in each category:
Type Description
cron.hourly backup will be run every hour.
cron.daily backup will be run once a day (or in pre-established hours).
cron.weekly backup will be run once a week (or in pre-established days).
cron.monthly backup will be run every month.
After choosing how the shrink will be run, simply move the script to the desired cron folder. After that,
select the time for the backup to be run with the vi /etc/crontab command, and then select the time the
script should be run, which should be set as follows:
• In the 1st position the minutes (0-59)

• In the 2nd position the hours (0-23)
• In the 3rd position the day (1-31)
• In the 4th position the month (1-12)
• In the 5th position the week day (mon, tue, wed, thu, fri, sat, sun) or (0-6)

Figure 87. Setting the crontab time
After changing to the time you have chosen, close and save the file with “:wq”. CRON shall run the script
on the time informed in this file.
7.2.PCGAGETv1 & PCGAGETv2
To use the PCGAGETv1 and PCGAGETv2 command it is necessary that Java is previously installed in the
machine or server (in any operating system).
To check the syntax of the commands, simply run command:
• pcgagetv1.jar -X ou pcgagetv1.jar -h ou pcgagetv1.jar -help ou pcgagetv1.jar –help.
• The same parameters to show the syntax in protocol v1 will also work for pcgagetv2.jar.
7.2.1.Version 1
Syntax for command PCGAGETv1:
java -jar pcgagetv1.jar [NXE1] <SERIAL> <IP> <USER> <PASSWORD> <SLOT> <PORT> <COMMAND>
<ARRAY DE BYTES>
• [NXE1] = OPTIONAL. In NxE1 devices it has 4 bytes and in the rest 1 byte (for instance,
devices DM705, DM706C, DM704, and DM991C). This parameter should be used when
making requests in order to pre-establish the size of the DEV field.
• <SERIAL> = Serial number of GET target deice.
• <ARRAY OF BYTES> = IMPORTANT: BYTES ALWAYS IN HEXADECIMAL AND EVERY
BYTE SEPARATED BY SPACE.
Example of command PCGAGETv1:
# java -jar pcgagetv1.jar nxe1 8821107 10.0.10.251 nms nms 0 0 8001

Figure 88. Setting the crontab time
7.2.2. Version 2
Syntax for command PCGAGETv2:
java -jar pcgagetv2.jar <TYPEREQUEST> <IP> <USER> <PASSWORD> <SLOT> <PORT>
<COMMAND> <ARRAY DE BYTES>
• <TYPEREQUEST> = Refers to the type of action the Manager wants to make for a certain
request, and it can be either: info, status, config, test, performance, action.
• <ARRAY OF BYTES> = IMPORTANT: BYTES ALWAYS IN HEXADECIMAL AND EVERY
BYTE SEPARATED BY SPACE.
Example of command PCGAGETv2:
# java -jar pcgagetv2.jar status 10.9.0.41 nms nms 0 0 11022

Figure 89.Example of command PCGAGETv2
7.3.Scheduled Polling
The polling, process responsible for collecting the network devices data, has now the flexibility of
scheduling configuration. In previous DmView releases, it was possible to configure an interval between
pollings (example: each 6 hours); now it is possible to configure specific dates and times (example: every
day beginning at 01:00 a.m,). The configuration model is the same of Cron software of Linux. Cron format
for defining the scheduled polling frequency.
The pattern is a list of five single space-separated fields: minute, hour, day, month, weekday. Month and
weekday names can be given as the first three letters of the English names.
Example patterns:
0**** The top of every hour of every day.

0 8-10 * * * 8, 9 and 10 o'clock of every day.
0/30 8-10 * * * 8:00, 8:30, 9:00, 9:30 and 10 o'clock every day.
0 9-17 * * MON-FRI On the hour nine-to-five weekdays.
0 0 25 12 ? Every Christmas Day at midnight.

7.4.Configuring Distributed Poller
With the distributed poller functionality, it can have more than one active instance of poller, aiming to dis-
tribute the execution of polling between these instances, thus relieving the load on the servers that run the
poller. When more than one instance of poller is running, the first instance that was up is considered the
master instance. Some services will be started only by this instance, since they require only one entry
point. An example is the scheduled polling in the application: it is triggered in the master instance and the
polling requests arriving are distributed among the other instances.
If the master instance fail, one of the remaining instances will take the role.
The scheduled poller settings are held in hazelcast.conf file located in the DmView conf folder. This file
contains the following information:
• hazelcast.jmx=false
Enable/Disable the Hazelcast MBeans monitoring
• hazelcast.group.name=nms
• hazelcast.group.password=nms
Cluster credentials (do not have relation with the database credentials).
• hazelcast.network.port=5701
Port’s configuration that will be used by Hazelcast to communicate with the cluster.
• hazelcast.network.outbound.ports=38001-38010
Outbound ports that will be used (also to communicate with the cluster).
• hazelcast.network.join.tcp-ip.members=127.0.0.1:5701
• hazelcast.network.join.tcp-ip.connection-timeout-seconds=10
Cluster members configuration (IPv4 address) and timeout to be used during the negotiation of a new
node to cluster input. In the members option, all the machines that will be cluster members must be spe-
cified. For this, you must put all IP addresses and their ports (<IP>: <port>), separated by commas (eg, a
valid value for this field is considering three machines with addresses 1.1.1.1, 1.1. 1.2 and 1.1.1.3 would
be:
hazelcast.network.join.tcp-ip.members = 1.1.1.1: 5701,1.1.1.2: 5701,1.1.1.3: 5701
It is highly recommended that ALL hazelcast.conf files of the machines which will be part of the
cluster have the same configuration". That will avoid problems such as:
• Differences in identifying the cluster, in other words, hazelcast.group.name and hazelcast.group.-

password different parameters in each hazelcast.conf file;
• Conflict at port definition to be used by Hazelcast, which means, different hazelcast.network.port
parameters;
• Conflict at the definition of cluster members, mainly at the hazelcast.network.join.tcp-ip.members
parameter.
To configure a scheduled poller instance:
a. It was added a setting parameter at nms.conf file present in the DmView installation
root folder, called nms.poller.distributed.enabled which value will be true or false.

b. Change the nms.poller.distributed.enabled parameter to true.
c. Edit the hazelcast.conf file located at conf folder of the DmView installation, updating it
with the information from others servers configured as Slave, as elucidated above.
d. Start the service NMS Poller. In the DmView logs folder, inside the poller will be created
a file called hazelcast.log. This file contains all the information about the connected in-
stances at the server. On every fail or new connection this file is updated with the follow-
ing information:
Members [1] {
Member [172.23.5.200]:5701 this
e. With the arrival of new poller instances, this message is increased. Example:
Members [3] {
Member [172.23.5.201]:5701 this

Member [172.23.5.202]:5701
Member [172.23.5.203]:5701
}

Phone number: +55 51 3933-3000
Support: +55 51 3933-3122
Fax: +55 51 3933-3003

www.datacom.ind.br/en

204.4128.29 - DmView-9.0 - Installation Manual

Uploaded by

Copyright:

Available Formats

204.4128.29 - DmView-9.0 - Installation Manual

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

204.4128.29 - DmView-9.0 - Installation Manual

Uploaded by

Copyright:

Available Formats

DMVIEW 9.

204.4128.29 - DmView-9.0 - Installation Manual.doc - Page 1 of 94

Quality Management System

204.4128.29 - DmView-9.0 - Installation Manual.doc - Page 2 of 94

oPhone number: +55 51 3933-3122

oFax: +55 51 3358-0101

oPhone number: +55 51 3933-3000

oFax: +55 51 3933-3003

oRua América, 1000 – Eldorado do Sul, RS - Brazil

oZIP CODE: 92990-000

204.4128.29 - DmView-9.0 - Installation Manual.doc - Page 3 of 94

These notes explain further some detail presented in the text.

204.4128.29 - DmView-9.0 - Installation Manual.doc - Page 4 of 94

• 204.4127.28 - DmView – Web Portal Manual

• 204.4128.28 - DmView – Installation Manual

• 204.4129.28 - DmView – General Operation Manual

• 204.4130.28 - DmView – Ethernet Switches Management Manual

• 204.4131.28 - DmView – PDH-SDH Management Manual

• 184.0010.01 – DmView – DM4600 User Guide

204.4128.29 - DmView-9.0 - Installation Manual.doc - Page 5 of 94

204.4128.29 - DmView-9.0 - Installation Manual.doc - Page 6 of 94

204.4128.29 - DmView-9.0 - Installation Manual.doc - Page 7 of 94

• Running diagnostic actions and viewing performance parameters and counters.

• Programmable backup and rotation of managed element configuration storage.

• Correlation of events by port and by customizable circuit.

• Audit logs for user actions.

• Support to redundant servers operating in cluster for high automatic availability.

204.4128.29 - DmView-9.0 - Installation Manual.doc - Page 8 of 94

The DmView is available in the following versions:

204.4128.29 - DmView-9.0 - Installation Manual.doc - Page 9 of 94

• Software and minimum hardware configuration required by DmView;

• Application Server – WildFly;

• Configuring the nms.conf file;

2.1.Software and hardware required by DmView

o Windows Server 2008 64 bits;

o Windows Server 2012 64 bits;

o CentOS 6.5 64 bits;

o Windows Server 2008 64 bits;

o Windows Server 2012 64 bits;

o CentOS 6.5 64 bits*;

o Oracle Linux Server 5.8 64 bits (Unbreakable).

204.4128.29 - DmView-9.0 - Installation Manual.doc - Page 10 of 94

◦ Intel Core I5 or higher;

The additional software programs required by DmView are listed below:

o Oracle Standard/Enterprise Edition 11g 64 bits (not included in DmView installation);

o MongoDB 3.0.5 (not included in DmView installation).

o WildFly 8.1.0.Final (not included in DmView installation).

Control panel → User Accounts → Change user account control settings.

Enable the ‘do not give notice’, and click on OK.

204.4128.29 - DmView-9.0 - Installation Manual.doc - Page 11 of 94

2.In the Control Panel, select Add/Remove Programs;

3.In Add/Remove Programs, select Add/Remove Windows Components;

5.Click on the OK button;

6.When requested, insert the Windows installation CD and click on Ok;

2.2.2 Web Browser

• Internet Explorer (7.0 or later);

• Mozilla Firefox (3.5 or later).

2.2.3 Microsoft Terminal Service/Remote Desktop (optional)

2.3.Application Server - WildFly