SJ-20140724091740-024-NetNumen U31 R18 (V12.13.50) ZTE Data Collection Software Installation - 614166

NetNumen U31 R18
Unified Element Management System

ZTE Data Collection Software Installation
Version: V12.13.50
ZTE CORPORATION
No. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://support.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright © 2014 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or
distribution of this document or any portion of this document, in any form by any means, without the prior written
consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by
contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE
CORPORATION or of their respective owners.
This document is provided “as is”, and all express, implied, or statutory warranties, representations or conditions
are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,
title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the
use of or reliance on the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications
covering the subject matter of this document. Except as expressly provided in any written license between ZTE
CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter
herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit the ZTE technical support website http://support.zte.com.cn to inquire for related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
Revision No. Revision Date Revision Reason
R1.0 2014-11-15 First edition
Serial Number: SJ-20140724091740-024
Publishing Date: 2014-11-15 (R1.0)
SJ-20140724091740-024|2014-11-15 (R1.0) ZTE Proprietary and Confidential

Contents
About This Manual ......................................................................................... I
Chapter 1 Overview .................................................................................... 1-1
1.1 System Functions............................................................................................... 1-1
1.2 System Architecture ........................................................................................... 1-1
1.2.1 Hardware Structure .................................................................................. 1-1
1.2.2 Software Architecture ............................................................................... 1-2
1.3 Configuration Requirements................................................................................ 1-2
1.3.1 Server Configuration Requirements ........................................................... 1-2
1.3.2 Client Configuration Requirements ............................................................ 1-3
1.4 Preparation Before Installation ............................................................................ 1-3
1.4.1 Overview of Server Software Installation .................................................... 1-3
1.4.2 Installation Preparations ........................................................................... 1-4
1.4.3 Configurations Before Installation .............................................................. 1-5
Chapter 2 GUI Wizard Installation of ZDC Server.................................... 2-1

2.1 Installing the Master Node of the ZDC Server....................................................... 2-1
2.2 Installing the ZDC Software In Distributed Mode................................................. 2-18
Chapter 3 Silent Installation of ZDC Software ......................................... 3-1

Chapter 4 Configuration After ZDC Server Installation .......................... 4-1
4.1 Configuring the IP Address for EMS Interconnection............................................. 4-1
4.2 Starting the ZDC Server...................................................................................... 4-1
4.3 Configuring the ZDC Server ................................................................................ 4-2
4.3.1 Configuring Global Parameters ................................................................. 4-4
4.3.2 Configuring DB Multiplex Setting ............................................................... 4-5
4.3.3 Configuring FTP Data Sources.................................................................. 4-8
4.3.4 Configuring ETL Multiplex Setting.............................................................4-11
4.3.5 Import a PM Task Template..................................................................... 4-14
4.3.6 Configuring Data Filter Setting ................................................................ 4-15
Figures............................................................................................................. I
Tables ............................................................................................................ III
Glossary .........................................................................................................V

This page intentionally left blank.
II

About This Manual
Purpose
The NetNumen U31 R18 (hereinafter referred to as the NetNumen U31 or the EMS) is an
NE management system that manages wireless NEs.
As an independent system in the NetNumen U31, the ZTE Data Collection (hereinafter
referred to as the ZDC) management system extracts and converts NM performance
service data, and loads it to the database (called the ETL process). It provides data
source services to the ERM report subsystem of the NetNumen U31 and the performance
data query subsystem of the EMS.
This manual describes how to install the ZDC software and configure initial settings.
Intended Audience
This manual is intended for:
l Maintenance engineers
l Software debugging engineers
What Is in This Manual
Chapter 1, Overview Describes functions, system architecture, configuration requirements,

installation contents, and installation preparations of the ZDC system.
Chapter 2, GUI Wizard Describes how to install the server of the ZDC system in GUI wizard
Installation of the ZDC installation mode, including on the master node and distributed slave
Server nodes.
Chapter 3, Silent Installation Describes how to install the ZDC system in silent installation mode.
of ZDC Software
Chapter 4, Configurations Describes how to start the ZDC server and configure it after
After ZDC Server Installation installation.
Conventions
This manual uses the following conventions.
Note: provides additional information about a topic.

II

Chapter 1
Overview
Table of Contents
System Functions.......................................................................................................1-1
System Architecture ...................................................................................................1-1
Configuration Requirements .......................................................................................1-2
Preparation Before Installation ...................................................................................1-3
1.1 System Functions

The ZDC management system enables users to collect data in WEB mode. It provides
extended report management functions, such as collecting data required by the report
system.
Users can query the operational status and database status of the ZDC server, query
statuses of data collection tasks, and start or stop the ZDC server.
1.2 System Architecture

Before installing the ZDC system, users must be familiar with the system architecture. This
section describes the hardware structure and software architecture of the ZDC system.
1.2.1 Hardware Structure

The ZDC system uses a browser/server architecture, where SUN or IBM servers installed
with the Unix system are used on the server. The server is installed with a SybaseIQ
database, and deployed as a stand-alone server.
Because all core functional modules of the ZDC system operate at the server side, and it
maintains and saves quantities of data, the system load at the server side is high. Thus,
high requirements are imposed upon the system configuration of the server side.
Servers are logically divided into hosts and storage devices.
l The hosts process data, so their processing speeds largely determine system
performance. Hosts constitute the bottom-layer physical platform for the ZDC system
to operate on.
l The storage devices store data. Because the ZDC system saves quantities of
important data, storage devices not only include built-in disks on server hosts, but
also include stand-alone data storage devices that provide large capacities and are
highly reliable, such as disk arrays.
1-1

NetNumen U31 R18 ZTE Data Collection Software Installation
It is recommended that databases be deployed on shared disk arrays, to provide

shared access for all service functions.
1.2.2 Software Architecture

The software architecture of the ZDC system consists of server software and clients, see
Figure 1-1.
Figure 1-1 ZDC System Software Architecture
l The server software architecture includes:

à Operating system platform, which is usually the Solaris or AIX system.
à JAVA virtual machine.

à Database platform. The Sybase IQ database system is used.
à ZDC server software. This software provides extended report management
functions developed by ZTE as needed.
l The architecture of a client includes:
à Operating system platform, which is usually the Windows system.
à A Web browser for the client to use the data collection functions.
1.3 Configuration Requirements

1.3.1 Server Configuration Requirements
For the hardware requirements of the ZDC server, refer to Table 1-1.
Table 1-1 ZDC Server Hardware Requirements
Management Object Configuration Requirements
Server type SUN M4000 or IBM P740
1-2

