TECHNICAL COMMUNICATION No. TC0835 Ed.

01

OmniVista 4760 Nb of pages : 12 Date : 16 October 2006

URGENT

NOT URGENT TEMPORARY PERMANENT

SUBJECT : MANAGING THE DISK AND RAM IN RELEASE 4.1

Please find hereafter the documentation regarding the management of disk and RAM in Release 4.1.

1
 OmniVista 4760
MANAGING THE DISK AND RAM IN
RELEASE 4.1

CONTENTS

1. DESCRIPTION ..............................................................................3

2. DISK SIZE ....................................................................................3

3. REPORTS......................................................................................4
3.1. Optimizing the parameters ....................................................................... 4
3.2. Trace of exports ........................................................................................ 5

4. MANAGING THE RAM .................................................................5

4.1. Introduction .............................................................................................. 5
4.2. System memory ........................................................................................ 5
4.2.1. Physical memory...............................................................................................5
4.2.2. Virtual memory.................................................................................................6
4.3. Java memory ............................................................................................ 6
4.3.1. Client installed only ..........................................................................................6
4.3.2. Client launched from a java applet...................................................................7
4.3.3. Client installed on the server ............................................................................7
4.3.4. Scheduled jobs (NMC process)..........................................................................7
4.4. Sybase server cache.................................................................................. 7
4.4.1. Process of changing RAM capacity ....................................................................7
4.4.2. Sybase Central administration Console ............................................................8
4.4.3. Upgrading the Sybase cache ............................................................................8
4.4.4. Typical configuration of Sybase cache ..............................................................9
4.5. Process of changing RAM capacity ............................................................ 9

Ed. 01 / 16 October 2006 1 TC0835

 OmniVista 4760
MANAGING THE DISK AND RAM IN
RELEASE 4.1

TC0835 2 Ed. 01 / 16 October 2006

 OmniVista 4760
MANAGING THE DISK AND RAM IN
RELEASE 4.1

1. DESCRIPTION
One needs to update the disk and RAM capacity of OmniVista 4760 server:
− to take into account an increase of subscribers capacity,
− to add new application on the server,
− or to improve the performance of the application.
If the disk or the RAM are saturated, the server is going to:
− send a 4760 alarm,
− block some applications,
− close the 4760 services.

2. DISK SIZE
We recommend you to setup your server by respecting the values of size /disk occupation.

Minimal values
Disk space available for installing OmniVista 4760 35 % free
Partition c:\ (Prog Sybase) 8 GB
Partition d:\ (4760 + Bases) 16 GB
Disk 40 GB

By default, the server ensures a correct functioning of applications with the following sizes:

First Threshold Second Threshold

Applications Directory
(directory size) (directory size)
OXE_software download 4760_ARC/dhs3mgr 1,5 GB 2 GB
Saverestore 4760_ARC/4760Backup 1,5 GB 2 GB
A4400backup 4760_ARC/4400Backup 350 MB 500 MB
Temp directory 4760_ARC/temp 500 MB 550 MB
OXO_software 4760_ARC/oxo/sw 1 GB 1,5 GB
OXO_Backup 4760_ARC/oxo/data 350 MB 500 MB

Alert threshold Blocking threshold

Ed. 01 / 16 October 2006 3 TC0835

 OmniVista 4760
MANAGING THE DISK AND RAM IN
RELEASE 4.1

3. REPORTS

3.1. Optimizing the parameters

Problem
Some reports have missing information and end with the message Report truncated to the
requested size
Solution
To display and modify the limits of report exports
− Open the System directory.
− Expand the branch:
nmc > NmcConfiguration > GlobalPreferences >ReportingTool
− If the export of a report fails in scheduled mode, tick the Check memory for large
exported reports option.

For large exports, this parameter:

• limits the memory used by the extractor to the memory values defined in LDAP,
• limits the number of simultaneous jobs,
• avoids the blockings on memory overflow.
HTML exports do not exceed 150 pages and Excel exports 1000 pages.
Recommendations
Do not generate on the whole database. The processing of a large file will need CPU time and
memory. These limits are not only due to OmniVista 4760 but also to the performances of your PC
and to the network environment.

TC0835 4 Ed. 01 / 16 October 2006

 OmniVista 4760
