Avaya PeriView Reference Manual (Software Release 2.1) - Business Communications Manager Manual de usuario descargar pdf (Pagina 37)

Working with PeriView

# P0602566 Ver: 2.7 Page 23

Browser-based PeriView and the Java Cache

When PeriView is accessed by a web browser, the Java files (.class and .jar) are

typically copied to a local Java file cache. Putting these files in a local cache speeds

loading the next time the web page (PeriView) is accessed.

This caching may prevent PeriView updates/changes from appearing the next time

you start PeriView from the browser. For example, you apply a PeriView patch which

adds a new menu option. The next time you use PeriView in the browser, you may not

see the new menu option. The browser is using the cached (older) version. Similar

behavior may occur if you access one version of PeriView on a system, then use the

browser to access a different version of PeriView on a different system.

The Java files are cached by a Java plug-in. The cache much be cleared using the Java

plugin Control Panel. The cached files cannot be removed by clearing the browser

cache. To clear the Java cache:

On Windows 2000 systems:

1. Start > Settings > Control Panel

2. Select the Java Plug-In

1 2 ... 32 33 34 35 36 37 38 39 40 41 42 ... 287 288

Sin comentarios

Avaya PeriView Reference Manual (Software Release 2.1) - Business Communications Manager Manual de usuario Pagina 37