Chapter 1 Overview
Physical memory ≥32 GB
Built-in disk ≥300 GB
For the software requirements of the ZDC server, refer to Table 1-2.
Table 1-2 ZDC Server Software Requirements
Operating system Solaris10, Red Hat Linux, or AIX V6.1
Database Sybase IQ15.4 for SUN Solaris or Sybase IQ15.4

for IBM AIX
1.3.2 Client Configuration Requirements

PCs are used as clients of the ZDC system. For the hardware requirements of clients,
refer to Table 1-3.
Table 1-3 Client Hardware Requirements
CPU 3.0 GHz or faster
Memory 2 GB
Built-in hard disk 60 GB
For the software requirements of clients, refer to Table 1-4.
Table 1-4 Client Software Requirements
Operating system Windows 2000 or above
Browser IE 8.0 and IE 9.0
Document browsing tool MS Office 2000 or above
Antivirus software McAfee, Norton, Trend
1.4 Preparation Before Installation

1.4.1 Overview of Server Software Installation
This procedure describes how to install software on the ZDC server under the following
prerequisites:
1-3

l The ZDC server is installed with the operating system and database system.
l The ZDC server is already installed and configured with the Sybase IQ Multiplex
cluster setting. On each node in the Sybase IQ Multiplex cluster, the ZDC database
instance is started and gets online.
l The operating client is installed with the operating system and a WEB browser.
If the ZDC system is deployed in distributed mode, the following is required in addition:
l The ZDC software is installed on the coordinator server node in the Sybase IQ
Multiplex cluster, which acts as the master node in the distributed ZDC system.
l The distributed ZDC version package is installed on assistant server nodes in the
Sybase IQ Multiplex cluster. These nodes act as the slave nodes in the distributed
ZDC system.
1.4.2 Installation Preparations

For a description of the preparations you must make before installing the ZDC system,
refer to Table 1-5.
Table 1-5 ZDC System Installation Preparations
Item Preparation Requirements
Software installed on the server l Operating system

l Database
l The ZDC database is configured.
Character set of the operating system on the l EN_US.UTF-8

server l Zh_CN.GB18030
root user on the server You have created the root user and know the
password.
Software installed on the client Operating system
Free space on the partition where the ZDC At least 100 GB

software is installed
Free space on the partition where the database 3 TB (for a raw device)
home directory is located 500 GB (for a file system)
Free space on the partition where table space 600 GB (for a raw device)
files of the database are saved 100 GB (for a file system)
ZDC version installation package ZDCV12.13.xx.zip
Remote terminal that is used to install the ZDC The graphic terminal software VNC is installed.
server software
Before installing the ZDC server software, you must know the values of required
parameters. For a description of the parameters, refer to Table 1-6.
1-4

Chapter 1 Overview
Table 1-6 Parameter Preparation Before Installation
Item Parameter Description Value
Database connection Database IP address IP address of the ZDC IP address of the server
parameters during or hostname server where the ZDC server
installation of the ZDC software is installed
server software
Port Port number for the 5555
ZDC database instance
Superuser name of the Name of the superuser dba

database for logging in to the
database
Superuser password Password of the U_tywg_2008

superuser for logging in
to the database
Database parameter Default path for Storage path for /home/sybase/zte_zdc

settings during database files database data files.
installation of the ZDC This directory is
server software already created during
database installation.
Host configuration IP address of the active IP address of the ZDC IP address of the server
parameters during server server where the ZDC server
installation of the ZDC software is installed
server software
1.4.3 Configurations Before Installation

To install and run the ZDC software, you must log in to the operating system as the root
user.
Before installing the ZDC software, configure the following settings.
1. Configure the hosts file on the ZDC server.
a. Log in to the operating system as the root user, and run the following command to
query the server name.
#hostname
b. Get the IP address of the ZDC server.
c. Run the following commands to add the relationship between the IP address and
server name of the ZDC server into the /etc/hosts file.
#cd /etc
#vi hosts
For example, if the IP address of the ZDC server is 10.62.102.242 and the server
name is zdc1, add the following content:
1-5

10.62.102.242 zdc1
Run the following command to save the /etc/hosts file and quit:
# :wq
2. Perform the following steps to upload the version file and decompress it:
a. Upload the compressed ZDC installation file ZDCV12.13.xx.zip to the /home
/zdc_version path (The following steps use this path as an example. You can
select a different path).
b. Run the following commands to enter the folder where the compressed version
file is located, and decompress it.
# cd /home/zdc_version
# unzip ZDCV12.13.xx.zip
3. Run the following commands as the root user to grant read, write, and execute
permissions to the full /home/zdc_version path where the installation script is
saved (including its parent paths).
# chmod –R 755 /home/zdc_version
# chmod 755 /home
4. If a single ZDC server is deployed, set the storage path of the ZDC database. For
mounting points /datafile/main and /datafile/index on the file system of the
disk array, their owners must be the sybase user who has read and write permissions.
# chmod –R 755 /datafile/main
# chmod –R 755 /datafile/index
5. Before installing the ZDC software, run the following command to check whether an
old ZDC version is running on the operating system.
# ps -ef | grep zdc
If an old ZDC version is running, run the kill -9 process id command to kill all processes.
6. If the ZDC database has been installed before, you must clear up all the remaining
contents of the previous database version.
l To reserve previous tables or data, if the current version is incompatible with
the previous version, each product must provide separate scripts. Contact the
technical support of the corresponding product.
l If the previous tables or data is not required, use the unload function of the ZDC
system to clear up the remaining database contents of the previous version.
1-6

Chapter 2
GUI Wizard Installation of
ZDC Server
Table of Contents
Installing the Master Node of the ZDC Server.............................................................2-1
Installing the ZDC Software In Distributed Mode.......................................................2-18
2.1 Installing the Master Node of the ZDC Server

This procedure describes how to install the master node of the ZDC server. The entire
installation process takes 30-90 minutes.
Steps
1. On a remote terminal, connect to the server by using the VNC tool.
2. Open the Terminal window, and run the following commands to start the ZDC
installation wizard.
# cd /zdc_version
# ./setup.sh
When the window displays a message asking you to enter the extraction path, press
the Enter key to use the default path. The version package is extracted automatically.
After that, the installation wizard window is displayed.
3. In the Select Language window, select English from the Language drop-down list,
see Figure 2-1. Click Next.
2-1