MANAGING THE DISK AND RAM IN
RELEASE 4.1

Notes
• Export a large pdf file will use a large memory space (> 256 MB) and time.
• Display a 3 MB html file is almost impossible on Internet Explorer.
• Your mail server can reject a report > 10 MB.
• Try to print a report can generate the printing of thousand useless pages.

3.2. Trace of exports

For checking the report exports, you can set the viewer in trace mode:
− Edit the 4760\Client\bin\NMCViewer.properties file:
− Modify the first line
Log4j.rootLogger=info, R
by
Log4j.rootLogger=debug,R
− Check the result of the trace in the 4760/log/NMC_Viewer.log file.

4. MANAGING THE RAM

4.1. Introduction
This RAM update does not consist on a replacement of the RAM chipset.
The RAM available for the OmniVista 4760 application depends on:
− Operating System side:
• Physical memory.
• Cache memory: with the Pagefile.sys file.
− Java application side:
• Cache memory reserved for the client application.
• Cache memory reserved for the scheduled jobs.
− 4760 database side:
• Cache memory allocated by the SQL Sybase server.
• Cache memory allocated by the LDAP server.

4.2. System memory

4.2.1. Physical memory

One must ensure that appropriate physical memory is available based upon the number of users.
Please see the chart for the physical memory requirements.

Nb of users < 250 250 to 5000 5000 to 50 000

RAM 512 MB 1 GB 2 GB

Ed. 01 / 16 October 2006 5 TC0835

 OmniVista 4760
MANAGING THE DISK AND RAM IN
RELEASE 4.1

4.2.2. Virtual memory

If the pre-requisite has been respected, the cache memory must be 1.5 times the physical RAM size.

Do not saturate the system partition.

If need be, set part of the virtual memory on an other partition.
As the OmniPCX Enterprise partitions have a large size, create dhs3mgr on a
separate partition of OmniVista 4760 one.

If the size of the RAM exceeds the pre-requisite, it is useless to allocate as much virtual memory.
Example
On a server equipped with a 1 GB RAM, to manage a small number of users (example 256 users), it
is better to minimize the cache to 512 MB to make the best use of the physical RAM.
In addition, Windows manages two Initial and Max parameters: set the same value for these
two parameters.
Under Windows 2000:
1 Right click on My Computer, then select Properties.
2 Select the Advanced tab.
3 Under Performance Option, click on Change.
4 Enter the values of Initial and Max.
5 Confirm the management by clicking on the Set button.
Under Windows 2000:
1 Right click on My Computer, then select Properties.
2 Select the Advanced tab.
3 Under Performances, click on Parameters then on Avanced. Under Virtual
Memory click on Change.

4.3. Java memory

4.3.1. Client installed only

On a remote PC, the 4760 client shortcut corresponds to the RunNmc.bat file located under
Client4760\bin\runNmc.bat.
− Edit this file using Notepad.
− Go to the FamNT_LAUNCH_4760_JAVA_SHELL item.
− The START /B ... line details the launching parameters of the Java application:
• executable : java.exe
• allocated memory -Xmx256m , -DJUSEDMEM=256, i.e. 256 MB.
• ...

TC0835 6 Ed. 01 / 16 October 2006

 OmniVista 4760
MANAGING THE DISK AND RAM IN
RELEASE 4.1

These two -Xmx256m and DJUSEDMEM=256 values can be set to 512 (if the client PC has really
512 MB RAM), to allow the client to launch actions requiring more memory, such as:
• display of a large size configuration grid,
• export / import of configuration or directory data.

4.3.2. Client launched from a java applet

Optimization not available.

4.3.3. Client installed on the server

The RunNmc.bat file is located under the 4760\Client\bin directory.

4.3.4. Scheduled jobs (NMC process)

The server can execute several types of scheduled jobs: service, nmc process, or executable defined
by the administrator.
The following NMC process jobs can be optimized in memory.
• Export/Import of LDIF file.
• Accumulation of accounting.
To perform this optimization:
− Open the system directory.
− Select NMC\Name of server\Servers\Name of server.
− Under the JVM Parameter tab, the JVM Memory Argument field specifies the memory
reserved:

-Xmx256 , -DJUSEDMEM=256

