Documente Academic
Documente Profesional
Documente Cultură
1.System Principle
2.Client Management
6.System Maintenance
8.Appendix
V100R005
iManager M2000 Intelligent Report System
User Manual
BOM 31013268
Huawei Technologies Co., Ltd. provides customers with comprehensive technical support
and service. Please feel free to contact our local office, customer care center or company
headquarters.
Website: http://www.huawei.com
Email: support@huawei.com
Copyright © 2003 Huawei Technologies Co., Ltd.
Trademarks
All other trademarks mentioned in this manual are the property of their respective
holders.
Notice
The information in this manual is subject to change without notice. Every effort has
been made in the preparation of this manual to ensure accuracy of the contents, but
all statements, information, and recommendations in this manual do not constitute
the warranty of any kind, express or implied.
About This Manual
Version
The product version corresponds to the manual is iManager M2000 Mobile Network
Management System-V100R005.
This manual details the philosophy of the intelligent report system, Client management,
installation and maintenance of the system. It is divided into 6 chapters, followed by the
appendices.
z Module 1 System Principle introduces some basic concepts of the system,
statistics and generation of reports, logical structure of the system and its
functions.
z Module 2 Client Management covers the contents of user/user group
management, data dictionary management and authorization management.
z Module 3 Introduction to Report Designer gives the idea of unitizing the tool to
create reports.
z Module 4 Collection of Original Data includes three parts: Item table mapping,
measurement task registration and data source configuration.
z Module 5 Report Customization Examples details the procedure of defining a
report.
z Module 6 System Maintenance
z Module 7 Installation of Report System
z Module 8 Appendix covers the Conventional SQL Statements, Description of
Multi-object Parameter Structure, and Abbreviations.
Target Readers
Conventions
This manual uses the following conventions:
I. General conventions
Convention Description
Arial Narrow Warnings, Cautions, Notes and Tips are in Arial Narrow.
Convention Description
Alternative items are grouped in braces and separated by vertical bars. One is
{ x | y | ... }
selected.
Alternative items are grouped in braces and separated by vertical bars. A minimum
{ x | y | ... } *
of one or a maximum of all can be selected.
Convention Description
<> Button names are inside angle brackets. For example, click <OK> button.
Window names, menu items, data table and field names are inside square
[]
brackets. For example, pop up the [New User] window.
Format Description
Press the key with the key name inside angle brackets. For example, <Enter>,
<Key>
<Tab>, <Backspace>, or <A>.
Format Description
Press the keys concurrently. For example, <Ctrl+Alt+A> means the three keys
<Key1+Key2>
should be pressed concurrently.
Press the keys in turn. For example, <Alt, A> means the two keys should be
<Key1, Key2>
pressed in turn.
V. Mouse operation
Action Description
Click Press the left button or right button quickly (left button by default).
Double Click Press the left button twice continuously and quickly.
Drag Press and hold the left button and drag it to a certain position.
VI. Symbols
Eye-catching symbols are also used in the manual to highlight the points worthy of
special attention during the operation. They are defined as follows:
Environmental Protection
This product has been designed to comply with the requirements on environmental
protection. For the proper storage, use and disposal of this product, national laws and
regulations must be observed.
HUAWEI
System Principle
User Manual System Principle
iManager M2000 Intelligent Report System Table of Contents
Table of Contents
i
User Manual System Principle
iManager M2000 Intelligent Report System Chapter 1 Overview
Chapter 1 Overview
This module mainly describes the basic concepts concerning the IN report system so
that the user can learn about this system on such aspects as its statistics generation
process, logical structure, functions and interfaces it provides, and how to create a
report which is a common concern among users.
This module describes user / user group management, data dictionary management
and authority management.
This is the preparation for report creation, including three parts: index table mapping,
measurement task registration and data source configuration.
The report designer is the report editing environment. Here you must use tools to
complete the basic design of report style, which is the premise for final report output.
You cannot create complicated reports without this report designer.
Based on the report principles, this module describes how to realize a report
requirement and guides the user to customize reports, namely, it provides an example
to demonstrate the detailed report customizing procedures.
1-1
User Manual System Principle
iManager M2000 Intelligent Report System Chapter 1 Overview
It describes the installation procedures of the report server software, including the
installation of report server software and report server Patch, server unloading,
upgrading and configuration, as well as the installation and configuration of
independent database proxy server.
SQL statements may be used when you create a query. This part briefly describes the
use of some conventional statements.
It is very necessary to understand the multi-object parameter structure. You may use
this structure when you register a measurement task (If multiple object members are
involved).
Appendix C Abbreviations
The report system requires JDK1.3 or above. JDK is the product developed by the third
party, and JDK1.3 raises the demands for different operating systems as follows:
z For the Solaris operating system, Solaris2.6, Solaris2.7 or Solaris2.8 is available.
In the installation package, the JDK1.3 package and its corresponding patch
package are provided.
z For the HP-UX operating system, HP-UX 11.0 or above is required.
z For the IBM's AIX operating system, AIX4 or AIX5 is required.
z For the Windows operating system, Windows 98, Windows 2000, or Windows NT
4.0 or above is required.
1-2
User Manual System Principle
iManager M2000 Intelligent Report System Chapter 2 System Principle
2.1.1 Overview
The Intelligent Report System is a set of powerful data mining tools. Relying on this
system, the user can design adequate report templates, extract expected data from the
specified database, then summarize and calculate these data so as to display and
output meaningful reports, through which the user can easily get all data of the service
system and then make analysis and decisions.
iManager M2000 can quickly trace the users’ requirement for reports and customize the
right report system, which can save enormous workload for maintenance personnel in
report designing. The system automatically analyzes all original data and outputs
statistics reports on the daily or monthly basis, which minimizes the possibility of data
error occurrence caused by manual intervention and makes the data accurate and
convincing.
2.1.2 Glossary
Glossary Description
Report client The report client provides the interfaces of the system administration, report template
design and report query for the report system.
Report server It is used to handle the service request from the report client, and meanwhile returns
the corresponding result to the client. The data collection request will be forwarded to
the database proxy server.
Database Proxy Server It is used to collect the data form the service database, and transmit the result to the
report server in batch, and then the report server will return the result to the report
client.
System database The system database is used to store such system data of the report system as the
user information, user group information, database proxy server information,
datasource information, data dictionary of the business data. The system database
can be accessed via the report server.
Template file The template file is used to define the format of a report, as well as the binary file of
datasource required to be accessed in the format *.FRF. Generally, the template file is
stored in the report server. The report client can keep a copy of the template file.
Report file The report file of the report system is a binary file, which is generated after the report
is queried. It includes the report elements like the table, data and statistic chart in the
*.FRP format. The report file can be viewed with a report browser.
License file The license file is the encrypted text configuration file to control the system authority.
It will be released to users after it is configured by Huawei personnel.
2-1
User Manual System Principle
iManager M2000 Intelligent Report System Chapter 2 System Principle
Glossary Description
Report browser The report browser is a stand-alone program for browsing the report file. With the
browser, the report file generated by the report system can be viewed.
The report system can be divided into three parts, the report client, the report server,
and database proxy server. These three parts coordinately access the service
database opened by the service system. The architecture of the system is shown in
Figure 2-1.
From the figure, it is known that only a report server is allowed in the report system,
whereas multiple report clients in the system. The report server establishes the
licensing mechanism, and meanwhile the number of the clients connected to the report
server cannot exceed to the number of Licenses. Multiple database proxy servers are
available here. Each database proxy server is permitted to access multiple service
databases, that is, each service database can be accessed by multiple database proxy
servers.
2-2
User Manual System Principle
iManager M2000 Intelligent Report System Chapter 2 System Principle
2-3
User Manual System Principle
iManager M2000 Intelligent Report System Chapter 2 System Principle
Note:
HTTP is adopted in the communication between the report client and the report server, and Socket
between the report server and the database proxy server. The database proxy server accesses the
service database via JDBC.
1) Log file
The log file is used to record the operation information and error information, and it is
installed in the log sub-directory of the installation directory in the report server.
2) Template file
The template file is stored in the file system of the report server, and its information is
recorded in the system database. The file is transmitted via HTTP to the report client.
3) Local template file
The local template file is stored in the file format on the local machine.
4) Report file
The report file is stored in the file format on the local machine. The file in common
format can be exported from the report file.
Including:
z HTML (*.htm and *.html)
z TXT (*.txt)
z EXCEL (*.xls)
2-4
User Manual System Principle
iManager M2000 Intelligent Report System Chapter 2 System Principle
The report system is a completely stand-alone system, where the authority and files
can be administered, and the report creation for the service database can be
conducted by accessing the service database.
The report server is the kernel element of the report system, and it provides the
webpage development to the outside and binds the report service program. A user can
access this webpage via a browser, and perform the installation by downloading the
installation package of client software. After the installation, the user can log in to the
report service program via the client software to obtain the services provided by the
server including the user management, datasource management, report and template
management.
I. User management
The administrator can create or modify users or user groups for the report system, and
maintain the user relationship of the system, which is described in detail in the
following.
1) The administrator can create a series of user group with each user group
corresponding to a service (with the License file of each service to distinguish the
services).
2) The administrator can grant the authorities to the user group such as which data
source and template can be accessed, and how much can be applied in the
access.
3) The administrator can create a series of users, each of whom belongs to one or
multiple user groups.
When a user wants to log in to the report system, he should type his ID and password,
and select the corresponding working user group.
The administrator needs to write the architecture information of the service database to
be dealt into the datasource, and he will design the report template file based on these
datasource definitions. Meanwhile, the datasource administrator needs to configure the
datasource information on the basis of the database proxy server installation of the
system, and allocate the database proxy servers employed by each datasource in the
access.
2-5
User Manual System Principle
iManager M2000 Intelligent Report System Chapter 2 System Principle
Note:
The information of a datasource includes the content as follows:
1) The basic information of the datasource such as the IP address and the port of the server where the
datasource is located, type of the database (e.g. Oracle, Informix, etc.), database name, login ID and
password. Via the above information, the system can access the business data.
2) The information about the table and stored procedure of the datasource
3) Defining which of the proxy programs the system can use to access the datasource.
The report management is similar to the file management, and it aims at managing the
report template file, report file and relevant data file.
The design and query of reports involve the database proxy server. A user can design
the report template file and store it in the home directory of the report service program.
These template files are called in the query, and the service databases are accessed
according to the designed content of the template files. Among them, the report service
program is responsible for sending and receiving the data, whereas the database proxy
server aims at the business data collection.
The report template file includes two parts: the format and the datasource definition.
The format of the report is used to define the appearance of the report, such as the
header, footer and heading. The datasource definition of the report is used to define the
tables or the stored procedures of a certain datasource to be accessed, and these
tables and stored procedures should return a result set, which the system employs to
generate a report.
The report file is a binary file, which is generated by the system after the template file
has obtained the data. Its content includes two parts: format of the report and the data
of the report.
Note:
The relevant data information of the management of user, datasource and template is stored in the system
database.
2-1
User Manual System Principle
iManager M2000 Intelligent Report System Chapter 2 System Principle
A user logged in to the report system can manage users, datasources and reports. So
the authority management can be divided into three types, namely, user management,
datasource management and report management.
z User management authority: With the authority, a user can create, modify or
delete a user group, user, authorize a user or change the home user group of a
user, or manage an online user.
z Datasource management authority: With the authority, a user can create, modify
or delete the datasource, table or database proxy server, stored procedure or
range, configure the database proxy server for the datasource, and fetch the
datasource information from the service database system.
z Report management authority: With the authority, a user can create, modify or
delete the report template file, design a template file, and get a report by querying
the template.
For each kind of authority, it can be classified into four levels in an ascending order,
namely, no right, read only, read/write and full rights.
z No right: There is no authority at all.
z Read only: Relevant information can be viewed. For the report management, the
authority is to query reports only.
z Read/write: The relevant information can be modified, but cannot be created,
deleted and renamed.
z Full rights: It means any operation can be performed.
The report system supports the independent authority management mechanism, and it
adopts the user group-user mode.
In general, there are multiple user groups existing in the report system, and each user
group can handle only service, that is, it corresponds to a License file.
There are also multiple users in the report system, and each user can conduct the
management to the users, datasources and reports after he logs in to the report system
via the report system client.
2-2
User Manual System Principle
iManager M2000 Intelligent Report System Chapter 2 System Principle
Note:
1) In the initialization, the system has created the super user group administrators and the super user
admin. During the course of the report system operation, a user can create a new user group and user.
2) Administrators and admin are prohibited from being deleted. Except admin, other users cannot
modify the properties of administrators and admin.
IV. Relationship between the user group authority and the user authority
Note:
1) The user authority is the subset of the user group authority of the home group, that is, the authority of
the user should be no more than that of his home user group.
2) Both the user group authority and the user authority are limited by License.
A user may fall into multiple user groups, but when he intends to log in to the report
system, he can select only a user group. For the details, please refer to Section 1.2.2
“Logging in to the Report System” of Client Management module. Then the current
authority of the user is that of the current user group.
Example:
There is a user a, and he belongs to two user groups, A and B, simultaneously. The
authorities of A and B and the authorities of a in A and B are shown in Table 2-2.
2-3
User Manual System Principle
iManager M2000 Intelligent Report System Chapter 2 System Principle
Datasource
Report management User management
Authority category management
authority authority
authority
Authority of user group A Read-only Full rights Full rights
Authority of user group B Full rights Read-only Read-only
Authority of user a in user group A No right Read/Write Read/Write
Authority of user a in user group B Read/Write No right No right
When “a” logs in to the report system, if he selects user group A, he will have the same
authority as user group A; if he selects user group B, then he has the same authority as
user group B.
Note:
In the report system and the user manual, a certain user’s (or a user group’s) authority sometimes may be
described in a format similar to “1/3/2”. Each number represents a kind of authority, and they respectively
represent the report management authority, user management authority and datasource management
authority from the left to right. The value range of each number is from 0 to 3, respectively corresponding to
four authority levels, no right, read-only, read/write and full rights in an ascending order. So, 1/3/2 means
that a user’s (or a user group’s) report management authority is read-only, the user management authority
is full rights, and the datasource management authority is read/write.
2.5.1 Overview
The Intelligent Report System has powerful customization and statistical functions,
mainly including:
z Powerful report design function
z Flexible report customization function
z Convenient report statistics
z Independence from the service system
z Supplying report browser
z Supporting the distributed large-capacity service system
z Various report I/O formats
z Strict authority control
z Security guarantee
z Supporting multiple data sources access
2-4
User Manual System Principle
iManager M2000 Intelligent Report System Chapter 2 System Principle
2.5.2 Functions
With the report design function provided by the Report System, report template files in
a fixed format can be designed and called by different users, which avoids design
duplication.
Besides, report designers can create, modify, delete or save report template files any
time. The report template files can be conveniently updated and distributed in time. The
operator can select any report template file within his authority and execute report
statistics. This is applicable for all common report formats at any complication degree.
During report designing, the preview function is supported, which enables the designer
to get a general view of the report being designed at any time and zoom the report as
required. When the report format is designed, the report content can be designed
conveniently according to the detailed statistics.
Data of each report can be directly queried through the defined SQL statement or
obtained by the invoked store procedure.
The system provides simple report customization functions for report designers who
may not well understand the SQL and the store procedures.
The report customization interface is like a Wizard interface, which guides the user to
fill in the related information step by step and generate a report conveniently. When the
report is invoked again, the user can modify the customization information directly
without repeating the configuration.
2-5
User Manual System Principle
iManager M2000 Intelligent Report System Chapter 2 System Principle
The system provides convenient report statistics functions enabling the user to perform
report statistics conveniently and efficiently.
z Graphic display function
For report statistics data, the system provides the graphic display function, which can
display the detailed changes of the statistics and query data. The graphic display
modes include graph, histogram, and pie chart, etc. The graph color can be set. The
data change tendency can be shown through the dynamic graphical display function,
which is effective for the comparison between two or among more groups of statistics
data.
z Automatic code meaning conversion
In the service system, some codes are used to tag the data with special meaning to
save database space or for system design.
For example, each of the following codes represents a phone fault respectively:
During report statistics, if a field error is found in the report, the statistics data should not
be 01, 02 or 03, but disconnected, short-circuited or not hooked on. During report
customization, the user doesn't know whether to get the meaning of a fault cause from
another table, therefore, the report tool provides the function of converting the code into
the meaning it represents automatically.
z Totaling functions
The include several types: row and column totaling, specified field totaling, grand
totaling, row and column subtotaling, grouping subtotaling, page subtotaling, and
percentage, etc..
2-6
User Manual System Principle
iManager M2000 Intelligent Report System Chapter 2 System Principle
A certain value can be preset for the statistics query data, which will be highlighted in
special font or special color once beyond this preset value.
z Preview function
The report statistics supports preview function and zooming function in the preview
mode. It also supports the saving & reading, format conversion and printing functions
for report files.
z Extraction in batch
For the statistics of enormous data, the batch extraction function can be used. For
example: extract 500 records each time.
z Report statistics query conditions
The report statistics query conditions directly reflect the report statistics contents. With
the input query conditions, the report can generate final, complete and executable SQL
statements or executable store procedures.
There are various types of report statistics query conditions, include start time and end
time, service type, region, number, service status, user name, etc. or the combination of
several of them. After the report content is customized, the report tool can generate the
corresponding statistics query conditions.
During report statistics, the report tool will pop up a window, in which the user can input
the conditions. In addition, the report tool can automatically judge whether the input
value of the query condition is valid according to the specified rules.
The query condition supports multi-value input. For example, if a statistics condition is
"Employee ID", you can input 1, 2 or even more numbers. It also supports the relational
operator formula and the Boolean formula.
The report tool supports the flexible definition of the query time.
During query statistics, the query progress can be displayed and can reflect the number
of records meeting the conditions and the total number of cords. The query can be
aborted at any time and the system will report the number of data actually obtained,
generate a report and display the message "Part of results" in an obvious place.
As a universal report tool, the Intelligent Report System is independent from the service
system. In another word, any required report can be designed through the report tool
for any service system.
2-7
User Manual System Principle
iManager M2000 Intelligent Report System Chapter 2 System Principle
Except this relationship, it has nothing to do with the type of operating system used in
the service system.
z Independent from database
The report tool supports the major database, like Oracle, SQL Server, Sybase, and
Informix, etc. and the standard SQL. It does not own any feature associated with the
specified database, so as to be independent from the database.
z Independent from specific services
The IN report system is independent from all other parts but the data in the service
system database.
The Intelligent Report System supports the distributed large-capacity service system. It
does not limit the number of report users but supports the concurrent operation of
multiple users. However the number of the users connected with the server at the same
time is controlled by the system License and should not be over 250.
The system is not connected with the database directly. Instead, it realizes
communication through a secure communication mechanism, which shields visitors
beyond the LAN so as to prevent illegal intrusion.
The output formats provide by the IN report system include but not limited to the
following forms: printing, RTF file, TXT file, HTML file, EXCEL file, report files in special
format etc.
2-8
User Manual System Principle
iManager M2000 Intelligent Report System Chapter 2 System Principle
1) User types
The report system features for strict authority control. It has four types of users: system
administrator, report designer, report statistician and end user.
z The system administrator can set and control the authority for report designers
and ordinary users.
z The report designer is authorized to design reports but not for all data in the
service system.
z The report statistician is authorized to execute report statistics but not for all data
in the service system.
z The end user is authorized to execute query and statistics only the data related
with himself.
The management authority is independent from the design and statistics authority.
Namely, the administrator has no authority for report design and statistics. However,
the statistics authority is included in the design authority.
A report user can have more than one identity. A user can be the administrator and the
designer or statistician at the same time, which is determined by his authority.
2) Authority control
The authority control includes:
z Operation authority control
It mainly refers to the report design and statistics authority.
z Data authority control
It decides what kind of data the user has the design and statistics authority for.
The data authority can be defined according to different data sources, region, unit or
other special data.
z User authority control
The user authority control is set by the system administrator, who decides whether a
user has the report design authority or report statistics authority, and what data can be
accessed with the authority.
Several people with the same authority can be managed through a group.
z Database authority control
2-9
User Manual System Principle
iManager M2000 Intelligent Report System Chapter 2 System Principle
Authority levels are set in the database. A user can access the corresponding data
according to his authority. All report tool users have read-only authority for all data.
The report system guarantees the security of the data and operations. Its guarantee
concerns operation, storage, transmission, input, output, etc. including:
z Complete authority management
The strict authority control ensures that only authorized users can access the
corresponding data.
Authority levels are set in the database. The user can access the corresponding data
according to his authority. Except the system administrator and the report designer, all
other users only have the read-only authority for all data.
z Detailed log record
The log mainly contains the important operation and error records. The important
operation records contain such items as operator, operation time, operation items and
operated data, etc. The error record contains such items as operator, error occurrence
time, error-generating module, error cause, original data of error, and so on.
The log record is generated in the file form and is not affected by the database error.
The log view function is provided to determine the supervisor, local error cause and
recover faults, etc. according to the log.
The log also has the clearance function, which is used to clear history logs. Before
clearance, the log should be backed up or confirmed as useless. The system always
asks the user to confirm to prevent mis-operations.
z Complete alarm mechanism
The error alarm is used to report system errors or data errors so that the user can timely
handle them.
z Secure transmission mechanism
Data transmission mainly refers to the data transmission between the report tool and
the database, and between the browser and the report tool. The system guarantees
that the data is not intercepted illegally.
z Secure storage mechanism
The system guarantees the data storage security, especially for report template files
and report data configuration, etc.
The specialized data of the report tool, like user and authority, etc., are stored in the
system database.
z History data clearance function
2-10
User Manual System Principle
iManager M2000 Intelligent Report System Chapter 2 System Principle
This function is used to automatically clear temporary data generated by the report
system so as to prevent junk data.
z Error processing mechanism
Processing mechanisms are provided corresponding to system errors or data errors so
that the statistics and data security are not affected.
When there is a system error occurs, the error cause and the corresponding
recommended solution are provided so that the user can quickly locate the error and
handle it
The system has a self-repairing mechanism which can prevent the system functions
being affected by system errors.
A proxy can connect and access multiple databases of different types simultaneously.
2.6 Attributes
I. Reliability
The report system features a multi-layer Browser/Server structure. The Http protocol is
adopted for the communication between the Client and the system midware, while the
Socket protocol is adopted between system midware and data access midware. If any
fault occurs, you can load the Client again without affecting the whole system.
Therefore, high reliability can be ensured even in the case of heavy user access and
data transfer.
II. Security
The Socket protocol is used between the system midware and the data access
midware. For data transfer, the self-defined object class is used, which ensures high
security.
2) Interface security
Inter-module data transfer is realized via the self-defined object class of the system,
which features high security.
3) Database security
The system data is stored in the system database MySQL, which is specially used for
the report system and whose password is encrypted through encryption algorithm.
2-11
User Manual System Principle
iManager M2000 Intelligent Report System Chapter 2 System Principle
III. Maintainability
1) Template file. The self-defined template format and contents are all stored in the
template file. Any authorized user can directly modify the template file with the
Client tool.
2) Data operation. Any data access to the report is realized via intermediate data
access, and the maintenance to all data access functions of the report system can
be realized through the midware maintenance.
3) Service database encapsulation: The report system encapsulates the fields of the
service system database adopted by the user. To modify the field information
corresponding to the report, you can directly modify the field encapsulation
information corresponding to this field.
4) The system can automatically record the debugging information for online
maintenance.
5) The log management function is used to record system error information for
tracing and maintenance.
6) The system midware contains all alarm information displayed via the console for
the system administrator.
IV. Transplantability
The report system midware is designed via Java and connected with the database via
JDBC. The system has its own MySQL relationship database, which can run on any
platform. The standard SQL is adopted for the operations of the system database and
the service database, so the system can be transplanted between different databases.
The report system is a self-sufficient system and has nothing to do with the service
system.
2-12
User Manual System Principle
iManager M2000 Intelligent Report System Chapter 2 System Principle
1) Get original data -> 2) Associate data -> 3) Calculate data to get statistics result -> 4)
Edit format and then output report. The following are the detailed steps:
Step 1:
Step 2:
Extract the expected data from a number of tables, and then conduct data association.
Step 3:
According to the extracted data, conduct grouping and summarizing calculation (get
summation of peer office types according to the same office direction) or arithmetic
calculation (get the answered call attempt ratio as per the number of answered calls
and the number of call attempts), and so on.
Step 4:
2-13
User Manual System Principle
iManager M2000 Intelligent Report System Chapter 2 System Principle
Traffic Configuration
database database
Data extraction
1
Office
Peer office type
Office Number of call Number of Number of direction No.
direction No. attempts connected calls answered calls 1 To BSC
1 300 250 200 2 To provincial MSC
2 400 350 300 3 To provincialMSC
3 500 450 400
Associate 2
4
Number of Number of Number of answered
Peer office type
call attempts connected calls answered calls Ratio Formatted output
As shown in Figure 2-2, the statistics and generation procedures for the answered ratio
are described as follows:
Step 1:
In Figure 2-2, Step 1 is to extract "Office Direction Performance Statistics Result Table"
(Traffic Database Table) and the "Configuration Information Table" (Configuration
Database Table) of office directions from the database. In these two tables, we can see
the statistics results of three office directions on such aspects of call attempts,
connected calls and answered calls, as well as the peer office types of these three
office directions. Then, we conduct the statistics of the performance items for the same
peer office type.
Step 2:
Step 2 is to combine the "Office Direction Performance Statistics Result Table" and the
"Configuration Information Table" of office directions, associate them and get the
expected "Peer Office Type" (Remove "Office Direction Numbers" without exact
meaning).
2-14
User Manual System Principle
iManager M2000 Intelligent Report System Chapter 2 System Principle
Step 3:
Summarize the indices with the same peer office, i.e. respectively get the summation of
call attempts, connected calls and answered calls in the two data "to provincial MSC",
and combine the results into one record. But there is only one record of "to BSC", so the
combined result is also one record. Then, divide "the number of answered calls" with
"the number of call attempts" to get the answered ratio. Thus the data summarizing and
operation is completed.
Step 4:
Step 4 is to edit the format, including arranging tables, modifying font, setting titles, and
so on. Finally, output the result in the specified format.
In the IN report system, all steps in Section 2.7.1 Measurement and Generating
Process are saved in a "Report Template". You may define these steps to get different
report contents and styles, then save them and use this template for statistics.
To design a report template according to the above steps, you should also operate as
per the following steps:
Step 1:
Define the "Data Dictionary" in the Intelligent Report System so as to define all the
service data sources.
The "Data Dictionary" defines the database where the service data is located, the
available data tables or the field meaning of the storage process, etc. Once the "Data
Dictionary" is defined, the source of original data is thus defined.
Once the original data source is available, you can determine how to summarize and
operate these data.
Step 2:
Define the "Query Definition Wizard" so as to define the data tables, inter-table
association and data filtering conditions used in the template.
The "Query Definition Wizard" defines the following items: data source (the database
providing original data), data set (the tables or storage process to be used, and how to
associate them), parameters entered during the storage process (if the storage
process is used), output result (available data, and can be used for inter-field operation),
user query condition (used to filter expected data), grouping and sequencing.
Step 3:
2-15
User Manual System Principle
iManager M2000 Intelligent Report System Chapter 2 System Principle
Define the data operation formula, grouping condition and summarizing method in the
template. These items can be realized through report band, rectangle object, operation
presentation format, and so on in this system.
The report band specifies the range and rules for display fields and data operation. In a
rectangle object, you can define the field, operation formula or text format
corresponding to the data. The operation expression includes arithmetic calculation,
database functions, and logical judgment. It also provides powerful calculation
functions.
Step 4:
Define the template format including font, location, and color, etc; or add decorative
tables or pictures.
The defined template can be saved in the system database. You can transfer the query
authority of this template to other user groups.
The IN report system can be divided into an architecture illustrated in Figure 2-3 as per
its functional modules.
IN report system
Format editor
Line section object
Data proxy wizard
Rectangle object
Diagram object
.
.
.
The specific use of each function is available in the operation guide part.
2-16
HUAWEI
Client Management
User Manual Client Management
iManager M2000 Intelligent Report System Table of Contents
Table of Contents
i
User Manual Client Management
iManager M2000 Intelligent Report System Table of Contents
ii
User Manual Client Management
iManager M2000 Intelligent Report System Table of Contents
iii
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 1 Installation and Operation of Report System Client
2) Click <Install Report System Client> or click the link Report System Client
Software V200_R001_XXX to start installing the report system client.
Please install the report system client according to the following Setup Wizard.
1-1
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 1 Installation and Operation of Report System Client
3) Click the Report browser V200_R001_XXX to download the report client tools.
Note:
1) The installation of the report system client is so simple that what a user needs to do is to select <Next>
continuously. All the configurations adopt the default values.
2) The report browser can be used directly without being installed.
3) Run this program from its current location can be selected in the client download, which facilitates
the installation.
z Or, click the icon on the desktop to start the report system client.
1-2
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 1 Installation and Operation of Report System Client
2) In the User Login window, as shown in Figure 1-3, type the IP address of the report
server: HTTP port No. of the report server in Login Website, as shown in Figure
1-3.
3) Input the User ID and User Password.
Note:
After it is installed, the report system will automatically create an initial user ID admin (the super
administrator) with the initial password as admin. The user has the complete user management authority
and data source authority.
1-3
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 1 Installation and Operation of Report System Client
Note:
More configuration items included in the advanced configuration are shown in the following.
1) Save the Password and Automatic Login: If the configuration is employed, the user automatically
logs in to the system in the next start.
2) Use Firewall Proxy: To employ the configuration, the user must input the firewall proxy name and
password.
3) Use SSL Transmission: The configuration can be employed only when the report server supports the
SSL security socket. The report server does not support it by default.
5) After all the configurations are performed, click <Login>. The system pops up the
window for selecting the user group, as shown in Figure 1-4.
6) Select the user group, and the system creates the system data environment.
Note:
1) A user accessing the report system may fall into multiple user groups. But he can only select a user
group when logging in to the report system client. Now, the user authority is the authority available in the
user group.
2) For the description of the specific authority, please see Section 2.4 “Overview of the Authority
Management” of Client Management module.
3) With the shortcuts such as <Alt+1>, <Alt+2>, etc., a user can select the user group conveniently.
1-4
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 1 Installation and Operation of Report System Client
Caution:
1) If a user wants to design a report or a template, he must select the With Designing Permission check
box. Otherwise, though he is granted the authority in the user group to design a report or template, he
cannot perform it.
2) Both the users with designing permission and those with browsing permission connected to the report
server are restricted by License file, and in general, the users with designing permission are less than
those with browsing permission, so it is recommended that the check box should not be checked if
unnecessary.
8) Finally, the system pops up the report system client manager window, as shown in
Figure 1-5.
The report system client manager window shown in Figure 1-5 is similar to that of the
resource manager in the MS Windows system except for several aspects that should
be paid more attention to.
1-5
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 1 Installation and Operation of Report System Client
buttons, a user can switch the views among Report management, User
management, and Datasource management. (The window as shown in Figure 1-5
appears when the Report tab page is selected).
2) The sub-menus under the [Operation] menu vary with different operating objects
selected by a user. For example, if a user selects a user group, the sub-menus
under the [Operation] menu will change to [New User Group], [Modify User
Group], [Delete User Group] and [New User]. If he selects a user, the
sub-menus will be [New User], [Modify User], [Delete User], [Unlock User],
[Activate User] and [Deactivate User].
1-6
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 2 Public Functions of the Report System Client
I. Task description
1) Select the [System/Switch User Group] menu in the report system client
manager window. The system pops up the window for selecting the user group, as
shown in Figure 1-4.
2) Select the user group for this login, and then re-enter the report system client
manager window after the system has created the system data environment.
I. Task description
It is to log in to the report server as another user or logs in to other report servers.
1) Select the [System/Switch User] menu in the report system client manager
window. The system pops up the User Login window, as shown in Figure 1-3.
2) The following operations are the same as those of user logging in to the report
system. For specific operations, please refer to Section 1.2.2 “Logging in to the
Report System”.
I. Task description
2-1
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 2 Public Functions of the Report System Client
2) Input the old password and the new password in the Old Password and New
Password text boxes respectively, and input the new password again in the
Confirm Password text box. After that, click <OK> to finish the password of the
current user change.
I. Task description
Select the [System/Query the System Information] menu in the report system client
manager window. The system pops up the window for querying the current system
information, as shown in Figure 2-2
2-2
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 2 Public Functions of the Report System Client
For the description of the fields related to the operation of querying the current system
information, please refer to Table 2-1.
Table 2-1 Description of fields related to the operation of querying the current system information
Field Description
The current service is related to the License. A service corresponds to a
Current Service License, while a License corresponds to a user group. Therefore, different
services can be obtained in the user login by selecting different user groups.
The current service key is related to License, and it records the key words of
Current Service Key
the current service, and works as the key of the current service.
Whether the schedule monitoring is started. The schedule task is available
Schedule Monitoring only when the schedule monitoring is started. The schedule monitoring can
be started by selecting the [Tools/Schedule monitor] menu.
Means whether the user is allowed to log out if his operation times out. If
allowed, the user will log out if he has no operation in a period of time. If he
Logout When Timeout wants to conduct any operation, he should log in to the report system again.
The user timing out logs out automatically by selecting the [Tools/Schedule
monitor] menu.
Means whether the user is allowed to design a report. The permission is
Report Designing Permission available only when the user checks With Designing Permission check
box in the login.
Last System Error Displays relevant information about the last system error.
It is the storing path of the template file, which is stored on the local machine
Template File Path
in the file format.
2-3
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 2 Public Functions of the Report System Client
The editing function includes such sub-functions as Find, Reset, Expand All, Collasple
All, Select All and Invert Selection.
The viewing function includes such sub-functions as Tool bar (involving Standard
Toolbar, Operation Toolbar and Management Toolbar), Management Page (Report
Management Page) User Management Page, Datasource Management Page), Full
Screen, Small Icon, List, Details and Refresh.
The help function includes such sub-functions as Help, Home Page and About.
The editing, viewing and help functions are relatively simple, and they have the similar
style to that of the MS Windows, which is easy to understand, so the detailed
description is omitted in this manual.
The auxiliary tools of the report system include Schedule Monitor, System Backup and
Clear Local Data Files.
I. Task description
Caution:
A user can create a schedule task in the report system client. But only when Start Schedule Monitor in
the Schedule Monitor is checked, will the system monitor the schedule task. Only when the executing
conditions are satisfied, will the system execute the scheduled task.
1) Select the [Tools/Schedule Monitor] menu in the report system client manager
window. The system pops up the schedule monitor window, as shown in Figure
2-3.
2-4
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 2 Public Functions of the Report System Client
Note:
The schedule task shown in the window is just one scheduled task created by the current user.
2) The user may select or clear the check box of Start Schedule Monitor or Can
Not Logout Automatically. The user can clear the log list window in the lower
part in the window by clicking <Clear Log>.
3) The user clicks <Return> to exit the window.
For the description of the fields and controls in the schedule monitor window, please
refer to Table 2-2.
Table 2-2 Description of fields and controls in the schedule monitor window
2-5
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 2 Public Functions of the Report System Client
I. Task description
The general procedure is: Define the datasource in a system and design the template
file; then back up the datasource and restore to the new system.
1) Select the [Tools/System Backup] menu in the report system client manager
window.
2) In the Huawei Report System Backup Tool window, as shown in Figure 2-4, select
to conduct the operations such as Backup Datasource, Backup Template Group
and Restore Template Group.
z Backup datasource
In the window as shown in Figure 2-4, input the database script file path and name (by
clicking on the right of the text box) generated by the backup datasource, and
select the type of the database which generates the script. Click <OK> to finish the
datasource backup.
2-6
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 2 Public Functions of the Report System Client
Note:
1) Backup Datasource will convert all the contents (including datasource, table, stored procedure,
available database proxy server, database proxy server, value range and authorization) of the datasource
in the datasource list into the SQL script of a certain database type.
2) Backup file path: A valid Windows file name with completed path; if not exist, it will be created; otherwise,
you will be inquired about whether to cover it.
3) Type of the SQL script, including MS SQL Server, Sybase, Informix, Oracle.
4) If the ID conflicts, user can edit this SQL script manually to get proper ID.
5) The user can execute the backup SQL script in the database system to recover the datasource.
Select the backup path of the current template group and click <OK>. The system
stores the current template group according to the directory structure of the local
machine, and the template file uses its name as the name of the backed up file.
Caution:
Before a user backs up the template group, he should select a template group in the [Report
Management] tab in the report system client manager window.
2-7
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 2 Public Functions of the Report System Client
Select the local path of the template group to be restored and click <OK>. The system
will create a template group with the current folder name, and then read the template
file and sub-directory in this folder in turn. The template file will be created as the
template with local filename, whereas sub-directory will be created as the sub-template
group.
Caution:
The properties of the template and its sub-template are set by default. For any special requirements,
please modify it manually.
Note:
The operations of backing up template groups and restoring template groups are reverse to each other. In
the actual operation, a template group is usually backed up to a path on the local machine. To recover the
template group, the backup template group directory generated in this directory will be selected directly.
Example:
2-8
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 2 Public Functions of the Report System Client
If the current template group is test1 with the backup path as C:\, then a test1
sub-directory is generated in C:\ after the template is backed up. To restore the test1
template group, the restore path is C:\test1\. The relation between the paths in this
example is shown in Table 2-3.
Current template group Backup path Local path of the backup template group _
test1 C:\ C:\test1\
For the description of the fields related to the operation of backing up and restoring the
system, please refer to Table 2-4.
Table 2-4 Description of fields related to the operation of backing up and restoring the system
2-9
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 2 Public Functions of the Report System Client
I. Task description
Note:
If a user logs in to the report system with the report client, after a period, the local machine will be filled with
such data files as the report template file, report file, XML script, data file, etc. These files will occupy a
large space, and not be re-used. So, the user can empty the space by deleting these files.
1) Select the [Tools/Clear Local Data Files] menu in the report system client
manager window.
Note:
As shown in the figure above, the local files are partitioned according to the IP address of the report server.
For example, a 10.76.176.124 data folder represents the local data file generated by the report server with
the IP address as 10.76.176.124, while a 10.76.144.175 data folder represents the local data file
generated by the report server with the IP address as 10.76.144.175.
2) In the Clear Data File window, as shown in Figure 2-7, click <Select All>, <Select
None> or <Select> to select the local data files to be cleared, then click <OK> to
finish the operation.
2-10
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 2 Public Functions of the Report System Client
The description of controls related to the operation of clearing the local data files is
shown in Table 2-5.
Table 2-5 Description of controls related to the operation of clearing the local data files
Control Description
<Select All> Deletes all the local files corresponding to the data folders.
<Select None> No file is to be deleted.
<Select> Deletes the local files corresponding to the selected data folders.
2-11
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 3 User and User Group Management
The management to the user and user management in the report system can be
divided into the user management and user group management. To conduct the
management to a user and user group, a user should enter the user list. (You can select
the [View/Management Page/User Management Page] menu in the report system
client manager window to enter the user list, similar to that shown in Figure 3-1.)
With different objects selected by the user, different contents are shown in the box in
the right part of the window. If the user selects User Group List, the corresponding
information of all user groups will be shown in the box. If the user selects a certain user
group, the corresponding information of this user group will be displayed. If the user
selects User List, the corresponding information of all users will be shown.
3-1
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 3 User and User Group Management
Caution:
Please make sure that the non-query operations such as addition, modification or deletion can be
performed to a user only on a client at the same time. Otherwise, the concurrent operations may lead to
abnormity.
I. Task description
It is to create a user group in the report system, and meanwhile set the maximum
authority to it.
1) Select a user group in the window as shown in Figure 3-1, and select the
[Operation/New User Group] menu. The system pops up the New User Group
window, as shown in Figure 3-2.
3-2
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 3 User and User Group Management
2) Input and select the corresponding information of the user group, and click <OK>
to finish the user group creation.
Note:
If a user clicks <Apply>, the system can also finish the user group creation. Now, the user can continue to
create other user groups without exiting the New User Group window.
For the description of the fields related to the operation of creating a new user group,
please refer to Table 3-1 .
Table 3-1 Description of fields related to the operation of creating a user group
3-3
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 3 User and User Group Management
When authorizing operations on template groups and datasources, the user can click
<Sel All>, <Sel None> or <Select> to select template groups and datasources. For the
detailed description, please refer to Table 3-3.
Caution:
The License file corresponding to the user group may restrict the user group’s access to some types of the
template or datasource. Therefore, though some template groups or datasource are authorized here, in
the actual operation, the users in the user group cannot access them due to restriction of the License file.
Table 3-2 Description of controls related to the operation of authorizing operations on template groups
and datasources
Control Description
Grants both the template groups and datasource allowed to be access by
<Sel All>
the current user to the user group being operated.
<Sel None> Cancels all the authorities from the user group being operated.
<Select> Grants the selected template groups and datasource to the user group being
operated.
3-4
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 3 User and User Group Management
I. Task description
It is to modify relevant information of an existing user group except the user group ID.
1) Select a user group in the window as shown in Figure 3-1, and select the
[Operation/Modify User Group] menu.
2) In the Modify User Group window, as shown in Figure 3-3, modify the relevant
information of the user group except for the user group ID. After the modification,
click <OK> to finish the user group modification.
Caution:
Only after a user refreshes the setting or re-log in to the system, can the modification to the template
groups or datasources, which operations are authorized on, come into effect.
3-5
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 3 User and User Group Management
For the description of the fields related to the operation of modify a user group, please
refer to Table 3-1.
I. Task description
1) Select a user group in the window as shown in Figure 3-1, and select the
[Operation/Delete User Group] menu. The system prompts "Are you sure to
delete the 1 user Group(s)?".
2) Click <OK> to finish the deletion. To cancel it, click <Cancel>.
I. Task description
1) Select User List in the window as shown in Figure 3-1, and select the
[Operation/New User] menu.
3-6
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 3 User and User Group Management
2) In the New User window, as shown in Figure 3-4, input and select relevant
information of a user, and meanwhile specify the user group that the user belongs
to.
3) Click <Add> to pop up the User Group Authorize window, as shown in Figure 3-5.
3-7
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 3 User and User Group Management
4) Select the user group to be authorized in the user group list to grant the authority
to the user, by which he can log in to the user group.
Note:
1) A user can select the corresponding authority from the Management authority drop-down list. Now the
user’s authority in the user group is the intersection of Management authority and Maximum
management authority of the user group, that is, the smaller one of the two. For example,
Management authority is the report administrator authority, 3/0/1, and Maximum management
authority of the user group is 1/2/2, the user’s authority in the user group is 1/0/1.
2) The user can also customize the maximum report management authority, maximum user management
authority and maximum datasource management authority in the user group by clicking the buttons in the
lower part of the window.
Users in the report system can be divided into the system administrator and user
administrator based on different authorities. For the detailed corresponding relationship,
please refer to Table 3-4.
3-8
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 3 User and User Group Management
Table 3-3 The corresponding relationship between the user type and authority in the report system
Authority
Field
Report authority User authority Datasource authority
Super
Full Rights Full Rights Full Rights
Administrator
User Administrator No Right Full Rights No Right
Data Dictionary
Read Only No Right Full Rights
Administrator
Report
Full Rights No Right Read Only
Administrator
Report Designer Read/Write No Right Read Only
Internal Designer Read Only No Right Read Only
External Designer Read Only No Right No Right
Note:
1) If a user clicks <Apply>, the user creation is also finished. Now, the user can continue to create other
users without exiting the New User Group window.
2) The user can also create user groups in batch with their IDs separated by “;”. Now, the employee ID and
user name of a user serve as his user ID. For the other properties, all users’ are identical.
For the description of the fields and controls related to the operation of creating a user,
please refer to Table 3-4.
Table 3-4 Description of fields and controls related to the operation of creating a user
3-9
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 3 User and User Group Management
I. Task description
1) Select User List in the window as shown in Figure 3-1, and select the user to be
modified in the box on the right. Select [Operation/Modify User] to pop up the
Modify User window, as shown in Figure 3-6.
3-10
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 3 User and User Group Management
2) Modify the relevant information of the user except his user ID. After the
modification, click <OK> to finish the user modification.
Note:
1) By pressing <Ctrl> or <Shift>, multiple users can be selected simultaneously and the properties of
users can be modified in batch.
2) By double clicking the text box of the user property or right clicking the check box of the user property,
the color of the control can be changed. When the color of the control is light gray, the corresponding user
property will remain unchanged.
For the description of the fields related to the operation of modifying a user, please refer
to Table 3-4.
3-11
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 3 User and User Group Management
I. Task description
1) Select User List in the window as shown in Figure 3-1 , and select the user to be
deleted in the box on the right. Select [Operation/Delete User] to pop up the
prompt “Are you sure to delete the 1 user(s)?”
2) Click <OK> to finish the deletion. To cancel the operation, click <Cancel>.
Note:
Pressing <Ctrl> or <Shift>, a user can select multiple users simultaneously and then delete them in batch.
I. Task description
Note:
If the Allow to Login Repeatedly check box is not selected for a user, he will be locked by the system
once he logs in successfully. The possible abnormity may leads to the deadlock of the client program in the
report system. After the client program is restarted, the user is still locked, and cannot re-log in. A feasible
method is to log in as another user and execute the operation of unlocking the user.
1) Select a user to be unblocked in the window as shown in Figure 3-1 (the blocked
user is marked with in the Lock column), and select [Operation/Unlock]. The
3-12
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 3 User and User Group Management
I. Task description
I. Task description
1) Select the activated user in the window as shown in Figure 3-1 (the activated user
has no mark on in the Activate column), and select the [Operation/Deactivate]
menu. The system prompts "Are you sure to deactivate the 1 user(s)?"
2) Click <OK> to finish the deactivation (the user is marked with in the Activate
3-13
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 4 Datasource Management
The management to the datasource of the report system consists of five parts, namely,
datasource management, table management, stored procedure management, value
list management, and database proxy server management. Before conducting the
management to the datasource, a user should enter the datasource management
window by selecting the [View/Management Page/Datasource Management Page]
menu in the report system client manager window, as shown in Figure 4-1.
With different objects selected, different contents are shown in the box in the right part
of the window. If a user selects the Datasource List, all the corresponding information
about the datasource will be displayed in the right box. If he selects a certain
datasource, the objects of Table List, Stored Procedure and Usable Proxy List will
be shown in the box. If he selects Table List, all the information corresponding to the
tables selected by the datasource will be listed. If he selects Stored Procedure, all the
stored procedures of this datasource will be displayed. If he selects Usable Proxy List,
all the usable database proxy servers of this datasource will be shown. If he selects
4-1
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 4 Datasource Management
Range List, all the value lists will be displayed. If he selects Proxy List, all the
database proxy servers will be displayed.
Caution:
Please make sure that the non-query operations such as addition, modification or deletion can be
performed to a datasource, table, stored procedure, value list or database proxy server only on a client at
the same time. Otherwise, the concurrent operations may lead to abnormity.
The datasource covers all the information required in accessing the service database,
such as the database name, database type, datasource IP address and port, database
user name and password. Only when the information is obtained, can the report system
access the service database.
The datasource is composed of two parts, table and stored procedure. By accessing
tables or invoking the stored procedure in the service database, the report system
obtains business data to make a report.
Meanwhile, the database proxy server must be defined for datasource. A service
database can be accessed via one or more proxy servers. The method to configure a
database proxy server is to configure a database proxy server list first, and then set the
usable proxy server list in the content of the datasource. For the specific operation
procedure, please refer to Section 4.1.4 "Setting a Usable Proxy Server for a
Datasource”. If the setting is successful, a user can read the data structure of the
service database, design a report template for it and query data from it.
I. Task description
It is to create a datasource in the report system, the aim of which is to obtain the
relevant information of the service database that a user can access.
4-2
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 4 Datasource Management
Note:
After the creation, it is suggested that a user configure the database proxy server first, and then read the
information of its table or stored procedure to judge whether the data configured are correct.
Caution:
If the service database type is Sybase, a user should make sure the business has been patched. If the
service database is not patched, please run the scrip program patchforjconn2.bat (the Windows
operating system, including Windows 98/2000/NT) or patchforjconn2.sh (the UNIX operating system) in
the sub-directory bin in the installation directory of the report server. For the detailed configuration, please
refer to Table 4-2.
1) Select Datasource List in the window as shown in Figure 4-1 and select
[Operation/New Datasource].
2) In the New Datasource window, as shown in Figure 4-2, input or select the basic
information of the datasource, and click <OK> to finish the datasource creation.
4-3
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 4 Datasource Management
Note:
Click <Apply>, the datasource creation can also be performed. Now, the user does can continue to create
other datasources without exiting the New Datasource window.
For the description of the fields related to the operation of creating a datasource, please
refer to Table 4-1.
4-4
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 4 Datasource Management
I. Task description
4-5
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 4 Datasource Management
2) In the Modify Datasource window, as shown in Figure 4-3, after the modification,
click <OK> to finish the datasource modification.
For the description of the fields related to the operation of modifying a datasource,
please refer to Table 4-1.
I. Task description
Note:
To delete a datasource just means that the report system will not conduct the management to the
datasource any more, and does not mean the home database of the datasource will be deleted.
4-6
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 4 Datasource Management
2) Click <OK> to finish the datasource deletion. To cancel the operation, click
<Cancel>.
I. Task description
It is to set some proxy servers that can provide services for the datasource being
edited.
1) Select Usable Proxy List under a certain datasource in the window as shown in
Figure 4-1, and select [Operation/Set Usable Proxy].
In the Set Usable Proxy window, as shown in Figure 4-4, the existing database proxy
servers in the report system are displayed in the upper part in the window, while the
proxy servers that provide services for the current datasource set in the lower part.
4-7
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 4 Datasource Management
2) Set the database proxy server for the current datasource by clicking or .
3) Click the <OK> button, and the operation of setting a usable proxy server is
finished.
For the description of the fields and controls involved in the operation of setting a
usable proxy server, please refer to Table 4-3.
Table 4-3 Description of fields and controls related to the operation of setting a usable proxy server
If the report system needs to access the tables in the database system, the preferred
way is to create a table in the list of the datasource tables. (An available way is to
extract all the tables in the datasource with the Get All Table function, and set the
database management table according to the requirements)
For the convenience of accessing the table of datasource, it needs to set an alias for
the table and for the field in the table, which can be realized by the operation of
modifying table.
I. Task description
4-8
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 4 Datasource Management
Caution:
The newly created table should be a table that exists in the datasource. New Table is just used to describe
its structure, which permits the report system to access it correctly.
1) Select Table List under a certain datasource in the window as shown in Figure
4-1, or select [Operation/New Table]. The system pops up the New Table window,
as shown in Figure 4-5.
2) Input or select relevant information of the table, and click <OK> to finish the table
creation.
Here, the relationship between the field in the table and the range list can be
established. For the detailed introduction to the range list, please refer to Section 4.4
“Range List Management”.
Example:
Assuming a table has a Week field, which is used for describing week, then the
corresponding relationship between the field and the range list of week can be
4-9
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 4 Datasource Management
established. (The precondition is that the range list of week has been defined in the
report system.)
3) Input Week with the alias of Week, and select Range and then appears.
4) Click the button to pop up the Get Range window as shown in Figure 4-6.
5) Select Week and click <OK>. Now the corresponding relationship between Week
and range list of week is established, and character of week will appear in the
range list line of the Week row.
For the description of the fields related to the operation of creating a table, please refer
to Table 4-4.
4-10
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 4 Datasource Management
4-11
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 4 Datasource Management
I. Task description
1) Select Table List under a certain datasource in the window as shown in Figure 4-1,
and the table to be modified will be displayed in the box on the right.
2) Select [Operation/Modify Table]. The system pops up the Modify Table window,
as shown in Figure 4-7.
4-12
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 4 Datasource Management
For the description of the fields related to the operation of modifying a table, please
refer to Table 4-4.
I. Task description
Note:
To delete a table means that the report system cannot manage or query the table any more, and does not
means deleting the table in the actual database.
1) Select Table List under a certain datasource in the window as shown in Figure 4-1,
and the table to be deleted will be displayed in the box on the right.
2) Select [Operation/Delete Table] to pop up the prompt “Are you sure to delete the
1 Table(s)?”
3) Click <OK> to finish the table deletion. To cancel the operation, click <Cancel>.
Note:
Pressing both <Ctrl> and <Shift>, a user can select multiple tables simultaneously and then delete these
tables in batch.
I. Task description
It is to read all the table information in the datasource from the service database.
4-13
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 4 Datasource Management
Caution:
1) The operation of getting all tables cannot be executed normally unless the datasource information is
configured correctly and the database proxy server is set well. So, this operation can be employed to
check whether or not the datasource information and database proxy server are configured correctly.
2) The operation of getting all tables is restricted by License. The table without the authority will not be
shown.
1) Select Table List under a datasource in the window as shown in Figure 4-1.
2) Select [Operation/ Get All Table] to pop up the Get Table window, as shown in
Figure 4-8.
3) All the tables that can be managed in the datasource are shown in the Get Table
window. To select the table to be managed, check the check box before each
table.
4) Click <OK> to finish the table list of this datasource creation.
Note:
1) Table generated via the operation of getting all tables has the same name with its alias. So the alias
should be modified manually after the operation. With it, the table can be queried more easily and directly.
2) If the obtained table name does not conform to the naming rule (such as the space at the end, and
reload mark), then it should be modified manually.
4-14
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 4 Datasource Management
For the description of the fields and controls related to the operation of getting all tables,
please refer to Table 4-5.
Table 4-5 Description of fields and controls related to the operation of getting all tables
I. Task description
Caution:
1) The newly added stored procedure must be an existing stored procedure in the datasource. The
operation of adding a stored procedure is just describing its structure, which allows the report system to
access it correctly.
2) A stored procedure, which does not return the result set, is meaningless to the report system. Therefore,
what is added through this operation is a stored procedure which can return the result set.
4-15
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 4 Datasource Management
3) Input relevant information of the stored procedure and click <OK> to finish the
stored procedure addition.
Example:
Assuming that a system database with its type as Informix already has a stored
procedure.
create procedure sp_getuser(userid int) returning
int, int, int, varchar(64);
define ifield1 int;
define ifield2 int;
define ifield3 int;
define sfield4 varchar(64);
foreach
select columnid, tableid, dsid, columnname into ifield1, ifield2, ifield3,
sfield4
from rptcolumn where columnid = userid
return ifield1,ifield2,ifield3,sfield4 with resume;
end foreach;
end procedure;
Because the stored procedure has parameters, and it can return the result set, it is
available in the report system.
4-16
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 4 Datasource Management
Note:
In Informix, the structure like "foreach… …end foreach" is employed to return the query result to a table.
Only when the with resume statement is added, can the query result set be returned. Otherwise the query
results will be returned one by one.
Now, the stored procedure sp_getuser can be added to the datasource setting in the
report system.
4) In the window as shown in Figure 4-9, enter sp_getuser in SP Name, and Get
user information in Note.
5) Click <Parameter>, and enter relevant parameters of the stored procedure, as
shown in Figure 4-10.
6) Click <Result Set> and enter relevant results of the stored procedure, as shown in
Figure 4-11.
4-17
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 4 Datasource Management
7) Click <OK> to finish the operation of adding the stored procedure sp_getuser.
Note:
If the parameter or result parameter entered the stored procedure is the field in table of the datasource, the
field can be imported by clicking <Import Fields>. For the detailed operation procedure, please refer to
Section 4.3.2 “Importing Fields of a Stored Procedure”.
For the description of the fields related to the operation of adding a stored procedure,
please refer to Table 4-6.
Table 4-6 Description of fields related to the operation of adding a stored procedure
4-18
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 4 Datasource Management
4-19
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 4 Datasource Management
I. Task description
It is to import Parameter or Result Set of the stored procedure in the Import Field
mode.
1) Click <Import Field> in the window as shown in Figure 4-9 to pop up the window
for importing the fields of the stored procedure, as shown in Figure 4-12.
2) Select the database where the stored procedure is located, or select one or more
fields in the table, or one or more fields in other stored procedures as Parameter
or Result Set.
4-20
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 4 Datasource Management
For the description of the controls related to the operation of importing fields of a stored
procedure, please refer to Table 4-7.
Table 4-7 Description of controls related to the operation of importing fields of a stored procedure
Control Description
The imported fields will overwrite the original ones. That is, import Import
Fields to overwrite the original Import Fields; import Result Set to
overwrite the original Result Set.
The imported fields will be added to the end. That is, if Import Fields is
imported, it will be appended after the original Import Fields. If Result
Set is imported, it will be appended to the end of the original Result Set.
<Sel All> All the fields of the selected tables or stored procedures are imported.
<Sel None> All the fields of the selected tables or stored procedures are cancelled.
I. Task description
4-21
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 4 Datasource Management
For the description of the fields related to the operation of modifying a stored procedure,
please refer to Table 4-6.
I. Task description
4-22
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 4 Datasource Management
Note:
Pressing <Ctrl> or <Shift>, a user can select multiple stored procedures simultaneously and then delete
them in batch.
I. Task description
It is to read all the information of the stored procedures in the datasource from the
service database.
Caution:
1) The operation of getting all stored procedures cannot be executed normally unless the datasource
information is configured correctly and the database proxy server is set well. Therefore, this operation can
be employed to check whether or not the datasource information and database proxy server are
configured correctly.
2) The operation of getting all stored procedures is restricted by License. The stored procedure without the
authority will not be shown.
4-23
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 4 Datasource Management
3) All the stored procedures that can be managed in the datasource are shown in the
Get Stored Procedure window. To select the stored procedures to be managed,
check the check box before each stored procedure.
4) Click <OK> to finish the stored procedure list of this datasource creation in the
report system.
Note:
1) A stored procedure generated via the operation of getting all stored procedures has the same name with
its alias. So the alias should be modified manually after the operation. With it, the stored procedure can be
queried more easily and directly.
2) The operation of getting all stored procedures does not include the input field and returned fields, so
these fields should be added or imported manually.
3) If the name of the obtained stored procedure does not conform to the naming rule (such as the space at
the end, and reload mark), then it should be modified manually.
For the description of the fields and controls related to the operation of getting all stored
procedures, please refer to Table 4-8.
Table 4-8 Description of fields and controls related to the operation of automatically getting all stored
procedures
4-24
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 4 Datasource Management
The key role of a value list is to establish a corresponding relationship between a field
and a description in a certain table of the service database. For example, there is a field
month in a certain business table. Its value range is from 1 to 12, which corresponds to
January, February, March… December respectively.
So, a range list can be created with the values of 1~12, and the corresponding
description January, February, March, … December, and meanwhile it is bound to
month. (For the actual binding method, please refer to Section 4.2.1 “Creating a Table”)
So in the design or query, the value of month is represented with from January to
December. In this sense, the window becomes more friendly and more convenient to
operate.
I. Task description
Here, creating “Week range list” is taken as the example to explain the method of
creating a range list. To create other range lists, please refer to this example.
1) Select Range List in the window as shown in Figure 4-1 and select
[Operation/New Range List]. The system pops up the New Range window, as
shown in Figure 4-15.
4-25
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 4 Datasource Management
2) Input Week in the Range name with the Note as Week range list.
3) Directly enter the value and description of the range list or import the value and
on the low-left in the window) to pop up the window for setting items in the range,
as shown in Figure 4-16.
4-26
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 4 Datasource Management
4) Set the values of the week range list. The values are numbers in DBC case, such
as 1, 2, etc, and the value range is from 1 to 7. Click <Import List> to import the
seven values set to the range list.
5) Click to set the values of the week range list, as shown in Figure 4-17 .
4-27
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 4 Datasource Management
6) Check To Value and click <OK>, and the values of the week range list are shown
in the window, as shown in Figure 4-18.
4-28
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 4 Datasource Management
7) Set the description of the week range list. The description of the week range list is
in form like Monday, Tuesday, etc., and the value range is from 1 to 7. Click
<Import List>, and import the set seven descriptions to the range list.
8) Click to set the description of the week range list, as shown in Figure 4-19.
9) Check To Description and click <OK>. The description of the week range list is
shown in the window, as shown in Figure 4-20.
4-29
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 4 Datasource Management
For the description of the fields related to the operation of creating a range list, please
refer to Table 4-9 .
Table 4-9 Description of fields related to the operation of creating a range list
The controls related to the generation of description and value of the range list is
depicted in Table 4-10.
4-30
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 4 Datasource Management
Table 4-10 Description of controls related to the generation of description and value of range list
Control Description
Clicks this button to pop up the Set items in the range window, in which
the values and descriptions of the range list can be set.
The values and descriptions of range list can be generated in three
modes, Generator, SQL, and Original.
Selects the content format of the value and description. Take the
description of the week range list for example, week is filled in the first
column, Monday/Tuesday is filled in the second, and the third column is
null.
Selects the range of value or description. Fox example, the generation
range of description of week range list is 1~7 (the upper limit is 1,
whereas the lower limit is 7), while that of season range list is 1~4.
Inputs the SQL command in the left text box, while selects the
datasource which executes the SQL command in the right list box.
The radio buttons on the left can decide to collect the value or description
of the existing range list, while in the list box on the right, the range list to
be collected can be selected.
Self represents the range list being edited.
Generates the values or descriptions of the range list according to the
user’s setting.
Adds the selected items to the list box on the right. Double click the
selected items on the lift list box to perform the same function.
Adds all the items to the list box on the right.
Deletes all the items from the list box on the right.
Deletes the selected items from the list box on the right. Double click the
selected items in the right list box to perform the same function.
Moves the selected item in the right list box line up by a line.
Moves the selected item in the right list box down by a line.
I. Task description
1) Select User List in the window as shown in Figure 4-1, and select the range list to
be modified in the box on the right.
2) Select [Operation/Modify Range List] to pop up the Modify Range window, as
shown in Figure 4-21.
4-31
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 4 Datasource Management
3) Modify relevant information of the range list. For the detailed operation procedure,
please refer to Section 4.4.1 “Creating a Range List”.
For the description of the fields related to the operation of modifying a range list, please
refer to Table 4-9 and Table 4-10.
I. Task description
1) Select Range List in the window as shown in Figure 4-1 and the range list to be
deleted in the box on the right.
2) Select [Operation/Delete Range List], and the system gives a prompt to confirm
the deletion.
z Click <OK>to finish the range list deletion. To cancel the operation, click
<Cancel>.
4-32
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 4 Datasource Management
I. Task description
Caution:
Only the proxy server installed and configured or running on the report server is granted to conduct the
operation. Therefore, a new database proxy server is generally created by administrator.
1) Select Proxy List in the window as shown in Figure 4-1, and select
[Operation/New Proxy]. The system pops up the New Proxy window, as shown in
Figure 4-22.
4-33
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 4 Datasource Management
2) Input the relevant information of the database proxy server, and click <OK> to
finish the operation.
Note:
1) The new database proxy server creation can also be performed by clicking <Apply>. In this case, the
user can continue to create other database proxy servers without exiting the New Proxy window.
2) Whether the configuration of the database proxy server is correct or not can be checked by the mode of
acquiring the list of tables of the datasource using the database proxy server. If the acquiring operation
succeeds, it means the configuration is correct, but if it fails, it demonstrates either the database proxy
server configuration or the datasource configuration.
3) After the database proxy server is created, it can be configured in database proxy server list.
For the description of the fields related to the operation of creating a database proxy
server, please refer to Table 4-11.
Table 4-11 Description of fields related to the operation of creating a database proxy server
4-34
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 4 Datasource Management
I. Task description
It is to modify relevant properties of the database proxy server except its ID.
1) Select Proxy List in the window as shown in Figure 4-1, and select a database to
be modified in the box on the right. Select [Operation/Modify Proxy] to pop up the
Modify Proxy window, as shown in Figure 4-23.
Note:
1) Pressing <Ctrl> or <Shift>, the user can select multiple database proxy servers simultaneously and
modify them in batch.
2) In modifying the database proxy servers in batch, double click the text box of the property of the
database proxy server, which can change the color of the control. If it is light gray, the property cannot be
modified, that is, each database proxy server should keep the property value.
4-35
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 4 Datasource Management
For the description of the fields related to the operation of modifying a database proxy
server, please refer to Table 4-11.
I. Task description
1) Select Proxy List in the window as shown in Figure 4-1, and select a database to
be deleted in the box on the right. Select [Operation/Delete Proxy] and the
system will give the prompt “Are you sure to delete the 1 Proxy(s)?”
2) Click <OK> to finish the deletion. To cancel it, click <Cancel>.
4-36
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 5 Report and Template Management
The report and template management of the report system falls into six parts: template
group management, sub-template group management, template file management,
scheduled task management, report query and statistics, and report template design.
Before the operation of report and template management, enter the report
management tab by selecting [View/Management Page/Report Management Page]
in the report system client manager window, as shown in Figure 5-1.
The contents on the right of the window vary with different objects selected by the user.
If the user selects Template Group List, the information of all template groups able to
be managed currently will be displayed. If the user selects a specific template group,
the sub-template groups and template files contained in this template group will be
displayed. If the user selects a specific template file, the corresponding scheduled task
of this template file and such local files as report file generated during query with this
template will be displayed.
5-1
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 5 Report and Template Management
Caution:
Please ensure that only one client performs such non-query operations as addition, modification and
deletion to the same template group, sub-template, template file and scheduled task at some moment.
Also, ensure that only one client performs design on the same template at some moment. Otherwise,
abnormity may occur due to simultaneous operations.
I. Task description
It is to create a template group in the current report system. After a template group is
created, the user can create sub-template groups and template files.
1) Select Template Group List, and then select [Operation/New Template Group]
in the window as shown in Figure 5-1.
2) In the New Template Group window, as shown in Figure 5-2, input the related
information of template group and then click <OK>. Then a new template group is
created.
5-2
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 5 Report and Template Management
For the description of the fields related to the operation of creating a template group,
please refer to Table 5-1.
Table 5-1 Description of fields related to the operation of creating a template group
I. Task description
Modify the related information of template group and then click <OK>.
5-3
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 5 Report and Template Management
For the description of the fields related to the operation of modifying a template group,
please refer to Table 5-1.
I. Task description
I. Task description
It is to store the template groups, sub-template groups and template files created by the
user in the local file system of client of the report system.
Compared with the file system, the storage structure of template group is like a
directory. The sub-template groups and template files of this template group are equal
to the sub-directories of a directory.
Therefore, changing to folder means entering the local storage directory of template
group, sub-template group or template file. If the directory has not been established yet,
the system will enter the directory after establishing it.
5-4
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 5 Report and Template Management
I. Task description
5-5
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 5 Report and Template Management
2) Refer to Section 2.3.2 “Backing up and Restoring the System” for the sequent
operations.
z Restoring the template group
3) Select Template Group List and then [Operation/Restore Template Group] in
the window as shown in Figure 5-1. The system pops up the template group
restoring window, as shown in Figure 5-6.
4) Refer to Section 2.3.2 “Backing up and Restoring the System” for the sequent
operations.
For the description of the fields related to the operations of backing up and restoring
template groups, please refer to Section 2.3.2 “Backing up and Restoring the
System”.
I. Task description
5-6
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 5 Report and Template Management
1) Select the template group to be created with a new sub-template group and then
[Operation/New Sub Template Group] in the window as shown in Figure 5-1.
The system pops up the New Sub Template Group window, as shown in Figure
5-7.
2) Input the related information of sub-template group and then click <OK>. Then a
new sub-template group is created.
For the description of the fields related to the operation of creating a sub-template
group, please refer to Table 5-2.
Table 5-2 Description of fields related to the operation of creating a sub-template group
5-7
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 5 Report and Template Management
I. Task description
5-8
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 5 Report and Template Management
For the description of the fields related to the operation of modifying a sub-template
group, please refer to Table 5-2.
I. Task description
I. Task description
It is to create a new template file under a template group or a sub-template group. The
template file is a binary file shared by all users, with the extension name FRF. The user
can choose a template file to query and obtain the *.FRP report file.
5-9
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 5 Report and Template Management
Note:
1) Template file design can start after a new template file is created. Refer to Section 5.5.1 “Designing a
Template File” for the detailed operation procedure.
2) The user can invoke the template file to query for report. Refer to Section 5.5.2 “Querying a Template
File” for the detailed operation procedure.
3) For the report with statistic time limit, create a new scheduled task for its template file. Refer to 5.4.1
“Creating a Scheduled Task” for the detailed operation procedure.
1) Select the template group or sub-template group to be created with new template
file and then [Operation/New Template] in the window as shown in Figure 5-1.
The system pops up the New Template window, as shown in Figure 5-9.
2) Input the related information of template file and then click <OK> to fulfill the
operation of creating a new template file.
5-10
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 5 Report and Template Management
For the description of the fields related to the operation of creating a template file,
please refer to Table 5-3.
Table 5-3 Description of fields related to the operation of creating a template file
5-11
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 5 Report and Template Management
I. Task description
5-12
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 5 Report and Template Management
For the description of the fields related to the operation of modifying a template file,
please refer to Table 5-3.
I. Task description
5-13
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 5 Report and Template Management
I. Task description
Figure 5-11 Selecting the path of downloading the template file and the file name
2) Select the path of downloading the template file and input the file name (the
default file name: The name of template file. frf) for saving.
3) Click <Save> to fulfil the operation of downloading the template file.
I. Task description
It is to upload the local .frf file of the template file to the report server.
1) Select the template group or sub-template group whose template file needs to be
uploaded and then [Operation/Upload Template] in the window as shown in
Figure 5-1. The system pops up the Open dialog box, as shown in Figure 5-12.
5-14
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 5 Report and Template Management
2) After selecting the template file to be uploaded, click <Open>. The system
generates a template file under the current template group or sub-template group.
I. Task description
It is to use the local template file to overwrite the template file on the report server, so as
to upgrade the template file of report server.
5-15
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 5 Report and Template Management
2) After selecting the local template file, click <Open> to upgrade the template file of
report server.
The operation of changing to folder of template file is similar to that of template group.
Therefore, please refer to Section 5.1.4 “Changing to Folder”.
I. Task description
It is to create a new scheduled task for a template, so as to query the report at the
specified time.
Note:
For the reports with statistic time limit (e.g. daily reports need statistics at 4 a.m. every day, monthly reports
need statistics on the first day of each month, etc.), create a scheduled task for its template file.
5-16
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 5 Report and Template Management
1) Select the template file to be created with new scheduled task and then
[Operation/New Schedule] in the window as shown in Figure 5-1. The system
pops up the New Schedule window, as shown in Figure 5-14.
Caution:
Only if the check box Activate This Schedule is checked, and after it is monitored and meets the
execution condition, the scheduled task can be executed automatically. For the related operations of
monitoring the scheduled task, refer to Section 2.3.1 “Schedule Monitor”.
2) Select Schedule Type and Schedule Start Date. Then, click <Advanced>. The
system pops up the window for setting the advanced property of scheduled task,
as shown in Figure 5-15.
5-17
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 5 Report and Template Management
3) After setting the advanced property of scheduled task, click <OK> to return to the
New Schedule window.
4) Click <OK> to create a new schedule.
For the description of the fields related to the operation of creating a scheduled task,
please refer to Table 5-4.
Table 5-4 Description of fields related to the operation of creating a scheduled task
5-18
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 5 Report and Template Management
Note:
1) Additional Condition is the most commonly used advanced property. Time macro is allowed in the
additional query condition.
2) The format of macro time is [Time format, difference of execution and current time]. In parameter
difference of execution and current time, + means time behind and – means time ahead. Y stands for
year, M for month, D for day and H for hour. The smallest unit is hour.
5-19
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 5 Report and Template Management
Example:
Suppose the current execution time of some scheduled task is 12:00:00 06-26-2002,
the returned results of time macro and their meaning are shown in Table 5-5.
"(StatDate >= '[YYYY-MM-DD, -M1]') and (StatDate < '[YYYY-MM-DD]')" are usually
used in the monthly statistic report, indicating that the time range for querying the report
is from the last month to the current execution time.
I. Task description
5-20
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 5 Report and Template Management
2) Modify the property of the scheduled task. Or click <Advanced> to modify the
advanced property of the scheduled task.
3) After the modification is completed, click <OK> to modify the scheduled task.
For the description of the fields related to the operation of modifying a scheduled task,
please refer to Table 5-4.
I. Task description
5-21
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 5 Report and Template Management
I. Task description
2) The user can perform the operations related to the report design in this window,
such as configuring the datasource for report access, customizing the advanced
properties of field and setting controls. For the detailed operations, refer to Module
5 “Report Customization Examples”.
5-22
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 5 Report and Template Management
I. Task description
It is to query the database according to the designed template file to generate report.
1) Select the designed template file and then [Operation/Query Template] in the
window as shown in Figure 5-1.
2) If query condition, sorting condition or query statement has been set upon the
report design, the system will pop up the query window, as shown in Figure 5-18.
Otherwise, the system will execute the query operation automatically without
popping up the query window. After the related query condition is set, click <OK>.
Note:
The window as shown in Figure 5-18 is only an example of the report system query window. The window
will vary with the different template file designed by the user. At most five areas will be included in this
window. For the detailed description, refer to Table 5-6.
3) Finally, the system will pop up the report browsing window, as shown in Figure
5-19. Meanwhile, the newly generated report file will be added in the right box.
5-23
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 5 Report and Template Management
A complete report query window consists of heading area, condition list area, input area,
buttons and SQL information area. Please refer to Table 5-6 for details.
Area Description
Top part of the window, as shown in Figure 5-18, providing some
Heading area
prompt to the user
Middle part of the window, as shown in Figure 5-18, in which the user
Condition list area
can set the information related to the query field or sorting.
Not displayed in the window, as shown in Figure 5-18, generally under
Input area Condition list area. The user can input a part of the SQL statement for
powerful function.
The area of the window, as shown in Figure 5-18, where such buttons
Button area as <SQL>, <OK>, <Cancel>, etc are located The user can click the
button as required.
The lowest part of the window, as shown in Figure 5-18, which displays
the generated SQL statement in real time and can be hidden by clicking
<SQL>.
SQL information area
Only if Show SQL or Hide SQL is set in the operation of setting the
report query window, this area may appear. Please refer to “Setting the
Report Query Window” part.
Please refer to Table 5-7 for the detailed attention points in setting Query Field,
Custom Sorting and Custom SQL in the report query window.
5-24
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 5 Report and Template Management
Field Description
It sets a condition of a certain field. For instance, if the field stands for
Sign 1, Value 1 month, sign 1 means later than and value 1 indicates February, the
meaning of this field is the month later than February.
It sets another condition of a certain field. It is valid only if And/Or is set.
For instance, if the field stands for month, then sign 2 means earlier than
Sign 2, Value 2
and value 2 indicates June. The meaning of this field is the month earlier
than June.
Query Field It shows the relationship between the two conditions of a field. If it is set
And/Or to And, the query condition of the month field is that the month is
between February and June.
It sets the relation between the condition of the current line and that of
And / Or column
the next line.
It is the description about this line, e.g. value range, meaning of the
Note current condition. By clicking the button, a dialog box will pop up to
display the note.
It sets the sorting type based on this field. Ascending order,
Custom Sorting Sign 1, value 1 descending order and not sorting (select the option without value in
the drop-down list) are optional.
Adding the
Input manually the From statement after the previous From statement.
From statement
It is usually "Sign, Table name”, e.g. “, Table1”.
manually
Setting the Input manually the From statement to overwrite the previous From
From statement statement. It is usually "Table Name1, Table Name2 …”, e.g. “Table1,
manually Table2”.
Adding the
Custom SQL Input manually the Where statement after the previous Where
Where
statement. It is usually "Sign condition”,
statement
e.g. “And (Ranged = 100)”.
manually
Setting the
Input manually the condition statement to overwrite to the previous
Where
Where statement. It must be a completed condition, e.g. “(Tableid=14)
statement
And (Rangeid=100)”.
manually
I. Task description
It is to browse the report file generated upon querying the template file.
1) Select the template file queried in the window as shown in Figure 5-1 and the
generated report file in the right box.
2) Select [Operation/Display Report File], and the system pops up the report
browsing window, similar to Figure 5-9.
5-25
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 5 Report and Template Management
I. Task description
It is to delete the report file generated upon querying the template file.
1) Select the template file of the report file to be deleted in the window as shown in
Figure 5-1and the report file to be deleted in the right box.
2) Select [Operation/Delete Report File], and the system pops up a window
prompting “Are you sure to delete the Report File(s)?”
3) If the user clicks <OK>, the system will delete the report file. If the user clicks
<Cancel>, the system will cancel the deletion operation.
I. Task description
It is to save the report file to the local PC. It can be frf, as well as Excel, HTML, TXT
format, and so on.
1) Select the template file for saving the report file in the window as shown in Figure
5-1 and the report file to be saved in the right box.
2) Select [Operation/Copy Report File], and the system pops up the Save As dialog
box, as shown in Figure 5-20.
5-26
User Manual Client Management
iManager M2000 Intelligent Report System Chapter 5 Report and Template Management
After selecting or inputting the saving path, file name and saving type of the report file,
click <Save>. The system will copy the report file.
5-27
HUAWEI
Table of Contents
i
User Manual Introduction to Report Designer
iManager M2000 Intelligent Report System Table of Contents
ii
User Manual Introduction to Report Designer
iManager M2000 Intelligent Report System Chapter 1 Introduction to Report Designer
This chapter mainly describes the report designer on such aspects as main menu,
toolbar, report object bar, and so on.
I. Main menu
z [File] menu
The [File] menu for template design contains all submenus listed in Table 1-1.
1-1
User Manual Introduction to Report Designer
iManager M2000 Intelligent Report System Chapter 1 Introduction to Report Designer
z [Edit] menu
The [Edit] menu for template design contains all submenus listed in Table 1-2.
z [Tool] menu
The [Tool] menu contains all submenus, as shown in Table 1-3.
z [Menu] items
Click [Options] submenu, then an option configuration window will pop up, as shown in
Figure 1-2.
1-2
User Manual Introduction to Report Designer
iManager M2000 Intelligent Report System Chapter 1 Introduction to Report Designer
Column Meaning
Show grid Whether to show the grids of the design environment
Align to grid The object can be for one grid each time
Designer Drawing objects Whether to show object content during movement
page Grid size Including three kinds of pixels as 4/8/18
Report units Including 3 units: pixel, mm and inch
Page position 3 locations: center, left and right
Colored buttons Whether to show the button colors
Whether to add an object, which can automatically display the Edit
Editing after insert
Others window.
Show report band titles Whether to show the title of the report band object
Localize property names Whether to display the localized attribute name in the object viewer,
Use the object’s font All editors use the font of this object
Editor page
Use fixed setting Each editor uses specified font
1-3
User Manual Introduction to Report Designer
iManager M2000 Intelligent Report System Chapter 1 Introduction to Report Designer
1.2 Toolbar
When the cursor stays on the shortcut button for 2 seconds, the system will pop up the
description of this button. All shortcut buttons are described in the following table in
detail:
1-4
User Manual Introduction to Report Designer
iManager M2000 Intelligent Report System Chapter 1 Introduction to Report Designer
Icon Descriptions
Set font
Set font size
Set the font as bold, italic and underlined
Set text color
If the specified condition is satisfied, all set objects will be displayed in the preset
condition.
It is used to set the Alignment mode (align against the left, center or the right)
The font can be aligned against the top, align against the center vertically and align
against the bottom
The object bar is used to display data set or self-defined information. You can place the
self-defined information in the report object bar to customize report.
1-5
User Manual Introduction to Report Designer
iManager M2000 Intelligent Report System Chapter 1 Introduction to Report Designer
This system is a report generating tool based on the report band design style. The
report band of the intelligent report system includes report title, report summation, page
header and footer, main item header, main item data, column header and footer, group
header and footer.
Click and drag it to the design interface, then the system will pop up a window of
Insert New Report Band Type as shown in Figure 1-6.
1-6
User Manual Introduction to Report Designer
iManager M2000 Intelligent Report System Chapter 1 Introduction to Report Designer
Once the report band type is selected, you can edit other report object elements. For
example:
z Select the Insert Page Header report band, then you can add several rectangle
rectangle text objects representing the data fields on the report band, and use
them to display the report data of the corresponding query result.
Caution:
To make a rectangle show the data field value, you must associate this rectangle with the data field or the
variable.
z Select to insert the report band Main Item Footer to perform statistics for the main
item data. Add rectangle text object to get the summation and average value,
etc. You can also directly enter the function in the text editor.
The detailed operation procedures are described in section 1.4.3 .
1-7
User Manual Introduction to Report Designer
iManager M2000 Intelligent Report System Chapter 1 Introduction to Report Designer
It is used to set multi-line text in a report, including setting the shape, color, size, font,
alignment mode and rotation of the text. It can also be used to set the variable, data
field and expression of the text, and to associate database fields.
Click to place a rectangle object on the window, then the system will automatically
pop up an Edit window in which you can input data. You may enter all kinds of
characters, associated data field or system variables, etc.
The rectangle text is used very frequently. It can be used for text edition, such as
inserting expressions and data fields, etc. Figure 1-8 shows the toolbar of the text
editor.
The format editor may be used to set the variable format of the text. The variables may
be displayed as plain text, numerical values, date, time and Boolean value.
1-8
User Manual Introduction to Report Designer
iManager M2000 Intelligent Report System Chapter 1 Introduction to Report Designer
Note:
The text object can also be used for other setting, such as:
Stretch Option: the character string of the text determines the object height. The report option switch of the
object must be open. Upon printing, the object will calculate the maximum height according to the stretch
option.
Auto Size Option: The object dimension will be automatically set.
I. Insert expression
You can enter the function format directly in the text editor for data statistics like
summation or averaging value. The expression editor is shown in Figure 1-9.
1-9
User Manual Introduction to Report Designer
iManager M2000 Intelligent Report System Chapter 1 Introduction to Report Designer
Buttons Descriptions
Used to show the field selection window.
Used to show variable selection window.
Used to show the function selection
window.
From left to right, such buttons are: plus,
minus, times, divide, equal to, unequal to,
greater than, smaller than, greater than or
equal to, smaller than or equal to, And, Or,
Not. Each button can be used to add a
symbol into the editor which has the related
function. For instance, click <Add> button,
"+" symbol will be added in the expression
input box.
1-10
User Manual Introduction to Report Designer
iManager M2000 Intelligent Report System Chapter 1 Introduction to Report Designer
this expression, Band1 is the position for the object name of the main item data
Band.
z Date: Return to the current date. For example: To add the current date in the
report, you can input the expression [DATE] in the Edit box. Note: the "[ ]" symbol
must be used to enclose the input expression.
z FORMATDATETIME: It is used to format the date output format. For example: To
get the date output format yyyy-mm-dd, you can use the following expression:
[FORMATDATETIME( 'yyyy-mm-dd',[date])].
z Time: Used to get the current time of the system.
z MAX: It is used to get the max. value of a field. The method is described in the Use
of AVG Function.
z MIN: It is used to get the min. value of a field. The method is described in the Use
of AVG Function
z PAGE#: Return to the current page. Upon printing, the report page No. may be
required. You can input [PAGE#] to get this number.
z SUM: It is used to calculate the summation of fields. The method is described in
the Use of AVG Function
z TOTALPAGES: It is set to show the total page number and often used at the end
of a report.
Caution:
To use this function, you must tick the option "Twice Report" in the "Report Setting" menu.
To get more information about a function, click this function, then the description of it
will appear on the lower part of the window, as shown in Figure 1-10.
1-11
User Manual Introduction to Report Designer
iManager M2000 Intelligent Report System Chapter 1 Introduction to Report Designer
For example: after selecting the AVG function, you should select the fields for this
function to get the average value to implement the "Insert Expression" function in the
rectangle text object (of course, this rectangle text object must be a text object added in
a report band).
1-12
User Manual Introduction to Report Designer
iManager M2000 Intelligent Report System Chapter 1 Introduction to Report Designer
Besides the variables in "Return Field, Query Conditions", other variables like variables
in the "System Variables" are also be applicable. After selection, click <OK> to save the
setting.
Similarly, you can also set the relationship between other rectangle objects and fields or
variables.
To make a rectangle show the numerical value of the data field, this rectangle must be
associated with the data field or the variable. Firstly enter the rectangle edit box, click
<Insert Field> button, then select a field for association in the popup window, as shown
in Figure 1-12.
1-13
User Manual Introduction to Report Designer
iManager M2000 Intelligent Report System Chapter 1 Introduction to Report Designer
1.4.5 Picture-
Set picture in the report based on BMP/WMF/ICO/JPG format. The picture may be
specified either from the file or from the large binary field of the database. The following
options may be set for graphics:
Stretch: Stretch the graphic to fill the rectangular box of the object.
Aspect ratio: Keep proper vertical and horizontal ratio when the object is being drawn.
1.4.6 Scribe-
This tool is be used to draw a horizontal or vertical line, to draw table lines. The user
can set the line width and line color.
1.4.7 Chart-
To set the chart object corresponding to the main item data, firstly use the chart object
to drag a report band of the main item data type to the interface, then set its data source
as a virtual data set.
After inserting the chart object into the design interface, the system will pop up a chart
attribute setting window, as shown in Figure 1-13.
1-14
User Manual Introduction to Report Designer
iManager M2000 Intelligent Report System Chapter 1 Introduction to Report Designer
The data to be entered into the chart type setting window are described in Table 1-9.
1-15
User Manual Introduction to Report Designer
iManager M2000 Intelligent Report System Chapter 1 Introduction to Report Designer
The data to be entered in the icon flag setting window are described in Table 1-11.
Five types of charts can be used in the report: line, point, bar, zone and cake.
Two text objects must be specified for the chart data as value and legend.
The text object of a chart value should include format symbols, such as "10 000.00" or
"$100.00". The system will automatically pick the figure from the text and ignore all
non-figure symbols. Higher formats like "10000km2" cannot be used as numerical value
1-16
User Manual Introduction to Report Designer
iManager M2000 Intelligent Report System Chapter 1 Introduction to Report Designer
of the chart. The chart value can only be invisible objects created with the same content
but without format.
The shadow rectangle object is used to show the special display effect and make the
report attractive. Drag a shadow rectangle object from the design toolbar to a report,
this rectangle object will automatically display the attribute edit box. The "Attribute Edit
Box" is illustrated in Figure 1-16.
The data parameters to be entered in the editor window for shadow rectangle attributes
are described as follows.
z The left window is used to enter data which can be a normal character string, or an
expression or a data field.
z The curve option indicates whether the four corners of the shadow edit box are
round. The value in the nearby editor box can be used to control the rounding
degree of each corner
z The shadow width indicates the shadow area size of the shadow rectangle object.
The color indicates the foreground color of the shadow rectangle object.
When the Italics Color is selected, the right option may change as shown in Figure
1-17.
1-17
User Manual Introduction to Report Designer
iManager M2000 Intelligent Report System Chapter 1 Introduction to Report Designer
The parameters for the color selection window are described as follows.
z Style: direction of the graded colors.
z Start color: the start color of the graded colors.
z End color: the end color of the graded colors.
1.4.9 Shapes-
In the report, following shapes can be generated: round, ellipse, rectangle, round-angle
rectangle, triangle, Diagonas, and so on.
The object viewer should be used to set the shape type. Select this object, press <F11>
or select [Tool/Toolbar/Object Viewer], then you can activate the object viewer, as
shown in Figure 1-18.
1-18
User Manual Introduction to Report Designer
iManager M2000 Intelligent Report System Chapter 1 Introduction to Report Designer
Parameters Descriptions
SkRectangle Rectangle
gsRoundRectangle Round-angle rectangle
SkEllipse Round
gsTrangle Triangle
gsDiagonal1 Left diagona
gsDiagonal2 Right diagona
Table 1-13 describes the normal attributes in the attribute setting window for the objects
shown in Figure 1-18.
1-19
User Manual Introduction to Report Designer
iManager M2000 Intelligent Report System Chapter 1 Introduction to Report Designer
Attribute Descriptions
BandAlign It is used to select the alignment mode for objects in the report band
FillColor Background color of the object
Border line color Object border line color
Border line type The type of the object border line
Border line width Width of the border line
Height Object height
Left margin X-axis position of the object
Invoke the input contents of the text editor, but if the object does not support
Contents
the content display, this attribute is invalid
Top margin Y-axis value of the object
Visible Whether the user can see the object
Width Object width
When the object length range is not large enough to display all the contents,
AutoWidth
the contents will be displayed in the next line automatically
Set a restriction to this object, for example: this object cannot be edited, or
Restrictions:
deleted, etc.
1. Memo cannot be edited
1. This object cannot be used to edit the displayed content
2. Contents cannot be edited
2. No content can be edited, nor any Edit window pops up
3. Cannot be modified
3. The object cannot be modified
4. Size cannot be changed
4. The object size cannot be changed
5. Cannot be moved
5. The object cannot be moved
6. Cannot be deleted
6. The object cannot be deleted
Stretched The object contents automatically fill the whole object display space
psSolid line
psDash line
psDot line
Border line type
psDashDot combination
psDashDotDot conbination
psDouble line
When insert a report object, if it is necessary, user can set its attributes in order to
output correct and applied Excel report format.
Select the Rectangle Text Object, press F11 or select [Tools/Toolbars/Object inspector].
In “Object inspector” window, as Figure 1-19 shown, about those detailed description of
attributes, please refer to 1.4.9 chapter.
1-20
User Manual Introduction to Report Designer
iManager M2000 Intelligent Report System Chapter 1 Introduction to Report Designer
User can design the output format of report by setting its “GridOption” item. The
process is shown as Figure 1-20.
1-21
User Manual Introduction to Report Designer
iManager M2000 Intelligent Report System Chapter 1 Introduction to Report Designer
z Column number in the grid : Which column does the rectangle text object locate in
the certain band?
z Row number in the grid: Which row does the rectangle text object locate in the
certain band?
z Width (how many columns): How many columns does the rectangle text object
cover in the certain band?
z Height (how many rows): How many rows does the rectangle text object cover in
the certain band?
Example, if “Total” item need cover two rows in output report, it can be realized by
setting “GridOption” in Object inspector window.
Once report is output, user can export it as frp, Excel, htm, txt format, and so on.
This align toolbar can be used to arrange multiple design objects in a certain order.
(The first selected object will be used as reference.) Table 1-14 describes the functions
of the alignment toolbar.
1-22
User Manual Introduction to Report Designer
iManager M2000 Intelligent Report System Chapter 1 Introduction to Report Designer
Controls Descriptions
Page setup
1-23
User Manual Introduction to Report Designer
iManager M2000 Intelligent Report System Chapter 2 Report Design
This includes the following items: query definition wizard, definition variables, and drag
report design objects to the interface to design, preview and save.
I. Task description
Select the template file to be designed and then click [Operation/Design Template].
The system pops up the report designer window, as shown in Figure 2-1.
2-1
User Manual Introduction to Report Designer
iManager M2000 Intelligent Report System Chapter 2 Report Design
Caution:
Please ensure that the fields and stored procedure adopted in designing the report template are the real
information in the database. Otherwise, abnormity may occur upon querying the report or previewing the
operation, or exiting the client may fail.
2.2.1 Overview
Defining the data source is to design a SQL command or a store procedure command
to access the database. Select the menu [File/Datasource manager] to invoke the
datasource definition wizard window, as shown in Figure 2-2.
2-2
User Manual Introduction to Report Designer
iManager M2000 Intelligent Report System Chapter 2 Report Design
This window has six pages: "Data Source", "Output Result", "User Query
Condition" and "Grouping and Sequencing". Through these five pages, you can
define the SQL command or the store procedure command.
Select A.a,B.b, Count (B.c) From A,B Where (A.a=B.a) and (A.a = X) Group by A.b
Order by B.b
Execute procedure C(v1, v2, v3) (Implicit definition, not reflected in the command)
z "User Query Condition" impact
Select A.a,B.b, Count (B.c) From A,B Where A.a=B.a and (A.a = X) Group by A.b
Order by B.b
Select A.a,B.b, Count (B.c) From A,B Where (A.a=B.a) and (A.a = X) Group by A.b
Order by B.b
"Sequencing" impact:
Select A.a,B.b, Count (B.c) From A,B Where (A.a=B.a) and (A.a = X) Group by A.b
Order by B.b
From the above description we can see: this interface disassembles the SQL command
and the standard store procedure command into different parts and then defines the
parts separately, so that the SQL command and the store procedure command can be
automatically combined for database query.
You cannot start design a report unless you understand the data table structure and
have registered the M2000 performance task.
2-3
User Manual Introduction to Report Designer
iManager M2000 Intelligent Report System Chapter 2 Report Design
Summarization is always necessary to get the required report measurement items via
the field result of data table.
z The summarizing mode may be summation, average calculation or the
combination of the two modes. Here two concepts are involved as time dimension
and object dimension. In a task you can summarize the results of an object on an
index by time. Similarly, you can summarize the measured objects in a task.
z The summarization level may be Not Summarize, One-level Summarize or
Two-level Summarize. Two-level Summarize is to summarize the result data
according to certain conditions first, then summarize the result of the first
summarization so as to complete the whole summarizing process. The intelligent
report can carry out two levels of summarization at most.
How to define summarizing modes and summarizing levels depends on how much the
report maker understands about the report and the indices.
Multiple tasks may be generated after the indices required for report measurement item
are registered.
z If the objects of these tasks are completely consistent, the report measurement
items may not be disassembled. Tasks can be associated through objects and
time.
z If the objects of these tasks are not consistent, you should decide whether to
disassemble the report. For example: The measurement item of a report requires
to generate report records by means of NE, but the objects in the measurement
item including Mobile Switching Center (MSC) and office direction. Then, you can
summarize the office directions of this NE first and associate these office
directions with the MSC objects. In this case, you may not disassemble the report.
Normally, it is recommended to disassemble the report into several sub-reports for
statistics.
The data source is the statistics result set of registered system measurement tasks,
therefore, user should complete system traffic registration on the performance Client
prior to making a report.
Defined data source is used as the input source upon report generation.
2-4
User Manual Introduction to Report Designer
iManager M2000 Intelligent Report System Chapter 2 Report Design
I. Task description
Datasource definition is very important. It defines the source of report data. In addition,
it specifies which data field to be returned and what conditions to be followed to return
the "Output Field". The user query "Condition" defines which fields to be queried upon
query statistics and how to sequence the returned fields. You cannot get the correct
data to generate reports unless the above steps are correctly defined.
2) The user can set the datasource, data table and stored procedure accessed by the
report in the Datasource tab page in the Report Template Datasource Manager
window. As shown in Figure 2-2, after the user selects the datasource to be
2-5
User Manual Introduction to Report Designer
iManager M2000 Intelligent Report System Chapter 2 Report Design
accessed by the report in the drop-down list box, all the tables and stored
procedures corresponding to the datasource will be listed in the lower box. The
user can add or delete the tables and stored procedures with the four buttons in
the middle (refer to Table 2-1 for the functions of the four buttons). The right box
will list the tables and stored procedures required by the user.
Note:
One report can only use a datasource, but it can use one or more tables. However, only one stored
procedure is allowed for a report.
3) The user can define the returned result of the report query through switching over
to the Output Result tab page as shown in Figure 2-3.
Note:
1) The user can define the return field for the report query and the order of the fields. If a stored procedure
is queried, all fields must be returned in sequence.
2) If the user checks check box Use Keyword “Distinct”, the return record for the report query is unique.
In the case of report with large data, the user may check the Return Records Only check box, then the
system will only return the specified mount of records.
2-6
User Manual Introduction to Report Designer
iManager M2000 Intelligent Report System Chapter 2 Report Design
4) If the user expects that the returned result is an expression consisting of several
fields, just click to enter the window for editing computed columns, as shown
in Figure 2-4.
2-7
User Manual Introduction to Report Designer
iManager M2000 Intelligent Report System Chapter 2 Report Design
5) After setting the column expression, click <OK> to return to Output Result tab
page. The generated column expression is also the output result of report query.
For the setting of the column expression, refer to the example in the latter part of
this section.
6) After switching to the Conditions tab page as shown in Figure 2-5, the user can set
three additional conditions – Condition, Query Field and Extended in this tab page.
2-8
User Manual Introduction to Report Designer
iManager M2000 Intelligent Report System Chapter 2 Report Design
2-9
User Manual Introduction to Report Designer
iManager M2000 Intelligent Report System Chapter 2 Report Design
Note:
1) If the user selects Condition, these conditions will be added to the Where part of the SQL statement
directly. It should be noted that the stored procedure has no default condition.
The method of setting the default condition is: In the left panel, select field 1 and field 2 in the upper list box
and the lower list box respectively, define the signs and add them into the right list. The condition relation
between lines can be adjusted with <AND> and <OR>, and their order can be adjusted with and
.
If the macro LoginUser is selected, it will be replaced by the current user ID.
2) If the user selects Query Field, he can set the condition as he wants with the selected field during the
query. Please refer to Section 5.5.2 “Querying a Template File” of Client Management module for the
detailed operations. Two condition formats of "Field = Field" and "Field = Constant" are allowed in the
Condition tab page, while only the latter is allowed in the Query Field tab page.
The method of setting Condition is as follows: Double click the selected query field to set its advanced
properties. Please refer to Section 2.4 “Customizing Advanced Properties of Query Field” for the detailed
operations.
The query field includes the macro, which is the variable name within the symbol {} and can be defined by
the user. Please refer to Section 2.6 “Creating a Macro”.
3) If the user selects Extended, the user can input the From and Where parts of the SQL statement. The
input can be set at the end of original table or conditions, or be set to overwrite the original table or
conditions.
Due to manual input, the report system cannot ensure the correctness of the input. Please input the
contents based on rules. For the rules, please refer to Section 5.5.2 “Querying a Template File” of Client
Management module .
If Set When Querying is checked, the user should input these extended conditions upon querying report.
7) After switching to the Group And Sort tab page as shown in Figure 2-6, the user
can set the grouping or sorting conditions for the output result of the report.
2-10
User Manual Introduction to Report Designer
iManager M2000 Intelligent Report System Chapter 2 Report Design
Note:
1) If the user needs to set Group Field, the selected fields will be added to the Group By part of the SQL
statement in turn. They do not affect the stored procedure.
According to the SQL syntax, each non-computed column will be automatically added into the group field if
the computed column is adopted in the output result.
By clicking and , the order of group fields can be adjusted. The output results will vary with
the different sequences.
2) If the user needs to set Sort Field, the selected fields will be added to the Order By part of the SQL
statement in turn. They do not affect the stored procedure.
The sorting mode is selected through / .
By clicking and , the order of sort fields can be adjusted. The output results will vary with the
different sequences.
3) If the user needs to set Custom Sorting, the selected fields will also be added sequentially into the
Order By part of the SQL statement. However, which order to be used and whether to sort are determined
by the querying user.
Double click the selected the field for sorting or click after selecting the field for sorting to set its
advanced properties. Please refer to Section 2.5 “Customizing Advanced Properties of Sorting” for the
detailed operations.
By clicking and , the order of sort fields can be adjusted. The output results will vary with the
different sequences.
2-11
User Manual Introduction to Report Designer
iManager M2000 Intelligent Report System Chapter 2 Report Design
8) After switching to the Custom SQL tab page as shown in Figure 2-7, the user can
customize the SQL statement for report query.
Note:
1) There is a certain format for the user-defined SQL statement. The user can click <About User-defined
SQL> to view the points for attention when manually typing the SQL statement.
2) All functions of Custom SQL can be fulfilled with Extended in the Conditions tab page.
3) If Use The User-defined SQL, Condition and Group And Sort are selected, the relevant setting on
the tab page and the limit condition for the datasource are all invalid. However, the user-defined macro is
valid. Therefore, the user can define macro as the SQL statement to add the user-defined query condition,
or sorting and grouping condition.
4) It is recommended to modify the required SQL statement based on the current SQL statement after
clicking <Show Current SQL>.
5) After customizing the SQL statement, query the report to see whether the correct result can be returned.
2-12
User Manual Introduction to Report Designer
iManager M2000 Intelligent Report System Chapter 2 Report Design
Suppose fields sum1 and sum2 in the accessed table represent income1 and income2
respectively. The income of the whole year is sum1 plus sum2.
10) Select [intpdb2.Table.Test.Field.income1] in the Columns drop-down list box in
the window as shown in Figure 2-4
11) Click <Insert> to add the field into the Value of computed column text box, as
shown in Figure 2-8.
2-13
User Manual Introduction to Report Designer
iManager M2000 Intelligent Report System Chapter 2 Report Design
Figure 2-8 Adding the field of the first half year income to the column expression
2-14
User Manual Introduction to Report Designer
iManager M2000 Intelligent Report System Chapter 2 Report Design
For the description of controls in the Report Template Datasource Manager window,
refer to Table 2-1.
Table 2-1 Description of controls in the Report Template Datasource Manager window
2-15
User Manual Introduction to Report Designer
iManager M2000 Intelligent Report System Chapter 2 Report Design
The variable setting function is mainly to shorten and simplify the field length, therefore
a variable must be set to make a simplified alias for the data field after the query
definition wizard has been set. The generated variables can be either used for report
design or for query statistics.
Select [File/Data dictionary] from the toolbar to pop up the "Set Variables" window.
The default variables are returned fields and user conditions which are used to create
aliases for returned fields and user conditions, etc.
The pull-down list box: contains [MainRptDataSet] and [System Variables]. The
former is the dedicated data set of the system and cannot be modified by the user, while
the latter lists all variables of all current system definitions, such as date variables, and
row variables, etc. The user can define another variable to contain these variables.
2-16
User Manual Introduction to Report Designer
iManager M2000 Intelligent Report System Chapter 2 Report Design
Caution:
The alias variable is exclusive. In other words, if this variable has appeared in one variable directory, it will
not appear in another variable directory.
2-17
User Manual Introduction to Report Designer
iManager M2000 Intelligent Report System Chapter 2 Report Design
Select "Return Field, User Condition", click <New Variable> to create a variable "ME
ID", then click the "PerformanceDB.TB.Digital Mobile Switch Traffic.FD.ME ID" in the
right part of the window, thus the association between the variable and the field is
established as shown in Figure 2-11.
Similarly, more associations of between variables and fields can be established. The
variable names must be exclusive.
I. Task description
It is to customize the advanced properties of query field. The advanced properties will
be shown in the report query window once they are set.
1) Select a condition in the Query Field box in the Condition tab page in the Report
Template Datasource Manager window, and then click . The system pops up
2-18
User Manual Introduction to Report Designer
iManager M2000 Intelligent Report System Chapter 2 Report Design
the window for customizing advanced properties of the query field, as shown in
Figure 2-12.
In the window for customizing advanced properties of the query field, the operation
objects include Query Field Caption, Setting Control, Operators, Description,
Default value and Value expression.
2) After setting the advanced properties, click <OK>.
For the description of the fields and controls related to the operation of customizing
advanced properties of the query field, please refer to Table 2-3.
2-19
User Manual Introduction to Report Designer
iManager M2000 Intelligent Report System Chapter 2 Report Design
Table 2-3 Description of fields related to the operation of customizing advanced properties of query field
For the description of the related controls, please refer to Table 2-4.
2-20
User Manual Introduction to Report Designer
iManager M2000 Intelligent Report System Chapter 2 Report Design
2-21
User Manual Introduction to Report Designer
iManager M2000 Intelligent Report System Chapter 2 Report Design
The time formats available for the time picker are shown in Table 2-5.
I. Task description
1) Enter the Custom Sorting tab page in the Group And Sort tab page of the Report
Template Datasource Manager window, as shown in Figure 2-13.
2-22
User Manual Introduction to Report Designer
iManager M2000 Intelligent Report System Chapter 2 Report Design
2) Select a field and click , then the system pops up the window for setting
advanced properties of sorting for the field, as shown in Figure 2-14.
3) The user may set the allowed sorting modes and the default sorting mode for the
field.
Note:
In Figure 2-14, checking the check box means that the sorting mode is allowed and selecting the radio
button indicates that the sorting mode is the default.
I. Task description
It is to create a new macro. And it is valid in User-define SQL, Condition, Query Field
and Extended.
Note:
1) When setting query conditions, the macro appears in the conditions and it should be set by the user.
2) The user can add the macro in the customized SQL statement, thus the user can add the customized
conditions to the customized SQL statement.
3) The example taken in this section is creating a new macro in the Condition box in the Condition tab
page in the Report Template Datasource Manager window.
2-23
User Manual Introduction to Report Designer
iManager M2000 Intelligent Report System Chapter 2 Report Design
1) Enter the Query Field box in the Condition tab page in the Report Template
Datasource Manager window, as shown in Figure 2-15.
2) Click and then the system pops up the New User-defined Macro window, as
shown in Figure 2-16.
2-24
User Manual Introduction to Report Designer
iManager M2000 Intelligent Report System Chapter 2 Report Design
3) Check the Edit The Macro Immediately check box, and click <OK> after filling in
the related information. The system pops up the window for customizing advanced
properties of the query field, as shown in Figure 2-17.
For the description of the fields related to the operation of creating a macro, please
refer to Table 2-6 .
Default
Field Description Value range
value
It is a string of 64 bytes at most. It cannot be the same as
Macro Name Name of the macro
the name of user-defined variable and function.
If yes, sign and value are valid simultaneously in the
Whether signs are
Include Sign query window; otherwise, only value is valid. No
contained
Yes or No
Edit The Whether to edit macro The properties of macro are the same as the advanced
Macro properties immediately properties of query field. Yes
Immediately after creation Yes or No
2-25
User Manual Introduction to Report Designer
iManager M2000 Intelligent Report System Chapter 2 Report Design
I. Task description
1) Select [File/Set Interface for querying window] in the report designer window, as
shown in Figure 2-1, and then the system pops up the window for setting the style
for querying window, as shown in Figure 2-18.
Figure 2-18 Setting the style for the report query window
2) The user can set the style for the report query window in the window above. Click
<OK>. Then the system will save the setting of user.
For the description of the fields related to the style setting operation, please refer to
Table 2-7.
2-26
User Manual Introduction to Report Designer
iManager M2000 Intelligent Report System Chapter 2 Report Design
I. Task description
It is to add notes to the current template. A good report note should contain the key
content of the report. Thus, it is convenient for the sequent design of other people since
they can learn the intention of the original designer with ease by editing the report note.
1) Select [File/Edit the report comment] in the report designer window, as shown in
Figure 2-1 , and then the system pops up the Report template file comment
definition window, as shown in Figure 2-19.
2-27
User Manual Introduction to Report Designer
iManager M2000 Intelligent Report System Chapter 2 Report Design
Figure 2-19 Defining the notes for the report template file
From the figure, we can know that each note falls into Caption and Description, in the
string without length limit.
Note:
1) If the number of items to be added exceeds six, click <È> after selecting the last item to add a note.
2) At most 64 notes are allowed.
Click <OK>. Then, the system will save the notes of report template file.
I. Task description
It is to set the style and mode of report in the report template builder.
2-28
User Manual Introduction to Report Designer
iManager M2000 Intelligent Report System Chapter 2 Report Design
2) Specify the report style based on the actual requirement or personal preference
and then click <OK>. The system will save the modification of user. Once the user
queries the report with this template file again, the report in new style will be
generated.
The Report Template Builder window consists of four tab pages, i.e. Data, Title, Table
Style and Page Header/Footer. Please refer to Table 2-8 for details.
Table 2-8 Description of tab pages in the Report Template Builder window
2-29
User Manual Introduction to Report Designer
iManager M2000 Intelligent Report System Chapter 2 Report Design
I. Task description
1) Select and drag the Master Fooder report in the report designer window, as shown
in Figure 2-1. Click in the left tool bar, and then the system will add a statistic
chart object in the blank area of the Master Fooder report. Double click the object
to pop up the chart object window, as shown in Figure 2-21.
2) After the properties of chart object are set, click <OK>. When the user queries the
report with this template file again, the statistic chart expected by user will appear.
The chart object window includes three tab pages, i.e. Type, Data and Marks. Please
refer to Table 2-9 for the description.
2-30
User Manual Introduction to Report Designer
iManager M2000 Intelligent Report System Chapter 2 Report Design
The content of this section is identical with that in Section 5.6.2 “Querying the Template
File” of Client Management module. Please refer to the section.
2-31
HUAWEI
Table of Contents
i
User Manual Collection of Original Data
iManager M2000 Intelligent Report System Chapter 1 Collection of Original Data
After getting the report style and understanding the meaning of each measurement
item in the report format, we should first figure out where to get the data (namely the
data source) and how to perform mapping between data of data source and
measurement items in the report so as to complete this report
The iManager M2000 system provides database interfaces to users through the
configuration database “cfgdb” and the performance database “pmdb”, which are the
most common means. These two databases are the data sources for report creation.
We set the data sources respectively as m2000.cfgdb and m2000.pmdb.
To map the data in the data source to the measurement items of the report, the report
designer has to understand the table structure and related information provided in the
data source.
In the iManager M2000 performance database pmdb, the key data table is the Task
Result Table.
The user can specify relevant performance items and objects as required to register a
task. Each task forms a table in the performance database, namely the Task Result
Table. Task Result Tables keeps the object result data in each period. Relying on
these data, the user can make reports with relevant performance.
A Task Result Table can be named as tbl_rstxxx, in which xxx is the task No.
generated after the task is successfully registered. The user can get this task No. by
viewing the task list on the performance console of the iManager M2000 system.
Table 1-1 The field information of the Task Result Table is:
1-1
User Manual Collection of Original Data
iManager M2000 Intelligent Report System Chapter 1 Collection of Original Data
Field name:
|validate|dw_me_id|starttime|stat_period|objset_m0|objset_m1|objset_m2|m_id300|m
_id301|m_id317|
1-2
User Manual Collection of Original Data
iManager M2000 Intelligent Report System Chapter 1 Collection of Original Data
The table structure of the system configuration database cfgdb is described in the
appendix. You can also query the cfgdb table structure in the server in the following
methods:
1>use cfgdb
2>go
2>go
You may only query the system tables like tblClass, tblMO, tblManagedElement,
tblInherited, tblAttr, tblString, tblList and tblInvalid etc.
1>sp_help tblMO
2>go
Once you have understood the above task result tables, you can complete the
mapping for report data.
The report data mapping contains two parts: index mapping and object mapping.
I. Index mapping
To map the indices of a report measurement item, you should take the following
steps:
z Find the corresponding item in the item set for all report measurement items
according to their meaning. Sometimes, report measurement may be
corresponding to one item or realized by calculation of multiple items. You
should remember the function set name, item ID and object type for each item.
z Classify the items belonging to the same function set and sharing the same
object type as one group.
z Register performance tasks on the performance console by group with the
consistent task period. After registration, you can see the task No. of this task on
the iManager M2000 performance Client. The detailed registration steps are
described in "Measurement Task Registration".
1-3
User Manual Collection of Original Data
iManager M2000 Intelligent Report System Chapter 1 Collection of Original Data
Note:
Whether to group the items can be judged on the iManager M2000 performance application Client.
When registering performance tasks and selecting items on the performance Client, you can classify the
items that can be selected together as one group.
All values of the performance result table object members from objset_m1 to
objset_mn are presented via ObjectID or the character string entered by the user. In a
report, members of the ObjectID type should be translated into information which can
be detected by the user. To map the objects, you should take the following steps:
z Get the related object type according to the registered task. This object type can
be detected on the performance Client. Get the object structure from the
appendix.
z Get object members of the object structure according to the report measurement
objects. Namely, which object member should be used to match the report
measurement item. For example: The object members of a multi-condition object
are: MSC, calling number, call source office direction, outgoing office direction,
called number, and call attribute. If the report is output as per the calling number,
the object member is objset_m2. If the report is output as per the call source
office direction, the object member is objset_m3.
z If an object member is ObjectID, it should be translated via the object information
table in the configuration database. You should first get the table name of this
object type in the configuration database table. For example: If you perform
report measurement by office direction, the name of the office direction ObjectID
should be corresponding to the configuration table tblOffice. Then you should
record the name of the required configuration table and understand the field
structure of this configuration table.
z To map the data in the performance database and the configuration database,
you should create the mapping of the configuration table in the performance
database. If the configuration table to be mapped is tblOffice, you may observe
the following steps:
m2000 user:
1>use pmdb
2>go
1-4
User Manual Collection of Original Data
iManager M2000 Intelligent Report System Chapter 1 Collection of Original Data
2>go
1>quit
In the M2000 IN report system, the performance measurement task result table is
used as the data source for report designing, therefore you must register the
performance measurement task to customize report templates in the report system.
Note:
The performance measurement task can only be created by users who have at least the normal service
operation authority for centralized performance management.
The following are the detailed steps for measurement task registration:
1) In the centralized performance management system select the menu
[Task/New], then a dialog box for new tasks will pop up, as shown in Figure 1-1.
1-5
User Manual Collection of Original Data
iManager M2000 Intelligent Report System Chapter 1 Collection of Original Data
Note:
If a specific NE is selected, the report data only contains the measurement data of this NE.
If all NEs are selected, the report data will contain the measurement data of all NEs.
It is recommended to select all NEs if allowed by the resources.
To select objects for the multi-object parameter structure, please see Section 1.2.2 of this module for
details.
3) Click the page tag "Item Info." to select the performance index items to be
measured, as shown in Figure 1-2. On the left are the indices to be selected and
on the right are the selected ones. You may click the buttons in the middle to
select or remove the items.
1-6
User Manual Collection of Original Data
iManager M2000 Intelligent Report System Chapter 1 Collection of Original Data
Note:
You may only select the indices required currently, or some other indices for report extension.
4) Click the "Time Info" page tag to set the time information of the measurement
task, as shown in Figure 1-3.
1-7
User Manual Collection of Original Data
iManager M2000 Intelligent Report System Chapter 1 Collection of Original Data
On the "Time Info" page, you can set information concerning the measurement time
including measurement period, time segment, measurement mode, and so on. Table
1-2 describes all the parameters.
Column Description
It is the start date of the measurement task and set as the current system
Start Date
date.
It is the measurement period with the unit as minute. The recommended
Measurement Period
period is 60 minutes.
It is the measurement time segment for report making. It can be the
Measurement Time Segment user-defined busy-hour time segment. The default time segment can be set
as 00:00~24:00
Please select the "Semi-permanent" type. It is a task with start date only,
Measurement Type
namely this task will not stop unless it is canceled manually.
Duration of a task with a limited period. It is invalid to the "semi-permanent"
Number of measurement days
task.
Please select measurement by day. The measurement by day starts from
Measurement mode
the start date. It is activated every day during the limited period.
Storage duration of the latest Store the latest measurement results generated since the start date. The
measurement result default duration is 7 days.
1-8
User Manual Collection of Original Data
iManager M2000 Intelligent Report System Chapter 1 Collection of Original Data
Note:
In the "Measurement Time Segment" you may enter three time segments. If the actual measurement
time segments of a task are less than three, you may enter the actual time segments in the time order
and leave the rest time segments as null. The system will automatically calculate the number of time
segments used in the task.
After setting the "Object Information", "Index Information" and "Time Information",
click <OK>, then the system checks whether any invalid or incomplete parameter
exists. If there is any invalid or incomplete, the system will report the error information
and ask you to enter the parameters again.
5) If there is no incorrect information, the system will create a new task and pop up
a task registration response window and display the operation results:
Succeeded.
The overall operation result is displayed in the information column on the upper part
of the window, including success or failure, as well as the failure causes. In the lower
part are the results of all NEs registered in this task, including success or failure, as
well as the failure causes. Only when the operations on all NEs concerned in this task
are successful, will the system display success in the overall result report.
If a task is successfully created, its information will be added to the task list window.
1-9
User Manual Collection of Original Data
iManager M2000 Intelligent Report System Chapter 1 Collection of Original Data
Selection modes:
z Switch: Selected from the interface
z Caller number: Manually enter the prefix of the calling number
z Inlet office direction No.: Selected from the interface
z Outlet office direction No.: Selected from the interface
z Called number: Manually enter the prefix of the called number
z Call type: Selected from the interface
1-10
User Manual Collection of Original Data
iManager M2000 Intelligent Report System Chapter 1 Collection of Original Data
Selection modes:
z Observed cell: Selected from the interface
z Adjacent cell CGI: Manually enter the CGI of the adjacent cell
1-11
User Manual Collection of Original Data
iManager M2000 Intelligent Report System Chapter 1 Collection of Original Data
Figure 1-6 Selection interface for office direction destination object information
Selection modes:
z Office direction: Selected from the interface
z Destination: Selected from the interface
1-12
User Manual Collection of Original Data
iManager M2000 Intelligent Report System Chapter 1 Collection of Original Data
Figure 1-7 Selection interface for intelligent event measurement parameter object
Selection modes:
z Service key: Selected from the interface
z SCP: Selected from the interface
1-13
User Manual Collection of Original Data
iManager M2000 Intelligent Report System Chapter 1 Collection of Original Data
Selection modes:
z DSP: Selected from the interface
z Source network flag: Selected from the interface
z Source signaling point code: Manually enter it (OPC)
The relative content of adding data source has been introduced in second chapter.
In the iManager M2000 system, following information may be displayed after the initial
installation:
1-14
User Manual Collection of Original Data
iManager M2000 Intelligent Report System Chapter 1 Collection of Original Data
You cannot start to design a report unless you have understood the data table
structure and registered the M2000 performance task.
Summarization is always necessary to get the required report measurement items via
the field result of data table.
z The summarizing mode may be summation, average calculation or the
combination of these two modes. Here two concepts occur as time dimension
and object dimension. In a task you can summarize the results of an object on
an index by time. Similarly, you can summarize the measured objects in a task.
z The summarization level may be Not Summarize, One-level Summarize or
Two-level Summarize. Two-level Summarize is to summarize the result data
according to certain conditions first, and then summarize the result of the first
summarization according to certain conditions so as to complete the whole
summarizing process. The intelligent report can carry out two levels of
summarization at most
1-15
User Manual Collection of Original Data
iManager M2000 Intelligent Report System Chapter 1 Collection of Original Data
Confirm whether to disassemble all measurement items in the report into sub-reports.
Multiple tasks may be generated after the indices required for report measurement
item are registered.
z If the objects of these tasks are completely consistent, the report measurement
items may not be disassembled. Multiple tasks can be associated through
objects and time.
z If the objects of these tasks are not consistent, you should judge whether to
disassemble the report. For example: The measurement item of a report requires
to generate report records by means of NE, but the objects in the measurement
item including switches and office directions. In this case, you can summarize
the office directions of this NE first, and then associate these office directions
with the switch objects. Then, you may not disassemble the report. Normally, it is
recommended to disassemble the report into several sub-reports for
measurement.
Now, you have finished the three steps: M2000 index mapping, measurement task
registration and data source configuration. Then you can start template designing.
The detailed description is available in the part of "Introduction to IN Report
Designer".
1-16
HUAWEI
Table of Contents
i
User Manual Report Customization Examples
iManager M2000 Intelligent Report System Chapter 1 Report Customization Examples
Report construction can be realized via two modes: generated via the system’s preset
template and customized.
To generate reports via the system’s preset template, you may only register the system
task on the centralized performance application console of the iManager M2000
system, then select the report template in the intelligent report system, and enter the
user query conditions.
The process of customizing reports is described in the System Principle part of this
manual.
1-1
User Manual Report Customization Examples
iManager M2000 Intelligent Report System Chapter 1 Report Customization Examples
Note:
During report construction, a lot of system resources will be used, therefore it is specially recommended to
exit all irrelevant application programs during this process. Previewing system report may affect the
system efficiency due to too many operations, therefore it is recommended to exit all irrelevant application
programs during this operation.
Code
It is obvious that fields like "ME Name" and "ME ID" are needed besides the index item
to customize a complete report.
The above report contains only one index. The following description demonstrates how
to collect data of “CPU occupation radio” index.
The meaning and statistics point of CPU occupation radio. Refer to Table 1-1.
Table 1-1 Index meaning and statistics point of CPU occupation radio
1-2
User Manual Report Customization Examples
iManager M2000 Intelligent Report System Chapter 1 Report Customization Examples
Analyze report indices and specify which traffic measurement tasks to be registered.
Open the centralized performance system in the iManager M2000 system and register
the report tasks required on the centralized performance console.
Index information: select the management type [BSC] τ function set [CPU
Measurement Function] τ function subset [CPU Measurement Function]. The
following index (In the square bracket is the index ID is contained, which can be queried
in the self-defined index window and will be used in the later operation):
z Occupation radio [303000]
Time information: The recommended measurement period is 60 minutes and the
recommended measurement time segment is the busy hours. The result storage
duration can be the required days. All other parameters can be set by default.
After the successful task registration, the new task No. will be displayed in the task table
window as XXX, which will be used in the later operation.
In this example one report task is registered. If the measurement items belong to
different function sets, multiple tasks should be registered. Even if they belong to the
same function set, but to different measurement object types, it is also necessary to
register several tasks.
Log in to the Intelligent Report System as a user with the system administrator group
authority, then click the [View/Management Pages/Datasource Management Page],
or select Data tab directly.
In the Report System Client window, first define the information of the data source, i.e.
the database where measurement results are stored, as shown in Figure 1-2.
1-3
User Manual Report Customization Examples
iManager M2000 Intelligent Report System Chapter 1 Report Customization Examples
The data source IP address should be the real address where the data is stored.
Generally, it is the IP address of M2000 server. If the report server and the M2000
server are installed separately, please fill in the actual IP address.
Then, add a table in this data source, i.e. to manually fill in the required parameters of
the measurement result table, as shown in Figure 1-3.
1-4
User Manual Report Customization Examples
iManager M2000 Intelligent Report System Chapter 1 Report Customization Examples
In tbl_rstXXX, XXX is the task No., while in m_idxxxxx, xxxxx is the index ID of the task
index.
All task result tables have the same fields as follows, which should be entered
manually:
dw_me_id management unit ID integer
starttime measurement start time datetime
stat_period measurement period integer
objset_m1 object ID integer
The needed is not only the task result table. It is also necessary to get NE name from
the configuration table (which should be used in the layer-1 summarization). Therefore,
tblME (management element table) is also needed.
We can associate out the NE name via the formula Task Result Table. ME ID = ME
Table. NE ID.
1-5
User Manual Report Customization Examples
iManager M2000 Intelligent Report System Chapter 1 Report Customization Examples
To customize a report template, we should disassemble the report as per the actual
case. Sometimes it is necessary to disassemble one report into several templates.
Because only the task result tables of the same object type can be associated if the
report has several task result tables, and the association conditions are the object ID
and the start time. If the measurement objects of the task result tables are of different
types, they cannot be kept in the same report template. Then it is necessary to
disassemble one report into several report templates.
1-6
User Manual Report Customization Examples
iManager M2000 Intelligent Report System Chapter 1 Report Customization Examples
Defined data source is used as the input source for report generation. It can be one or
more data sources. All report data sources are listed on the data source page.
Note:
If there are several task result tables, only those tables, whose object type are same, can be associated,
such as ME ID (Object ID), and start time can used as associated condition. Otherwise, it is necessary to
customize several report temples to realize requirement.
These fields are calculated via the database. Namely the server realizes the layer-1
summarization.
1-7
User Manual Report Customization Examples
iManager M2000 Intelligent Report System Chapter 1 Report Customization Examples
Normal traffic measurement reports require that the user can input start time for query
measurement, or input the specific ME ID for query.
In the separable group list, the non-calculated fields in the output result can be
displayed but cannot be edited.
1-8
User Manual Report Customization Examples
iManager M2000 Intelligent Report System Chapter 1 Report Customization Examples
In the above five steps, the data source of report template is defined. This data source
is the main item data and will be used as the template input data.
1) Report generation
Basic report design can be conducted once the query definition wizard and variables
are correctly created.
Click the shortcut icon to pop up a dialog box "Insert Fields", as shown in Figure
1-8.
Select the fields to be inserted, and click <OK>, then a simple report will be
immediately generated.
But a complete template needs at least four report bands as report title, page header,
main item data, and page footer.
Some templates, which require the secondary summarization also need other report
bands as group header and footer, report total, and so on.
1-9
User Manual Report Customization Examples
iManager M2000 Intelligent Report System Chapter 1 Report Customization Examples
Generally only the constant or the system variables are needed for the designing of
report bands like report title, page header and footer, etc.
The layer-1 summarization can be realized in the server, but the layer-2 summarization
is realized via the group header and footer.
2) Add report title
Click the icon in the report object bar to insert a new report band, then select
"Report Title" type.
1-10
User Manual Report Customization Examples
iManager M2000 Intelligent Report System Chapter 1 Report Customization Examples
ME table.Field. ME ID"], then we can group by ME ID. All records with the same ME ID
are classified in one group.
Figure 1-11 Add a group header: grouping condition 1 (to group by ME ID)
The result after grouping will be output to the group header, therefore it is necessary to
add group footer.
5) Add group footer
Calculate the summation or average of the data, which are calculated and grouped on
the group footer. The items in the group footer and the ones in the group header are in
one-to-one correspondence.
z ME name
We can insert data fields by clicking the icon in the text editor. Select
"PMsource.Table.ME table.Field.ME Name" to establish connection with the "ME
Name" in the group footer.
1-11
User Manual Report Customization Examples
iManager M2000 Intelligent Report System Chapter 1 Report Customization Examples
z ME ID
z Occupation radio
1-12
User Manual Report Customization Examples
iManager M2000 Intelligent Report System Chapter 1 Report Customization Examples
Figure 1-15 The final report style (in the Edit status)
But the last step is to preview the template. Through template preview we can check
the final output effect of the template and make some adjustment if necessary, besides,
we can also check out some syntax errors.
1-13
HUAWEI
System Maintenance
User Manual System Maintenance
iManager M2000 Intelligent Report System Table of Contents
Table of Contents
i
User Manual System Maintenance
iManager M2000 Intelligent Report System Chapter 1 System Maintenance
The IN report system is designed in the Browser/Server structure. Its Client is realized
via IE+ActiveX. It provides a powerful report graphic designing environment and
ensures that the user can complete all operations in the browser. The system
midware is installed in the Web Server and realized via Java+Application servers. The
data connection midware is equipped with Java executable files and JDBC universal
interfaces, which realizes the cross-platform transplantation and distribution.
The Client exchanges data with the background through HTTP. The background
system is designed in the JWS+BEAN service mode. The medium between the Client
and the background Web Server is Java Sever Pages (JSP). Client requests are sent
to the Web Server via JSP for explanation and then realized by the relevant
procedure invoked.
Generally, the operation of one Client invokes one JSP which will then invoke one
BEAN to implement the corresponding operation. If the Client wants to upload a file, it
sends a request and uploads basic file parameters (including the file size and file
storage directory, etc.). When the JSP receives the request and the parameters, it
invokes a BEAN for file uploading and sends the parameters to this BEAN, which will
then process the file and return a flag indicating whether the uploading succeeds or
fails.
The system midware is connected with the data connection midware via Socket.
The Client is equipped with the IE+ActiveX realization mode, and its structure is
simple with little user intervention, therefore the maintenance of the intelligent report
system is described in the midware of the system.
The midware management and maintenance is carried out on the following aspects:
1) System database maintenance
2) System service program maintenance
3) Memory management of Java virtual machine (JVM)
4) System troubleshooting
Currently the IN report system supports four large-capacity databases: Oracle, SQL
Server, Informix, and Sybase.
1-1
User Manual System Maintenance
iManager M2000 Intelligent Report System Chapter 1 System Maintenance
The operational environment of each database requires a different JDBC driver and
different description mode of database connection string. The JDBC drivers must be
provided by or compatible with the used database or provided by the third party.
Besides, the description modes of database connection strings are available.
1-2
User Manual System Maintenance
iManager M2000 Intelligent Report System Chapter 1 System Maintenance
1-3
User Manual System Maintenance
iManager M2000 Intelligent Report System Chapter 1 System Maintenance
1-4
User Manual System Maintenance
iManager M2000 Intelligent Report System Chapter 1 System Maintenance
1-5
User Manual System Maintenance
iManager M2000 Intelligent Report System Chapter 1 System Maintenance
The midware of the intelligent report system provides two service programs. One is
the Web Server Resin which forwards Http messages in the Web service. The other
program is the DatabaseProxyServer which is responsible for the connection with the
service database. These two servers can be started and stopped respectively via the
following scripts:
1) Bootscript for the Web Server: httpd_start
Usage: httpd_start
2) Stop script for the Web Server: httpd_stop
Usage: httpd_stop
3) Bootscript for the database proxy server program: proxyserver
Usage: proxyserver
Once started with the above scripts, the service processes will begin to run on the
background. The following methods can be adopted to observe them:
1-6
User Manual System Maintenance
iManager M2000 Intelligent Report System Chapter 1 System Maintenance
After the Web Server is started, there are three processes which can be observed via
filtering the resin:
ps -ef|grep resin
m2000 2557 1 0 18:41:45 ? 0:00 perl ./resin1.2.0/bin/wrapper.pl -chdir
-name httpd -class com.caucho.server.ht
m2000 2559 2557 0 18:41:45 ? 0:00 sh -c /usr/java/bin/java
-Dresin.home=/export/home/m2000/report/resin1.2.0 co
m2000 2560 2559 0 18:41:45 ? 0:13
usr/java/bin/../bin/sparc/native_threads/java
-Dresin.home=/export/home/m2000/
When the database proxy server is started, there is only one process which can be
observed via the following commands:
$ps -ef|grep java|grep rpt
m2000 2575 1 0 18:41:49 ? 0:05
/usr/bin/../java/bin/../bin/sparc/native_threads/java
com.huawei.iin.rpt.databa
If the corresponding process is not available, please start it with the bootscript.
The midware of the intelligent report system is equipped with the Java cross-platform
technology. All of its system programs are written in the JAVA language. Therefore the
system midware must run on the JVM (Java Virtual Machine).
According to the features of the JVM and its programming language, the server
memory management requires manual intervention in certain circumstances, normally
when the Client submits enormous data collection requests to the system midware.
When the JVM starts the application programs, the default minimum memory is 2M
and the maximum memory is 64M. If the midware collects an enormous amount of
data (for example, thousands of records) while the JVM memory is insufficient to
store all the records, the JVM will a prompt for memory overflow. In this case, manual
intervention is necessary to increase memory capacity so as to meet the data saving
requirement.
In order to prevent memory overflow, you need to roughly estimate the data amount
of the service database in the system and the level of output data amount of the
report, and then adjust the starting parameters of the JVM to provide sufficient
memory.
The IN report system consists of two parts: Web Server and Database Proxy Server.
Both of them run on the JVM. Therefore they should be management separately
1-7
User Manual System Maintenance
iManager M2000 Intelligent Report System Chapter 1 System Maintenance
according to the actual case. The management methods are in the running scripts of
the two service programs.
The running memory of Resin can be adjusted through the memory parameters set
via the script (named as httpd.bat in the Windows).
Note:
httpd.sh (httpd) is Resin service starting program. -J-Xms is the parameter of the minimum occupied
memory parameter for the specified JVM with the minimum memory as 32MB. -J-Xmx is the parameter
for the maximum occupied memory of the specified JVM with the maximum memory as 256MB.
The running memory of the database proxy server can be adjusted through the
memory parameter setting via the script proxyserver (named as proxyserver.bat in
Windows).
Note:
-Xms is the parameter for the minimum occupied memory of the specific JVM with the minimum memory
as 12MB; while -Xmx is the parameter for the maximum occupied memory of the specific JVM with the
maximum memory as 256MB.
1-8
User Manual System Maintenance
iManager M2000 Intelligent Report System Chapter 1 System Maintenance
Report log files are mainly stored in directories /log. The detailed information is
described in Table 1-14. You can view the report log so as to pull in the faults listed in
sections 1.5.1 and 1.5.2 , then get the corresponding solutions.
Besides, if you install the log viewer in Win98/WinNT, the log viewer and server
programs are installed in the same computer, you can view all logs. If your server is
installed in Unix or the log viewer and server programs are not on the same host, you
can only browse the SQL logs in the Client.
The log viewer is generally oriented for report designers. Upon report query, they can
use it as design aid to simultaneously view the contents of the SQL command or the
store procedure command string sent to the service database.
If the report you have designed cannot produce the correct result, you can copy the
SQL command or the store procedure command string displayed in the log viewer to
the Client of the database system (e.g. dbaccess) so that you can find out the cause
for database access error.
[Caption]
1=WebServer Log file
2=WebServer operation log
3=WebServer error log
4=ProxyServer log file
5=ProxyServer operation log
6=ProxyServer error log
7=Resin log file
8=Year
9=Month
1-9
User Manual System Maintenance
iManager M2000 Intelligent Report System Chapter 1 System Maintenance
10=Date
11=Operation flow log
12=operation error log
13=error info log
14=Client query statement log
The midware of the IN report system midware can be used to monitor the running
status on the following aspects:
1) Resin running interface
2) inrpt/log/log.txt log files
Common operation errors are returned to the Client. The fault information displayed
on the Client is packed and can only indicate the general type of a fault. To exactly
locate the fault and detect the fault cause, the system administrator should conduct
query on the monitor terminal of the server.
The installation and configuration of the midware must be accurate and correct. It
involves the installation and setting of third party components, and the setting of
system midware operational environment (including the setting of system
environment and system files). The following are some examples:
1) java.lang.ClassNotFoundException: The path configuration of the system
environment is incorrect so JVM (Java Virtual Machine) cannot find the
corresponding class. Please check whether the system environment variable
CLASSPATH is correctly configured.
2) java.lang. NoClassDefFoundError: java.lang.NoClassDefFoundError: The path
configuration of the system environment is incorrect so JVM cannot find the
corresponding class. Please check whether the system environment variable
CLASSPATH is correctly configured.
3) java.lang. FileNotFoundException: The path configuration of the system is
incorrect so JVM cannot find the corresponding files. Please check whether the
1-10
User Manual System Maintenance
iManager M2000 Intelligent Report System Chapter 1 System Maintenance
Config file, Log file and the Template file exist, or check whether the path or file
configured in the *.conf file under inrpt/conf/ exists.
Faults occur in the communication between the system midware and the database
proxy. When the Client wants to collect report data, the TCP/IP connection will be
established between the report system midware and the database proxy server. Such
connection is built upon the relationship between the database proxy and the data
source in the data table RptProxyDS. The following are examples for communications
faults.
1-11
User Manual System Maintenance
iManager M2000 Intelligent Report System Chapter 1 System Maintenance
1) The relationship between the database proxy server and data source is not
established. Please add relationship records between the data source and the
proxy server with the database proxy management tool.
2) The network is not accessible between the midware server of the report system
and the database proxy server. Please check whether the network between the
two servers is normal.
3) The definition of the database proxy server is incorrect or the database proxy
server is not started. Please check whether the data table RptProxyDS and the
configuration file Proxyserver.conf are correctly defined.
The third party components included in the system midware are: Resin1.2.0, JDK1.3
(Java Development Kit) and the system database. Common faults are:
1) The Client is inaccessible: Please check whether resin runs normally.
2) JDK cannot run normally.
3) The system prompts for "out of memory". It is because the data amount of one or
several reports queried is too large and exceeds the default memory capacity of
the JVM. Please refer to Section 1.3 and make necessary adjustment.
The installation and configuration of JDK1.3 is not correct on the database proxy
server. The correct installation method is described in the Installation of Report
System module.
1-12
User Manual System Maintenance
iManager M2000 Intelligent Report System Chapter 1 System Maintenance
1-13
HUAWEI
Table of Contents
i
User Manual Installation of Report System
iManager M2000 Intelligent Report System Chapter 1 Installation of Report System
1.1 Overview
The report system midware is installed in the Web Server and realized via Java and the
Application Servers. The data midware is equipped with Java executable files and
JDBC universal interfaces, which realize the cross-platform transplantation and
distribution.
The Client of the user-defined report system does not require too much routine
maintenance except the maintenance for the browser, which is determined by the
system structure. But when the iManager M2000 system is upgraded, the report
system also needs to be upgraded as per the following instructions:
z If the report template is changed, delete all frf template files in windows/temp upon
upgrading, otherwise, the result will be displayed via the old template.
z Besides, after upgrading the iManager M2000 server, copy the latest report server
license files (systemuser.conf) to the directory /export/home/inrpt/conf.
The interlayer service system part of the user-defined report system is described in
Table 1-1.
1-1
User Manual Installation of Report System
iManager M2000 Intelligent Report System Chapter 1 Installation of Report System
Note:
1) The part containing (*) can run on other equipment.
2) The service database and Proxy server can be associated via topology.
1.1.3 Preparations
I. Environment Requirements
The report system requires JDK1.3 or above. JDK is the product developed by the third
party, and JDK1.3 raises the demands for different operating systems as follows:
z For the Solaris operating system, Solaris2.6, Solaris2.7 or Solaris2.8 is available.
In the installation package, the JDK1.3 package and its corresponding patch
package are provided.
z For the HP-UX operating system, HP-UX 11.0 or above is required.
z For the IBM's AIX operating system, AIX4 or AIX5 is required.
For the Windows operating system, Windows 98, Windows 2000, or Windows NT 4.0 or
above is required.
II. Preparations
1) First, check whether the Sybase database can work normally and ensure the two
database devices (data_dev and log_dev) have been correctly installed. We can
check the Sybase database by executing the isql command. The command ps
-ef|grep dataserver can help check whether the Sybase database process is
running. If login to the Sybase database fails, errors may exist and you should
check the installation process.
2) If the M2000 user-defined report server has been installed, it should be uninstalled
first.
3) Prepare installation media: CD or tape.
4) If CDROM is used as installation medium, install it into the system manually if
automatic installation is not supported.
5) If tape is used as the installation medium, execute drvconfig first so that the tape
equipment can be loaded into the system. The CD directory is usually
/cdrom/cdrom0, while the tape directory might be /dev/rmt/0 which is decided by
the specific system.
1-2
User Manual Installation of Report System
iManager M2000 Intelligent Report System Chapter 1 Installation of Report System
Information Description
root user password Mandatory
m2000 user and password Mandatory
Installation package inrpt_210.tar.Z Mandatory
JDK installation package jdk_sun58.tar Mandatory
Database scripts and template files package rptdata.tar Mandatory
sybase user password Mandatory
For the detailed installation and setup procedure, see Figure 1-2.
1-3
User Manual Installation of Report System
iManager M2000 Intelligent Report System Chapter 1 Installation of Report System
First switch over to a Sybase user, and create a directory to store files to be installed
(create the directory as bak2 in this example).
#su -sybase
$mkdir bak2
$cd bak2
Then upload the files needed by installation into the directory bak2.
1-4
User Manual Installation of Report System
iManager M2000 Intelligent Report System Chapter 1 Installation of Report System
Note:
Upload the installation packages inrpt_210.tar.Z, rptdata.tar and jdk_sun58.tar.
1. This step is executed in the Window system via PC.
2. In the following part, the bold contents in each square bracket is the explanation of the command.
3. The directory e:\rptinstall and the Sybase host directory "/export/home/sybase are determined by the
actual case. In this description, we only take an example.
4. The BIN format should be adopted.
c:\>ftp 10.129.27.100
ftp> cd bak2
ftp>bin
ftp> prompt
[Close the dialog mode – no confirmation prompt will be given for the later
transmission]
1-5
User Manual Installation of Report System
iManager M2000 Intelligent Report System Chapter 1 Installation of Report System
ftp> bye
[Exit]
c:\>
1.2.4 Unpackage
# su - sybase
$ cd bak2
$ pwd
/export/home/sybase/bak2
$ uncompress inrpt_210.tar.Z
Note:
1. The host directory "/export/home/sybase of Sybase is determined by the actual case. In this description,
we only take an example.
2. The content in the following square bracket is the explanation of the command.
3. The user name and password of the database inprtdb must be consistent with the new settings for
system installation.
4. No error prompt should occur in the following operation. If any occurs, please contact Huawei local
office.
5. The typical installation cannot be selected unless the password of the database superuser sa is set as
server1234.
#su - sybase
1-6
User Manual Installation of Report System
iManager M2000 Intelligent Report System Chapter 1 Installation of Report System
$ cd bak2
$ crtrptdb2.sh
Please choose between typical installation and custom installation.
choices:
t -- typical
c -- custom [?,q] c
Caution:
Here the system asks whether to select the typical installation or the customized installation. You can
press <Enter> for customized installation. During installation, the system will ask you to input the
password for Sybase system administrator. Note: If you enter a sa password except server1234, please
select customized installation.
[Enter the sa password for the superuser of the sybase database. Here
server1234 is only an example. Please enter the actual password]
Input db user [default report].
Press enter if you agree [?,q] report
[Enter the user name of the inrptdb database to be created. Here report is only
an example. Please enter the actual user name, for example: m2000]
Input passwd [default report].
Press enter if you agree [?,q] report
[Enter the user password of the inrptdb database to be created. Here report is
only an example. Please enter the acutal password. If the user name in the last
step is m2000, the password for m2000 is required here]
Input database size[default 100M].
Press enter if you agree [?,q] 100
1-7
User Manual Installation of Report System
iManager M2000 Intelligent Report System Chapter 1 Installation of Report System
Caution:
1. In the following three Cautions, the user name and password set for the database must be consistent
with the settings made upon database creation. For example: If the host user of the inrptdb2 databse is
M2000, you have to enter M2000 and its corresponding password. If the host user of the inrptdb2
database is report, you must enter report as the user.
2. In the following part, the content in each square bracket is the explanation of the command.
3. During a series of installation prompts, you must pay close attention to the Cautions.
(a) First decompress the installation package inrpt_sun_5_6.tar, which has been
uploaded into the directory /export/home/sybase/bak2.
#su -sybase
$ cd bak2
(b) Then run the installation script files to install the new system.
$ sh setup.sh
=================================================================
(1) Install JAVA SDK if necessary, JAVA SDK V1.3 or later is required.
(2) Install WebServer.
(3) Install one or more Proxy Servers.
-----------------------------------------------------------------
Note: As a convention, press 'Enter' to select the default later.
-----------------------------------------------------------------
Press 'Enter' to continue...
1-8
User Manual Installation of Report System
iManager M2000 Intelligent Report System Chapter 1 Installation of Report System
Caution:
During installation, the system will give some prompts for which default values are available. You may
press <Enter> if you don’t make any change.
Do not click <Y> unless it is a question of yes/no, otherwise the system will recognize the letter "y" as a
new value instead of the default value.)
================================================================
Install JDK 1.3 ? ([1]Yes [2]No [0]Quit)[Default:1]:
================================================================
[In the case of initial installation, JDK should be installed. Press <Enter> to start
installing JDK]
Please input JDK's installation pathname, which must be absolute,
not end with '/', be the parent of directory 'bin', and have the
same last one of name sequence with the default pathname.
[Default: /usr/j2sdk1_3_1_02]:
1-9
User Manual Installation of Report System
iManager M2000 Intelligent Report System Chapter 1 Installation of Report System
[Type in "Yes"]
Unpacking...
Checksumming...
Extracting...
Archive: ./install.sfx.4139
replace j2sdk1_3_1_02/jre/bin/sparc/native_threads/java? [y]es, [n]o, [A]ll,
[N]one, [r]ename: A
inflating: j2sdk1_3_1_02/jre/bin/sparc/native_threads/java
...
java version "1.3.1_02"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_02-b02)
Java HotSpot(TM) Client VM (build 1.3.1_02-b02, mixed mode)
Press "Return" to back to console...
For parameter description of intelligent report server installation, see Table 1-3.
================================================================
Install WebServer? ([1]Yes [2]No [0]Quit)[Default:1]:
[Please modify the directory to be installed for the report system, normally as
"/export/home/inrpt"(it’s a example)]
Note:
This installation directory is the user directory for installing intelligent report.
If the user or user group does not exist, you need create them.
Create them? ([1]Yes [0]No) [Default:1]:
1-10
User Manual Installation of Report System
iManager M2000 Intelligent Report System Chapter 1 Installation of Report System
[Enter the new password of the inrpt user created just now]
...
Change current directory to '/export/home/inrpt'.
----------------------------------------------------------------
Copy installation package 'web_unix_cn_2_1_0.tar'...OK!
Decompress WebServer installation package 'web_unix_cn_2_1_0.tar'...
.......
Warning:
Upgrading will clear the system database of current system, and template files, if any,
will be deleted.
How to transfer? (1-Automatically 0-Manually or not upgrade)
[Default: 0]:
Note:
Here, “couldn't set locale correctly” may appear in the screen, and this is caused by the mismatch of
system character set. This message can be neglected because the system is not affected.
------------------------------------------------------------------------------------------------
Next, we will, if necessary, initialize system database.
1-11
User Manual Installation of Report System
iManager M2000 Intelligent Report System Chapter 1 Installation of Report System
[The port No. must be modified, because the normal port No. used in the system
is 4100. The input format must be: IP address: port No.]
Database name/SID[inrptdb2]:
JDBC extended options[]:
User name[]:report
[Enter the database user name. The report here is an example. Please enter the
actual user name]
User password[]:report
[Enter the password of the report database user. "report" is only an example.
Please enter the actual password]
Initialize system database? (y-Initialize/n-Don't)[Don't]:y
[Press <Enter>, and the upgrade is not based on the existing version]
INRPT Server's HTTP port number[8088]:
1-12
User Manual Installation of Report System
iManager M2000 Intelligent Report System Chapter 1 Installation of Report System
--------------------------------------------------------------------------
Note:
Here, "Unexpected exception : SqlState: ZZZZZ com.sybase.jdbc2.jdbc.SybSQLException: Cannot drop
the table 'RptColumn', because it doesn't exist in the system catalogs., ErrorCode: 3701" may appear in
the screen, because these tables have not been created in the new system, and the message is provided
when the installation program attempts to delete these tables. The system will automatically create these
tables. The message can be neglected because the system is not affected.
1-13
User Manual Installation of Report System
iManager M2000 Intelligent Report System Chapter 1 Installation of Report System
1-14
User Manual Installation of Report System
iManager M2000 Intelligent Report System Chapter 1 Installation of Report System
For parameters description of intelligent report database proxy installation, see Table
1-4.
Install ProxyServer? ([1]Yes [2]No [0]Quit)[Default:1]:
Please input the UNIX user group name of ProxyServer.
[Default:inrpt]:
[User group name: inrpt. Press <Enter>, and use the default value]
Please input the UNIX user name of ProxyServer..
[Default:inrpt]:
[User name: inrpt. Press <Enter>, and use the default value]
Please input the home directory of user inrpt, which must be absolute, not end
with '/'. [Default:/export/home/inrpt] :
1-15
User Manual Installation of Report System
iManager M2000 Intelligent Report System Chapter 1 Installation of Report System
[Press <Enter>, and use the default value. It is unnecessary to install other
ProxyServer]
----------------------------------------------------------------------------------------------------------
1-16
User Manual Installation of Report System
iManager M2000 Intelligent Report System Chapter 1 Installation of Report System
# su - inrpt
Note:
"/export/home/Sybase" and "/export/home/inrpt" are the master directory of Sybase and inrpt user. Please
modify them upon requirements.
# su – sybase
$ cd bak2
$ sh set_report.sh
1-17
User Manual Installation of Report System
iManager M2000 Intelligent Report System Chapter 1 Installation of Report System
bcp RptColumn...
...
$ sh set_ds_db.sh
Input username of datasource database [default report].
[Here it refers to the password of database user m2000, not the password of Unix
user]
(1 row affected)
(1 row affected)
(1 row affected)
# su - inrpt
[hostname]% cp -r /export/home/sybase/bak2/template .
Note:
"/export/home/Sybase" and "/export/home/inrpt" are the master directory of Sybase and inrpt user. Please
modify them upon requirements.
1-18
User Manual Installation of Report System
iManager M2000 Intelligent Report System Chapter 1 Installation of Report System
# su - inrpt
hostname% cd
hostname% b
Start intelligent report system client manager, and select [Tool/Clear Local Data Files] to
clear the local temporary files stored in client.
To user the report template, the user needs to register the corresponding system tasks
in the performance service console. In performance service console, select
[Task/Register System Task] to register system task.
1-19
User Manual Installation of Report System
iManager M2000 Intelligent Report System Chapter 1 Installation of Report System
# su - inrpt
[hostname]
[hostname]e
Report system upgrade is to upgrade the current system, i.e., upgrade report template.
For the detailed upgrade steps, see Release Notes. Shut down old version report
system firstly in case of upgrading.
# su – inrpt
[hostname]e
[hostname]pwd
/export/home/inrpt
# cp -r /export/home/inrpt/template ./template_bak2
2> go
2> go
1> quit
1-20
User Manual Installation of Report System
iManager M2000 Intelligent Report System Chapter 1 Installation of Report System
Put the above generated “inrptbak.tar” backup files in a safe place. If the files are
moved to PC, they should be in bin format.
1.3.3 Upgrading
I. Upload the files to be installed to the directory created in the first step
Caution:
$ pwd
/export/home/sybase/bak2
$ ls upgrade.tar
upgrade.tar
1-21
User Manual Installation of Report System
iManager M2000 Intelligent Report System Chapter 1 Installation of Report System
# su -sybase
$ cd bak2
$ pwd
/export/home/sybase/bak2
$ chmod +x set_report.sh
$ set_report.sh
Input report database username [default report].
Press enter if you agree [?,q] report
[Enter the user name of the report database inrptdb, which should be consistent
with the user name upon inrptdb creation]
Input report database user password [default report].
Press enter if you agree [?,q] report
[Enter the user password of the report database inrptdb, which should be
consistent with the password upon inrptdb creation. ]
Input report datasource ip address.
Press enter if you agree [?,q] 10.129.10.11
[Enter the IP addresses of the report data source and the server of the M2000
databases pmdb and cfgdb.]
Input report proxy ip address.
Press enter if you agree [?,q] 10.129.10.11
[Enter the IP addresses of the report proxy server and the report system server]
bcp RptSP...
Starting copy...
0 rows copied.
Clock Time (ms.): total = 1
bcp RptTable...
1-22
User Manual Installation of Report System
iManager M2000 Intelligent Report System Chapter 1 Installation of Report System
Starting copy...
......
$
# su - inrpt
[hostname]cd inrpt/template
[hostname]pwd
/export/home/inrpt/template
# su -sybase
$ cd bak2
$ chmod +x set_ds_db.sh
$ set_ds_db.sh
Input username of datasource database [default report].
Press enter if you agree [?,q] m2000
[User name of the data source database (pmdb and cfgdb of the M2000 system) ]
Input password of datasource database [default report].
Press enter if you agree [?,q] Z83fC868fZ07jW67
[User password of the data source database (pmdb and cfgdb of the M2000
system)]
# su - inrpt
[hostname]:>cd
[hostname]:>b
1-23
User Manual Installation of Report System
iManager M2000 Intelligent Report System Chapter 1 Installation of Report System
[hostname]:>
If the upgrading fails, please handle the failure in the following steps:
FTP the stored inrptbak.tar files to /export/home/sybase/bak2 in the bin format, with the
ftp user as Sybase.
# su – sybase
$cd bak2
# su - inrpt
[hostname] e
[hostname] pwd
/export/home/inrpt
[hostname]cd /template
[hostname]rm *
# su - sybase
$ cd bak2
$ isql -Usa -Pserver1234
1> load database inrptdb2 from "/export/home/sybase/bak2/inrptdb2.dat"
2> go
1> online database inrptdb2
2> go
1> quit
1-24
HUAWEI
Appendix
User Manual Appendix
iManager M2000 Intelligent Report System Table of Contents
Table of Contents
i
User Manual Appendix
iManager M2000 Intelligent Report System Appendix A Conventional SQL Statements
Select * from bill_s where payment like '415%'? Delete rows with duplicated values
Use like for Text and char. The wildcards '%' and '-' can be used respectively for
multiple characters and single characters.
Value comparison =, >, <, >=, <=, !=, !> and !<
Range specified between exp1 and exp2 /net between exp1 and exp2
Predication like
When "=" is used for the comparison of two data, the connection is called as
equivalent connection. If any other comparison operator is used, the connection is
called as inequivalent connection.
Equivalent connection:
A-1
User Manual Appendix
iManager M2000 Intelligent Report System Appendix A Conventional SQL Statements
Inequivalent connection:
Among the columns with the same name in the target connection column, only one
column is reserved.
A.1.3 Subquery
I. Subquery of expression
You can select all size comparison operators can be used. Between operator and
subquery "all" or "any" can be used.
Where pub_id in
The associated query is to get the value of the external parent query by means of
nested query. The nested query should be repeatedly executed for several times.
Aggregation function:
A-2
User Manual Appendix
iManager M2000 Intelligent Report System Appendix A Conventional SQL Statements
Sum([all|distinct]expression),avg([all|distinct]
exoression) ,Count([all|distinct]expression), count(*), max(expression),
min(expression)
Having has the similar function with where, but where cannot be used for aggregation
functions
A-3
User Manual Appendix
iManager M2000 Intelligent Report System Appendix B Description of Multi-object Parameter Structure
I. Multi-combination object
B-1
User Manual Appendix
iManager M2000 Intelligent Report System Appendix B Description of Multi-object Parameter Structure
B-2
User Manual Appendix
iManager M2000 Intelligent Report System Appendix C Abbreviations
Appendix C Abbreviations
F
FTP File Transfer Protocol
G
GCI Cell Global Identification
H
HTML Hypertext Markup Language
HTTP Hypertext transfer Protocol
I
IP Internet Protocol
J
JDBC Java Database Connectivity
JDK Java Developer’s Kit
JSP Java Server Pages
JVM Java Virtual Machine
L
LAN Local Area Network
M
ME Management Element
MSC Mobile Switch Center
MTP Message Transfer Part
N
NE Network Element
O
OMC Operation and Maintenance Center
OPC Original (signaling) Point Code
P
PS Proxy Server
R
RTF Rich Text Format
S
SCP Service Control Point
SDK Software Development Kit
SP Stored Procedure
SQL Structured Query Language
SSL Security Socket Layer
T
TCP Transfer Control Protocol
C-1
User Manual Appendix
iManager M2000 Intelligent Report System Appendix C Abbreviations
U
URL Uniform Resource Locator
V
VM Virtual Machine
W
WMF Windows Metafile
C-2