Figure 2-1 Select Language Window
Note:
The language that is selected during ZDC server installation must match the default
character set of the root user on the operating system.
4. The License Agreement window is displayed. Select I accept the license

agreement. Click Next.
5. The Select Installation Type window is displayed. Set Installation styles to Initial
installation, and set Installation types to Server Program, see Figure 2-2. Click
Next.
2-2

Chapter 2 GUI Wizard Installation of ZDC Server
Figure 2-2 Select Installation Style Window
The following two Installation styles are available:

l Initial installation: Initial installation indicates a completely new installation. You
need to select the language type and installation path to install the version.
It is applicable to the scenario that the ZDC software is installed for the first time
or reinstalled.
l Delta installation: Delta installation is applicable to the scenario that an old

version has been installed in the system, and you only need to add new functions
based on the old version. In delta installation mode, the system reads the
language type and installation path of the old version to make incremental
installation.
By default, Installation types is set to Server Program.
6. The Management Scale window is displayed. Select the installation scale according
to the prompts and actual requirements, see Figure 2-3. Click Next.
2-3

Figure 2-3 Management Scale Window
l Scale 1 is applicable to the single-server deployment mode. If scale 1 is selected,

the Distributed installation for multiple file systems check box cannot be
selected.
l Scale 2 to Scale 7 are applicable to the distributed deployment mode. If a scale
from Scale 2 to Scale 7 is selected, the Distributed installation for multiple file
systems check box must be selected.
7. The Select Product window is displayed. Select the product packages to be installed,
and set the installation path, see Figure 2-4. Click Next.
2-4

Figure 2-4 Select Product Window
After selecting All Products, you can only select the DAP Wireless Model
Management sub-node under the DAP Platform node.
Set the installation path to /home/zdc.
8. If the configured installation path does not exist, a message box is displayed asking
you whether to create this path. Click Yes.
9. The Database Connection Configuration window is displayed. Set database
connection parameters as needed, see Figure 2-5.
2-5

Figure 2-5 Database Connection Configuration Window
For a description of the parameters in the window, refer to Table 2-1.
Table 2-1 Database Connection Parameter Descriptions
Parameter Description
Database Type Database type of the NM server. Select SYBASE IQ.
Oracle Connection Type This parameter does not need to be set.
Database IP or Hostname IP address of the server where the ZDC server software is
installed.
If the server has multiple IP addresses, select the internal
IP address (namely, the internal IP address that is used to
interconnect with the EMS/ZDC server).
Database Port Port number for the ZDC database instance. Set this
parameter to 5555.
Oracle SID or Service Name This parameter does not need to be set.
Database Superuser Name Name of the superuser for logging in to the database. Set
this parameter to dba.
Password Password of the superuser. Set this parameter to

U_tywg_2008.
10. After setting parameters in the Database Connection Configuration window, click
Test Database Connection. The installation software displays a message notifying
you whether database connection is successful.
2-6

l If the connection fails, adjust the configuration until database connection is

successful.
l If the connection is successful, click Next in the Database Connection
Configuration window.
11. The Select Store Type window is displayed. Select File System or RAW Device from
the Storage Type drop-down list, see Figure 2-6. In distributed deployment mode,
Storage Type must be set to RAW Device.
Figure 2-6 Select Store Type Window
12. The Database Configuration window is displayed. Set the database file saving path
and space size of each database as needed, see Figure 2-7.
2-7

Figure 2-7 Database Configuration Window
l To continue using the old ZDC database on the current server (meaning that an
old ZDC version and an old ZDC database have been installed and configured),
do not modify any configuration in this step. Click Next directly.
l In first installation, you must configure the saving path for ZDC database files in
this step.
i. Highlight the first row as shown in Figure 2-7. The Path Config area is
displayed, see Figure 2-8.
2-8

Figure 2-8 Path Config Window
ii. Click Path Config. The Database Configuration dialog box is displayed.
Modify the default path of database data files to the parent path of the
mounting point on the disk array, see Figure 2-9.
Figure 2-9 Database Configuration Window
For the file system storage type, such as /datafile/zdcdbfile/, set it to

the parent path of the file system’s mounting point on the disk array.
For the raw device storage type, such as /datafile/, set it to the parent
path of the raw device’s mounting point on the disk array.
If the ZDC server is deployed in distributed mode, you must select the parent
path of the raw device’s mounting point on the disk array.
iii. In the DAP Common Config area, double-click a common record. In the
pop-up Database Configuration dialog box, set the public database space
as needed, see Figure 2-10.
2-9

Figure 2-10 Database Configuration Dialog Box
Select the number of database files from the Please select Path number
drop-down list. This number of database file records will be displayed in the
table below. Double-click the Need disk space size (M) cell to modify the
size of each database data file in the unit of MBs.
For the file system storage type, the number and size of data files in the
common database are determined according to the scale of wireless cells
managed by the ZDC. For details, refer to Table 2-2.
Table 2-2 Reference Settings for the Number and Size of Data Files
Number of
Installation Database File Size of Each Database
Scale Cell Scale Paths File (MB)
Scale 1 <=5000 2 200000
Scale 2 <=10000 2 400000
Scale 3 <=20000 4 400000
Scale 4 <=40000 4 800000
Scale 5 <=60000 4 1000000
Scale 6 <=80000 4 1200000
Scale 7 <=100000 4 1400000
2-10

Note:
For the file system storage type, because a file with the size of hundreds of
gigabytes needs to be created under each path. This step requires a long
period of time.
13. The Host Information Configuration window is displayed, see Figure 2-11. Set the
parameters, and then click Next.
Figure 2-11 Host Information Configuration Window
In a single-server system, set The master server address or hostname to the IP

address of the ZDC server. If the master server has multiple IP addresses, select the
internal IP address (namely, the internal IP address that is used to interconnect with
the EMS/ZDC server).
In a dual-server system, set The master server address or hostname to the IP
address of the master ZDC server. Select the The standby server (for hot-standby)
check box, and then enter the IP address of the slave ZDC server in the text box next
to it.
From the Timezone and DST configuration drop-down list, select whether to support
the multi-timezone setting and DST setting.
14. The System Information Detection window is displayed. If the above steps are
correct, the detection will pass successfully, see Figure 2-12. Click Next.
2-11

Figure 2-12 System Information Detection Window
15. The Installation Information Confirmation window is displayed, see Figure 2-13.
Verify that the installation information is correct. Click Install.
Figure 2-13 Installation Information Confirmation Window
The Unzip and Copy Files window is displayed, showing that the system starts to
extract and copy files.
16. After files are extracted and copied completely (see Figure 2-14), click Next.
2-12