− Extend the options –Xmx256 –DJUSEDMEM=256 to 512.

Specific case of Export/Import of PCX configuration files.
In the NMC \ NmcConfiguration GlobalPreferences \ Configuration \
OXEAccess system directory, change the value of JVM Memory size for scheduled
job from 256 to 512.

4.4. Sybase server cache

The parameters of memory cache of SQL server are defined in the initial installation. In the event
that one has changed the RAM capacity, one should manually upgrade the engine of Sybase
database.

4.4.1. Process of changing RAM capacity

− Change the RAM capacity.
− Upgrade the Windows cache.

Ed. 01 / 16 October 2006 7 TC0835

 OmniVista 4760
MANAGING THE DISK AND RAM IN
RELEASE 4.1

− Close the 4760 and database services:

• launch the 4760 Service-Manager application,
• click on the Select button then click the Write Execute rights,
• select the NMC Service Manager service then click on Stop,
• select the NMC50 Database service then click on Stop.
− Change the cache size using Sybase Central; see next sections.
− Restart the server PC.

4.4.2. Sybase Central administration Console

The administration application of Sybase server is called Sybase Central. It manages the command
line which launches the Sybase server:
• Name of the executable.
• Parameters of caches.
To launch Sybase Central, use the Windows menu
Start\Programs\SQL Anywhere 9\Sybase Central
To check the command line, under Sybase Central:
− Select in the tree, the entry
Sybase central\ Adaptative Server Anywhere 9\Services
− In the details grid, with a right click on the nmc50entry, display the Properties menu.
− Select the tab Configuration.

For a 4760 server R4.1, equipped with 512 MB RAM, the default parameters are:

[Filename] d:\4760\Sybase\SQL Anywhere 7\win32\dbsrv7.exe

[Parameters -ti 0 -m -c 16M -ch 192M -sb 0 –xtcpip[Port=30011) -n
PCSERVER_4760 "d:\4760\data\nmc5.db"

Notes
• The -c option corresponds to the minimum value of cache.
• The–ch option corresponds to the maximum value of cache.
• The database is called <server PC name>_4760.

4.4.3. Upgrading the Sybase cache

After modifying the server RAM, the parameters of Sybase cache (–c and –ch options) can be
changed. The section "Typical Configuration of Sybase cache" provides the values of cache
depending on the available RAM.

For instance, if the server changes from 512 MB RAM to 1024 MB RAM:
− Upgrade the Parameters field
-ti 0 -m -c 16M -ch 192M -sb 0 -x -n PCSERVER_4760 "d:\4760\data\nmc5.db"
with
-ti 0 -m -c 32M -ch 640M -sb 0 -x -n PCSERVER_4760 "d:\4760\data\nmc5.db"

TC0835 8 Ed. 01 / 16 October 2006

 OmniVista 4760
MANAGING THE DISK AND RAM IN
RELEASE 4.1

− Close Sybase Central.

− Restart the server PC.
In case of error when closing Sybase Central :
− Check the Filename field; e.g., if it has quotation marks
« d:\Sybase\SQL Anywhere 9\win32\dbsrv9.exe »
− Remove the quotation marks at the beginning and at the end to obtain
d:\Sybase\SQL Anywhere 9\win32\dbsrv9.exe

4.4.4. Typical configuration of Sybase cache

RAM size OmniVista 4760 R4.1 Installation

512 MB [ConfigType1]
MIN_CACHE = 32 MB
MAX_CACHE = 256 MB

1024 MB [ConfigType2]
MIN_CACHE = 32 MB
MAX_CACHE = 640 MB
2048MB [ConfigType2]
MIN_CACHE = 64 MB
MAX_CACHE = 1024 MB

4.5. Process of changing RAM capacity

− Change the RAM capacity.
− Upgrade the Windows cache.
− Close the 4760 and database services:
• launch the 4760 Service-Manager application,
• click on the Select button then click the Write Execute rights,
• select the NMC Service Manager service then click on Stop,
• select the NMC50 Database service then click on Stop.
− Restart the server PC.

Ed. 01 / 16 October 2006 9 TC0835

 OmniVista 4760
MANAGING THE DISK AND RAM IN
RELEASE 4.1

TC0835 10 Ed. 01 / 16 October 2006