Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
No. TC1660
Ed. 01
OmniVista 4760
Nb of pages : 72
Date : 06-04-2012
URGENT
NOT URGENT
TEMPORARY
PERMANENT
OmniVista 4760
INSTALLATION PROCEDURE FOR
VERSION 5.2.02.00.b - RELEASE 5.2
CONTENTS
1.
GENERAL ................................................................................... 7
2.
2.1.
2.2.
2.3.
3.
3.1.
References ............................................................................................... 8
3.2.
Patches..................................................................................................... 9
3.2.1.
Mandatory patches delivered with the DVD-ROM versionErreur ! Signet non dfini.9
3.2.2.
3.3.
4.
PREREQUISITES ....................................................................... 10
4.1.
4.1.1.
4.1.2.
4.1.3.
4.2.
4.2.1.
4.2.2.
4.2.3.
4.2.4.
4.2.5.
4.3.
4.4.
TC1660
OmniVista 4760
INSTALLATION PROCEDURE FOR
VERSION 5.2.02.00.b - RELEASE 5.2
4.5.
5.
5.1.
5.2.
5.3.
5.4.
Security .................................................................................................. 22
5.5.
6.
INSTALLATION ........................................................................ 23
6.1.
6.2.
6.2.1.
6.2.2.
6.3.
6.4.
6.5.
6.6.
7.
6.6.1.
Installation ................................................................................................ 29
6.6.2.
UPGRADES .............................................................................. 31
7.1.
Prerequisites .......................................................................................... 31
7.2.
7.3.
7.4.
7.5.
8.
7.5.1.
7.5.2.
8.1.
8.2.
OMC ....................................................................................................... 34
TC1660
OmniVista 4760
INSTALLATION PROCEDURE FOR
VERSION 5.2.02.00.b - RELEASE 5.2
9.
APPENDIX
APPENDIX 1 CORRECTIONS
APPENDIX 2 RECOMMENDATIONS
APPENDIX 3 ADVANCED MANAGEMENT
APPENDIX 4 NEW FEATURES
APPENDIX 5 IDENTIFIED DEFAULTS AND RESTRICTIONS
TC1660
OmniVista 4760
INSTALLATION PROCEDURE FOR
VERSION 5.2.02.00.b - RELEASE 5.2
TC1660
OmniVista 4760
INSTALLATION PROCEDURE FOR
VERSION 5.2.02.00.b - RELEASE 5.2
1.
GENERAL
This document describes the installation procedure for OmniVista 4760 version 5.2.02.00.b.
It refers to the Installation manual and Administrator manual.
These documents are essential since this procedure does not provide full installation details.
To implement the SIP Device Management server, please refer to the Installation manual of this product.
SIP Device Management Server must have the version 1.2.000.010 or higher to
be compatible with OmniVista 4760 R5.2. The current version is 1.2.000.020.
SIP DMS is not compatible with Windows 2008 and Windows 7
It is also highly recommended to consult on "Alcatel-Lucent Business Portal"
(http://www.businessportal.alcatel-lucent.com/) ; software downloading and technical communications
can contain new information regarding OmniVista 4760 Release 5.2.
Refer to appendixes to respect the recommendations of installation and management.
The following Technical Communications are essential for the OmniVista 4760 maintenance:
TG0029 Trouble shooting Guide
TG0033 OmniPCX Enterprise Interworking
TCV020 Emails sending by OmniVista 4760
TCV039 License management
TCV060 Directory Management
TCV061 Alarms filtering from OmniPCX Enterprise to OmniVista 4760
TC0835 Disks and memory management
TC0846 Accounting: Investigation elements
TC0858 Traffic observation: Investigation elements
TC0953 OmniVista 4760 license on OmniPCX Office: Max users reached, client in deprecated mode
TC1007-Ed02 OmniVista 4760 Installation / Uninstallation
CAUTION
Each time you are requested to erase or edit a file, it is absolutely necessary to make a copy of the
original.
These operations must be performed by an expert (ACSE) trained on the product. In the opposite side,
you can contact the "Professional Services" (mailto:professional.services@alcatel-lucent.com ).
TC1660
OmniVista 4760
INSTALLATION PROCEDURE FOR
VERSION 5.2.02.00.b - RELEASE 5.2
2.
2.1.
Non-operational configuration
2.2.
Capacities higher than 30000 subscribers or 800 nodes (OmniVista 4760 PCS).
2.3.
Specific process
Creation of limited user accounts to the management of some PCXs (ACI/ACL LDAP).
3.
3.1.
References
OmniVista 4760 Release 5.2 package: 3BH 11632 AKAC which contains following items:
Security Guide
Security Guide
SIP Device Management software DVD: 3BH 11761 AAAD which contains:
TC1660
OmniVista 4760
INSTALLATION PROCEDURE FOR
VERSION 5.2.02.00.b - RELEASE 5.2
3.2.
Patches
3.3.
License file
For more details, refer to the technical communication TCV039-Ed07 OmniVista 4760 licenses.
To install OmniVista 4760 and to access the various clients, you must have a specific license file for
your PCX network and which describes the available modules.
In Actis, choose one PCX in the network and specify in its configuration that it is the declaration
node for OmniVista 4760 server.
CAUTION
If the declaration node is OmniPCX 4400 R5.0 Ux, you can no more get the OmniVista 4760
license file.
If the declaration node is OmniPCX Office, OmniPCX Enterprise R5.0 Lx, the license file is
produced on BPWS/ELP.
10
11
12
13
R3.0
R3.1
R3.2
R4.0
R4.1
R4.2.x
R5.0
R5.1.x
R5.2
End of corrections
10/05
04/06
10/06
04/07
01/08
05/09
01/10
06/11
End of support
10/06
04/07
10/07
04/08
01/09
05/10
01/11
06/12
4760
JRE
2008
1.6.0.21
SunTM Directory
Service Enterprise
Edition
DSEE 7.0
Sybase
Apache
PHP
SQL Anywhere 10
10.0.1.4157
2.2.16.0
5.2.14.1
4
TC1660
OmniVista 4760
INSTALLATION PROCEDURE FOR
VERSION 5.2.02.00.b - RELEASE 5.2
4.
PREREQUISITES
This section describes the prerequisites required to install OmniVista 4760 server and client applications.
4.1.
Server PC prerequisites
Notes
Minimum implies a targeted use of the application. The use of the client PC on the server PC must be
minimum, that is to say with a single module opened.
There is no mass processing (more than 100 entries managed in the grid). Otherwise, the requirements
must be modified to take account of the needs associated with the client application.
In all cases, the performance of the OmniVista 4760 client part is better if the client application is
started from a remote PC.
Capacities greater than 30000 users and 400 PCX require Alcatel agreement to check your system
configuration and to help you to generate the license file.
10
TC1660
OmniVista 4760
INSTALLATION PROCEDURE FOR
VERSION 5.2.02.00.b - RELEASE 5.2
Windows 7 and 2008 are not supported for PPP connectivity and SIP Manager.
For OmniPCX Office, Windows Vista and 7 are supported from OXO R7.0, and Windows 2008
from OXO R8.0
2 Ghz CPU and 4 GB RAM are strongly recommended for Windows 2008 R2 server.
Virtual solution validated on VMware ESX.VMware release supported from 3.5 (VMware itself is not
supported by Alcatel-Lucent),no PPP connection (only IP), SIP manager not supported, maximum 30000
users, directory replication not supported.
Data Centre and other specific Windows editions (Entreprise Edition) are not validated. Regarding
Small business edition this Windows edition is packaged as a Windows Domain Controller: it
includes Active directory server, an LDAP server which prevent OmniVista 4760 default installation.
For any request regarding such validation, you can contact the Alcatel Professional Services.
Processors types are given as examples. The frequency clock is a minimum requirement.
Maximum size of database supported by 4760 is 10 GB or 30 Million of Tickets
For OmniVista 4760 R5.2 Alcatel-Lucent has selected:
- HP PC Compaq pro 6000 from HP
- DL 380 G7 server from HP
11
TC1660
OmniVista 4760
INSTALLATION PROCEDURE FOR
VERSION 5.2.02.00.b - RELEASE 5.2
12
TC1660
OmniVista 4760
INSTALLATION PROCEDURE FOR
VERSION 5.2.02.00.b - RELEASE 5.2
13
TC1660
OmniVista 4760
INSTALLATION PROCEDURE FOR
VERSION 5.2.02.00.b - RELEASE 5.2
Test environment:
14
TC1660
OmniVista 4760
INSTALLATION PROCEDURE FOR
VERSION 5.2.02.00.b - RELEASE 5.2
Hard disk.
A NTFS partition must be set for installing the SunTM DSEE Server. When installing the server, it is
better to keep the defaults directories and to change only the physical drives.
RAM.
Check that the virtual memory is correctly set; the size of the maximum virtual memory must be twice
the physical RAM. Moreover the disk using the exchange file must have enough free space. Refer to
the technical communication TC0835 Managing the disk and RAM in Release 4.1.
An other JAVA application can use the Classpath environment variable. In that case, the line of
parameters can exceed the limit size and prevent the installation of the server.
The Path environment variable giving the access path to Windows and to its dll, which will receive
the access path to OmniVista 4760 binary and to Sybase must be valid.
The Path is managed through the System icon of Windows Control Panel.
15
TC1660
OmniVista 4760
INSTALLATION PROCEDURE FOR
VERSION 5.2.02.00.b - RELEASE 5.2
C:\Windows
C:\winnt\system32 or
;
C:\Windows\system32
The name of the computer must not have the following characters ., -, + (dot, dash, plus). You
make sure that the "NetBios name of the computer" is the same as the "name of the computer". To
read the "NetBios name of the computer", click on the button Other from modification window of
the name of the computer.
For the first OmniVista 4760 server installation on a new PC, this one has to be connected to the IP
network. Otherwise the installation would fail during the SunTM DSEE server installation. The
message in the log file is:
com.iplanet.install.svrutil.wbSvrutil::getHostName: can't determine
host name: java.net.UnknownHostException:
4.2.
PCX prerequisites
The compatible OmniPCX 4400 releases depend on the type of PCX Server connection.
The problems related to phase out PCX releases are not fixed (example: the hang-up via STAP is not
available in OmniPCX 4400 Release 3.0).
16
TC1660
OmniVista 4760
INSTALLATION PROCEDURE FOR
VERSION 5.2.02.00.b - RELEASE 5.2
Release
PCX
3.0
3.2M
3.2 C2
4.1
4.1.1
4.2.1
5.0 Ux
5.0.1 Ux
5.0 Lx
5.1
5.1.1
5.1.2
6.0
6.0.1
6.1
6.1.1
6.2
7.0
7.1
8.0
8.0.1
9.0
9.0
9.1
IP or IP/X25
connection
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
R5.2
R5.2
R5.2.2
R5.2.2
R9.1
R10.0
R10.1
R10.1
I1.605.22
J1.410.39.a
J2.402.12.a
J2.501.9.a
Yes
Yes
Yes
Yes
PPP connection
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
No
No
No
Yes
No
Yes
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes (1)
Yes (1)
Yes
Yes (2)
Yes (2)
Yes (2)
Yes (2)
Notes
(1) In R9.0, for using the PPP connection, the version must be H1.301.31.b or higher (crms00169291).
(2) Only with Windows 2003.
CAUTION
OmniPCX Enterprise whose hostname length greater than 16 characters must be in version
F3.301.36, F2.502.9 (or greater) so that LDAP/PCX synchronization runs properly
(XTSce69070).
PCX Releases are regularly updated. The new values also concerns previous OmniVista releases.
17
TC1660
OmniVista 4760
INSTALLATION PROCEDURE FOR
VERSION 5.2.02.00.b - RELEASE 5.2
IP connection
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
PPP connection
(1)
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes (3)
Yes (3)
Yes (3)
(1)
Windows 2003 server is mandatory to receive urgent alarms on the fly.
No S0 modems with OminPCX Office 1.x.
1 B channel-ISDN connectivity with OmniPCX Office 400/15.3 and Multitech
ISDN modem.
(2) The check of attached node requires an OmniPCX Office versions 2.0.
For more information, refer to the technical communication TCV039
OmniVista 4760 licenses.
(3) Only with Windows 2003
4.2.3. OMC Release Compatibility with Operating Systems
OMC Releases
min
600 / 14.1.d
700 / 8.1.c
800/24.1.a
810/31.1.a
820/15.1.a
Windows XP
SP2
Yes
Yes
Yes
Yes
Yes
Windows 2003
SP1/2
Yes
Yes
Yes
Yes
Yes
Windows 7
Windows 2008
No
Yes
Yes
Yes
Yes
No
No
Yes
Yes
Yes
18
TC1660
OmniVista 4760
INSTALLATION PROCEDURE FOR
VERSION 5.2.02.00.b - RELEASE 5.2
OmniVista 4760 R4.2 is the last release compatible with Alcatel-Lucent Office
(4200).
OmniVista 4760 R5.2 is no more compatible with Alcatel-Lucent Office (4200).
4.2.5. OmniPCX 4400/Enterprise software locks
The modules of the OmniVista application are validated by the server license file. On the other hand the
access to data of the various PCXs requires having appropriate software locks in each PCX:
OmniVista 4760 modules
Configuration
Accounting
Directory
Traffic observation
VoIP
Alarms
Secured SSH connection to
OmniPCX Enterprise
OmniVista 4760 error messages typical to software lock problem PBX side:
Configuration: The "Cmise reject: broken association" message is displayed in the lower part of
the configuration application window.
19
TC1660
OmniVista 4760
INSTALLATION PROCEDURE FOR
VERSION 5.2.02.00.b - RELEASE 5.2
4.3.
4.4.
4.5.
SIP Device Management Server must have the version 1.2.000.010 or higher to be compatible with
OmniVista 4760 R5.2. The current version is 1.2.000.020.
SIP DM is not compatible with Windows 2008 and Windows 7.
20
TC1660
OmniVista 4760
INSTALLATION PROCEDURE FOR
VERSION 5.2.02.00.b - RELEASE 5.2
5.
5.1.
The table below supplies the information to be collected before installing the server and clients:
Windows data
Installation data
Management data
IP Address
License file
Directory
Host name
Passwords
Carrier configuration
Directory root
Connection to PCXs
Access security
Backup mode
Windows data.
They are used to integrate the server PC in client computer network.
Installation data.
They are essential to undertake the server installation.
Management data.
They are used to define with the client the information to be completed after installation.
5.2.
Company directory
The company directory management is described in the technical communication TCV060 Directory
Management.
5.3.
Carrier configuration
The Code book import function is used to automatically import all accounting carrier parameters in a
database from previously created text files.
Refer to Administrator Manual Section 4 Accounting/Traffic/VoIP, to create these text files in required
formats.
An A4715/A4740 -> A4760 carrier migration tool can be used to retrieve the carrier data of the same
tariff area. This tool operates only from version 4_4.14x of Alcatel 4715/A4740. Its functioning is
described in the technical communication TCV002 Alcatel 4715/4740 carrier data migration to
OmniVista 4760.
An A4755 -> A4760 carrier migration tool can be used to retrieve the carrier data of the same tariff
area. Its functioning is described in the technical communication TCV017 Carrier data migration from
Alcatel 4755 to OmniVista 4760.
21
TC1660
OmniVista 4760
INSTALLATION PROCEDURE FOR
VERSION 5.2.02.00.b - RELEASE 5.2
CAUTION
Each Code book import must be followed by a cost recalculation. It can be scheduled or run
manually. The recalculation process can take several hours depending on the number of tickets.
There are ten Code book files. Generally, they are located in a directory which has the carrier
name:
Information file
: .inf,
Area file
: .rgn,
City / Country file
: .ccn,
Direction file
: .dir,
Tariff file
: .trf,
Calendar file
: .cal,
Installation file
: .itl,
Adjustment file
: .adj.
ISDN services file
: .fct
Trunk groups file
: .trg (starting from R4.2)
The .inf ; .itl ; .dir ; .ccn files must be changed depending on the site.
In the .itl file, the node names must be exactly the same as declared in the system directory; ensure
the correct case.
Note
The import never deletes an object. It can only create or update the objects information in the files. The
needed deletion is carried out manually or with the Clean Carrier Configuration application in the
scheduler. These cleans are needed to keep the OmniVista 4760 performances.
5.4.
Security
The Security Guide provides all useful information to integrate OmniVista 4760 into a secured company
network.
Establish with the client, the access security to manage inside the application:
5.5.
Backup mode
22
TC1660
OmniVista 4760
INSTALLATION PROCEDURE FOR
VERSION 5.2.02.00.b - RELEASE 5.2
6.
INSTALLATION
6.1.
Only Operating System and JRE are factory installed on the PC delivered by Alcatel. Disabling the Onaccess scan mechanism can provide a real installation time gain.
6.2.
Before beginning the installation, prepare the Server PC accordingly to section 4 PREREQUISITES.
The installation fails if the operating system is not running in SP1 at least.
Refer to technical communication TC1007-Ed02 OmniVista 4760 Installation
/ Uninstallation chapter 6.14.
On W2003 ,hotfix KB956572 must be removed (freeze TOMCAT installation)
and replaced by the KB971812.
It is recommended to stop all Antivirus programs. Especially the Etrust software (Computer
Associates) prevents the installation of JRE.
If the PC has Dell Open Management services, close these services and copy the JTC1012.dll
file from 4760\bin directory to c:\Program Files\Dell\openmanage\oldiags\bin directory before
confirming the reboot of the PC when the installation is completed.
If the application has been installed previously and you must restart with an empty database, refer to
Appendix 3.
Main installation steps are given below (for more details refer to Installation Manual):
Preliminaries
Create debug.lock file to prevent rollback under Temp directory:
Default:
Document
Settings/Administrator/Local
Settings/Temp/
(W2003 or XP)
Users/Administrator/Appdata/Local/Temp (W2008 or Win7)
This folder is hidden by default in Windows Explorer:
select from Tools/Folder options/View:
folder
Show
hidden
files
and
To set trace mode installation, after copying 4760 software on hard disk, modify
ServerSetup.ini:
by
On 4760 Server:
Installation log file on server is in:
23
TC1660
OmniVista 4760
INSTALLATION PROCEDURE FOR
VERSION 5.2.02.00.b - RELEASE 5.2
Client4760\bin\4760Client.log on client
Installation
To install or upgrade a remote server using a Terminal Server or Remote
Desktop connection, it is mandatory to start the session as console
(command mstsc.exe /console (Windows 2003, Windows XP SP2) or
mstsc.exe /admin (Windows XP SP3, Windows Vista)).
Otherwise the operation would fail.
In the installation fails, contact the Technical Support by providing the OmniVista
4760_install.log log.
If an installation fails, refer to the technical communication TC1007 OmniVista 4760 Installation
/ Uninstallation for a possible manual uninstallation.
24
TC1660
OmniVista 4760
INSTALLATION PROCEDURE FOR
VERSION 5.2.02.00.b - RELEASE 5.2
Type
String
Destination directory
Directory
Directory
Localization language
Application administrator
logon
Database administrator
logon
Password
LDAP port
HTTP port
LDAPS port
TOMCATport
Directory
Directory
Directory
FQDN
Name or IP address
Country name
Language name
Default: AdminNmc
Fixed: DBA
Default: 389
Default: 80
Default: 636
Default: 8090
Always
are
escaped
Directory exists, is empty and is not a root
directory such as C:\
Directory exists, is empty and is not a root
directory such as C:\
Directory exists, is empty and is not a root
directory such as C:\
Directory exists, is empty and is not a root
directory such as C:\
Directory exists, is empty and is not a root
directory such as C:\
DNS domain exists
Hostname less or equal to 15 characters
Name can be resolved
See Table: OmniVista 4760 supported
countries
See Table: OmniVista 4760 supported
countries
ASCII characters
Characters not in: ,+\<>;#&%|^
Characters in ASCII letters and digits and
_$#
ASCII characters
Length is at least 8
LDAP constraint: characters not in:
,+\<>;#&%|^ and <space>
ASA constraint: characters not in
!%&()*+,-./:;<=>?\^`{|}~
and
<space>
In [1-1024] and [5000-65535]
In [1-1024] and [5000-65535]
In [1-1024] and [5000-65535]
In [1-1024] and [5000-65535]
Launch ServerSetup.exe .
After starting ServerSetup.exe, the system checks if software is already installed by
searching this registry entry:
HKEY_CLASSES_ROOT\Installer\Products\9850FC3C721B51C43A740ECDBC7CE478
25
TC1660
OmniVista 4760
INSTALLATION PROCEDURE FOR
VERSION 5.2.02.00.b - RELEASE 5.2
If the hostname has more than 15 characters, the LDAP installation will fail. The limitation to 15
characters is written in the registry.
The registry key is found in the place:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog.
During installation, the setup files are extracted and copied in the %Temp% folder. If the space in
the %Temp% folder is less than required, then it will not copy all the files in the %Temp% folder.
So to make sure that there is enough space in %Temp% folder a check has been done during
installation. The setup will not continue to install if the temp size is less than 100 MB. The
threshold value is maintained at 100 MB to make sure that it has enough space to keep the
extracted files from the setup during installation. The estimation is calculated from the space
occupied by the installation files in the %Temp% folder. This space checking is only applicable
for Server.
3
If the correct Java Runtime Environment (JRE) (1.6.0_11) is not detected, its installation will start
automatically.
Specify:
the Company Name which will be used as directory root,
the installation directory of OmniVista 4760 (this access path must not have space as
Program Files), of Sun ONE Directory server, of Sybase software and database SQL.
Sybase software should never be installed in the same directory as
OmniVista 4760; the upgrade towards a higher version would fail.
Specify:
The numbers of the LDAP, LDAPS , HTTP and TOMCAT ports are standardized. Do not
change them unless you need to,
Enter the unique password which will be set for the 4 accounts:
Directory manager
Admin
Adminnmc
dba
Unauthorized characters are listed in the table above.
Enter:
the IP name / address of the e-mail server if used,
choose the Country that gives the Language, the paper size and the
currency (parameters used for the accounting),
The Cost Centers management method.
26
TC1660
OmniVista 4760
INSTALLATION PROCEDURE FOR
VERSION 5.2.02.00.b - RELEASE 5.2
6.3.
Description
Installation date, format MM-DD-YY
Version that has been installed
DNS domain
Install directory
Host name (without domain)
Httpd server port
Secured LDAP port
TOMCAT port
LDAP server port
Company name
Sybase ASA installation directory
Database files directory (*.db)
SunTM DSEE installation directory
Installation time, format HH:MM:SS
Current version at install time (never changed) (created with installation)
Version that has been upgraded (created when upgrading)
The patches delivered with a version will be automatically installed at the end of the installation
procedure of the product.
Patches are in .ace format.
This type of patch can carry out the following processes:
Control (stop / start) one or several Windows services.
Execute a SQL script.
Import a LDIFF file.
Extract an archive (4760 helps for example).
Copy files.
Launch an application.
27
TC1660
OmniVista 4760
INSTALLATION PROCEDURE FOR
VERSION 5.2.02.00.b - RELEASE 5.2
6.4.
Server post-installation
Post-installation is described in the Installation manual. Carry out in more the operations described
below.
When the installation and the configuration are finished, we recommend performing a server
data backup on a networked disk or on a CDROM.
Manage the sharing of archive directory of tickets to allow the restoration of these tickets.
Example: Name of sharing: 4760_ARC, Reading right for Everyone.
In order to retain the correct version of JRE, you should disable the automatic
check of upgrades.
In the Control Panel, use the standard display (the default display of Windows XP masks some
icons):
Click on java,
6.5.
If it is not the case, ask the network manager to correct the DNS management or to complete host
file (under winnt or Windows\system32\drivers\etc\) of Client PC and Server PC with:
IP_Address Host_Name Host_Name.DNS_Suffix_Name
Example: 155.166.123.156 OmniVista OmniVista.alcatel.fr
28
TC1660
OmniVista 4760
INSTALLATION PROCEDURE FOR
VERSION 5.2.02.00.b - RELEASE 5.2
Method 1
1
Launch ClientSetup.exe.
If the correct Java Runtime Environment (JRE) (1.6.0.21) is not detected, its installation will start
automatically.
In order to retain the correct version of JRE, you should disable the automatic
check of upgrades.
In the Control Panel, use the standard display (the default display of Windows XP masks some
icons):
Click on java,
With a 4760 client installed under Vista, a warning message is displayed. Select the Dont show this
message again option.
Method 2
When the server is already installed you can download the client installation file using this url:
http:/server_name/cgi-bin/OmniVista4760Client.exe (replace server_name by your OmniVista 4760
server name).
For more information, refer to the Installation Manual.
6.6.
6.6.1. Installation
Contact the client network manager to authenticate the OmniVista 4760 server with its name and its
IP address in intranet sites.
If a request of proxy authorization occurs during this procedure, you will probably not be able to
access the application since the network manager does not allow this type of connection.
Use your WEB browser to access the OmniVista 4760 home page.
29
TC1660
OmniVista 4760
INSTALLATION PROCEDURE FOR
VERSION 5.2.02.00.b - RELEASE 5.2
Following management will prevent from a language switch after search in the directory. In this case
the No such object error message is also displayed.
The management described concerns Internet Explorer 6.0. An equivalent management has to be
done for other browsers.
Before accessing the JAVA page of the network management, install the JAVA Plug-in:
If the correct JRE version (1.6.0.21) is already installed on the station, go to the point 5.
On the home page, click on the before using the Alcatel-Lucent OmniVista
4760 NMS for the first time or from a new server, please install
JRE.
On the home page, click on the To open Java application writing rights link.
Click on Open.
30
TC1660
OmniVista 4760
INSTALLATION PROCEDURE FOR
VERSION 5.2.02.00.b - RELEASE 5.2
If from the PC, you cannot ping to OmniVista.alcatel.fr, there is a name or domain problem.
Check the hosts file or the addresses of the DNS server.
If the hosts file is used (without DNS), it must contains a line like below:
ip_address server_name server_name.domain
Example
155.166.123.156 OmniVista OmniVista.alcatel
7.
UPGRADES
Perform OmniVista 4760 server data backup then a defragmentation before starting upgrade.
7.1.
Prerequisites
Close all Windows opened before starting server upgrade but do not
stop NMC Services.
The installation fails if the operating system is not running in SP1 at least.
On W2003,hotfix KB956572 must be removed and replaced by KB971812.
Stop if necessary the SIP DM Server services.
Temp4760 folder
This folder will be created under the %Temp% folder. During the upgrade it makes a backup of the data
and then uninstalls and reinstalls and finally makes an import of the data backup. So during the backup
operation the Temp4760 folder is used to keep the backup files. It stores the files in ace format.
Currently ten ACE files are stored. The Temp4760 folder is created depending upon the path given
during installation of LDAP, Sybase or 4760.
If the path drive letter for the LDAP is E: then Temp4760 will be created in the path
E:\Temp\Temp4760\.
During the LDAP database backup the Save_Ldapbasesfiles.ace file will be stored in the path
E:\Temp\Temp4760\. If the Sybase is installed in path drive D: then the
Save_ASAdatabasefiles.ace file will be available in the path D:\Temp\Temp4760.
7.2.
Close the NMC service manager with the OmniVista 4760 service manager.
As soon as the dependent services have all been closed, copy the field of type xxyyyzza.sw4760
supplied by Actis, renaming it nmc.license after renaming old nmc.license file (and not
nmc.license.txt). Check this name by right clicking \Properties. Then move this file in the
4760\etc installation directory.
31
TC1660
OmniVista 4760
INSTALLATION PROCEDURE FOR
VERSION 5.2.02.00.b - RELEASE 5.2
7.3.
Versions
5.0.07.02.b/5.0.07.03.c/5.0.07.05.b
5.1.04.00.b
5.1.06.03.c
5.2.01.03.d
Backup parameters (PCX in System Directory, Logins, Directory, Carriers definitions, accounting
tickets).
Reinstall if necessary a new operating system compatible with OmniVista 4760 R5.2.
Get the directory manager and dba passwords. You should have a license compatible with the
Release R5.2 (version 12 or 13).
The customizing carried out on the various "themes" offered for Web Client will be saved during the
upgrade in the 4760\(web)client\thmes directory.
The customizing carried out on the welcome page of Web Client is not saved. If necessary, you
should save the modified data of the 4760\webclient (R4.0) or 4760\client (other releases)
directory.
The customizing of the topology is saved during the upgrade. For security, it is possible to first export
the data from the system directory:
Nmc\nmcConfiguration\globalPreferences\topology
The Java RunTime Environment (JRE) will be installed if its version is not correct:
1 It is advisable to stop any On-access scan mechanism. Disabling the On-access scan
mechanism can provide a real installation time gain.
2 Check all OmniVista 4760 services have been started.
32
TC1660
OmniVista 4760
INSTALLATION PROCEDURE FOR
VERSION 5.2.02.00.b - RELEASE 5.2
7.4.
The corrective patches are installed automatically at the end of 4760 server update if they are available
in the installation CD-ROM.
To manually install a patch copy the correspondent .ace file in the 4760\Install\Patches folder
and launch the 4760\install\Patchinstaller.exe command.
You can consult the patch installation log in \4760\install\patch_installer.log.
The installed patch list is in \4760\install\patch_history.ini.
7.5.
When a client PC running an earlier version connects to a server in 5.2.02.00.b, the system proposes an
update from this server. This update is running correctly only from a client version equal or greater than
3.2.05.00.b. For client version less than 3.2.05.00.b, do not accept the update procedure otherwise
client could not open anymore. Under such circumstance, it is necessary to uninstall the client and to
reinstall it.
If the client is in version lower than R5.1, it is kept. An additional new client in R5.1 is installed in a
directory named Client4760 5.1.
This allows the cohabitation of several versions on a same PC.
A client can also be installed by launching the ClientSetup.exe file.
The rules of cohabitation above will also apply.
7.5.1. Installing the patch
There are no more patches specific "clients".
When connecting a client to server, the version of the nmc50.jar file is checked.
If the client version is below, an upgrade is available when connecting to the server. The upgrade is
carried out automatically.
7.5.2. Disabling the automatic upgrades of JRE
In order to retain the correct version of JRE, you should disable the automatic check of upgrades.
In the Control Panel, use the standard display (the default display of Windows XP masks some icons):
33
TC1660
OmniVista 4760
INSTALLATION PROCEDURE FOR
VERSION 5.2.02.00.b - RELEASE 5.2
8.
OmniPCX OFFICE
Refer to the Technical Communication TCV049 Installation procedure for Release 2.1/3.x for OmniPCX
Office (IP, ppp, Accounting, Alarms, Troubleshooting).
8.1.
The management described below has to be applied, not only for the save/restore/download
operations, but also to enter into PCX configuration.
The OmniPCX Office data are saved by default on the 4760 server PC in the directory
4760_ARC/OXO/data. This directory is shared as 4760-databases during 4760 installation (or 4760PM5 in case of upgrade operation), with read access to everyone.
CAUTION
If the 4760_ARC\OXO\data directory already exists before 4760 server installation (for instance after
uninstalling a previous 4760 server) and has a shared name, this name will not be modified by 4760
R4.1 installation. To use OmniPCX Configuration application from 4760 server, Windows directory
shared name must be the same as the name defined in OmniVista 4760 System directory (this name can
be configured in /NmcConfiguration GlobalPreferences / Config / OXOAccess).
The PC administrator has to allow the writing right on the sharing to a local user. Remove "Everyone"
from the list of users. In the sharing management, for the user limit, "Maximum allowed" has to be
validated. A reboot of the PC can be needed to take into account the management.
This local user has to be declared in the 4760 server:
System directory / NmcConfiguration / GlobalPreferences/Config/OXOAccess
The URGALARM user can be used if its already created or all other local user with permanent
password.
The software versions to be downloaded to the PCX have to be stored in the directory
4760_ARC/OXO/sw. For security reasons, it is no more required to share this directory.
8.2.
OMC
From R4.0, OmniVista 4760 does not support PM5 software. To configure OmniPCX Office (whatever is
the version) through OmniVista 4760, OMC software has to be installed on the server and client PCs.
OmniPCX Office can be configured from a 4760 client after following the procedure below:
Run 4760 client, open Configuration application and launch the "Configure" menu after
selecting an OmniPCX Office: OMC client will be automatically open.
34
TC1660
OmniVista 4760
INSTALLATION PROCEDURE FOR
VERSION 5.2.02.00.b - RELEASE 5.2
Notes
9.
The same procedure has to be applied on PC hosting 4760 server to perform OmniPCX Office
maintenance operations.
Administrative parameters (mandatory customer information) must be configured on each
OmniPCX Office that we aim to manage from OmniVista 4760.
35
TC1660
OmniVista 4760
INSTALLATION PROCEDURE FOR
VERSION 5.2.02.00.b RELEASE 5.2
APPENDIX 1
CORRECTIONS
CORRECTIONS
CONTENTS
Corrections in R5.1
1.
ACCOUNTING-PTP-VOIP ........................................................... 3
2.
MAINTENANCE .......................................................................... 3
3.
AUDIT ........................................................................................ 3
4.
SCHEDULER ............................................................................... 3
5.
REPORTS .................................................................................... 3
6.
CONNECTIVITY .......................................................................... 3
Corrections in R5.1.1
1.
MAINTENANCE .......................................................................... 3
2.
AUDIT ........................................................................................ 4
3.
ANNUAIRE ................................................................................ 4
Corrections in R5.2
1.
2.
Ed. 01 / 06-04-2012
TC1660
OmniVista 4760
INSTALLATION PROCEDURE FOR
VERSION 5.2.02.00.b RELEASE 5.2
3.
APPENDIX 1
CORRECTIONS
Ed. 01 / 06-04-2012
TC1660
OmniVista 4760
INSTALLATION PROCEDURE FOR
VERSION 5.2.02.00.b RELEASE 5.2
APPENDIX 1
CORRECTIONS
Corrections in R5.1
1.
ACCOUNTING-PTP-VoIP
2.
MAINTENANCE
crms00153645 4760 R5.0/ Software download/noautostart not sent for H1 PCX release / 192752061.
3.
AUDIT
4.
SCHEDULER
crms00167838 Incorrect PCX config export status in the scheduler (mao off) / 1-95128131.
5.
REPORTS
6.
CONNECTIVITY
Corrections in R5.1.1
1.
MAINTENANCE
Ed. 01 / 06-04-2012
TC1660
OmniVista 4760
INSTALLATION PROCEDURE FOR
VERSION 5.2.02.00.b RELEASE 5.2
2.
APPENDIX 1
CORRECTIONS
AUDIT
3.
ANNUAIRE
Corrections in R5.2
1.
CR id
CR headline
crms00256881
Directory/link creation
crms00347803
crms00347804
crms00348669
Adminnmc locked
crms00348858
crms348925
crms00350346
crms00351328
crms00364110
crms00365836
crms00368525
crms00368529
crms00368533
Ed. 01 / 06-04-2012
TC1660
OmniVista 4760
INSTALLATION PROCEDURE FOR
VERSION 5.2.02.00.b RELEASE 5.2
2.
APPENDIX 1
CORRECTIONS
Ed. 01 / 06-04-2012
TC1660
OmniVista 4760
INSTALLATION PROCEDURE FOR
VERSION 5.2.02.00.b RELEASE 5.2
3.
APPENDIX 1
CORRECTIONS
Ed. 01 / 06-04-2012
TC1660
OmniVista 4760
INSTALLATION PROCEDURE FOR
VERSION 5.2.02.00.b RELEASE 5.2
Ed. 01 / 06-04-2012
APPENDIX 1
CORRECTIONS
TC1660
OmniVista 4760
INSTALLATION PROCEDURE FOR
VERSION 5.2.02.00.b RELEASE 5.2
Ed. 01 / 06-04-2012
APPENDIX 1
CORRECTIONS
TC1660
OmniVista 4760
INSTALLATION PROCEDURE FOR
VERSION 5.2.02.00.b - RELEASE 5.2
APPENDIX 2
RECOMMENDATIONS
RECOMMENDATIONS
CONTENTS
1.
1.1.
1.2.
1.3.
2.
SECURITY ................................................................................... 3
2.1.
Password ................................................................................................. 3
2.2.
Rights ....................................................................................................... 4
3.
DIRECTORY ................................................................................ 4
3.1.
3.2.
4.
CONFIGURATION ...................................................................... 5
4.1.
4.2.
5.
ALARMS ..................................................................................... 5
5.1.
6.
TOPOLOGY ................................................................................ 6
7.
ACCOUNTING ........................................................................... 6
7.1.
7.1.1.
Management overview................................................................................ 6
7.1.2.
7.2.
Ed. 01 / 06-04-2012
TC1660
OmniVista 4760
INSTALLATION PROCEDURE FOR
VERSION 5.2.02.00.b - RELEASE 5.2
APPENDIX 2
RECOMMENDATIONS
7.3.
7.4.
8.
7.4.1.
7.4.2.
8.1.
9.
SCHEDULER ............................................................................... 8
9.1.
Backup ..................................................................................................... 9
10.5.2.
Restore ..................................................................................................... 9
Ed. 01 / 06-04-2012
TC1660
OmniVista 4760
INSTALLATION PROCEDURE FOR
VERSION 5.2.02.00.b - RELEASE 5.2
APPENDIX 2
RECOMMENDATIONS
1.
INFRASTRUCTURE / INSTALLATION
1.1.
1.2.
Driver version for Windows 2000/XP, that is supplied with MOXA box, is not supported:
Not stable.
Use only the 1.5.18 version supplied on folder TOOLS\MOXA of OmniVista 4760 CD-ROM.
1.3.
Restart.
It is recommended to manage the MOXA IP address in the same sub-network than the server one.
It is not recommended to use more than 3 MOXA boxes.
2.
SECURITY
2.1.
Password
Rules
ASCII characters
Length at least = 8
LDAP constraint: characters not in : ,+"\<>;#&%|^ and <space>
ASA constraint: characters not in
Ed. 01 / 06-04-2012
TC1660
OmniVista 4760
INSTALLATION PROCEDURE FOR
VERSION 5.2.02.00.b - RELEASE 5.2
APPENDIX 2
RECOMMENDATIONS
Admin and DBA are needed for the maintenance and the upgrade of server,
Admin and Directory Manager cannot connect to the OmniVista, they are used for advanced
management of the SunTM DSEE.
Do not use AdminNMC, after installation for standard management of OmniVista 4760. Create
other administrator or manager accounts in order to retain the preferences of the various administrators
and managers and always keep a supervisor account even if the password is lost.
2.2.
Rights
To allocate a right to an OmniVista login, select the predefined groups such as Directory Expert,
Network Expert and add members to these groups.
A login can belong to several predefined groups. In this case, these rights correspond to the sum of
rights of each group.
If there is no relevant profile:
allocate the rights individually:
select each application,
add a specific right (read, write, etc.) corresponding to the individual.
3.
DIRECTORY
3.1.
Be careful to disk space needed if you inserting photos in the directory: a 20 KB jpg format photo takes
70 KB in LDAP (10 000 photos => 700 MB in LDAP base).
3.2.
When creating the PCX, you must specify the number of network node. On network 0 node 1, you must
not enter 001 but directly 1 otherwise the Past Time Performance files loading in database no longer
works.
Avoid the used of . (dot) in the name of the Network, Sub-Network and PCX (In some cases it could be a
problem during restoration of archives accounting tickets)
Example to avoid: Name of PCX : Brest.Alcatel
Ed. 01 / 06-04-2012
TC1660
OmniVista 4760
INSTALLATION PROCEDURE FOR
VERSION 5.2.02.00.b - RELEASE 5.2
4.
CONFIGURATION
4.1.
APPENDIX 2
RECOMMENDATIONS
Make sure to cut all connections in progress to this PCX via OmniVista 4760:
cut Telnet,
close Configuration,
but above all in the technical directory, deactivate the Alarm Processing.
As soon as the connection has been cut, carry out your modification in the "Connectivity" tab then if
necessary reactivate the alarm processing.
4.2.
Its extremely inadvisable to name a great amount of free users in the same way (example:
name=FREE). This rule as well concerns Dect Shells.
Its recommended adding an information in the First name field (example: extension number).
To prevent from entry creation for these extensions in the Enterprise Directory, you have to not validate
the Call by name function.
These extensions s successive allocations / unallocations lead to a lot of inactive sets creation into the
accounting organization.
The cleaning of a great amount of inactive free of ticket entries regularly fails; refer to XTSce15452.
5.
ALARMS
5.1.
Alarm supervision
If a PCX has to centralize all the network alarms and events, you must correctly manage the nodes
supervised by this PCX in the PCX incident management. Do not set the node to supervise itself.
If the management is incorrect, the alarm server will be saturated by the events sending which damage
the application operation (slow down, close of some services and disk saturation).
At 4760 server level, create this alarm centralizing PCX to do not restore alarms from a PCX still
unknown in 4760. Do not check the box Alarm Review on the PCX monitored otherwise the alarms
will be doubled.
Starting from R2.1, a character "_" is added to the server name, in the "Events Routing discriminator"
created in the OmniPCX 4400 and Enterprise (SERVER_ instead of SERVER). The number of names being
restricted to 16, it is recommended to suppress previous names in the PCX. If a PCX is not able to create
an "Events Routing discriminator" the alarms are not sent to the corresponding server.
Ed. 01 / 06-04-2012
TC1660
OmniVista 4760
INSTALLATION PROCEDURE FOR
VERSION 5.2.02.00.b - RELEASE 5.2
6.
APPENDIX 2
RECOMMENDATIONS
TOPOLOGY
When the OmniVista 4760 manages a complex PCX network including a lot of inter-nodes links, the
topology display delay can be very long. According to the configuration type, following two solutions
decreases this display time:
a parameter in the Topology application, allows to enable/disable the display of the VPN links:
Preferences\Topology\Configuration\Display VPN links
a script allows to suppress the display ot the inter-node links to reduce the display delay of the
network. It is included in the TOOL directory of the installation CD.
To launch this script proceed as follows:
edit the delnodelink.bat file and enter your own Directory Manager password,
Before any upgrade operation, caution has to be taken to be able to retrieve the work.
7.
ACCOUNTING
7.1.
7.1.1.
Management overview
input the carrier tariffs in the local currency or in the referenced currency,
cost calculation will be performed in the referenced currency (after applying a conversion rate, if
necessary),
7.1.2.
At server installation, the selection of country = Default takes into account the country defined in
Regional Settings of Windows and initializes referenced currency.
7.2.
This option is only for OmniPCX 4400 and OmniPCX Enterprise Ux and Lx PCXs.
During the installation, you must define the management method of cost centers. If you choose to
dissociate the PCX cost centers from the OmniVista ones, you must manage them in the OmniVista
Ed. 01 / 06-04-2012
TC1660
OmniVista 4760
INSTALLATION PROCEDURE FOR
VERSION 5.2.02.00.b - RELEASE 5.2
APPENDIX 2
RECOMMENDATIONS
application. The Cost Center field, in OmniVista, will be completely independent from the cost
center managed on the PCX, there will be no synchronization in either direction.
To force a cost center in the accounting organization:
create a cost center directly in the accounting organization; then move the entries in this cost center.
The Configuration module will continue to see the PCX cost centers.
7.3.
By default, the tickets and reports are purged after 3 months (94 days).
Before modifying these parameters, analyze the site to check that the limit of 20 GB of accounting data
(30 millions tickets) will not be exceeded. Then make the modifications:
7.4.
7.4.1.
Carrier management
Tariff: Managing the period
During management of tariffs, period, only the start time is managed, the application automatically
manages the end time.
Do not forget to create the period which begins at 00H00 and loop back with the 1 st one managed.
7.4.2.
During normal use, the number of Town / Country must be reduced. This information is in fact used to
identify in the reports the telephone directions frequently used; for example, to identify the subsidiaries of
a company.
It is not used to calculate the cost of telephone calls.
When the number of City / Country names becomes too high (>5000), the coherence check system
slows down the performance during accounting modifications.
Beyond 10000 Cities/Countries, the calculation of cost is impossible.
It is necessary to create areas and directions to optimize the treatment of the cities/countries.
Example
City country Name
Paris 0170
Paris 0171
Paris 0172
Region
Paris
Prefix 0170
Prefix 0171
Prefix 0172
In this example, for the Cities/Countries, the Paris entry appears 3 times whereas by using the regions
and directions, the Paris entry appears only once.
Ed. 01 / 06-04-2012
TC1660
OmniVista 4760
INSTALLATION PROCEDURE FOR
VERSION 5.2.02.00.b - RELEASE 5.2
8.
REPORT GENERATOR
8.1.
APPENDIX 2
RECOMMENDATIONS
CAUTION
The week defined in the report application does not begin on Monday but Sunday at 00h00 AM and
finishes on Saturday at 11h59 PM.
9.
SCHEDULER
9.1.
10. MAINTENANCE
10.1. Rule of partitioning
It is recommended to have only one partition per physical disk and to separate the partition system from
the application. In effect, if a partition seems to be too small, it is impossible to extend it without being
obliged to format and re-install.
Example: put OS on C: on a disc of 80 GB, and the application on D: on a disc of 72 GB.
If the network allows it, it is recommended to use "network" disk as working space to carry out upgrades,
defragmentation data backups. In effect, each of these operations requires for their working space near
the twice Sybase size therefore depending on the cases up to 40 GB.
Ed. 01 / 06-04-2012
TC1660
OmniVista 4760
INSTALLATION PROCEDURE FOR
VERSION 5.2.02.00.b - RELEASE 5.2
APPENDIX 2
RECOMMENDATIONS
You must schedule a backup at least once a week of the OmniVista 4760 data and purge these
backups to avoid the disk saturation.
Refer also to the chapter Tasks succession order (Scheduler) to correctly schedule this task.
Note
A backup must be carried out before any important operation on the server (Upgrade, Retrospective
Cost Calculation on the complete database, etc.).
OmniVista 4760 places the backup in a local directory of the PCX disk. The PCX can refuse the
copy if this local directory (\usr4\BACKUP\IMMED) already contains a backup.
Ed. 01 / 06-04-2012
TC1660
OmniVista 4760
INSTALLATION PROCEDURE FOR
VERSION 5.2.02.00.b - RELEASE 5.2
APPENDIX 3
ADVANCED MANAGEMENT
ADVANCED MANAGEMENT
CONTENTS
1.
1.1.
1.2.
1.2.1.
1.2.2.
1.3.
1.4.
1.5.
2.
DIRECTORY ................................................................................ 5
2.1.
2.2.
2.2.1.
2.3.
3.
3.1.
4.
4.1.
4.1.1.
Restriction .................................................................................................... 6
4.1.2.
Procedure .................................................................................................... 6
4.2.
4.3.
5.
MAINTENANCE .......................................................................... 8
5.1.
Ed. 01 / 06-04-2012
TC1660
OmniVista 4760
INSTALLATION PROCEDURE FOR
VERSION 5.2.02.00.b - RELEASE 5.2
6.
APPENDIX 3
ADVANCED MANAGEMENT
5.1.1.
Restriction .................................................................................................... 8
5.1.2.
5.1.3.
CONFIGURATION ...................................................................... 9
6.1.
Ed. 01 / 06-04-2012
TC1660
OmniVista 4760
INSTALLATION PROCEDURE FOR
VERSION 5.2.02.00.b - RELEASE 5.2
APPENDIX 3
ADVANCED MANAGEMENT
1.
INFRASTRUCTURE / INSTALLATION
1.1.
To reinstall the OmniVista 4760 server application with an empty database on a PC where OmniVista
has already been installed, you must first uninstall the application. The server module must be
uninstalled using a local administrator account.
To uninstall the OmniVista 4760 server:
Close all the OmniVista 4760 client applications. The SNMP and/or Compaq manufacturer services
must not be enabled during the uninstall phases.
Note
The Java Runtime Environment is not uninstalled.
Copy the PsExec directory from the uninstall tool.zip file available on the DVD of the
version (Tools) to c:\Program Files.
Launch reg_del.bat.
This commands opens the registry editor.
Remove the directories where are installed various components of the system: 4760 server,
Sybase, Netscape, SQL database.
Ed. 01 / 06-04-2012
TC1660
OmniVista 4760
INSTALLATION PROCEDURE FOR
VERSION 5.2.02.00.b - RELEASE 5.2
APPENDIX 3
ADVANCED MANAGEMENT
Refer to the technical communication TC1007 OmniVista 4760 Installation / Unsinstallation for
additional information about the manual uninstallation.
1.2.
1.3.
Recover the SQL database files in the 4760\data directory to copy them on the new PC after
installing the 4760 in the same version.
1.4.
dba
Admin
Directory Manager
The change is made by using the toolsOmnivista tool available from 4760\bin directory.
Directory Manager password is needed to change account passwords.
For more information, please refer to the technical communication TCV045 How to change OmniVista
4760 server passwords?.
1.5.
The ToolsOmnivista tool is used to update the organization of the accounting. It is used to assign
the tickets of inactive entities to the corresponding active entities. Then these inactive entities are
removed.
Ed. 01 / 06-04-2012
TC1660
OmniVista 4760
INSTALLATION PROCEDURE FOR
VERSION 5.2.02.00.b - RELEASE 5.2
APPENDIX 3
ADVANCED MANAGEMENT
This feature allows a re-sequencing of the organization after a period of adaptation which generally
follows the startup of a OmniVista 4760 server.
2.
DIRECTORY
2.1.
For more information, refer to Alcatel 4059 installation procedure; the minimum release is 4.014.10.
2.2.
Customize the results display and print parameters (number of lines, grid sort, attributes to display in
grid, printed attributes)
Customize the detail and edit parameters (attributes to display and to edit in detail view)
Customize fully the Custom theme (name, logo, logo position, colors, background, fonts).
2.3.
An integrated tool allows to modify most of the field names displayed in Company Directory from a Web
or installed client.
To launch this tool proceed as follows:
Start/Programs/OmniVista 4760/Tools/Customize dictionary
For more information, refer to the Administrator Manual - Directory section.
Ed. 01 / 06-04-2012
TC1660
OmniVista 4760
INSTALLATION PROCEDURE FOR
VERSION 5.2.02.00.b - RELEASE 5.2
3.
ALARMS - TOPOLOGY
3.1.
E-mail server
APPENDIX 3
ADVANCED MANAGEMENT
OmniVista 4760 can send alarms, reports or a accounting monitoring notification to an e-mail server
specifying a local or external e-mail address. Transmission is done via SMTP on the default port 25.
The sender's name of messages can be customized in the technical directory (nmc\server_name).
To check that the e-mail server can be reached by SMTP on port 25, try to connect via Telnet. On the
server PC, at the DOS command prompt, execute :
Telnet Server_Name_mail 25
If the SMTP port of your e-mail server is not the standard port 25, change it during the Telnet test. If the
test is successful on this port, copy the port number in the OmniVista 4760 application :
click on the machine name in the tree structure. In the data area, modify the attribute E-mail
server and set :
(do not insert spaces around the : )
E-mail_Server_Name:Port_Number
For more information, refer to the technical communication TCV020 Sending e-mails with
OmniVista 4760 Release 2.0.
4.
REPORT GENERATOR
4.1.
4.1.1. Restriction
To schedule a report with a file export to a network drive, OmniVista 4760 must be able to use a
Windows account with certain rights.
If the password is wrong or obsolete, the report will no longer be exported.
4.1.2. Procedure
Use an account with local administrator rights on the OmniVista Server PC. We will suppose that this
account is named ADM4760 and that the Server PC is named PCSERVER.
If the Server PC is installed in a Windows domain and that the users log in DOMUSER, therefore the
login of this account is DOMUSER\Adm4760.
If the Server PC is installed in a workgroup, the login of this account is PCSERVER \Adm4760.
1
Ed. 01 / 06-04-2012
TC1660
OmniVista 4760
INSTALLATION PROCEDURE FOR
VERSION 5.2.02.00.b - RELEASE 5.2
APPENDIX 3
ADVANCED MANAGEMENT
4 Grant the OmniVista 4760 the right to use this user. To do this :
click on NT Account ,
4.2.
The specific characters to languages (Polish, Czech, Chinese, Russian, etc.) are taken into account in
exported reports in pdf format.
To do that, you should specify the Windows font which supports these specific characters: under
NMC\serverName : complete Name of font family for pdf export and Available
font styles (pdf export) (set the font name in an application such as Word).
4.3.
The paper format for printing reports is selected when installing the server. However, you can change it
after. In the technical directory, click on the name of server in the tree. In the right window, select the
appropriate Paper Format.
Ed. 01 / 06-04-2012
TC1660
OmniVista 4760
INSTALLATION PROCEDURE FOR
VERSION 5.2.02.00.b - RELEASE 5.2
5.
MAINTENANCE
5.1.
APPENDIX 3
ADVANCED MANAGEMENT
5.1.1. Restriction
The OmniVista 4760 Server PC and the remote host must be located on the same Windows host
domain : in the same workgroup or in the same domain.
This backup mode requires using a Windows account. Therefore this account must be enabled of the
OmniVista 4760 server and have the right to move files on the remote host.
5.1.2. Procedure in a domain
For the requirements of this procedure, we will suppose that the hosts are installed in the same
DOMMACHINE domain and that the users are identified in the DOMUSER domain.
Use a networked account with local administrator rights on the OmniVista Server PC. Let us name this
account ADM4760. The login of this account is DOMUSER\Adm4760.
1
Share a repertory on the remote host for the user DOMUSER\ ADM4760.
Grant the Execcdex and SaveRestore services, the right to use this user. To do this :
click on NT Account ,
When the Maintenance module is run, you can select a network disk for the backup.
Ed. 01 / 06-04-2012
TC1660
OmniVista 4760
INSTALLATION PROCEDURE FOR
VERSION 5.2.02.00.b - RELEASE 5.2
APPENDIX 3
ADVANCED MANAGEMENT
Grant the Execcdex and SaveRestore services, the right to use this user. To do this :
click on NT Account ,
4 When the Maintenance module is run, you can select a network disk for the backup.
6.
CONFIGURATION
6.1.
The OmniPCX Enterprise security access profile 10 has been designed to allow some users such as
attendants to perform simple configuration operations.
By default, user with this profile will only have:
From Company directory, set the ATTENDANT4760 person into the member list of the
"Simplified Configuration" group (localized in Company name / Administration/ Groups).
From Security panel menu, open Access Control Editor for Configuration application: check
Profile 10 has been set to "Simplified Configuration" group.
If it is not the case, add or update rights of the "Simplified Configuration" group with:
Access Level= Normal
OmniPCX 4400 Access Level= Profile 10
Note
Profile (10) can be edited to add more available items (for instance program keys) or to remove
available items (for instance hunt groups).
Ed. 01 / 06-04-2012
TC1660
OmniVista 4760
INSTALLATION PROCEDURE FOR
VERSION 5.2.02.00.b - RELEASE 5.2
Ed. 01 / 06-04-2012
APPENDIX 3
ADVANCED MANAGEMENT
10
TC1660
OmniVista 4760
INSTALLATION PROCEDURE FOR
VERSION 5.2.2.00.b - RELEASE 5.2
APPENDIX 4
NEW FEATURES
NEW FEATURES
CONTENTS
New R5.2 Features
1.
INFRASTRUCTURE ...................................................................... 2
2.
MAINTENANCE .......................................................................... 2
1.
INFRASTRUCTURE ...................................................................... 3
2.
3.
Ed. 01 / 06-04-2012
TC1660
OmniVista 4760
INSTALLATION PROCEDURE FOR
VERSION 5.2.2.00.b - RELEASE 5.2
APPENDIX 4
NEW FEATURES
1. INFRASTRUCTURE
2. MAINTENANCE
OmniVista 4760 R5.2 supports the parallel download from Master PCX to Client PCX. This feature
is available from OXE R9.1 release onwards.
This feature will work only for the master PCXs which are either Appliance Server or Blade Server
having R9.1 release and above. There is no change in the status files.
Ed. 01 / 06-04-2012
TC1660
OmniVista 4760
INSTALLATION PROCEDURE FOR
VERSION 5.2.2.00.b - RELEASE 5.2
APPENDIX 4
NEW FEATURES
1. INFRASTRUCTURE
OS Migration
Steps.doc
3. SNMP Proxy
Ed. 01 / 06-04-2012
TC1660
OmniVista 4760
INSTALLATION PROCEDURE FOR
VERSION R5.2.2.00.b.c - RELEASE 5.2
APPENDIX 5
RESTRICTIONS AND IDENTIFIED
DEFAULTS
CONTENTS
1.
INFRASTRUCTURE ...................................................................... 3
2.
CONFIGURATION ...................................................................... 4
3.
DIRECTORY ................................................................................ 4
4.
INSTALLATION .......................................................................... 5
5.
MAINTENANCE .......................................................................... 5
6.
7.
8.
REPORT ..................................................................................... 5
9.
Ed. 01 / 06-04-2012
TC1660
OmniVista 4760
INSTALLATION PROCEDURE FOR
VERSION R5.2.2.00.b.c - RELEASE 5.2
Ed. 01 / 06-04-2012
APPENDIX 5
RESTRICTIONS AND IDENTIFIED
DEFAULTS
TC1660
OmniVista 4760
INSTALLATION PROCEDURE FOR
VERSION R5.2.2.00.b.c - RELEASE 5.2
1.
APPENDIX 5
RESTRICTIONS AND IDENTIFIED
DEFAULTS
INFRASTRUCTURE
Installation
The identifiers of Experts groups must not have accents.
Using a Web administration client on XP SP2 with firewall activated
The default automatic firewall configuration is only performed on standard 4760 client.
If you are using the Web applet, you need configure manually the XP firewall and add
the Corba port 30500 to 30509 on the XP client.
Path of installation for Sybase binaries
Do not install Sybase directly on the drive root (D:). In that case, if 4760 is uninstalled,
all data on D: will be removed.
Recommendation
Use C:\Program Files or C:\Program Files (x86) default folder to install
Sybase.
Refer to technical communication TCV056 Complete erasing of hard disk following
OmniVista 4760 uninstallation
Sybase software must not be installed in the same directory as OmniVista 4760; the
upgrade of server would fail.
Firefox limitation
If Firefox 1.0 is your default browser, you cannot launch the external application that
use Default Browser setting.
In technical (system) directory, in General tab, under NMC>Application>
External Applications, the default setting of the browser has to be replaced by:
Type= Windows application <Name of the binary> = C:\Program
Files\Mozilla Firefox\firefox.exe
SP1 installation on Windows 2003 Server
Some PCs, especially the HP ML370G4, require a Bios and some drivers update
before Windows 2003 Server SP1 patch installation. Otherwise the update procedure
would fail and the only solution would be to reinstall the operating system. It's
mandatory to have a 4760 data backup on a remote device. Refer to the technical
communication TCV066 Installation of Service Pack 1 for Windows 2003 over a
HP/Compaq ML370 server will end in a definitive crash of the PC and all data will be
lost.
Ed. 01 / 06-04-2012
TC1660
OmniVista 4760
INSTALLATION PROCEDURE FOR
VERSION R5.2.2.00.b.c - RELEASE 5.2
2.
APPENDIX 5
RESTRICTIONS AND IDENTIFIED
DEFAULTS
CONFIGURATION
3.
The first key typed just open the edit mode. The first character is not written in the field.
DIRECTORY
XTSce85390
Web directory: add edition ergonomics for Confidentiality field.
crms00192881 This is a system restriction
In the System Directory, the upper value for the Network number is 2140. Although
there is neither warning nor restriction when managing this field, a greater value will
lead to an error during Accounting Counter Calculation:
"Accounting: 233: 23502: com.sybase.jdbc2.jdbc.SybSQLException: Erreur SQL
Anywhere -195: the column 'PbxId' of the table 'EntityInfo' can not contain the value
NULL"
Ed. 01 / 06-04-2012
TC1660
OmniVista 4760
INSTALLATION PROCEDURE FOR
VERSION R5.2.2.00.b.c - RELEASE 5.2
4.
APPENDIX 5
RESTRICTIONS AND IDENTIFIED
DEFAULTS
INSTALLATION
crms00101845 4760 R4.2/Server uninstall: Displayed remaining time is totally erroneous / 183372904.
5.
MAINTENANCE
PCX versions before E2.504 (UNIX versions) do not accept the backup commands sent by OmniVista
4760.
For these versions, OmniVista 4760 can only recover the mao-dat and cho-dat files daily created by
the PCX in the /usr4/BACKUP/DAY directory.
The files created by the PCX immediate backup command can no more be recovered by OmniVista
4760 Maintenance application.
A possible backup can be carried out by a "manual" FTP transfer.
Software Download
Starting from OmniPCX Enterprise R9.1, intermediate log files for a software update are managed
differently:
Before R9.1:
A unique SofwareUpdatestus_X file in the /var/ftp/pcx/logs folder.
(X=context Id)
6.
REPORT
crms00285308 The export in pdf format using Arabic language is not supported.
Ed. 01 / 06-04-2012
TC1660
OmniVista 4760
INSTALLATION PROCEDURE FOR
VERSION R5.2.2.00.b.c - RELEASE 5.2
7.
APPENDIX 5
RESTRICTIONS AND IDENTIFIED
DEFAULTS
SIP DM
SIP Device Management Server must have the version 1.2.000.010 or higher to be compatible with
OmniVista 4760 R5.2. The current version is 1.2.000.020.
SIP DM is not compatible with Windows 2008 and Windows 7.
8.
OTHER
For Name/Surname displayed in Arabic on the 8000 & 9000 series phone
sets
As of OXE 9.1 latest version, the language can be chosen for each phone set,
from the phone set MMI or from OmniVista 4760 Configuration
The Arabic names are managed in OmniVista 4760 Configuration. Arabic
characters appear from right to left, aligned on the left.
Once a name is set up in Arabic, it is displayed in Arabic on all the OXE phone
sets
Names/surnames in Arabic (UTF8) are not synchronized in the OmniVista 4760
web Directory.
Only the English (non UTF8) names/surnames are synchronized. It means
that, for the web Directory or the Call by name overflow, names should
be created in Arabic and in English as well for the Directory.
Modification of English names is synchronized between OXE and the
Directory, but modifications in Arabic names should be made on both
sides.
Ed. 01 / 06-04-2012
TC1660
OmniVista 4760
INSTALLATION PROCEDURE FOR
VERSION R5.2.2.00.b.c - RELEASE 5.2
APPENDIX 5
RESTRICTIONS AND IDENTIFIED
DEFAULTS
Legal notice:
Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent.
All other trademarks are the property of their respective owners.
The information presented is subject to change without notice.
Alcatel-Lucent assumes no responsibility for inaccuracies contained herein.
Copyright 2012 Alcatel-Lucent. All rights reserved.
Ed. 01 / 06-04-2012
TC1660