Figure 2-14 Unzip and Copy Files Window
17. The Confirm message box is displayed, asking you whether to initialize the configured
database immediately, see Figure 2-15. Click Yes.
Figure 2-15 Confirming to Initialize the Configured Database
18. The Installation Database window is displayed. The system starts to initialize the
configured database.
2-13

19. After database initialization is finished, click Next. The ZDC Configuration Data
Initialization window is displayed, showing the process of ZDC configuration
initialization.
20. After ZDC configuration initialization is finished, click Next. The ZDC System window
is displayed, see Figure 2-16.
If... Then...
The ZDC is installed in distributed mode Go to Step 21..
The ZDC is installed in non-distributed mode Go to Step 27..
Figure 2-16 ZDC System Window
21. From the left tree in the ZDC System window, select Configuration Center >
Common Configuration > Console Configuration to highlight it.
22. In the right area, right-click All console instance(s). Right-click it and select Add
console instance, see Figure 2-17.
2-14

Figure 2-17 Selecting the Add Console Instance Option
23. The Add console instance dialog box is displayed. Enter the IP address of the new
console instance Console 2 (if the slave node has multiple IP addresses, enter the
internal IP address), see Figure 2-18.
Figure 2-18 Add Console Instance Dialog Box
2-15

24. Click OK. The new node Console 2 is added in the right area. Right-click the Console
2 node and select Add process instance, see Figure 2-19.
Figure 2-19 Selecting the Add Process Instance Option
25. The Add process instance dialog box is displayed. From the Please select process
name drop-down list, select DAP ETL Process, see Figure 2-20.
2-16

Figure 2-20 Add Process Instance Dialog Box
26. Click OK. The DAP ETL Process 2 node appears under the Console 2 node in the
console tree, see Figure 2-21.
Figure 2-21 Checking the Console Tree
2-17

If multiple slave ZDC nodes exist, repeat Step 21. to Step 26. to add console
configurations for all slave nodes. Each slave node can only have one DAP ETL
process under its console node.
27. Click Next. The System Initialization window is displayed, showing the system
initialization process.
28. After system initialization is finished, click Next. The Installation Finished window is
Figure 2-22 Installation Finished Window
29. Click Finish. The master node of the ZDC server is installed completely.
– End of Steps –
Related Tasks
After the master node of the ZDC server is installed, you must also perform the operations
described in 2.2 Installing the ZDC Software In Distributed Mode.
2.2 Installing the ZDC Software In Distributed Mode

This procedure describes how to install the ZDC software in distributed mode.
Prerequisite
The master node of the ZDC server has been installed. For details, refer to 2.1 Installing
the Master Node of the ZDC Server.
2-18

Steps
Preparing for the Version for Distributed ZDC Installation
1. After Step 29.in2.1 Installing the Master Node of the ZDC Server is finished, the
Message box is displayed, see Figure 2-23. Click OK.
Figure 2-23 Message Box
2. After preparation for the version for distributed ZDC installation is finished, the
Message box is displayed, see Figure 2-24. Click OK.
Figure 2-24 Message Box
3. The Terminal window is displayed. Run the following command to enter the ZDC
installation directory, and compress the entire distversion folder. The following
commands use the installation directory /home/zdc/ as an example. After the
commands are executed, the distversion.zip file is generated under the
/home/zdc/ directory.
# cd /home/zdc
# zip -r distversion.zip distversion/
Installing the Distributed Version On A Slave Node
4. Upload the distversion.zip file through FTP to the sub-directory on the slave ZDC
node, for example, the /home/zdcdist sub-directory on the slave ZDC node.
5. Run the following commands to enter the sub-directory of the slave ZDC node and
decompress the distversion.zip file. The extracted disversion sub-directory
will be generated under the /home/zdcdist directory.
# cd /home/zdcdist/
# unzip distversion.zip
6. Run the following commands to enter the /home/zdcdist/distversion

sub-directory, modify file execution permissions, and then run the syninstalltoo
l.sh file.
2-19

# cd /home/zdcdist/distversion
# chmod 755 syninstalltool.sh
# ./syninstalltool.sh
7. The system prompts you to enter the target installation path for the ZDC distributed
installation package on this slave node. For example, if /home/zdc2 is an empty
directory that is newly created, enter /home/zdc2, see Figure 2-25.
Figure 2-25 Entering the Installation Path
8. Press the Enter key to start automatic installation. When the operation system prompt
# is displayed, it indicates that the installation is finished.
At this time, the distributed version is installed to the /home/zdc2 directory. The
directory structure is similar to that after a common version is installed, including ums-s
erver, jdk, and uif subdirectories. In addition, a back-end service process is started
automatically (without human intervention). You can run the ps command to verify that
this process exists. For example, after you run the ps -ef | grep zdc2 command, see
Figure 2-26, the com.zte.ums.syn.ServerStarter information in the command
output indicates the back-end service process in the distributed environment.
Figure 2-26 Checking the Service Version
Shielding the Web Server On the Slave Node

9. Enter the ums-server/works/dapetl/deploy/ directory, open the jvmoptions
.sh file, and search for the following lines in this file.
jvm_opts="$jvm_opts -Dprogram.inst.usf.name=aos-webcontainer"
Modify aos-webcontainer into slave. After modification, this line is displayed as follows:
jvm_opts="$jvm_opts -Dprogram.inst.usf.name=slave"
Run the :wq command to save the modification.

10. Enter the ums-server/works/dapetl/deploy/ directory, open the deploy-dap
etl-common.properties file, and add the # symbol at the beginning of each of the
following lines.
jboss.jetty.http.port=31180
jboss.jetty.http.ports=31181
nginx.web.context.path.etl-web=/etl-web
After modification, they are displayed as follows:
2-20

#jboss.jetty.http.port=31180
#jboss.jetty.http.ports=31181
#nginx.web.context.path.etl-web=/etl-web
Run the :wq command to save the modification.

(Optional) Adding the Console Configuration for the Slave Node
11. Log in to the ZDC server and run the following command to enter the sub-directory of
the master node. Run aosfilestorage.
# cd /home/zdc/ums-server/utils/aosfilestorage/
# ./run.sh
If the "AosFileStorage server is started" message is displayed, aosfilestorage is

started and operating properly. Keep this window until console configuration for the
slave node is finished.
12. On a remote terminal, connect to the server by using the VNC tool.
13. Open the Terminal window, run the following command to open the ZDC software
parameter configuration window.
# cd /home/zdc/uif/
# ./runPlugCenter.sh
14. After the ./runPlugCenter.sh parameter is configured, two message boxes are
displayed. Click Yes on the message boxes for confirmation. The Parameter
Configuration dialog box is displayed.
For follow-up operations, refer to Step 21.to Step 26.in 2.1 Installing the Master Node
of the ZDC Server.
15. After console configuration for the slave node is finished, run the following commands
to quit aosfilestorage.
# cd /home/zdc/ums-server/utils/aosfilestorage/
# ./stop.sh
Starting the Master/Slave ZDC Servers
16. After running the following commands, do not enter any parameter, but press the Enter
key directly to start consoles of the master node and all slave nodes. As shown in
Figure 2-27, the master node and slave nodes are all started up.
# cd /home/zdc
# cd ums-server/
# ./console.sh
2-21

Figure 2-27 All Nodes Started
2-22

Chapter 3
Silent Installation of ZDC
Software
This procedure describes how to install the ZDC software in silent mode, including the
following two steps:
1. Generating a silent installation configuration file.
2. Performing silent installation.
Note:
The silent configuration file can only be used in installation of the local server where it is
generated, and cannot be used elsewhere.
The silent installation mode only supports ZDC installation scale 1.
Steps
Generating a Configuration File for Silent Installation
1. Run the following command to enter the ZDC installation software directory zdc_ver
sion.
#cd /zdc_version
2. Run the following command to generate the configuration file for silent installation. The
command format is:
./setup.sh -setupautocfg Configuration file type Output path of configuration file
Table 3-1 Parameter Descriptions for Silent Installation
setupautocfg Enables the mode of generating the configuration file.
Configuration file type Numeric type. Options include: nonlocal, local.

nonlocal indicates a configuration file for silent installation on
a different server.
local indicates a configuration file for silent installation on the
local server.
Output path of configuration Absolute path saving the configuration file.

file The output path of the configuration file must already exist, and
the current user has read/write permissions upon it.
3-1

For example,
l To generate a configuration file for silent installation on the local server, run the
following command:
#./setup.sh -setupautocfg local /datafile/
l To generate a configuration file for silent installation on a different server, run the
following command:
# ./setup.sh -setupautocfg nolocal /datafile/
3. After running the above commands, press the Enter key.

The follow-up operation steps are completely the same as those in GUI installation
mode. For details, refer to Step 3.to Step 15.in 2.1 Installing the Master Node of the
ZDC Server.
4. After files are extracted and copied completely, a message is displayed indicating that
the operation is finished. Click Finish.
5. Verify that the configuration file for silent installation is generated successfully. In
the above example, the silenceinstall-for-localhost.xml file is generated
under the /datafile/ directory, see Figure 3-1.
Figure 3-1 Checking the Configuration File for Silent Installation
6. Copy the silenceinstall-for-localhost.xml file to the decompressed conf

directory. In this example, the directory is: /datafile/ZDC_VERSION/ ZDCV12.1
3.50/conf/, so the following command is executed:
# cp silenceinstall-for-localhost.xml /export/home/ZDC_VERSION/ZDCV12.13.50/conf
7. Run the following command to rename silenceinstall-for-localhost.xml

into auto_installation.xml.
# mvsilenceinstall-for-localhost.xml auto_installation.xml
Performing Silent Installation

8. Run the following commands to perform silent installation. The command format is:
# cd Version file directory
# ./setup.sh Temporary directory Configuration file name Quit or not if system detection fails
For example,
l The version file directory is /datafile/ZDC_VERSION/ ZDCV12.13.50/.
l The temporary directory is /temp/.
3-2

Chapter 3 Silent Installation of ZDC Software
l The installation configuration file is auto_installation.xml.

l Quit or not if system detection fails: false (meaning that the system does not quit
if system detection fails).
Run the following commands:
# cd /datafile/ZDC_VERSION/ ZDCV12.13.50/
# ./setup.sh /temp/ auto_installation.xml false
Then, the silent installation process starts. After the installation process is finished,
the system returns to the command prompt, and the installed version does not start
up automatically.
During the silent installation process, if any script error occurs, the installation process
is not rolled back automatically. Thus, after installation is finished, the version may fail
to be started. In this case, you need to perform manual installation, solve the problem,
and then perform silent installation again.
3-3

3-4

Chapter 4
Configuration After ZDC
Server Installation
After the ZDC server is started, it can operate properly only after the post-installation
configurations are made.
Table of Contents
Configuring the IP Address for EMS Interconnection ..................................................4-1
Starting the ZDC Server .............................................................................................4-1
Configuring the ZDC Server .......................................................................................4-2
4.1 Configuring the IP Address for EMS Interconnection

This procedure describes, after the ZDC server is installed, how to configure the IP address
for EMS interconnection in the configuration file under the directory of the running ZDC
version. This IP address is the IP address of the master EMS node on which the main
EMS process is located.
Steps
1. Open the Terminal window. Run the following command to open the configuration file
deploy-zdc-config.properties:
$cd /ums-server/works/global/deploy/deploy-zdc-config.properties
$vi deploy-zdc-config.properties
This file defines the IP address of the master EMS node on which the main EMS
process is located. That is, in ems-ip-addr=127.0.0.1, 127.0.0.1 needs to be modified
into the IP address of the master EMS node. For example, if the actual IP address of
the master EMS node is 10.92.243.65, this command should be modified into ems-ip
-addr=10.92.243.65.
2. Run the :wq command to save the modification and quit the vi editor.
Restart the ZDC server to make the modification effective.
4.2 Starting the ZDC Server

This procedure describes how to start the ZDC server after the ZDC server software is
installed completely, or stop the ZDC server as needed.
4-1

Steps
1. After the ZDC server is installed completely, enter the /home/zdc/ums-server
folder as the root user, and run the following command to start the console.
# ./console.sh
In the distributed ZDC architecture, when you run the ./console.sh command, a
message is displayed asking you to enter the console that you want to start. You
do not enter any parameter, but press the Enter key directly to start consoles of the
master node and all slave nodes.
If the server software is started properly, the icon is displayed before each process,
indicating that the process is started, see Figure 4-1.
Figure 4-1 Console Window
2. To stop the ZDC server, enter the /home/zdc/ums-server directory, and run the
following command:
#./shutdown-console.sh
If the command window displays shutdown console:console1 success, the ZDC

server is stopped successfully.
4.3 Configuring the ZDC Server

This procedure describes how to configure the ZDC server on the WEB NM platform after
the ZDC server is started. Perform the following steps to open the configuration window:
4-2

Chapter 4 Configuration After ZDC Server Installation
1. In the URL address bar of the IE browser, enter http://IP:21180 (IP should be
replaced into the IP address of the corresponding server), and then press the ENTER
key. The login window of the WEB NM platform for ZDC server is displayed, see Figure
4-2.
Figure 4-2 Login Window of the Web NM Platform for ZDC Server
Note:
l After the ZDC server is installed, the default superuser login name is admin and
the password is null.
l It is recommended the IE 8.0 or higher versions be used to guarantee the display
effect.
2. Enter the user name and password, and click Login. The WEB NM platform window
for the ZDC server is displayed, see Figure 4-3.
Figure 4-3 Web NM Platform of the ZDC Server
4-3

3. Select Data Collection > Parameter Configuration. The Parameter Configuration

window is displayed, see Figure 4-4.
Figure 4-4 Parameter Configuration Window
Perform the following configurations in this window:

l Global parameter configuration
l DB multiplex configuration
l FTP data source configuration
l ETL multiplex configuration
l Data filter configuration
Keep the default settings for other configuration items in this window.
4.3.1 Configuring Global Parameters

This procedure describes how to configure the number of concurrent processes handled
by the ETL.
Prerequisite
The Parameter Configuration window is open.
Steps
1. In the Parameter Configuration window, select Global Configuration > Global
Parameter Configuration in the left navigation tree.The Global Parameter
Configuration page is displayed, see Figure 4-5.
4-4

Figure 4-5 Global Parameter Configuration Page
2. Check whether the values of L (data loading) frequent operation thread pool size
and L (data loading) unfrequent operation thread pool size parameters are both 5.
l Yes → Step 5..
l No → Step 3..
3. In L (data loading) frequent operation thread pool size and L (data loading)
unfrequent operation thread pool size text boxes, enter 5.
4. Click Modify.
5. Click the button to finish global parameter configuration.

4.3.2 Configuring DB Multiplex Setting

When the ZDC server executes an ETL task, it needs to access the database instance,
namely the ZDC database instance of the SybaseIQ database. This procedure describes
how to configured database parameters.
Prerequisite
Steps
1. In the Parameter Configuration window, select Global Configuration > DB
Multiplex Configuration in the left navigation tree. The DB Multiplex Configuration
page is displayed, see Figure 4-6.
4-5

Figure 4-6 DB Multiplex Configuration Page
2. In the toolbar, click the button. In ZDC single-node deployment mode,

the AddDB Multiplex Configuration dialog box is displayed, see Figure 4-7. For
ZDC distributed deployment mode, the AddDB Multiplex Configuration dialog box
is displayed, see Figure 4-8.
Figure 4-7 AddDB Multiplex Configuration Dialog Box - Single-Node Deployment
4-6

Figure 4-8 AddDB Multiplex Configuration Dialog Box - Distributed Deployment
For a description of the parameters, refer to Table 4-1.
Table 4-1 Parameter Descriptions for Adding DB Multiplex Configuration
Database Server Name l If the database server is configured in distributed mode, the
database server name comes from the configuration item in
the zdc.cfg configuration file.
For example, if the zdc.cfg configuration file includes the
configuration item -n 246, set the database server name to 246.
l If the database server is a single server, the database server
name can be self-defined by users.
IP Address Enter the IP address of the database server.
Database Node Type Select Coordinator Node or Assist Node from the drop-down list.
Select the node type based on the role of the node that is determined
by Database Server Name and IP Address parameters.
Server Type Select FTP or SFTP.
FTP Username Enter the FTP user name used to access the ZDC server through
FTP.
FTP Password Enter the FTP password used to access the ZDC server through
FTP.
FTP Port Default: 21.
UMS Install Path Enter the parent directory of ums-server after the ZDC version is
installed, such as /home/zdc1.
It must be a full path that the configured FTP account can access
through FTP.
4-7

3. Click Check. A message box is displayed, indicating that database connection is

successful.
4. Click Confirm. A message box is displayed, indicating that the database multiplex
configuration is successful.
The new database multiplex configuration is displayed in the right list, see Figure 4-9.
Figure 4-9 DB Multiplex Configuration Result
4.3.3 Configuring FTP Data Sources

The ZDC server obtains data files reported by the EMS through FTP. This procedure
describes how to configure EMS data sources of configuration data and performance data.
Prerequisite
Steps
1. In the Parameter Configuration window, select Task Configuration > FTP
Data Source Configuration in the left navigation tree. The FTP Data Source
Configuration page is displayed, see Figure 4-10.
4-8

Figure 4-10 FTP Data Source Configuration Page
2. In the toolbar, click the button. The Add FTP Data Source
Configuration dialog box is displayed, see Figure 4-11. Add FTP data sources for
configuration data.
Figure 4-11 Add FTP Data Source Configuration Page
4-9

Table 4-2 Parameter Descriptions for Adding An FTP Data Source
Task Name Select CM and PM to configure FTP data sources for

configuration data and performance data respectively.
This example configures an FTP data source for CM data first.
Server Type Select the server type. In this example, select FTP.
Server Describe Name Enter a character string that can identify the EMS server.
IP Address Enter the IP address of the EMS server.
FTP Username Enter the name of the user that can log in to the EMS server
through FTP. In this example, set it to uepcommon.
FTP Password Enter the password of the user that can log in to the EMS server
through FTP. In this example, set it to U_tywg_2008_ftp.
FTP Port Enter the port number on the EMS server that users can log in
to through FTP. The FTP port number is usually configured as
21111 or 21.
Download Path l For CM data sources, set the download path to the
/ppus/minos.ppu/minos-pm.pmu/NFS/zdc/cmdata/
directory on the EMS server , under which configuration data
files are saved.
l For PM data sources, set the download path to the
/ppus/minos.ppu/minos-pm.pmu/NFS/zdc/pmdata/
directory on the EMS server , under which performance data
files are saved.
File Coding By default, you do not need to enter any value, but use the default
encoding mode of the operating system.
Time Zone Time zone of the EMS data source.
Support Daylight Saving Select this check box if the EMS supports the DST.
Time
3. Click Confirm. A message box is displayed, indicating that the FTP data source for
CM data is configured successfully.
4. Repeat Step 2 to Step 3 to configure an FTP data source for PM data.
Figure 4-12 shows the configuration results.
4-10

Figure 4-12 FTP Data Source Configuration Results
5. Enter the ums-server/procs/ppus/minos.ppu/minos-pm-slave.pmu/mino

s-zdc-adapter.par/conf directory on the EMS server. Modify the configuration
file zxminos-zdc-config.xml by setting the character string false to true.
After the configuration file is modified, the EMS starts to report performance data and
configuration data immediately without being restarted.
l The EMS starts to report performance data without being restarted.
l The EMS reports configuration data at the scheduled interval of six hours. To
generate and report configuration data immediately, you can restart the EMS
server. After the EMS server is restarted, configuration data is generated and
reported within 15 minutes.
4.3.4 Configuring ETL Multiplex Setting

This procedure describes how to configure the ETL multiplex setting, so that the ZDC
server can extract configuration data and performance data from the EMS, convert them
and then save them in the database.
Prerequisite
Steps
1. In the Parameter Configuration window, select Task Configuration > ETL Multiplex
Configuration in the left navigation tree. The ETL Multiplex Configuration page is
4-11

Figure 4-13 ETL Multiplex Configuration Page
2. In the toolbar, click the button. The Add ETL Multiplex Configuration
dialog box is displayed, see Figure 4-14. Add ETL multiplex setting for configuration
data.
Figure 4-14 Add ETL Multiplex Configuration Page - CM Data
Table 4-3 Parameter Descriptions for Adding ETL Multiplex Configuration Page -
CM Data
Task Name Select CM and PM to configure ETL multiplex settings for

configuration data and performance data respectively.
This example configures ETL multiplex setting for CM data first.
Server Name Enter a character string that can identify the EMS server.
4-12

IP Address Enter the IP address of the ZDC server.

If the server has multiple IP addresses, select the smaller
IP address (namely, the smaller IP address that is used to
interconnect with the EMS/ZDC server).
Node Type Select Multiplex CM node.
3. Click Confirm. A message box is displayed, indicating that the ETL multiplex setting
for configuration data is configured successfully.
4. In the toolbar, click Add. The Add ETL Multiplex Configuration dialog box is
displayed, see Figure 4-15. Add ETL multiplex setting for performance data.
Figure 4-15 Parameter Descriptions for Adding ETL Multiplex Configuration Page -
PM Data
Options for the Node Type parameter include:

l In ZDC single-node mode, select all node types from the Node Type drop-down
list.
l In distributed ZDC multi-node mode:
à For the master node, select Multiplex extrace and transfer node and
Multiplex read node from the Node Type drop-down list.
à For the slave node, select Multiplex load node, Multiplex group node, and
Multiplex read node from the Node Type drop-down list.
5. Click Confirm. A message box is displayed, indicating that the ETL multiplex setting
for performance data is configured successfully.
Figure 4-16 shows the configuration results.
4-13

Figure 4-16 ETL Multiplex Configuration Results
4.3.5 Import a PM Task Template

This procedure describes how to import a PM task template.
The default PM task template is only applicable to the centralized ZDC deployment
(single-node) mode. In distributed ZDC deployment mode, you need to import a PM task
template.
Prerequisite
Acquire the PM-cluster.zip file from the version supplier, and save it to a local directory.
Steps
1. Select Data Collection > Template Management. The Template Management
window is displayed.
2. (Optional) In the Template Management list, select the task named PM, right-click it,
and then select Delete. The Question dialog box is displayed, see Figure 4-17. Click
Yes.
4-14

Figure 4-17 Question Dialog Box
3. Click the button in the toolbar. The Upload dialog box is displayed, see
Figure 4-18.
Figure 4-18 Upload Dialog Box
4. Click the button. In the pop-up Open dialog box, select the PM-cluster.zip file,
and then click Open.
5. In the Upload dialog box, click the button.

6. After the template is uploaded, click Close. The Upload Time of the PM task in the
Template Management window is the most up to date.
4.3.6 Configuring Data Filter Setting

After the ZDC server is installed successfully, by default all performance data collection
items are supported. This procedure describes how to filter unnecessary performance
data collection items as needed.
4-15

Prerequisite
Steps
1. In the Parameter Configuration window, select Task Configuration > Data Filter
Configuration in the left navigation tree. The Data Filter Configuration page is
displayed. Select PM from the Task Name drop-down list, see Figure 4-19.
Figure 4-19 Data Filter Configuration Page
By default, all performance data collection items are selected. You can remove some
collection items as needed. It is not recommended to modify the default setting.
4-16

Figures
Figure 1-1 ZDC System Software Architecture.......................................................... 1-2
Figure 2-1 Select Language Window ........................................................................ 2-2
Figure 2-2 Select Installation Style Window .............................................................. 2-3
Figure 2-3 Management Scale Window .................................................................... 2-4
Figure 2-4 Select Product Window ............................................................................ 2-5
Figure 2-5 Database Connection Configuration Window ........................................... 2-6
Figure 2-6 Select Store Type Window ....................................................................... 2-7
Figure 2-7 Database Configuration Window .............................................................. 2-8
Figure 2-8 Path Config Window ................................................................................ 2-9
Figure 2-9 Database Configuration Window .............................................................. 2-9
Figure 2-10 Database Configuration Dialog Box ..................................................... 2-10
Figure 2-11 Host Information Configuration Window ............................................... 2-11
Figure 2-12 System Information Detection Window................................................. 2-12
Figure 2-13 Installation Information Confirmation Window....................................... 2-12
Figure 2-14 Unzip and Copy Files Window ............................................................. 2-13
Figure 2-15 Confirming to Initialize the Configured Database.................................. 2-13
Figure 2-16 ZDC System Window ........................................................................... 2-14
Figure 2-17 Selecting the Add Console Instance Option ......................................... 2-15
Figure 2-18 Add Console Instance Dialog Box ........................................................ 2-15
Figure 2-19 Selecting the Add Process Instance Option.......................................... 2-16
Figure 2-20 Add Process Instance Dialog Box ........................................................ 2-17
Figure 2-21 Checking the Console Tree.................................................................. 2-17
Figure 2-22 Installation Finished Window................................................................ 2-18
Figure 2-23 Message Box ....................................................................................... 2-19
Figure 2-24 Message Box ....................................................................................... 2-19
Figure 2-25 Entering the Installation Path ............................................................... 2-20
Figure 2-26 Checking the Service Version .............................................................. 2-20
Figure 2-27 All Nodes Started ................................................................................. 2-22
Figure 3-1 Checking the Configuration File for Silent Installation............................... 3-2
Figure 4-1 Console Window...................................................................................... 4-2
Figure 4-2 Login Window of the Web NM Platform for ZDC Server ........................... 4-3
Figure 4-3 Web NM Platform of the ZDC Server ....................................................... 4-3

Figure 4-4 Parameter Configuration Window............................................................. 4-4

Figure 4-5 Global Parameter Configuration Page...................................................... 4-5
Figure 4-6 DB Multiplex Configuration Page ............................................................. 4-6
Figure 4-7 AddDB Multiplex Configuration Dialog Box - Single-Node
Deployment ............................................................................................ 4-6
Figure 4-8 AddDB Multiplex Configuration Dialog Box - Distributed
Deployment ............................................................................................ 4-7
Figure 4-9 DB Multiplex Configuration Result............................................................ 4-8
Figure 4-10 FTP Data Source Configuration Page .................................................... 4-9
Figure 4-11 Add FTP Data Source Configuration Page ............................................. 4-9
Figure 4-12 FTP Data Source Configuration Results............................................... 4-11
Figure 4-13 ETL Multiplex Configuration Page ........................................................ 4-12
Figure 4-14 Add ETL Multiplex Configuration Page - CM Data ................................ 4-12
Figure 4-15 Parameter Descriptions for Adding ETL Multiplex Configuration Page
- PM Data ............................................................................................. 4-13
Figure 4-16 ETL Multiplex Configuration Results .................................................... 4-14
Figure 4-17 Question Dialog Box ............................................................................ 4-15
Figure 4-18 Upload Dialog Box ............................................................................... 4-15
Figure 4-19 Data Filter Configuration Page ............................................................. 4-16
II

Tables
Table 1-1 ZDC Server Hardware Requirements ........................................................ 1-2
Table 1-2 ZDC Server Software Requirements.......................................................... 1-3
Table 1-3 Client Hardware Requirements.................................................................. 1-3
Table 1-4 Client Software Requirements ................................................................... 1-3
Table 1-5 ZDC System Installation Preparations ....................................................... 1-4
Table 1-6 Parameter Preparation Before Installation ................................................. 1-5
Table 2-1 Database Connection Parameter Descriptions .......................................... 2-6
Table 2-2 Reference Settings for the Number and Size of Data Files ...................... 2-10
Table 3-1 Parameter Descriptions for Silent Installation............................................. 3-1
Table 4-1 Parameter Descriptions for Adding DB Multiplex Configuration.................. 4-7
Table 4-2 Parameter Descriptions for Adding An FTP Data Source......................... 4-10
Table 4-3 Parameter Descriptions for Adding ETL Multiplex Configuration Page -
CM Data ................................................................................................ 4-12
III

Tables
IV

Glossary
EMS
- Element Management System
ERM
- Enhanced Report Management
ETL
- Extract,Transform and Load
FTP
- File Transfer Protocol
GUI
- Graphical User Interface
IP
- Internet Protocol
PC
- Personal Computer
SFTP
- Secure File Transfer Protocol
URL
- Uniform Resource Locator
VNC
- Virtual Network Computing
WEB
- Web

SJ-20140724091740-024-NetNumen U31 R18 (V12.13.50) ZTE Data Collection Software Installation - 614166

Uploaded by

Document Information

Original Title

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

SJ-20140724091740-024-NetNumen U31 R18 (V12.13.50) ZTE Data Collection Software Installation - 614166

Uploaded by

Copyright:

Available Formats

NetNumen U31 R18

Unified Element Management System

Revision No. Revision Date Revision Reason

R1.0 2014-11-15 First edition

Serial Number: SJ-20140724091740-024

Publishing Date: 2014-11-15 (R1.0)

SJ-20140724091740-024|2014-11-15 (R1.0) ZTE Proprietary and Confidential

Chapter 2 GUI Wizard Installation of ZDC Server.................................... 2-1

Chapter 3 Silent Installation of ZDC Software ......................................... 3-1

SJ-20140724091740-024|2014-11-15 (R1.0) ZTE Proprietary and Confidential

SJ-20140724091740-024|2014-11-15 (R1.0) ZTE Proprietary and Confidential

What Is in This Manual

Chapter 1, Overview Describes functions, system architecture, configuration requirements,

Note: provides additional information about a topic.

SJ-20140724091740-024|2014-11-15 (R1.0) ZTE Proprietary and Confidential

SJ-20140724091740-024|2014-11-15 (R1.0) ZTE Proprietary and Confidential

1.1 System Functions

1.2 System Architecture

1.2.1 Hardware Structure

SJ-20140724091740-024|2014-11-15 (R1.0) ZTE Proprietary and Confidential

It is recommended that databases be deployed on shared disk arrays, to provide

1.2.2 Software Architecture

Figure 1-1 ZDC System Software Architecture

l The server software architecture includes:

à JAVA virtual machine.

1.3 Configuration Requirements

Table 1-1 ZDC Server Hardware Requirements

Management Object Configuration Requirements

Server type SUN M4000 or IBM P740

SJ-20140724091740-024|2014-11-15 (R1.0) ZTE Proprietary and Confidential

Management Object Configuration Requirements

Physical memory ≥32 GB

Built-in disk ≥300 GB

Table 1-2 ZDC Server Software Requirements

Management Object Configuration Requirements

Operating system Solaris10, Red Hat Linux, or AIX V6.1

Database Sybase IQ15.4 for SUN Solaris or Sybase IQ15.4

1.3.2 Client Configuration Requirements

Table 1-3 Client Hardware Requirements

Management Object Configuration Requirements

CPU 3.0 GHz or faster

Built-in hard disk 60 GB

For the software requirements of clients, refer to Table 1-4.

Table 1-4 Client Software Requirements

Management Object Configuration Requirements

Operating system Windows 2000 or above

Browser IE 8.0 and IE 9.0

Document browsing tool MS Office 2000 or above

Antivirus software McAfee, Norton, Trend

1.4 Preparation Before Installation

SJ-20140724091740-024|2014-11-15 (R1.0) ZTE Proprietary and Confidential

1.4.2 Installation Preparations

Table 1-5 ZDC System Installation Preparations

Item Preparation Requirements

Software installed on the server l Operating system

Character set of the operating system on the l EN_US.UTF-8

Software installed on the client Operating system

Free space on the partition where the ZDC At least 100 GB

ZDC version installation package ZDCV12.13.xx.zip

SJ-20140724091740-024|2014-11-15 (R1.0) ZTE Proprietary and Confidential

Table 1-6 Parameter Preparation Before Installation

Item Parameter Description Value

Superuser name of the Name of the superuser dba